Tools & Wizards About Us
github.io screenshot

Report Summary

  • 87

    Performance

    Renders faster than
    89% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 71

    SEO

    Google-friendlier than
    30% of websites

github.io

GitHub Pages documentation - GitHub Docs

Page Load Speed

464 ms in total

First Response

24 ms

Resources Loaded

164 ms

Page Rendered

276 ms

github.io screenshot

About Website

Welcome to github.io homepage info - get ready to check Git Hub best content for China right away, or after learning these important things about github.io

Learn how to create a website directly from a repository on GitHub. Explore website building tools like Jekyll and troubleshoot issues with your GitHub Pages site.

Visit github.io

Key Findings

We analyzed Github.io page load time and found that the first response time was 24 ms and then it took 440 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

github.io performance score

87

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.5 s

95/100

10%

LCP (Largest Contentful Paint)

Value3.4 s

67/100

25%

SI (Speed Index)

Value1.5 s

100/100

10%

TBT (Total Blocking Time)

Value10 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.169

70/100

15%

TTI (Time to Interactive)

Value2.6 s

98/100

10%

Network Requests Diagram

pages.github.com

24 ms

pages.css

9 ms

logo.svg

14 ms

bootstrap.png

17 ms

jquery.js

24 ms

Our browser made a total of 21 requests to load all elements on the main page. We found that all of those requests were addressed to Github.io and no external sources were called. The less responsive or slowest element that took the longest time to load (115 ms) relates to the external source Pages.github.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 719.9 kB (28%)

Content Size

2.6 MB

After Optimization

1.9 MB

  • HTML
  • Images

In fact, the total size of Github.io main page is 2.6 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. 70% of websites need less resources to load. Images take 2.6 MB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 11.1 kB

  • Original 14.7 kB
  • After minification 13.3 kB
  • After compression 3.6 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 11.1 kB or 76% of the original size.

Image Optimization

-28%

Potential reduce by 708.7 kB

  • Original 2.6 MB
  • After minification 1.8 MB

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, Git Hub needs image optimization as it can save up to 708.7 kB or 28% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

Requests Breakdown

We found no issues to fix!

Requests Now

19

After Optimization

19

  • Images
  • JavaScript
  • CSS

The browser has sent 19 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Git Hub. According to our analytics all requests are already optimized.

Network Requests Diagram

pages.github.com

pages.github.com

24 ms

pages.css

pages.css

9 ms

logo.svg

logo.svg

14 ms

bootstrap.png

bootstrap.png

17 ms

jquery.js

jquery.js

24 ms

application.js

application.js

43 ms

dashboard@2x.png

dashboard@2x.png

40 ms

desktop-demo@2x.gif

desktop-demo@2x.gif

18 ms

repo-settings@2x.png

repo-settings@2x.png

17 ms

launch-theme-chooser@2x.png

launch-theme-chooser@2x.png

20 ms

theme-chooser@2x.png

theme-chooser@2x.png

115 ms

code-editor@2x.png

code-editor@2x.png

109 ms

commit-edits@2x.png

commit-edits@2x.png

40 ms

new-create-file@2x.png

new-create-file@2x.png

105 ms

new-index-html@2x.png

new-index-html@2x.png

112 ms

new-commit-file@2x.png

new-commit-file@2x.png

107 ms

source-setting@2x.png

source-setting@2x.png

109 ms

user-repo@2x.png

user-repo@2x.png

102 ms

setup-in-desktop@2x.png

setup-in-desktop@2x.png

105 ms

yeoman.png

yeoman.png

13 ms

octicons.woff

octicons.woff

10 ms

Accessibility Review

github.io accessibility score

84

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

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

github.io best practices score

75

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

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

github.io SEO score

71

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

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 Github.io 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 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

github.io

Open Graph data is detected on the main page of Git Hub. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: