github.io

github.io is SSL secured

Free website and domain report on github.io

Last Updated: 24th April, 2024
Overview

Snoop Summary for github.io

This is a free and comprehensive report about github.io. Github.io is hosted in Netherlands on a server with an IP address of 185.199.111.153, where the local currency is EUR and Dutch is the local language. Our records indicate that github.io is privately registered by GitHub, Inc.. If github.io was to be sold it would possibly be worth $518 USD (based on the daily revenue potential of the website over a 24 month period). Github.io is somewhat popular with an estimated 244 daily unique visitors. This report was last updated 24th April, 2024.

About github.io

Site Preview: github.io github.io
Title: GitHub Pages | Websites for you and your projects, hosted directly from your GitHub repository. Just edit, push, and your changes are live.
Description: Websites for you and your projects, hosted directly from your GitHub repository. Just edit, push, and your changes are live.
Keywords and Tags: internet services
Related Terms: bitbucket vs github, edit bookmarks, edit photos, edit pictures, github facebook php sdk, github login, idaho repository, jcenter repository, push pull, push up bra
Fav Icon:
Age: Over 10 years old
Domain Created: 3rd August, 2013
Domain Updated: 2nd September, 2023
Domain Expires: 3rd August, 2025
Review

Snoop Score

2/5

Valuation

$518 USD
Note: All valuation figures are estimates.

Popularity

Low
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 5,647,854
Alexa Reach:
SEMrush Rank (US):
SEMrush Authority Score:
Moz Domain Authority: 0
Moz Page Authority: 0

Organic vs Paid (Google Ads)

Traffic

Visitors

Daily Visitors: 244
Monthly Visitors: 7,434
Yearly Visitors: 89,149
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $1 USD
Monthly Revenue: $21 USD
Yearly Revenue: $254 USD
Note: All revenue figures are estimates.

Revenue By Country

SEO

Backlinks Analysis (SEMrush)

Top New Follow Links

Top Ranking Keywords (US)

Domain Analysis

Value Length
Domain: github.io 9
Domain Name: github 6
Extension (TLD): io 2
Expiry Check:

Page Speed Analysis

Average Load Time: 1.14 seconds
Load Time Comparison: Faster than 73% of sites

PageSpeed Insights

Avg. (All Categories) 70
Performance 92
Accessibility 79
Best Practices 80
SEO 83
Progressive Web App 18
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://pages.github.com/
Updated: 27th July, 2021

0.88 seconds
First Contentful Paint (FCP)
92%
5%
3%

0.00 seconds
First Input Delay (FID)
99%
1%
0%

Simulate loading on desktop
92

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for github.io. This includes details about optimizing page load times which can result in a better user experience.

Metrics

First Contentful Paint — 0.7 s
The time taken for the first image or text on the page to be rendered.
Speed Index — 0.9 s
The time taken for the page contents to be visibly populated.
Largest Contentful Paint — 0.9 s
The timing of the largest text or image that is painted.
Time to Interactive — 2.1 s
The time taken for the page to become fully interactive.
Total Blocking Time — 60 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).

Other

First Meaningful Paint — 0.7 s
The time taken for the primary content of the page to be rendered.
Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://github.io/
http/1.1
0
40.730999957304
432
0
301
https://pages.github.com/
h2
41.403000010177
125.06499997107
4567
14445
200
text/html
Document
https://pages.github.com/css/pages.css
h2
139.4319999963
204.66200000374
4066
12226
200
text/css
Stylesheet
https://pages.github.com/images/logo.svg
h2
139.58299998194
202.25299999584
3093
5577
200
image/svg+xml
Image
https://pages.github.com/images/slideshow/bootstrap.png
h2
141.79099997273
234.3899999978
157536
156915
200
image/png
Image
https://pages.github.com/images/dashboard@2x.png
h2
142.15099997818
254.80599998264
436003
435382
200
image/png
Image
https://pages.github.com/images/desktop-demo@2x.gif
h2
142.2779999557
221.53300000355
148272
147672
200
image/gif
Image
https://pages.github.com/images/repo-settings@2x.png
h2
142.49900000868
205.46099997591
93725
93103
200
image/png
Image
https://pages.github.com/images/launch-theme-chooser@2x.png
h2
142.65900000464
239.82700001216
97397
96778
200
image/png
Image
https://pages.github.com/images/theme-chooser@2x.png
h2
143.23499996681
213.71999999974
413027
412408
200
image/png
Image
https://pages.github.com/images/code-editor@2x.png
h2
144.63200001046
230.34700000426
238197
237574
200
image/png
Image
https://pages.github.com/images/commit-edits@2x.png
h2
144.80499998899
238.33699995885
157294
156674
200
image/png
Image
https://pages.github.com/images/new-create-file@2x.png
h2
144.92699998664
234.94200001005
118286
117665
200
image/png
Image
https://pages.github.com/images/new-index-html@2x.png
h2
146.50699996855
219.74599995883
75834
75214
200
image/png
Image
https://pages.github.com/images/new-commit-file@2x.png
h2
146.71999996062
237.8589999862
115720
115100
200
image/png
Image
https://pages.github.com/images/source-setting@2x.png
h2
146.86400000937
241.75899999682
131570
130949
200
image/png
Image
https://pages.github.com/js/jquery.js
h2
141.4329999825
168.49799995543
33735
93107
200
application/javascript
Script
https://pages.github.com/js/application.js
h2
141.67699997779
167.75299998699
2830
8554
200
application/javascript
Script
https://www.youtube-nocookie.com/embed/2MsN8gpT6jY?showinfo=0
h2
147.49899995513
209.91599996341
21884
51886
200
text/html
Document
https://pages.github.com/images/user-repo@2x.png
h2
210.4260000051
240.3269999777
160101
159480
200
image/png
Image
https://pages.github.com/images/setup-in-desktop@2x.png
h2
212.8570000059
252.6829999988
171156
170534
200
image/png
Image
https://pages.github.com/css/octicons.woff
h2
214.81699997094
233.47499995725
4090
3492
200
font/woff
Font
https://pages.github.com/images/slideshow/yeoman.png
h2
287.80399996322
374.33899997268
201315
200695
200
image/png
Image
https://www.youtube-nocookie.com/s/player/02486e7d/www-player-webp.css
h2
350.27999995509
376.02699996205
46407
331717
200
text/css
Stylesheet
https://www.youtube-nocookie.com/s/player/02486e7d/www-embed-player.vflset/www-embed-player.js
h2
351.68099997099
360.40999996476
65603
196514
200
text/javascript
Script
https://www.youtube-nocookie.com/s/player/02486e7d/player_ias.vflset/en_US/base.js
h2
351.7850000062
386.0889999778
501118
1751643
200
text/javascript
Script
https://www.youtube-nocookie.com/s/player/02486e7d/fetch-polyfill.vflset/fetch-polyfill.js
h2
351.97899997002
355.92599998927
3416
8543
200
text/javascript
Script
https://fonts.gstatic.com/s/roboto/v18/KFOmCnqEu92Fr1Mu4mxKKTU1Kg.woff2
h2
352.61699999683
355.33799999394
11506
10748
200
font/woff2
Font
https://www.youtube-nocookie.com/api/stats/qoe?event=streamingstats&cpn=udiXfumgUeIKoGnz&el=embedded&docid=2MsN8gpT6jY&ns=yt&fexp=23748146%2C23940237%2C23983296%2C24001373%2C24002022%2C24002025%2C24004644%2C24007246%2C24027400%2C24036236%2C24045411%2C24053866%2C24058128%2C24058812%2C24060921%2C24068842&cl=386768987&seq=1&cbrand=apple&cbr=Chrome&cbrver=88.0.4324.175&c=WEB_EMBEDDED_PLAYER&cver=1.20210725.0.0&cplayer=UNIPLAYER&cos=Macintosh&cosver=10_14_6&cplatform=DESKTOP&vps=0.000:N,0.000:ER&cmt=0.000:0.000,0.000:0.000&error=0.000:html5.missingapi:0.000:nocodecs.1;a6s.0&vis=0.000:0&bh=0.000:0.000
663.79299998516
754.15900000371
0
0
-1
Ping
https://www.google.com/js/th/15Ie8MSBp4IN3jcelD60kGm05ThBDTbI2ej_yOJ3Q94.js
h2
687.56099999882
691.38099998236
14214
35906
200
text/javascript
Script
https://www.youtube-nocookie.com/s/player/02486e7d/player_ias.vflset/en_US/embed.js
h2
736.79699999047
740.46499998076
8026
25246
200
text/javascript
Script
data
740.6830000109
740.75200001244
0
331
200
image/png
Image
https://www.youtube-nocookie.com/generate_204?oXzsNg
h2
917.96799999429
924.28799998015
251
0
204
text/plain
Image
https://www.youtube-nocookie.com/youtubei/v1/log_event?alt=json&key=AIzaSyAO_FJ2SlqU8Q4STEHLGCilw_Y9_11qcW8
h2
2767.7759999642
2786.3260000013
512
28
200
application/json
XHR
https://pages.github.com/images/slideshow/facebookdesign.png
h2
3280.6930000079
3374.3489999906
200112
199490
200
image/png
Image
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
135.871
7.884
145.678
7.102
215.249
40.255
255.777
42.199
298.456
6.896
317.231
6.933
332.226
23.764
387.918
9.09
401.123
17.135
486.654
111.437
605.496
140.121
745.734
14.19
765.005
6.809
774.483
13.383
791.936
134.597
929.087
8.571
2760.476
14.665
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Opportunities

Eliminate render-blocking resources
Resources, such as JavaScript and style sheets, can block the first paint of the page. Github.io should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
Defer offscreen images — Potential savings of 755 KiB
Time to Interactive can be slowed down by resources on the page. Github.io should consider lazy-loading offscreen and hidden images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://pages.github.com/images/dashboard@2x.png
435382
435382
https://pages.github.com/images/desktop-demo@2x.gif
147672
147672
https://pages.github.com/images/launch-theme-chooser@2x.png
96778
96778
https://pages.github.com/images/repo-settings@2x.png
93103
93103
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Github.io should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Github.io should consider minifying JS files.
Reduce unused CSS — Potential savings of 44 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Github.io should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.youtube-nocookie.com/s/player/02486e7d/www-player-webp.css
46407
44666
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 80 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
https://pages.github.com/
84.659
Avoid multiple page redirects — Potential savings of 190 ms
Redirects can cause additional delays before the page can begin loading. Github.io should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://github.io/
190
https://pages.github.com/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Github.io should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content — Potential savings of 72 KiB
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://pages.github.com/images/desktop-demo@2x.gif
147672
73836
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
URL Potential Savings (Ms)
https://pages.github.com/images/slideshow/bootstrap.png
0

Diagnostics

Avoids an excessive DOM size — 238 elements
A large DOM (Document Object Model) will increase memory usage, cause longer system calculations as well as costly layout reflows.
Statistic Element Value
Total DOM Elements
238
Maximum DOM Depth
~
8
Maximum Child Elements
11
Avoid chaining critical requests — 3 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Github.io should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures — 4 user timings
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
Name Type Start Time (Ms) Duration (Ms)
mark_pe
Mark
567.786
mark_fs
Mark
647.852
mark_qoes
Mark
661.811
mark_ol
Mark
754.157
JavaScript execution time — 0.4 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://www.youtube-nocookie.com/s/player/02486e7d/player_ias.vflset/en_US/base.js
239.485
182.577
41.149
https://www.youtube-nocookie.com/s/player/02486e7d/www-embed-player.vflset/www-embed-player.js
194.904
176.915
5.228
https://pages.github.com/
129.729
2.961
1.041
Unattributable
66.429
2.422
0.156
Minimizes main-thread work — 0.7 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Script Evaluation
416.628
Other
100.424
Style & Layout
74.709
Script Parsing & Compilation
56.832
Rendering
50.942
Parse HTML & CSS
22.759
Garbage Collection
13.48
Keep request counts low and transfer sizes small — 34 requests • 3,556 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
34
3641295
Image
18
2918889
Script
7
628942
Stylesheet
2
50473
Document
2
26451
Font
2
15596
Other
3
944
Media
0
0
Third-party
12
673369
Minimize third-party usage — Third-party code blocked the main thread for 160 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Transfer Size (Bytes) Main-Thread Blocking Time (Ms)
647217
159.605
14214
0
11506
0
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Avoid large layout shifts — 1 element found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.20356816390859
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks — 3 long tasks found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
https://www.youtube-nocookie.com/s/player/02486e7d/player_ias.vflset/en_US/base.js
2207
135
https://www.youtube-nocookie.com/s/player/02486e7d/www-embed-player.vflset/www-embed-player.js
1906
70
https://www.youtube-nocookie.com/s/player/02486e7d/player_ias.vflset/en_US/base.js
1850
56
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.

Budgets

Performance budget
It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.
Timing budget
It is advised to set a timing budget to monitor the performance of your site.

Metrics

Cumulative Layout Shift — 0.204
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

Max Potential First Input Delay — 140 ms
Users could experience a delay when interacting with the page.

Opportunities

Reduce unused JavaScript — Potential savings of 387 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.youtube-nocookie.com/s/player/02486e7d/player_ias.vflset/en_US/base.js
501118
359925
https://www.youtube-nocookie.com/s/player/02486e7d/www-embed-player.vflset/www-embed-player.js
65603
36070

Diagnostics

Avoid enormous network payloads — Total size was 3,556 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www.youtube-nocookie.com/s/player/02486e7d/player_ias.vflset/en_US/base.js
501118
https://pages.github.com/images/dashboard@2x.png
436003
https://pages.github.com/images/theme-chooser@2x.png
413027
https://pages.github.com/images/code-editor@2x.png
238197
https://pages.github.com/images/slideshow/yeoman.png
201315
https://pages.github.com/images/slideshow/facebookdesign.png
200112
https://pages.github.com/images/setup-in-desktop@2x.png
171156
https://pages.github.com/images/user-repo@2x.png
160101
https://pages.github.com/images/slideshow/bootstrap.png
157536
https://pages.github.com/images/commit-edits@2x.png
157294

Opportunities

Properly size images — Potential savings of 1,460 KiB
Images can slow down the page's load time. Github.io should consider serving more appropriate-sized images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://pages.github.com/images/theme-chooser@2x.png
412408
263941
https://pages.github.com/images/dashboard@2x.png
435382
194620
https://pages.github.com/images/code-editor@2x.png
237574
152047
https://pages.github.com/images/slideshow/yeoman.png
200695
150521
https://pages.github.com/images/slideshow/facebookdesign.png
199490
149618
https://pages.github.com/images/slideshow/bootstrap.png
156915
117686
https://pages.github.com/images/commit-edits@2x.png
156674
78337
https://pages.github.com/images/desktop-demo@2x.gif
147672
73836
https://pages.github.com/images/source-setting@2x.png
130949
65475
https://pages.github.com/images/new-create-file@2x.png
117665
58833
https://pages.github.com/images/new-commit-file@2x.png
115100
57550
https://pages.github.com/images/launch-theme-chooser@2x.png
96778
48389
https://pages.github.com/images/repo-settings@2x.png
93103
46552
https://pages.github.com/images/new-index-html@2x.png
75214
37607
Serve images in next-gen formats — Potential savings of 1,867 KiB
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://pages.github.com/images/dashboard@2x.png
435382
368248
https://pages.github.com/images/theme-chooser@2x.png
412408
338550
https://pages.github.com/images/code-editor@2x.png
237574
152162
https://pages.github.com/images/user-repo@2x.png
159480
131640
https://pages.github.com/images/commit-edits@2x.png
156674
107320
https://pages.github.com/images/setup-in-desktop@2x.png
170534
107244
https://pages.github.com/images/slideshow/yeoman.png
200695
98907
https://pages.github.com/images/slideshow/facebookdesign.png
199490
92928
https://pages.github.com/images/source-setting@2x.png
130949
85567
https://pages.github.com/images/new-commit-file@2x.png
115100
84394
https://pages.github.com/images/new-create-file@2x.png
117665
84027
https://pages.github.com/images/slideshow/bootstrap.png
156915
74323
https://pages.github.com/images/repo-settings@2x.png
93103
71175
https://pages.github.com/images/launch-theme-chooser@2x.png
96778
61248
https://pages.github.com/images/new-index-html@2x.png
75214
54212

Diagnostics

Serve static assets with an efficient cache policy — 21 resources found
Github.io can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
https://pages.github.com/images/dashboard@2x.png
600000
436003
https://pages.github.com/images/theme-chooser@2x.png
600000
413027
https://pages.github.com/images/code-editor@2x.png
600000
238197
https://pages.github.com/images/slideshow/yeoman.png
600000
201315
https://pages.github.com/images/slideshow/facebookdesign.png
600000
200112
https://pages.github.com/images/setup-in-desktop@2x.png
600000
171156
https://pages.github.com/images/user-repo@2x.png
600000
160101
https://pages.github.com/images/slideshow/bootstrap.png
600000
157536
https://pages.github.com/images/commit-edits@2x.png
600000
157294
https://pages.github.com/images/desktop-demo@2x.gif
600000
148272
https://pages.github.com/images/source-setting@2x.png
600000
131570
https://pages.github.com/images/new-create-file@2x.png
600000
118286
https://pages.github.com/images/new-commit-file@2x.png
600000
115720
https://pages.github.com/images/launch-theme-chooser@2x.png
600000
97397
https://pages.github.com/images/repo-settings@2x.png
600000
93725
https://pages.github.com/images/new-index-html@2x.png
600000
75834
https://pages.github.com/js/jquery.js
600000
33735
https://pages.github.com/css/octicons.woff
600000
4090
https://pages.github.com/css/pages.css
600000
4066
https://pages.github.com/images/logo.svg
600000
3093
https://pages.github.com/js/application.js
600000
2830
Ensure text remains visible during webfont load
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
URL Potential Savings (Ms)
https://pages.github.com/css/octicons.woff
18.657999986317
https://fonts.gstatic.com/s/roboto/v18/KFOmCnqEu92Fr1Mu4mxKKTU1Kg.woff2
2.7209999971092
Does not use passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Source
Image elements do not have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
URL Failing Elements
https://pages.github.com/images/slideshow/bootstrap.png
https://pages.github.com/images/logo.svg
79

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of github.io. This includes details about various page attributes that can be optimized.

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`button`, `link`, and `menuitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
ARIA `meter` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `progressbar` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
ARIA `tooltip` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `treeitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
`<object>` elements have `[alt]` text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.
Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Internationalization and localization

`<html>` element has a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Github.io may provide assistance to deaf or hearing-impaired users with captions on videos.

Contrast

Background and foreground colors do not have a sufficient contrast ratio.
Many (if not most) users find low-contrast text difficult or impossible to read.
Failing Elements
API

Names and labels

`<frame>` or `<iframe>` elements do not have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
Failing Elements
Links do not have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.

Navigation

Heading elements are not in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
Failing Elements

Manual Checks

The page has a logical tab order
The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.
Interactive controls are keyboard focusable
Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.
Interactive elements indicate their purpose and state
Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.
The user's focus is directed to new content added to the page
When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.
User focus is not accidentally trapped in a region
Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.
Custom controls have associated labels
Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.
Custom controls have ARIA roles
Ensure that all custom interactive controls have appropriate ARIA roles.
Visual order on the page follows DOM order
Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.
Offscreen content is hidden from assistive technology
Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.
HTML5 landmark elements are used to improve navigation
Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.
80

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that github.io should incorporate. This includes practices such as protecting pages with HTTPS.

Audits

Links to cross-origin destinations are safe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).
Description Directive Severity
No CSP found in enforcement mode
High

Audits

Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.
Serves images with appropriate resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

Audits

Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Properly defines charset
It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.
Avoids Application Cache
Application cache is deprecated and is no longer recommended.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
jQuery
1.10.2
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL Request Resolution
http://github.io/
Allowed
Includes front-end JavaScript libraries with known security vulnerabilities — 4 vulnerabilities detected
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Library Version Vulnerability Count Highest Severity
4
Medium

Audits

Displays images with incorrect aspect ratio
Ensure that image display dimensions match their natural aspect ratio.
URL Aspect Ratio (Displayed) Aspect Ratio (Actual)
https://pages.github.com/images/dashboard@2x.png
1054 x 1040 (1.01)
1906 x 1040 (1.83)
https://pages.github.com/images/theme-chooser@2x.png
720 x 1340 (0.54)
2000 x 1340 (1.49)
https://pages.github.com/images/code-editor@2x.png
720 x 1100 (0.65)
2000 x 1100 (1.82)
https://pages.github.com/images/commit-edits@2x.png
720 x 960 (0.75)
1440 x 960 (1.50)
https://pages.github.com/images/desktop-demo@2x.gif
841 x 816 (1.03)
1682 x 816 (2.06)
https://pages.github.com/images/source-setting@2x.png
720 x 790 (0.91)
1440 x 790 (1.82)
https://pages.github.com/images/new-create-file@2x.png
720 x 674 (1.07)
1440 x 674 (2.14)
https://pages.github.com/images/new-commit-file@2x.png
720 x 710 (1.01)
1440 x 710 (2.03)
https://pages.github.com/images/launch-theme-chooser@2x.png
720 x 620 (1.16)
1440 x 620 (2.32)
https://pages.github.com/images/repo-settings@2x.png
720 x 534 (1.35)
1440 x 534 (2.70)
https://pages.github.com/images/new-index-html@2x.png
720 x 682 (1.06)
1440 x 682 (2.11)
83

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for github.io. This includes optimizations such as providing meta data.

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Document has a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Links are crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Mobile Friendly

Document uses legible font sizes
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Tap targets are sized appropriately
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Mobile Friendly

Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of github.io on mobile screens.

Content Best Practices

Links do not have descriptive text — 1 link found
Make use of descriptive link text to assist search engines in understanding the content.

Manual Checks

Structured data is valid
Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
18

Progressive Web App

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of github.io. This includes details about web app manifests.

PWA Optimized

Redirects HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.
Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.

Installable

Web app manifest or service worker do not meet the installability requirements — 1 reason
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
Failure reason
No manifest was fetched

PWA Optimized

Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of github.io on mobile screens.
Does not provide a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.
Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.
Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.
Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.
Avg. (All Categories) 63
Performance 68
Accessibility 79
Best Practices 80
SEO 71
Progressive Web App 17
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://pages.github.com/
Updated: 27th July, 2021

1.75 seconds
First Contentful Paint (FCP)
77%
14%
9%

0.24 seconds
First Input Delay (FID)
33%
62%
5%

Simulate loading on mobile
68

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for github.io. This includes details about optimizing page load times which can result in a better user experience.

Opportunities

Eliminate render-blocking resources — Potential savings of 0 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Github.io should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://pages.github.com/css/pages.css
4067
150
Properly size images
Images can slow down the page's load time. Github.io should consider serving more appropriate-sized images.
Defer offscreen images — Potential savings of 660 KiB
Time to Interactive can be slowed down by resources on the page. Github.io should consider lazy-loading offscreen and hidden images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://pages.github.com/images/dashboard@2x.png
435382
435382
https://pages.github.com/images/desktop-demo@2x.gif
147672
147672
https://pages.github.com/images/repo-settings@2x.png
93103
93103
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Github.io should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Github.io should consider minifying JS files.
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 20 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
https://pages.github.com/
17.153
Avoid multiple page redirects — Potential savings of 630 ms
Redirects can cause additional delays before the page can begin loading. Github.io should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://github.io/
630
https://pages.github.com/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Github.io should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
URL Potential Savings (Ms)
https://pages.github.com/images/slideshow/bootstrap.png
0

Diagnostics

Avoids an excessive DOM size — 238 elements
A large DOM (Document Object Model) will increase memory usage, cause longer system calculations as well as costly layout reflows.
Statistic Element Value
Total DOM Elements
238
Maximum DOM Depth
~
8
Maximum Child Elements
11
Avoid chaining critical requests — 3 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Github.io should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures — 4 user timings
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
Name Type Start Time (Ms) Duration (Ms)
mark_pe
Mark
477.834
mark_fs
Mark
539.203
mark_qoes
Mark
554.583
mark_ol
Mark
619.106
Keep request counts low and transfer sizes small — 34 requests • 3,556 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
34
3641381
Image
18
2918916
Script
7
628923
Stylesheet
2
50474
Document
2
26542
Font
2
15596
Other
3
930
Media
0
0
Third-party
12
673449
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Avoid large layout shifts — 2 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.10771590970544
0.061055561722439
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks — 8 long tasks found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
https://www.youtube-nocookie.com/s/player/02486e7d/player_ias.vflset/en_US/base.js
10749
287
https://www.youtube-nocookie.com/s/player/02486e7d/www-embed-player.vflset/www-embed-player.js
9600
218
https://www.youtube-nocookie.com/s/player/02486e7d/player_ias.vflset/en_US/base.js
9390
210
Unattributable
636
124
https://pages.github.com/
2340
99
https://pages.github.com/js/jquery.js
3960
79
https://www.youtube-nocookie.com/s/player/02486e7d/www-embed-player.vflset/www-embed-player.js
4039
69
https://www.youtube-nocookie.com/s/player/02486e7d/www-embed-player.vflset/www-embed-player.js
4118
66
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.

Budgets

Performance budget
It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.
Timing budget
It is advised to set a timing budget to monitor the performance of your site.

Other

Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://github.io/
http/1.1
0
28.126999968663
418
0
301
https://pages.github.com/
h2
28.665999998339
44.821999967098
4564
14445
200
text/html
Document
https://pages.github.com/css/pages.css
h2
58.288999949582
74.476999987382
4067
12226
200
text/css
Stylesheet
https://pages.github.com/images/logo.svg
h2
58.54299996281
73.778999969363
3094
5577
200
image/svg+xml
Image
https://pages.github.com/images/slideshow/bootstrap.png
h2
61.320999986492
103.44899998745
157537
156915
200
image/png
Image
https://pages.github.com/images/dashboard@2x.png
h2
61.510999978054
137.46699999319
436003
435382
200
image/png
Image
https://pages.github.com/images/desktop-demo@2x.gif
h2
61.645999958273
88.264999969397
148292
147672
200
image/gif
Image
https://pages.github.com/images/repo-settings@2x.png
h2
61.804999946617
91.391999972984
93722
93103
200
image/png
Image
https://pages.github.com/images/launch-theme-chooser@2x.png
h2
61.995999945793
105.53799994523
97397
96778
200
image/png
Image
https://pages.github.com/images/theme-chooser@2x.png
h2
62.107999983709
135.32999996096
413031
412408
200
image/png
Image
https://pages.github.com/images/code-editor@2x.png
h2
62.281999969855
99.986999994144
238197
237574
200
image/png
Image
https://pages.github.com/images/commit-edits@2x.png
h2
62.913999950979
88.865999947302
157295
156674
200
image/png
Image
https://pages.github.com/images/new-create-file@2x.png
h2
64.140999980737
93.927999958396
118287
117665
200
image/png
Image
https://pages.github.com/images/new-index-html@2x.png
h2
64.316999982111
86.92199998768
75834
75214
200
image/png
Image
https://pages.github.com/images/new-commit-file@2x.png
h2
64.442999952007
99.203999969177
115721
115100
200
image/png
Image
https://pages.github.com/images/source-setting@2x.png
h2
64.564999949653
83.593999966979
131571
130949
200
image/png
Image
https://pages.github.com/js/jquery.js
h2
60.882999969181
78.932999982499
33736
93107
200
application/javascript
Script
https://pages.github.com/js/application.js
h2
61.051999975462
82.880000001751
2810
8554
200
application/javascript
Script
https://www.youtube-nocookie.com/embed/2MsN8gpT6jY?showinfo=0
h2
66.534999990836
118.97299997509
21978
52493
200
text/html
Document
https://pages.github.com/images/user-repo@2x.png
h2
80.844999989495
101.60499997437
160102
159480
200
image/png
Image
https://pages.github.com/images/setup-in-desktop@2x.png
h2
81.91899996018
104.93400000269
171154
170534
200
image/png
Image
https://pages.github.com/css/octicons.woff
h2
84.050999954343
112.21699998714
4090
3492
200
font/woff
Font
https://pages.github.com/images/slideshow/yeoman.png
h2
192.22599995555
222.76099998271
201316
200695
200
image/png
Image
https://www.youtube-nocookie.com/s/player/02486e7d/www-player.css
h2
241.39699997613
266.27999998163
46407
331717
200
text/css
Stylesheet
https://www.youtube-nocookie.com/s/player/02486e7d/www-embed-player.vflset/www-embed-player.js
h2
241.59099999815
254.99200000195
65603
196514
200
text/javascript
Script
https://www.youtube-nocookie.com/s/player/02486e7d/player_ias.vflset/en_US/base.js
h2
241.74599995604
275.27699997881
501118
1751643
200
text/javascript
Script
https://www.youtube-nocookie.com/s/player/02486e7d/fetch-polyfill.vflset/fetch-polyfill.js
h2
241.98199994862
246.8649999937
3416
8543
200
text/javascript
Script
https://fonts.gstatic.com/s/roboto/v18/KFOmCnqEu92Fr1Mu4mxKKTU1Kg.woff2
h2
246.30999995861
249.45499998285
11506
10748
200
font/woff2
Font
https://www.youtube-nocookie.com/api/stats/qoe?event=streamingstats&cpn=fej_DtAZAdbHltbg&el=embedded&docid=2MsN8gpT6jY&ns=yt&fexp=23748147%2C23983296%2C24001373%2C24002022%2C24002025%2C24004644%2C24007246%2C24045411%2C24047386%2C24053866%2C24058128%2C24058812%2C24060921%2C24068842&cl=386768987&seq=1&cbrand=motorola&cbr=Chrome%20Mobile&cbrver=88.0.4324.175&c=WEB_EMBEDDED_PLAYER&cver=1.20210725.0.0&cplayer=UNIPLAYER&cmodel=moto%20g%20(4)&cos=Android&cosver=7.0&cplatform=MOBILE&vps=0.000:N,0.000:ER&cmt=0.000:0.000,0.000:0.000&error=0.000:html5.missingapi:0.000:nocodecs.1;a6s.0&vis=0.000:0&bh=0.000:0.000
554.88899996271
625.18399994588
0
0
-1
Ping
https://www.google.com/js/th/15Ie8MSBp4IN3jcelD60kGm05ThBDTbI2ej_yOJ3Q94.js
h2
582.65899994876
697.03899999149
14214
35906
200
text/javascript
Script
https://www.youtube-nocookie.com/s/player/02486e7d/player_ias.vflset/en_US/embed.js
h2
605.65199999837
664.14999996778
8026
25246
200
text/javascript
Script
https://www.youtube-nocookie.com/generate_204?-4ieCw
h2
850.03299999516
858.34299999988
251
0
204
text/plain
Image
https://www.youtube-nocookie.com/youtubei/v1/log_event?alt=json&key=AIzaSyAO_FJ2SlqU8Q4STEHLGCilw_Y9_11qcW8
h2
2633.5179999587
2659.0539999888
512
28
200
application/json
XHR
https://pages.github.com/images/slideshow/facebookdesign.png
h2
3186.9509999524
3206.279999984
200112
199490
200
image/png
Image
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
55.455
7.184
64.523
7.151
85.9
49.657
147.985
7.045
162.866
39.432
205.787
6.487
216.021
31.043
262.397
5.151
274.871
10.108
289.295
17.374
398.275
104.862
505.809
108.756
614.68
8.722
624.661
7.001
675.654
14.105
705.915
6.37
714.511
143.556
2624.103
16.558
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Metrics

First Contentful Paint — 2.4 s
The time taken for the first image or text on the page to be rendered.
Speed Index — 5.2 s
The time taken for the page contents to be visibly populated.
Largest Contentful Paint — 3.1 s
The timing of the largest text or image that is painted.
Total Blocking Time — 350 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).
Cumulative Layout Shift — 0.169
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

First Meaningful Paint — 2.4 s
The time taken for the primary content of the page to be rendered.

Opportunities

Reduce unused CSS — Potential savings of 44 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Github.io should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.youtube-nocookie.com/s/player/02486e7d/www-player.css
46407
44731
Use video formats for animated content — Potential savings of 72 KiB
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://pages.github.com/images/desktop-demo@2x.gif
147672
73836

Diagnostics

Avoid enormous network payloads — Total size was 3,556 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www.youtube-nocookie.com/s/player/02486e7d/player_ias.vflset/en_US/base.js
501118
https://pages.github.com/images/dashboard@2x.png
436003
https://pages.github.com/images/theme-chooser@2x.png
413031
https://pages.github.com/images/code-editor@2x.png
238197
https://pages.github.com/images/slideshow/yeoman.png
201316
https://pages.github.com/images/slideshow/facebookdesign.png
200112
https://pages.github.com/images/setup-in-desktop@2x.png
171154
https://pages.github.com/images/user-repo@2x.png
160102
https://pages.github.com/images/slideshow/bootstrap.png
157537
https://pages.github.com/images/commit-edits@2x.png
157295
Reduce JavaScript execution time — 1.7 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://www.youtube-nocookie.com/s/player/02486e7d/player_ias.vflset/en_US/base.js
982.6
750.716
161.664
https://www.youtube-nocookie.com/s/player/02486e7d/www-embed-player.vflset/www-embed-player.js
659.892
580.808
20.484
https://pages.github.com/
490.716
11.96
4.376
Unattributable
368.832
12.112
0.904
https://www.youtube-nocookie.com/embed/2MsN8gpT6jY?showinfo=0
162.62
59.224
14.268
https://pages.github.com/js/jquery.js
144.228
107.256
9.928
Minimize main-thread work — 2.9 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Script Evaluation
1544.548
Other
402.952
Style & Layout
357.22
Rendering
240.248
Script Parsing & Compilation
227.072
Parse HTML & CSS
94.976
Garbage Collection
28.036

Metrics

Time to Interactive — 9.4 s
The time taken for the page to become fully interactive.

Other

Max Potential First Input Delay — 290 ms
Users could experience a delay when interacting with the page.
First Contentful Paint (3G) — 4689 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.

Opportunities

Reduce unused JavaScript — Potential savings of 403 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.youtube-nocookie.com/s/player/02486e7d/player_ias.vflset/en_US/base.js
501118
376864
https://www.youtube-nocookie.com/s/player/02486e7d/www-embed-player.vflset/www-embed-player.js
65603
36033
Serve images in next-gen formats — Potential savings of 1,867 KiB
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://pages.github.com/images/dashboard@2x.png
435382
368248
https://pages.github.com/images/theme-chooser@2x.png
412408
338550
https://pages.github.com/images/code-editor@2x.png
237574
152162
https://pages.github.com/images/user-repo@2x.png
159480
131640
https://pages.github.com/images/commit-edits@2x.png
156674
107320
https://pages.github.com/images/setup-in-desktop@2x.png
170534
107244
https://pages.github.com/images/slideshow/yeoman.png
200695
98907
https://pages.github.com/images/slideshow/facebookdesign.png
199490
92928
https://pages.github.com/images/source-setting@2x.png
130949
85567
https://pages.github.com/images/new-commit-file@2x.png
115100
84394
https://pages.github.com/images/new-create-file@2x.png
117665
84027
https://pages.github.com/images/slideshow/bootstrap.png
156915
74323
https://pages.github.com/images/repo-settings@2x.png
93103
71175
https://pages.github.com/images/launch-theme-chooser@2x.png
96778
61248
https://pages.github.com/images/new-index-html@2x.png
75214
54212

Diagnostics

Serve static assets with an efficient cache policy — 21 resources found
Github.io can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
https://pages.github.com/images/dashboard@2x.png
600000
436003
https://pages.github.com/images/theme-chooser@2x.png
600000
413031
https://pages.github.com/images/code-editor@2x.png
600000
238197
https://pages.github.com/images/slideshow/yeoman.png
600000
201316
https://pages.github.com/images/slideshow/facebookdesign.png
600000
200112
https://pages.github.com/images/setup-in-desktop@2x.png
600000
171154
https://pages.github.com/images/user-repo@2x.png
600000
160102
https://pages.github.com/images/slideshow/bootstrap.png
600000
157537
https://pages.github.com/images/commit-edits@2x.png
600000
157295
https://pages.github.com/images/desktop-demo@2x.gif
600000
148292
https://pages.github.com/images/source-setting@2x.png
600000
131571
https://pages.github.com/images/new-create-file@2x.png
600000
118287
https://pages.github.com/images/new-commit-file@2x.png
600000
115721
https://pages.github.com/images/launch-theme-chooser@2x.png
600000
97397
https://pages.github.com/images/repo-settings@2x.png
600000
93722
https://pages.github.com/images/new-index-html@2x.png
600000
75834
https://pages.github.com/js/jquery.js
600000
33736
https://pages.github.com/css/octicons.woff
600000
4090
https://pages.github.com/css/pages.css
600000
4067
https://pages.github.com/images/logo.svg
600000
3094
https://pages.github.com/js/application.js
600000
2810
Ensure text remains visible during webfont load
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
URL Potential Savings (Ms)
https://pages.github.com/css/octicons.woff
28.166000032797
https://fonts.gstatic.com/s/roboto/v18/KFOmCnqEu92Fr1Mu4mxKKTU1Kg.woff2
3.145000024233
Reduce the impact of third-party code — Third-party code blocked the main thread for 1,060 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Transfer Size (Bytes) Main-Thread Blocking Time (Ms)
647311
1056.74
14214
0
11506
0
Does not use passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Source
Image elements do not have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
URL Failing Elements
https://pages.github.com/images/slideshow/bootstrap.png
https://pages.github.com/images/logo.svg
79

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of github.io. This includes details about various page attributes that can be optimized.

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`button`, `link`, and `menuitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
ARIA `meter` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `progressbar` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
ARIA `tooltip` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `treeitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
`<object>` elements have `[alt]` text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.
Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Internationalization and localization

`<html>` element has a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Github.io may provide assistance to deaf or hearing-impaired users with captions on videos.

Contrast

Background and foreground colors do not have a sufficient contrast ratio.
Many (if not most) users find low-contrast text difficult or impossible to read.
Failing Elements
API

Names and labels

`<frame>` or `<iframe>` elements do not have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
Failing Elements
Links do not have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.

Navigation

Heading elements are not in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
Failing Elements

Manual Checks

The page has a logical tab order
The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.
Interactive controls are keyboard focusable
Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.
Interactive elements indicate their purpose and state
Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.
The user's focus is directed to new content added to the page
When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.
User focus is not accidentally trapped in a region
Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.
Custom controls have associated labels
Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.
Custom controls have ARIA roles
Ensure that all custom interactive controls have appropriate ARIA roles.
Visual order on the page follows DOM order
Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.
Offscreen content is hidden from assistive technology
Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.
HTML5 landmark elements are used to improve navigation
Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.
80

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that github.io should incorporate. This includes practices such as protecting pages with HTTPS.

Audits

Links to cross-origin destinations are safe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).
Description Directive Severity
No CSP found in enforcement mode
High

Audits

Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.
Serves images with appropriate resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

Audits

Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Properly defines charset
It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.
Avoids Application Cache
Application cache is deprecated and is no longer recommended.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
jQuery
1.10.2
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL Request Resolution
http://github.io/
Allowed
Includes front-end JavaScript libraries with known security vulnerabilities — 4 vulnerabilities detected
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Library Version Vulnerability Count Highest Severity
4
Medium

Audits

Displays images with incorrect aspect ratio
Ensure that image display dimensions match their natural aspect ratio.
URL Aspect Ratio (Displayed) Aspect Ratio (Actual)
https://pages.github.com/images/dashboard@2x.png
1054 x 1040 (1.01)
1906 x 1040 (1.83)
https://pages.github.com/images/theme-chooser@2x.png
720 x 1340 (0.54)
2000 x 1340 (1.49)
https://pages.github.com/images/code-editor@2x.png
720 x 1100 (0.65)
2000 x 1100 (1.82)
https://pages.github.com/images/commit-edits@2x.png
720 x 960 (0.75)
1440 x 960 (1.50)
https://pages.github.com/images/desktop-demo@2x.gif
841 x 816 (1.03)
1682 x 816 (2.06)
https://pages.github.com/images/source-setting@2x.png
720 x 790 (0.91)
1440 x 790 (1.82)
https://pages.github.com/images/new-create-file@2x.png
720 x 674 (1.07)
1440 x 674 (2.14)
https://pages.github.com/images/new-commit-file@2x.png
720 x 710 (1.01)
1440 x 710 (2.03)
https://pages.github.com/images/launch-theme-chooser@2x.png
720 x 620 (1.16)
1440 x 620 (2.32)
https://pages.github.com/images/repo-settings@2x.png
720 x 534 (1.35)
1440 x 534 (2.70)
https://pages.github.com/images/new-index-html@2x.png
720 x 682 (1.06)
1440 x 682 (2.11)
71

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for github.io. This includes optimizations such as providing meta data.

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Document has a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Links are crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Mobile Friendly

Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of github.io on mobile screens.
Document doesn't use legible font sizes
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Tap targets are not sized appropriately
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Content Best Practices

Links do not have descriptive text — 1 link found
Make use of descriptive link text to assist search engines in understanding the content.

Manual Checks

Structured data is valid
Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
17

Progressive Web App

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of github.io. This includes details about web app manifests.

PWA Optimized

Redirects HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.

Installable

Web app manifest or service worker do not meet the installability requirements — 1 reason
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
Failure reason
No manifest was fetched

PWA Optimized

Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Content is not sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of github.io on mobile screens.
Does not provide a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.
Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.
Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.
Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.
Hosting

Server Location

Server IP Address: 185.199.111.153
Continent: Europe
Country: Netherlands
Netherlands Flag
Region:
City:
Longitude: 4.8995
Latitude: 52.3824
Currencies: EUR
Languages: Dutch

Web Hosting Provider

Registration

Domain Registrant

Private Registration: Yes
Name: REDACTED FOR PRIVACY
Organization: GitHub, Inc.
Country: US
City: REDACTED FOR PRIVACY
State: CA
Post Code: REDACTED FOR PRIVACY
Email:
Phone: REDACTED FOR PRIVACY
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Name IP Address
MarkMonitor Inc. 172.64.148.104
Security

Visitor Safety

Mature Content: Not Likely
McAfee WebAdvisor Rating: Unknown
WOT Rating:
WOT Trustworthiness: 78/100
WOT Child Safety: 91/100
Note: Safety information is not guaranteed.

SSL/TLS Certificate

Issued To: *.github.io
Issued By: DigiCert Global G2 TLS RSA SHA256 2020 CA1
Valid From: 15th March, 2024
Valid To: 14th March, 2025
Subject: CN = *.github.io
O = GitHub, Inc.
L = San Francisco
S = US
Hash: 915f8897
Issuer: CN = DigiCert Global G2 TLS RSA SHA256 2020 CA1
O = DigiCert Inc
S = US
Version: 2
Serial Number: 8293580541129325440080546734590864923
Serial Number (Hex): 063D4917404D39E513CB3FEECD1B2E1B
Valid From: 15th March, 2024
Valid To: 14th March, 2024
Signature Algorithm (Short Name): RSA-SHA256
Signature Algorithm (Long Name): sha256WithRSAEncryption
Authority Key Identifier: keyid:74:85:80:C0:66:C7:DF:37:DE:CF:BD:29:37:AA:03:1D:BE:ED:CD:17
Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication
CRL Distribution Points:
Full Name:
URI:http://crl3.digicert.com/DigiCertGlobalG2TLSRSASHA2562020CA1-1.crl

Full Name:
URI:http://crl4.digicert.com/DigiCertGlobalG2TLSRSASHA2562020CA1-1.crl

Certificate Policies: Policy: 2.23.140.1.2.2
CPS: http://www.digicert.com/CPS

Authority Information Access: OCSP - URI:http://ocsp.digicert.com
CA Issuers - URI:http://cacerts.digicert.com/DigiCertGlobalG2TLSRSASHA2562020CA1-1.crt

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 4E:75:A3:27:5C:9A:10:C3:38:5B:6C:D4:DF:3F:52:EB:
1D:F0:E0:8E:1B:8D:69:C0:B1:FA:64:B1:62:9A:39:DF
Timestamp : Mar 15 19:00:46.848 2024 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:20:53:F3:39:DB:B5:9C:C7:42:90:DC:82:3B:
90:2B:86:E5:63:2E:38:74:52:C4:A9:1F:D7:10:23:26:
E4:A4:C8:F0:02:21:00:95:5F:4B:AE:AD:C2:00:D9:48:
3B:8A:93:4D:D9:2D:59:CA:0B:A4:5A:A2:42:87:B8:63:
20:7D:17:B2:B5:E1:F1
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 7D:59:1E:12:E1:78:2A:7B:1C:61:67:7C:5E:FD:F8:D0:
87:5C:14:A0:4E:95:9E:B9:03:2F:D9:0E:8C:2E:79:B8
Timestamp : Mar 15 19:00:46.849 2024 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:20:0B:1A:4B:04:36:A4:F9:35:8A:6A:BA:C2:
1E:56:67:E0:39:6A:C0:47:C0:37:79:6F:96:04:A8:DB:
51:D0:B9:4F:02:21:00:E2:72:B6:FB:D9:CD:25:03:6B:
2E:31:63:D6:4F:DD:8F:14:B6:91:BC:5A:C5:9F:D1:D5:
CC:8E:95:87:9D:18:66
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : E6:D2:31:63:40:77:8C:C1:10:41:06:D7:71:B9:CE:C1:
D2:40:F6:96:84:86:FB:BA:87:32:1D:FD:1E:37:8E:50
Timestamp : Mar 15 19:00:46.868 2024 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:46:02:21:00:F2:50:5F:84:00:AC:50:A3:33:4B:0A:
2B:3B:16:2E:6A:A6:99:4F:25:32:12:84:61:1D:93:81:
EB:35:01:0C:90:02:21:00:D9:8D:D5:84:FE:51:1B:E7:
5A:A5:C6:F0:62:05:5B:AD:39:60:5B:33:BB:28:4F:E5:
83:5C:75:D4:25:5C:CF:74
Key Usage: Digital Signature, Key Encipherment
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:*.github.com
DNS:*.githubusercontent.com
DNS:github.com
DNS:github.io
DNS:githubusercontent.com
DNS:www.github.com
DNS:*.github.io
Technical

DNS Lookup

A Records

Host IP Address Class TTL
github.io. 185.199.110.153 IN 3600
github.io. 185.199.108.153 IN 3600
github.io. 185.199.111.153 IN 3600
github.io. 185.199.109.153 IN 3600

NS Records

Host Nameserver Class TTL
github.io. dns1.p05.nsone.net. IN 900
github.io. dns2.p05.nsone.net. IN 900
github.io. dns3.p05.nsone.net. IN 900
github.io. dns4.p05.nsone.net. IN 900
github.io. ns-1339.awsdns-39.org. IN 900
github.io. ns-1622.awsdns-10.co.uk. IN 900
github.io. ns-393.awsdns-49.com. IN 900
github.io. ns-692.awsdns-22.net. IN 900

CAA Records

Domain Flags Tag Class TTL
digicert.com 0 issue IN 3600
letsencrypt.org 0 issue IN 3600
sectigo.com 0 issue IN 3600
digicert.com 0 issuewild IN 3600
sectigo.com 0 issuewild IN 3600

SOA Records

Domain Name Primary NS Responsible Email TTL
github.io. ns-1622.awsdns-10.co.uk. awsdns-hostmaster.amazon.com. 900

TXT Records

Host Value Class TTL
github.io. v=spf1 IN 3600

HTTP Response Headers

HTTP-Code: HTTP/2 200
server: GitHub.com
content-type: text/html; charset=utf-8
expires: 24th April, 2024
cache-control: max-age=600
date: 24th April, 2024
x-origin-cache: HIT
last-modified: 24th April, 2024
access-control-allow-origin: *
etag: "66284da1-381c"
x-proxy-cache: MISS
x-github-request-id: 6ECC:1714:1B6680:22204A:66284E62
accept-ranges: bytes
via: 1.1 varnish
age: 170
x-served-by: cache-chi-kigq8000171-CHI
x-cache: HIT
x-cache-hits: 2
x-timer: S1713922602.532558,VS0,VE1
vary: Accept-Encoding
x-fastly-request-id: 5a25262f9ed2766032485effab1ef883b316187b
content-length: 14364

Whois Lookup

Created: 3rd August, 2013
Changed: 2nd September, 2023
Expires: 3rd August, 2025
Registrar: MarkMonitor Inc.
Status: clientDeleteProhibited
clientTransferProhibited
clientUpdateProhibited
Nameservers: dns1.p05.nsone.net
dns2.p05.nsone.net
dns3.p05.nsone.net
dns4.p05.nsone.net
ns-1339.awsdns-39.org
ns-1622.awsdns-10.co.uk
ns-393.awsdns-49.com
ns-692.awsdns-22.net
Owner Name: REDACTED FOR PRIVACY
Owner Organization: GitHub, Inc.
Owner Street: REDACTED FOR PRIVACY
Owner Post Code: REDACTED FOR PRIVACY
Owner City: REDACTED FOR PRIVACY
Owner State: CA
Owner Country: US
Owner Phone: REDACTED FOR PRIVACY
Owner Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Admin Name: REDACTED FOR PRIVACY
Admin Organization: REDACTED FOR PRIVACY
Admin Street: REDACTED FOR PRIVACY
Admin Post Code: REDACTED FOR PRIVACY
Admin City: REDACTED FOR PRIVACY
Admin State: REDACTED FOR PRIVACY
Admin Country: REDACTED FOR PRIVACY
Admin Phone: REDACTED FOR PRIVACY
Admin Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Tech Name: REDACTED FOR PRIVACY
Tech Organization: REDACTED FOR PRIVACY
Tech Street: REDACTED FOR PRIVACY
Tech Post Code: REDACTED FOR PRIVACY
Tech City: REDACTED FOR PRIVACY
Tech State: REDACTED FOR PRIVACY
Tech Country: REDACTED FOR PRIVACY
Tech Phone: REDACTED FOR PRIVACY
Tech Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Full Whois: Domain Name: github.io
Registry Domain ID: ed6bb85607724679a294e61f95bc4bff-DONUTS
Registrar WHOIS Server: whois.markmonitor.com
Registrar URL: http://www.markmonitor.com
Updated Date: 2023-02-09T09:11:27Z
Creation Date: 2013-03-08T19:12:48Z
Registry Expiry Date: 2025-03-08T19:12:48Z
Registrar: MarkMonitor Inc.
Registrar IANA ID: 292
Registrar Abuse Contact Email: abusecomplaints@markmonitor.com
Registrar Abuse Contact Phone: +1.2083895740
Domain Status: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Domain Status: clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited
Registry Registrant ID: REDACTED FOR PRIVACY
Registrant Name: REDACTED FOR PRIVACY
Registrant Organization: GitHub, Inc.
Registrant Street: REDACTED FOR PRIVACY
Registrant City: REDACTED FOR PRIVACY
Registrant State/Province: CA
Registrant Postal Code: REDACTED FOR PRIVACY
Registrant Country: US
Registrant Phone: REDACTED FOR PRIVACY
Registrant Phone Ext: REDACTED FOR PRIVACY
Registrant Fax: REDACTED FOR PRIVACY
Registrant Fax Ext: REDACTED FOR PRIVACY
Registrant Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Registry Admin ID: REDACTED FOR PRIVACY
Admin Name: REDACTED FOR PRIVACY
Admin Organization: REDACTED FOR PRIVACY
Admin Street: REDACTED FOR PRIVACY
Admin City: REDACTED FOR PRIVACY
Admin State/Province: REDACTED FOR PRIVACY
Admin Postal Code: REDACTED FOR PRIVACY
Admin Country: REDACTED FOR PRIVACY
Admin Phone: REDACTED FOR PRIVACY
Admin Phone Ext: REDACTED FOR PRIVACY
Admin Fax: REDACTED FOR PRIVACY
Admin Fax Ext: REDACTED FOR PRIVACY
Admin Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Registry Tech ID: REDACTED FOR PRIVACY
Tech Name: REDACTED FOR PRIVACY
Tech Organization: REDACTED FOR PRIVACY
Tech Street: REDACTED FOR PRIVACY
Tech City: REDACTED FOR PRIVACY
Tech State/Province: REDACTED FOR PRIVACY
Tech Postal Code: REDACTED FOR PRIVACY
Tech Country: REDACTED FOR PRIVACY
Tech Phone: REDACTED FOR PRIVACY
Tech Phone Ext: REDACTED FOR PRIVACY
Tech Fax: REDACTED FOR PRIVACY
Tech Fax Ext: REDACTED FOR PRIVACY
Tech Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Name Server: ns-692.awsdns-22.net
Name Server: ns-1622.awsdns-10.co.uk
Name Server: dns1.p05.nsone.net
Name Server: dns2.p05.nsone.net
Name Server: dns3.p05.nsone.net
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of WHOIS database: 2024-04-24T01:36:42Z <<<

For more information on Whois status codes, please visit https://icann.org/epp

Terms of Use: Access to WHOIS information is provided to assist persons in determining the contents of a domain name registration record in the registry database. The data in this record is provided by Identity Digital or the Registry Operator for informational purposes only, and accuracy is not guaranteed. This service is intended only for query-based access. You agree that you will use this data only for lawful purposes and that, under no circumstances will you use this data to (a) allow, enable, or otherwise support the transmission by e-mail, telephone, or facsimile of mass unsolicited, commercial advertising or solicitations to entities other than the data recipient's own existing customers; or (b) enable high volume, automated, electronic processes that send queries or data to the systems of Registry Operator, a Registrar, or Identity Digital except as reasonably necessary to register domain names or modify existing registrations. When using the Whois service, please consider the following: The Whois service is not a replacement for standard EPP commands to the SRS service. Whois is not considered authoritative for registered domain objects. The Whois service may be scheduled for downtime during production or OT&E maintenance periods. Queries to the Whois services are throttled. If too many queries are received from a single IP address within a specified time, the service will begin to reject further queries for a period of time to prevent disruption of Whois service access. Abuse of the Whois system through data mining is mitigated by detecting and limiting bulk query access from single sources. Where applicable, the presence of a [Non-Public Data] tag indicates that such data is not made publicly available due to applicable data privacy laws or requirements. Should you wish to contact the registrant, please refer to the Whois records available through the registrar URL listed above. Access to non-public data may be provided, upon request, where it can be reasonably confirmed that the requester holds a specific legitimate interest and a proper legal basis for accessing the withheld data. Access to this data provided by Identity Digital can be requested by submitting a request via the form found at https://www.identity.digital/about/policies/whois-layered-access/. The Registrar of Record identified in this output may have an RDDS service that can be queried for additional information on how to contact the Registrant, Admin, or Tech contact of the queried domain name. Identity Digital Inc. and Registry Operator reserve the right to modify these terms at any time. By submitting this query, you agree to abide by this policy.

Nameservers

Name IP Address
dns1.p05.nsone.net 198.51.44.5
dns2.p05.nsone.net 198.51.45.5
dns3.p05.nsone.net 198.51.44.69
dns4.p05.nsone.net 198.51.45.69
ns-1339.awsdns-39.org 205.251.197.59
ns-1622.awsdns-10.co.uk 205.251.198.86
ns-393.awsdns-49.com 205.251.193.137
ns-692.awsdns-22.net 205.251.194.180
Related

Subdomains

Domain Subdomain
123tarunanand
7013145
a1app
ajinkyaz
akashnikhra

Similar Sites

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
0/5
$638,777,049 USD 5/5
0/5
0/5
$788 USD 1/5

Sites hosted on the same IP address

Domain Valuation Snoop Score
$869 USD 2/5
$2,244 USD 2/5
$2,679 USD 2/5
$801 USD 1/5
$7,356 USD 3/5