Tools & Wizards About Us
i8mark.com screenshot

Report Summary

  • 45

    Performance

    Renders faster than
    64% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 48% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

i8mark.com

i8mark | Lottery Results and Statistics

Page Load Speed

2.1 sec in total

First Response

444 ms

Resources Loaded

1.4 sec

Page Rendered

302 ms

i8mark.com screenshot

About Website

Visit i8mark.com now to see the best up-to-date I 8 Mark content and also check out these interesting facts you probably never knew about i8mark.com

Lottery Information, Results and Statistics.

Visit i8mark.com

Key Findings

We analyzed I8mark.com page load time and found that the first response time was 444 ms and then it took 1.7 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

i8mark.com performance score

45

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.0 s

85/100

10%

LCP (Largest Contentful Paint)

Value2.0 s

97/100

25%

SI (Speed Index)

Value8.0 s

22/100

10%

TBT (Total Blocking Time)

Value1,130 ms

23/100

30%

CLS (Cumulative Layout Shift)

Value0.505

16/100

15%

TTI (Time to Interactive)

Value14.0 s

10/100

10%

Network Requests Diagram

i8mark.com

444 ms

make_css.php

139 ms

jquery-ui.css

280 ms

jquery-1.9.1.min.js

343 ms

jquery-ui-1.10.2.js

477 ms

Our browser made a total of 37 requests to load all elements on the main page. We found that 27% of them (10 requests) were addressed to the original I8mark.com, 19% (7 requests) were made to Apis.google.com and 11% (4 requests) were made to Googleads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (477 ms) belongs to the original domain I8mark.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 979.0 kB (52%)

Content Size

1.9 MB

After Optimization

907.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of I8mark.com main page is 1.9 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 60% of websites need less resources to load. Javascripts take 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 50.2 kB

  • Original 60.4 kB
  • After minification 59.1 kB
  • After compression 10.2 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 50.2 kB or 83% of the original size.

Image Optimization

-0%

Potential reduce by 806 B

  • Original 505.1 kB
  • After minification 504.3 kB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. I 8 Mark images are well optimized though.

JavaScript Optimization

-70%

Potential reduce by 901.2 kB

  • Original 1.3 MB
  • After minification 1.1 MB
  • After compression 388.0 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 901.2 kB or 70% of the original size.

CSS Optimization

-84%

Potential reduce by 26.7 kB

  • Original 31.9 kB
  • After minification 26.9 kB
  • After compression 5.2 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. I8mark.com needs all CSS files to be minified and compressed as it can save up to 26.7 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 17 (47%)

Requests Now

36

After Optimization

19

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 36 CSS, Javascripts, AJAX and image requests in order to completely render the main page of I 8 Mark. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

i8mark.com

i8mark.com

444 ms

make_css.php

make_css.php

139 ms

jquery-ui.css

jquery-ui.css

280 ms

jquery-1.9.1.min.js

jquery-1.9.1.min.js

343 ms

jquery-ui-1.10.2.js

jquery-ui-1.10.2.js

477 ms

jquery.nicescroll.min.js

jquery.nicescroll.min.js

360 ms

myscript-1.9.js

myscript-1.9.js

286 ms

show_ads.js

show_ads.js

4 ms

ga.js

ga.js

9 ms

background.jpg

background.jpg

383 ms

all.js

all.js

8 ms

logo.jpg

logo.jpg

237 ms

1.png

1.png

237 ms

zrt_lookup.html

zrt_lookup.html

97 ms

show_ads_impl.js

show_ads_impl.js

50 ms

__utm.gif

__utm.gif

67 ms

107 ms

ads

ads

180 ms

osd.js

osd.js

133 ms

0sTQzbapM8j.js

0sTQzbapM8j.js

64 ms

0sTQzbapM8j.js

0sTQzbapM8j.js

141 ms

platform.js

platform.js

152 ms

widgets.js

widgets.js

129 ms

ads

ads

213 ms

ads

ads

110 ms

ping

ping

31 ms

like.php

like.php

97 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

8 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

9 ms

fastbutton

fastbutton

38 ms

postmessageRelay

postmessageRelay

66 ms

rs=AGLTcCOnDxwX8-LbpDmaxOBIoHm7W_kGNA

rs=AGLTcCOnDxwX8-LbpDmaxOBIoHm7W_kGNA

19 ms

Iv-bqISgsE7.js

Iv-bqISgsE7.js

43 ms

lH1ibRl5GKq.png

lH1ibRl5GKq.png

39 ms

971028622-postmessagerelay.js

971028622-postmessagerelay.js

32 ms

rpc:shindig_random.js

rpc:shindig_random.js

36 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

3 ms

Accessibility Review

i8mark.com accessibility score

79

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

i8mark.com best practices score

58

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

i8mark.com SEO score

100

Search Engine Optimization Advices

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise I8mark.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that I8mark.com main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

i8mark.com

Open Graph description is not detected on the main page of I 8 Mark. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: