Tools & Wizards About Us
stoplay.github.io screenshot

Report Summary

  • 73

    Performance

    Renders faster than
    82% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 89

    SEO

    Google-friendlier than
    66% of websites

stoplay.github.io

StoPlay - Chrome extension to stop/play music playing in your web-browser @stoplayext #stoplay

Page Load Speed

399 ms in total

First Response

14 ms

Resources Loaded

228 ms

Page Rendered

157 ms

stoplay.github.io screenshot

About Website

Click here to check amazing Stop Lay Github content for China. Otherwise, check out these important facts you probably never knew about stoplay.github.io

Download a free Google chrome extension to control music in browser with one click. A number of services supported, and new ones added on request.

Visit stoplay.github.io

Key Findings

We analyzed Stoplay.github.io page load time and found that the first response time was 14 ms and then it took 385 ms to load all DOM resources and completely render a web page. This is an excellent result, as only 5% of websites can load faster.

Performance Metrics

stoplay.github.io performance score

73

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.0 s

84/100

10%

LCP (Largest Contentful Paint)

Value3.9 s

51/100

25%

SI (Speed Index)

Value2.0 s

99/100

10%

TBT (Total Blocking Time)

Value370 ms

71/100

30%

CLS (Cumulative Layout Shift)

Value0.085

93/100

15%

TTI (Time to Interactive)

Value5.7 s

68/100

10%

Network Requests Diagram

stoplay.github.io

14 ms

stoplay.github.io

31 ms

bootstrap.min.css

35 ms

font-awesome.min.css

21 ms

style.css

21 ms

Our browser made a total of 16 requests to load all elements on the main page. We found that 56% of them (9 requests) were addressed to the original Stoplay.github.io, 13% (2 requests) were made to Netdna.bootstrapcdn.com and 13% (2 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (65 ms) relates to the external source Google-analytics.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 65.7 kB (9%)

Content Size

771.9 kB

After Optimization

706.2 kB

  • HTML
  • Images
  • JavaScript

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

HTML Optimization

-68%

Potential reduce by 6.2 kB

  • Original 9.1 kB
  • After minification 8.1 kB
  • After compression 2.9 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. This page needs HTML code to be minified as it can gain 1.0 kB, which is 11% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 6.2 kB or 68% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 649.0 kB
  • After minification 649.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. Stop Lay Github images are well optimized though.

JavaScript Optimization

-52%

Potential reduce by 59.5 kB

  • Original 113.8 kB
  • After minification 113.8 kB
  • After compression 54.4 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 59.5 kB or 52% of the original size.

Requests Breakdown

Number of requests can be reduced by 4 (31%)

Requests Now

13

After Optimization

9

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

stoplay.github.io

stoplay.github.io

14 ms

stoplay.github.io

stoplay.github.io

31 ms

bootstrap.min.css

bootstrap.min.css

35 ms

font-awesome.min.css

font-awesome.min.css

21 ms

style.css

style.css

21 ms

ChromeWebStore_Badge_v2_340x96.png

ChromeWebStore_Badge_v2_340x96.png

22 ms

screens1_1280_site_1.jpg

screens1_1280_site_1.jpg

27 ms

screens1_1280_site_2.jpg

screens1_1280_site_2.jpg

29 ms

screens1_1280_site_3.jpg

screens1_1280_site_3.jpg

33 ms

jquery.min.js

jquery.min.js

29 ms

bootstrap.min.js

bootstrap.min.js

57 ms

addthis_widget.js

addthis_widget.js

30 ms

widgets.js

widgets.js

48 ms

analytics.js

analytics.js

65 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

23 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

53 ms

Accessibility Review

stoplay.github.io accessibility score

85

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Links do not have a discernible name

Best Practices

stoplay.github.io best practices score

67

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

stoplay.github.io SEO score

89

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

High

Tap targets are not sized appropriately

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 Stoplay.github.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 Stoplay.github.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

stoplay.github.io

Open Graph description is not detected on the main page of Stop Lay Github. 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: