Report Summary

  • 47

    Performance

    Renders faster than
    67% 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

  • 90

    SEO

    Google-friendlier than
    69% of websites

gregallensworth.github.io

GitHub - gregallensworth/gregallensworth.github.io: Pages for demos etc

Page Load Speed

106 ms in total

First Response

22 ms

Resources Loaded

28 ms

Page Rendered

56 ms

gregallensworth.github.io screenshot

About Website

Visit gregallensworth.github.io now to see the best up-to-date Gregallensworth Git Hub content for China and also check out these interesting facts you probably never knew about gregallensworth.github.io

Pages for demos etc. Contribute to gregallensworth/gregallensworth.github.io development by creating an account on GitHub.

Visit gregallensworth.github.io

Key Findings

We analyzed Gregallensworth.github.io page load time and found that the first response time was 22 ms and then it took 84 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

gregallensworth.github.io performance score

47

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

49/100

10%

LCP (Largest Contentful Paint)

Value3.4 s

67/100

25%

SI (Speed Index)

Value4.8 s

66/100

10%

TBT (Total Blocking Time)

Value3,660 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value8.7 s

36/100

10%

Network Requests Diagram

gregallensworth.github.io

22 ms

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

Page Optimization Overview & Recommendations

Page size can be reduced by 336 B (66%)

Content Size

509 B

After Optimization

173 B

In fact, the total size of Gregallensworth.github.io main page is 509 B. This result falls within the top 5000 of lightweight and thus fast loading web pages. Only a small number of websites need less resources to load. HTML takes 509 B which makes up the majority of the site volume.

HTML Optimization

-66%

Potential reduce by 336 B

  • Original 509 B
  • After minification 437 B
  • After compression 173 B

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 72 B, which is 14% 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 336 B or 66% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

0

After Optimization

0

Besides the initial HTML request, no CSS, Javascripts, AJAX or image files were requested in the course of web page rendering.

Accessibility Review

gregallensworth.github.io 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

gregallensworth.github.io 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

gregallensworth.github.io SEO score

90

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Gregallensworth.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 Gregallensworth.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

Open Graph description is not detected on the main page of Gregallensworth Git Hub. 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: