Tools & Wizards About Us

Report Summary

  • 29

    Performance

    Renders faster than
    49% of other websites

  • 48

    Accessibility

    Visual factors better than
    that of 20% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

slither.io

slither.io

Page Load Speed

279 ms in total

First Response

81 ms

Resources Loaded

130 ms

Page Rendered

68 ms

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 81 ms and then it took 198 ms to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.

Performance Metrics

slither.io performance score

29

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value0.8 s

100/100

10%

LCP (Largest Contentful Paint)

Value9.1 s

1/100

25%

SI (Speed Index)

Value8.2 s

20/100

10%

TBT (Total Blocking Time)

Value7,690 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value12.2 s

15/100

10%

Network Requests Diagram

slither.io

81 ms

game0810242316.js

39 ms

changeskin2.png

13 ms

chooseserver.png

29 ms

entercode4.png

29 ms

Our browser made a total of 10 requests to load all elements on the main page. We found that all of those requests were addressed to Slither.io and no external sources were called. The less responsive or slowest element that took the longest time to load (81 ms) belongs to the original domain Slither.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 11.5 kB (4%)

Content Size

302.1 kB

After Optimization

290.6 kB

  • HTML
  • Images
  • JavaScript

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

HTML Optimization

-75%

Potential reduce by 9.9 kB

  • Original 13.2 kB
  • After minification 12.9 kB
  • After compression 3.3 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 9.9 kB or 75% of the original size.

Image Optimization

-1%

Potential reduce by 1.2 kB

  • Original 230.4 kB
  • After minification 229.2 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

-1%

Potential reduce by 377 B

  • Original 58.5 kB
  • After minification 58.5 kB
  • After compression 58.1 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. This website has mostly compressed JavaScripts.

Requests Breakdown

We found no issues to fix!

Requests Now

9

After Optimization

9

  • Images
  • JavaScript

The browser has sent 9 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Slither. According to our analytics all requests are already optimized.

Network Requests Diagram

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

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

High

Browser errors were logged to the console

SEO Factors

slither.io SEO score

83

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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

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: