Report Summary

  • 29

    Performance

    Renders faster than
    50% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 70% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    82% of websites

  • 91

    SEO

    Google-friendlier than
    71% of websites

stopwords.org

GitHub - moewe-io/stopwords: Stopwords for 43 languages in JSON format

Page Load Speed

2.5 sec in total

First Response

334 ms

Resources Loaded

1.7 sec

Page Rendered

548 ms

stopwords.org screenshot

About Website

Click here to check amazing Stopwords content. Otherwise, check out these important facts you probably never knew about stopwords.org

Stopwords for 43 languages in JSON format. Contribute to moewe-io/stopwords development by creating an account on GitHub.

Visit stopwords.org

Key Findings

We analyzed Stopwords.org page load time and found that the first response time was 334 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

stopwords.org performance score

29

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

17/100

10%

LCP (Largest Contentful Paint)

Value4.4 s

40/100

25%

SI (Speed Index)

Value9.5 s

11/100

10%

TBT (Total Blocking Time)

Value6,540 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value12.5 s

14/100

10%

Network Requests Diagram

stopwords.org

334 ms

stopwords

963 ms

light-5178aee0ee76.css

173 ms

dark-217d4f9c8e70.css

175 ms

primer-e1b46f4d01ea.css

230 ms

Our browser made a total of 48 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Stopwords.org, 96% (46 requests) were made to Github.githubassets.com and 2% (1 request) were made to Github.com. The less responsive or slowest element that took the longest time to load (963 ms) relates to the external source Github.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 166.2 kB (53%)

Content Size

313.5 kB

After Optimization

147.3 kB

In fact, the total size of Stopwords.org main page is 313.5 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. HTML takes 192.9 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 161.2 kB

  • Original 192.9 kB
  • After minification 183.2 kB
  • After compression 31.7 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 161.2 kB or 84% of the original size.

CSS Optimization

-4%

Potential reduce by 5.0 kB

  • Original 120.6 kB
  • After minification 116.2 kB
  • After compression 115.5 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. Stopwords.org has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 44 (96%)

Requests Now

46

After Optimization

2

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

Accessibility Review

stopwords.org accessibility score

88

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

High

[aria-hidden="true"] elements contain focusable descendents

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

stopwords.org best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

stopwords.org SEO score

91

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

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

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Stopwords.org 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 Stopwords.org 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 Stopwords. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: