Tools & Wizards About Us
slither.io screenshot

Report Summary

  • 26

    Performance

    Renders faster than
    47% of other websites

  • 48

    Accessibility

    Visual factors better than
    that of 20% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    57% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

slither.io

slither.io

Page Load Speed

3.6 sec in total

First Response

31 ms

Resources Loaded

3.3 sec

Page Rendered

287 ms

slither.io screenshot

About Website

Visit slither.io now to see the best up-to-date Slither content for United States and also check out these interesting facts you probably never knew about slither.io

The smash-hit game! Play with millions of players around the world and try to become the longest of the day!

Visit slither.io

Key Findings

We analyzed Slither.io page load time and found that the first response time was 31 ms and then it took 3.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

slither.io performance score

26

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value0.7 s

100/100

10%

LCP (Largest Contentful Paint)

Value11.9 s

0/100

25%

SI (Speed Index)

Value11.2 s

5/100

10%

TBT (Total Blocking Time)

Value11,080 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value16.1 s

6/100

10%

Network Requests Diagram

slither.io

31 ms

game404ee.js

9 ms

outstream.js

1892 ms

facebook.png

1881 ms

twitter3.png

6 ms

Our browser made a total of 35 requests to load all elements on the main page. We found that 40% of them (14 requests) were addressed to the original Slither.io, 17% (6 requests) were made to Apis.google.com and 9% (3 requests) were made to S.ytimg.com. The less responsive or slowest element that took the longest time to load (1.9 sec) relates to the external source Imasdk.googleapis.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 565.5 kB (50%)

Content Size

1.1 MB

After Optimization

563.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Slither.io main page is 1.1 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. 65% of websites need less resources to load. Javascripts take 684.7 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 83.8 kB

  • Original 106.0 kB
  • After minification 105.8 kB
  • After compression 22.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 83.8 kB or 79% of the original size.

Image Optimization

-0%

Potential reduce by 923 B

  • Original 303.6 kB
  • After minification 302.7 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. Slither images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 451.2 kB

  • Original 684.7 kB
  • After minification 684.7 kB
  • After compression 233.5 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 451.2 kB or 66% of the original size.

CSS Optimization

-84%

Potential reduce by 29.5 kB

  • Original 34.9 kB
  • After minification 34.9 kB
  • After compression 5.4 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. Slither.io needs all CSS files to be minified and compressed as it can save up to 29.5 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 13 (38%)

Requests Now

34

After Optimization

21

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

slither.io

slither.io

31 ms

game404ee.js

game404ee.js

9 ms

outstream.js

outstream.js

1892 ms

facebook.png

facebook.png

1881 ms

twitter3.png

twitter3.png

6 ms

changeskin2.png

changeskin2.png

1879 ms

highquality.png

highquality.png

1878 ms

prev3.png

prev3.png

5 ms

next3.png

next3.png

1878 ms

84 ms

i33628.txt

i33628.txt

60 ms

bg45.jpg

bg45.jpg

75 ms

gbg.jpg

gbg.jpg

74 ms

customskins2.png

customskins2.png

70 ms

lowquality.png

lowquality.png

72 ms

sdk.js

sdk.js

98 ms

platform.js

platform.js

158 ms

widgets.js

widgets.js

157 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

155 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

154 ms

subscribe_embed

subscribe_embed

299 ms

bridge3.130.0_en.html

bridge3.130.0_en.html

129 ms

client.js

client.js

44 ms

302 ms

www-subscribe-embed-vflv-8crR.css

www-subscribe-embed-vflv-8crR.css

315 ms

www-subscribe-embed.js

www-subscribe-embed.js

380 ms

button.07a87b943a27e2a4a74c40e24a4a5ccc.js

button.07a87b943a27e2a4a74c40e24a4a5ccc.js

201 ms

postmessageRelay

postmessageRelay

234 ms

xd_arbiter.php

xd_arbiter.php

177 ms

xd_arbiter.php

xd_arbiter.php

278 ms

www-hitchhiker-vflvB63an.png

www-hitchhiker-vflvB63an.png

94 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

117 ms

1077434459-postmessagerelay.js

1077434459-postmessagerelay.js

205 ms

rpc:shindig_random.js

rpc:shindig_random.js

100 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

112 ms

Accessibility Review

slither.io accessibility score

48

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

slither.io best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

SEO Factors

slither.io SEO score

92

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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 Slither.io 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 Slither.io 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

slither.io

Open Graph data is detected on the main page of Slither. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: