Tools & Wizards About Us
i8mark.com screenshot

Report Summary

  • 45

    Performance

    Renders faster than
    64% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

i8mark.com

i8mark | Lottery Results and Statistics

Page Load Speed

1.6 sec in total

First Response

178 ms

Resources Loaded

1.1 sec

Page Rendered

284 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 178 ms and then it took 1.4 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)

Value1.9 s

86/100

10%

LCP (Largest Contentful Paint)

Value1.9 s

97/100

25%

SI (Speed Index)

Value8.1 s

21/100

10%

TBT (Total Blocking Time)

Value1,050 ms

25/100

30%

CLS (Cumulative Layout Shift)

Value0.502

16/100

15%

TTI (Time to Interactive)

Value16.1 s

6/100

10%

Network Requests Diagram

i8mark.com

178 ms

css

88 ms

sp-responsive.css

63 ms

sp-menufication.css

123 ms

sp-styles.css

134 ms

Our browser made a total of 41 requests to load all elements on the main page. We found that 39% of them (16 requests) were addressed to the original I8mark.com, 15% (6 requests) were made to Apis.google.com and 12% (5 requests) were made to Zhuyinlibrary.org. The less responsive or slowest element that took the longest time to load (440 ms) relates to the external source Developers.google.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 68.8 kB (7%)

Content Size

956.6 kB

After Optimization

887.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-75%

Potential reduce by 21.3 kB

  • Original 28.5 kB
  • After minification 27.6 kB
  • After compression 7.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 21.3 kB or 75% of the original size.

Image Optimization

-1%

Potential reduce by 3.8 kB

  • Original 533.8 kB
  • After minification 530.0 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

-11%

Potential reduce by 39.8 kB

  • Original 370.4 kB
  • After minification 370.3 kB
  • After compression 330.6 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 39.8 kB or 11% of the original size.

CSS Optimization

-17%

Potential reduce by 4.0 kB

  • Original 23.9 kB
  • After minification 23.9 kB
  • After compression 19.9 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 4.0 kB or 17% of the original size.

Requests Breakdown

Number of requests can be reduced by 26 (68%)

Requests Now

38

After Optimization

12

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 38 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 20 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

i8mark.com

i8mark.com

178 ms

css

css

88 ms

sp-responsive.css

sp-responsive.css

63 ms

sp-menufication.css

sp-menufication.css

123 ms

sp-styles.css

sp-styles.css

134 ms

jquery-1.9.1.min.js

jquery-1.9.1.min.js

169 ms

jquery.menufication.min.js

jquery.menufication.min.js

133 ms

sp-menufication-setup.js

sp-menufication-setup.js

117 ms

js

js

132 ms

adsbygoogle.js

adsbygoogle.js

99 ms

jquery-ui.css

jquery-ui.css

131 ms

font-awesome.min.css

font-awesome.min.css

131 ms

page_header.css

page_header.css

239 ms

page_footer.css

page_footer.css

240 ms

sp-script-1.9.js

sp-script-1.9.js

130 ms

jquery-ui-1.10.2.js

jquery-ui-1.10.2.js

264 ms

jquery.cookie.js

jquery.cookie.js

130 ms

comment_like.js

comment_like.js

139 ms

page_header.js

page_header.js

216 ms

platform.js

platform.js

120 ms

widgets.js

widgets.js

160 ms

background.jpg

background.jpg

330 ms

logo.jpg

logo.jpg

137 ms

lot_dbs_img_1.png

lot_dbs_img_1.png

138 ms

lot_dbs_img_8.png

lot_dbs_img_8.png

138 ms

menufication-multiple-toggle.png

menufication-multiple-toggle.png

138 ms

all.js

all.js

132 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

47 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

104 ms

fastbutton

fastbutton

69 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

73 ms

all.js

all.js

61 ms

settings

settings

108 ms

postmessageRelay

postmessageRelay

38 ms

developers.google.com

developers.google.com

440 ms

1380534674-postmessagerelay.js

1380534674-postmessagerelay.js

22 ms

rpc:shindig_random.js

rpc:shindig_random.js

10 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

5 ms

button.856debeac157d9669cf51e73a08fbc93.js

button.856debeac157d9669cf51e73a08fbc93.js

14 ms

embeds

embeds

32 ms

tweet_button.2f70fb173b9000da126c79afe2098f02.en.html

tweet_button.2f70fb173b9000da126c79afe2098f02.en.html

17 ms

Accessibility Review

i8mark.com accessibility score

89

Accessibility Issues

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

High

Page has valid source maps

SEO Factors

i8mark.com SEO score

92

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

    EN

  • 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 it matches the claimed language. 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: