Report Summary

  • 95

    Performance

    Renders faster than
    93% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

websocketstest.com

Real-Time Web Test - Does your browser supports WebSockets?

Page Load Speed

1.1 sec in total

First Response

276 ms

Resources Loaded

648 ms

Page Rendered

175 ms

websocketstest.com screenshot

About Website

Click here to check amazing Web Sockets Test content for United States. Otherwise, check out these important facts you probably never knew about websocketstest.com

Visit websocketstest.com

Key Findings

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

Performance Metrics

websocketstest.com performance score

95

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.9 s

88/100

10%

LCP (Largest Contentful Paint)

Value2.4 s

92/100

25%

SI (Speed Index)

Value1.9 s

100/100

10%

TBT (Total Blocking Time)

Value20 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.095

91/100

15%

TTI (Time to Interactive)

Value2.1 s

99/100

10%

Network Requests Diagram

websocketstest.com

276 ms

prototype.js

84 ms

scriptaculous.js

105 ms

Orbited.js

204 ms

gclient.js

190 ms

Our browser made a total of 15 requests to load all elements on the main page. We found that 33% of them (5 requests) were addressed to the original Websocketstest.com, 53% (8 requests) were made to Ajax.googleapis.com and 13% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (276 ms) belongs to the original domain Websocketstest.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 116.8 kB (75%)

Content Size

155.7 kB

After Optimization

38.9 kB

In fact, the total size of Websocketstest.com main page is 155.7 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. 20% of websites need less resources to load. Javascripts take 122.4 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 22.1 kB

  • Original 29.3 kB
  • After minification 28.4 kB
  • After compression 7.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 22.1 kB or 75% of the original size.

Image Optimization

-11%

Potential reduce by 442 B

  • Original 4.0 kB
  • After minification 3.5 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. Obviously, Web Sockets Test needs image optimization as it can save up to 442 B or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-77%

Potential reduce by 94.3 kB

  • Original 122.4 kB
  • After minification 65.4 kB
  • After compression 28.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 94.3 kB or 77% of the original size.

Requests Breakdown

Number of requests can be reduced by 10 (71%)

Requests Now

14

After Optimization

4

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

Accessibility Review

websocketstest.com accessibility score

74

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.

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

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

Form elements do not have associated labels

Best Practices

websocketstest.com 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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

websocketstest.com SEO score

69

Search Engine Optimization Advices

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 Websocketstest.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 Websocketstest.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

Open Graph description is not detected on the main page of Web Sockets Test. 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: