Report Summary

  • 36

    Performance

    Renders faster than
    55% of other websites

  • 92

    Accessibility

    Visual factors better than
    that of 79% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

whynotwin11.org

GitHub - rcmaehl/WhyNotWin11: Detection Script to help identify why your PC is not Windows 11 Release Ready. Now Supporting Update Checks!

Page Load Speed

1.6 sec in total

First Response

501 ms

Resources Loaded

824 ms

Page Rendered

311 ms

whynotwin11.org screenshot

About Website

Welcome to whynotwin11.org homepage info - get ready to check Whynot Win11 best content right away, or after learning these important things about whynotwin11.org

Detection Script to help identify why your PC is not Windows 11 Release Ready. Now Supporting Update Checks! - GitHub - rcmaehl/WhyNotWin11: Detection Script to help identify why your PC is not Window...

Visit whynotwin11.org

Key Findings

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

Performance Metrics

whynotwin11.org performance score

36

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

38/100

10%

LCP (Largest Contentful Paint)

Value4.6 s

34/100

25%

SI (Speed Index)

Value5.3 s

58/100

10%

TBT (Total Blocking Time)

Value2,790 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value11.1 s

20/100

10%

Network Requests Diagram

501 ms

light-0eace2597ca3.css

76 ms

dark-a167e256da9c.css

87 ms

primer-primitives-2ef2a46b27ee.css

98 ms

primer-711f412bb361.css

106 ms

Our browser made a total of 95 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Whynotwin11.org, 14% (13 requests) were made to Avatars.githubusercontent.com and 7% (7 requests) were made to Camo.githubusercontent.com. The less responsive or slowest element that took the longest time to load (501 ms) relates to the external source Github.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 566.9 kB (38%)

Content Size

1.5 MB

After Optimization

936.9 kB

In fact, the total size of Whynotwin11.org main page is 1.5 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 692.3 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 262.6 kB

  • Original 314.7 kB
  • After minification 306.0 kB
  • After compression 52.1 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 262.6 kB or 83% of the original size.

Image Optimization

-31%

Potential reduce by 30.1 kB

  • Original 96.8 kB
  • After minification 66.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. Obviously, Whynot Win11 needs image optimization as it can save up to 30.1 kB or 31% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 760 B

  • Original 692.3 kB
  • After minification 692.3 kB
  • After compression 691.6 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.

CSS Optimization

-68%

Potential reduce by 273.4 kB

  • Original 399.9 kB
  • After minification 392.6 kB
  • After compression 126.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. Whynotwin11.org needs all CSS files to be minified and compressed as it can save up to 273.4 kB or 68% of the original size.

Requests Breakdown

Number of requests can be reduced by 70 (74%)

Requests Now

94

After Optimization

24

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

Accessibility Review

whynotwin11.org accessibility score

92

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

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

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

Missing source maps for large first-party JavaScript

SEO Factors

whynotwin11.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 Whynotwin11.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 Whynotwin11.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 Whynot Win11. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: