Show

Github.io GitHub Pages | Websites for you and your projects, hosted directly from your GitHub repository. Just edit, push, and your changes are live.

Websites for you and your projects, hosted directly from your GitHub repository. Just edit, push, and your changes are live.

Need help with your SEO?
Online Status
Online

Server IP address resolved: Yes
Http response code: 200
Response time: 0.09 sec.
Last Checked: 02/27/2019

Github.io receives about ninety unique visitors and ninety pageviews per day. The estimated value of github.io is zero USD. Each unique visitor makes about 1 pageviews on average.

Over the time github.io has been ranked as high as 157 in the world.

Github.io server is located in Netherlands, but, unfortunately, we cannot identify the countries where the visitors come from and thus it’s impossible to define if the distance can potentially affect the page load time.

At the time of the last check (January 28, 2019) github.io has a valid and up-to-date SSL certificate that expires on June 20, 2020.

According to Google Safe Browsing, Google Safe Search, Symantec and Web of Trust github.io is quite a safe domain.

Mobile-Friendly test indicates that github.io is well optimized for mobile and tablet devices, however website page loading time could be improved.

Global Rank
7,969,177
Average Load Time
1.14sec
Links In Count
117
Website Value
$0
Overview
Last Updated: 06/26/2019
Overall result - "github.io" is SAFE.
We gather website safety and reputation data and compare it with available third-party sources so we calculate own safety and trustworthiness rate based on information that we get.
Norton Connect Safe
Last Updated: 01/12/2019
NCS "github.io" OK.

Norton ConnectSafe evaluates github.io for any unsafe and insecure content. The results are critical for families with young children.

Google Safe Search
Last Updated: 10/10/2016
GSS "github.io" OK.

SafeSearch is used as a parental control tool to filter out any inappropriate for your children search results on your devices: phones, tablets or personal computers.

Google Safe Browsing
Last Updated: 02/18/2019
Malware not found at "github.io".
"github.io" is not a phishing page.
"github.io" does not install unwanted software.
"github.io" does not contain harmfull applications.
Google Safe Browsing notifies when websites are compromised by malicious actors. These protections work across Google products and provide a safer online experience.
Site Advisor
Last Updated: 01/09/2019
SA "github.io" OK.

McAfee assesses github.io for a meaningful set of security threats. Featured dangers from annoying pop-ups to hidden Trojans, that can steal your identity, will be revealed. McAfee does not analyze github.io for mature or inappropriate content, only security checks are evaluated.

Web of Trust
Last Updated: 01/09/2019
WOT "github.io" VERY GOOD.

The WOT calculates reputation of the github.io. This reputation system receives ratings from users and information from third-party sources, assesses the github.io for safety features and confirms, whether github.io is suitable for children.

SSL Information
Domain www.github.com
Issuer DigiCert SHA2 High Assurance Server CA
Algorithm RSA-SHA256
Valid form 06/27/2018
Expiration 06/20/2020
Signed Certificate is not self signed
Additional Domains www.github.com
*.github.io
*.githubusercontent.com
*.github.com
github.com
github.io
githubusercontent.com
Server Location
Amsterdam
Noord-Holland
Netherlands
ASN Information

ASN ID: 54113
ASN Title: FASTLY - Fastly, US

Last Update: 05/29/2019

#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/whois_tou.html
#
# If you see inaccuracies in the results, please report at
# https://www.arin.net/resources/whois_reporting/index.html
#
# Copyright 1997-2018, American Registry for Internet Numbers, Ltd.
#

ASNumber: 54113
ASName: FASTLY
ASHandle: AS54113
RegDate: 2011-10-04
Updated: 2012-03-02
Comment: http://www.fastly.com/
Ref: https://rdap.arin.net/registry/autnum/54113

OrgName: Fastly
OrgId: SKYCA-3
Address: PO Box 78266
City: San Francisco
StateProv: CA
PostalCode: 94107
Country: US
RegDate: 2011-09-16
Updated: 2017-03-30
Ref: https://rdap.arin.net/registry/entity/SKYCA-3

OrgNOCHandle: FNO19-ARIN
OrgNOCName: Fastly Network Operations
OrgNOCPhone: +1-415-404-9374
OrgNOCEmail: noc@fastly.com
OrgNOCRef: https://rdap.arin.net/registry/entity/FNO19-ARIN

OrgTechHandle: FRA19-ARIN
OrgTechName: Fastly RIR Administrator
OrgTechPhone: +1-415-404-9374
OrgTechEmail: rir-admin@fastly.com
OrgTechRef: https://rdap.arin.net/registry/entity/FRA19-ARIN

OrgAbuseHandle: ABUSE4771-ARIN
OrgAbuseName: Abuse Account
OrgAbusePhone: +1-415-496-9353
OrgAbuseEmail: abuse@fastly.com
OrgAbuseRef: https://rdap.arin.net/registry/entity/ABUSE4771-ARIN

#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/whois_tou.html
#
# If you see inaccuracies in the results, please report at
# https://www.arin.net/resources/whois_reporting/index.html
#
# Copyright 1997-2018, American Registry for Internet Numbers, Ltd.
#

HTML Metatags
Title
GitHub Pages | Websites for you and your projects, hosted directly from your GitHub repository. Just edit, push, and your changes are live.
The title is too long, search engines may need to shorten it in the search results and your keywords may not appear on the search results page. You should try to keep the length of the title somewhere between at least 10 characters and 70 characters.
Description
Websites for you and your projects, hosted directly from your GitHub repository. Just edit, push, and your changes are live.
The description has optimal length. Keep in mind that the "optimal" length will vary depending on the situation, and your primary goal should be to provide value and drive clicks.
Encoding
UTF-8
You should always specify the encoding used for an HTML page. If you don't, you risk that characters in your content are incorrectly interpreted. This is not just an issue of human readability, increasingly machines need to understand your data too.
Language
en English
Identifying the language of your content allows you to automatically do a number of things, from changing the look and behavior of a page, to assisting search engines in extracting information. If part of the page uses text in a different language, you can add a language attribute with a different value to the element that surrounds that content.
Language Region
Not Found
Images
Attribute ALT
Success, no any <img> without defined ALT attribute. Alt text is helpful to end users if they have images disabled or if the image does not properly load.
As a general rule, search engines do not interpret the content of image files. The text provided in the <img alt> attribute enables the site owner to provide relevant information to the search engine and to the end user.
H1-H6 Tags Information

For search engines, <H> tags helps understand the structure of the text on a page better. For users, headings are like anchors in a wall of text, navigating them through the page and making it easier to digest. The <h1> tag reinforces the core keyword(s) found in the <title>, <description>, and the <body>. We recommend that the <h1> tag includes keywords that reflect the contents of the page and that it is not longer than 150 characters in length, but don’t overuse the tags and the keywords in them. Keep it readable for users.

H1
Line 43, ...<h1>What is GitHub Pages?</h1>...
Line 48, ...<h1>Ready to get started? Build your own site from scratch or gen...
Line 261, ...<h1>Now that you’re up and running, here are a few things you sho...
Your H1 introduces the topic your page is all about, just as a title tells a reader what a book is all about. Remove redundant H1 tags from the page source, so that only one H1 tag exists.
H2
2 H2 tag(s).
The H2s are akin to book chapters, describing the main topics you’ll cover in sections of the article.
H3
Subsequent headers, H3s to H6s, serve as additional sub-headings within each section, just as a book chapter may be split up by multiple sub-topics.
H4
25 H4 tag(s).
H5
H6
Iframes Information
iFrame
Line 44, ...<iframe width="853" height="480" src="https://www.youtube.com/emb...
Since search engines consider the content in iframes to belong to another website, the best you can hope for is no effect on SEO. Iframes tend to neither help nor hurt your search engine ranking. For this reason, it’s best to refrain from using iframes on main pages that you want to rank high in search engine results. Instead, fill high-priority pages with useful, unique content and save iframes for other pages.
Code To Text Ratio
Code To Text Ratio
26.07 %
A good code to text ratio is anywhere from 25 to 70 percent. This percentage refers to the visible text ratio, as opposed to HTML elements, image tags and other non-visible information. This has become especially apparent since search engines, such as Google, released the Panda update which placed importance on content-driven sites.
Favicons

Favicons are the little piece of graphic that represents your brand on browser tabs, bookmark lists, search history, search ads and even search results. These files are placed in a file called favicon.ico and placed in the root directory of a website. There are no direct SEO effects of having favicons. However, there may be indirect benefits such as increased usability of site and bookmarks. It makes your website look more professional and help a users to remember your site while browsing through multiple URLs. If you want to get mentioned benefits you have to specify icons for different web browsers and sometimes even for different mobiles.

Default Favicon
Line 5, /favicon.ico
Backup icon for most desktop browsers (if no icon of the right size is found). Tag format <link rel="shortcut icon" href="path-to-16x16-icon.ico" type="image/x-icon" />
16x16 Optional Favicon
Standard icon for outdated browsers or small resolution hand held devices. Tag format <link rel="icon" type="image/png" sizes="16x16" href="path-to-16x16.png">
32x32 Optional Favicon
Standard for most desktop browsers. Tag format <link rel="icon" sizes="32x32" href="path-to-32x32.png">
96x96 Optional Favicon
Mostly used as GoogleTV icon. Tag format <link rel="icon" type="image/png" sizes="96x96" href="path-to-96x96.png">
Default Apple Icon
Backup icon for apple devices (if no icon of the right size is found). Preferrable size 60x60. Tag format <link rel="apple-touch-icon" sizes="72x72" href="path-to-small-icon.png">
180x180 Apple Icon
iPhone 6 plus icons. Tag format <link rel="apple-touch-icon" sizes="180x180" href="path-to-180x180.png">
152x152 Apple Icon
iPad, iPad mini icons. Tag format <link rel="apple-touch-icon" sizes="152x152" href="path-to-icon-152x152.png">
167x167 Apple Icon
iPad Pro icon. Tag format <link rel="apple-touch-icon" sizes="167x167" href="path-to-167x167.png">
Robots.txt Information

Robots.txt is a text file that website owners can create to tell search engine bots how to crawl and index pages on their site.

Robots File
Robots File Loaded successfully (/robots.txt)
You can have multiple lines of instructions to allow or disallow specific URLs and add multiple sitemaps. If you do not disallow a URL, then search engine bots assume that they are allowed to crawl it.
Disallow
Not found
Other User-Agent
Not found
Default User-Agent
Not found
Sitemap

A sitemap is an XML file where is provided information about each URL: when it was last updated, how often it changes, and how important it is in relation to other URLs in the site. Search engines crawling bots read this file to more efficiently and intelligently crawl your site and to find URLs that may be isolated from rest of the site's content.

Default Sitemap
Sitemap File Loaded successfully (/sitemap.xml)
Using a sitemap doesn't guarantee that all the items in your sitemap will be crawled and indexed, however, your site will benefit from having a sitemap.
WHOIS

Domain Name: GITHUB.IO
Registry Domain ID: D503300000040351827-LRMS
Registrar WHOIS Server: whois.markmonitor.com
Registrar URL: http://www.markmonitor.com
Updated Date: 2018-02-04T10:13:08Z
Creation Date: 2013-03-08T19:12:48Z
Registry Expiry Date: 2019-03-08T19:12:48Z
Registrar Registration Expiration Date:
Registrar: MarkMonitor Inc.
Registrar IANA ID: 292
Registrar Abuse Contact Email: abusecomplaints@markmonitor.com
Registrar Abuse Contact Phone: +1.2083895740
Reseller:
Domain Status: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Domain Status: clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited
Registrant Organization: GitHub, Inc.
Registrant State/Province: CA
Registrant Country: US
Name Server: NS1.P16.DYNECT.NET
Name Server: NS2.P16.DYNECT.NET
Name Server: NS-1622.AWSDNS-10.CO.UK
Name Server: NS-692.AWSDNS-22.NET
Name Server: NS-1339.AWSDNS-39.ORG
DNSSEC: unsigned

>>> Last update of WHOIS database: 2018-11-08T12:41:15Z

DNS Records
HostA RecordTTL
github.io185.199.111.1533600
github.io185.199.109.1533600
github.io185.199.108.1533600
github.io185.199.110.1533600
HostMX RecordPriorityTTL
HostNS RecordTTL
github.ions-1339.awsdns-39.org900
github.ions-1622.awsdns-10.co.uk900
github.ions-393.awsdns-49.com900
github.ions-692.awsdns-22.net900
github.ions1.p16.dynect.net900
github.ions2.p16.dynect.net900
github.ions3.p16.dynect.net900
github.ions4.p16.dynect.net900
HostTXT RecordTTL
github.iov=spf1 a -all3600

ns-1622.awsdns-10.co.uk
TTL: 900
Email address: awsdns-hostmaster.amazon.com
Serial: 1
Refresh: 7200
Retry: 900
Expire: 1209600
Minimum: 86400

Errors
Line: 44 Column: 3 - 126
"...s?</h1> <iframe width="853" height="480" src="https://www.youtube.com/embed/2MsN8gpT6jY?showinfo=0" frameborder="0" allowfullscreen></ifra..."
Line: 102 Column: 5 - 65
".../li> <li id="setup-in-desktop" class="option-newuser image-right"> ..."
Line: 129 Column: 11 - 15
"... <pre>&lt;!D..."
Line: 137 Column: 5 - 9
"...code> </li> ..."
Line: 126 Column: 7 - 28
"...p> <div class="terminal"> ..."
Warnings
Line: 95 Column: 5 - 65
".../li> <li id="setup-in-desktop" class="option-desktop image-right"> ..."

Last tested: 06/05/2017

Desktop
Desktop Speed
56%
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 601.7KiB (39% reduction).

Compressing https://pages.github.com/images/theme-chooser@2x.png could save 127.1KiB (32% reduction).
Compressing https://pages.github.com/images/code-editor@2x.png could save 104.1KiB (45% reduction).
Compressing https://pages.github.com/images/commit-edits@2x.png could save 60.6KiB (40% reduction).
Compressing https://pages.github.com/images/setup-in-desktop@2x.png could save 56.2KiB (33% reduction).
Compressing https://pages.github.com/images/source-setting@2x.png could save 53.7KiB (42% reduction).
Compressing https://pages.github.com/images/new-commit-file@2x.png could save 45.4KiB (41% reduction).
Compressing https://pages.github.com/images/new-create-file@2x.png could save 41.4KiB (37% reduction).
Compressing https://pages.github.com/images/launch-theme-chooser@2x.png could save 40.9KiB (44% reduction).
Compressing https://pages.github.com/images/repo-settings@2x.png could save 36.5KiB (41% reduction).
Compressing https://pages.github.com/images/new-index-html@2x.png could save 35.8KiB (49% reduction).

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.
Leverage browser caching for the following cacheable resources:

https://pages.github.com/css/octicons.woff (10 minutes)
https://pages.github.com/css/pages.css (10 minutes)
https://pages.github.com/images/code-editor@2x.png (10 minutes)
https://pages.github.com/images/commit-edits@2x.png (10 minutes)
https://pages.github.com/images/dashboard@2x.png (10 minutes)
https://pages.github.com/images/download-arrow@2x.png (10 minutes)
https://pages.github.com/images/download@2x.png (10 minutes)
https://pages.github.com/images/ghfm@2x.png (10 minutes)
https://pages.github.com/images/launch-theme-chooser@2x.png (10 minutes)
https://pages.github.com/images/logo.svg (10 minutes)
https://pages.github.com/images/new-commit-file@2x.png (10 minutes)
https://pages.github.com/images/new-create-file@2x.png (10 minutes)
https://pages.github.com/images/new-index-html@2x.png (10 minutes)
https://pages.github.com/images/repo-settings@2x.png (10 minutes)
https://pages.github.com/images/setup-in-desktop@2x.png (10 minutes)
https://pages.github.com/images/slideshow/bootstrap.png (10 minutes)
https://pages.github.com/images/slideshow/facebookdesign.png (10 minutes)
https://pages.github.com/images/slideshow/yeoman.png (10 minutes)
https://pages.github.com/images/source-setting@2x.png (10 minutes)
https://pages.github.com/images/sync-mac.png (10 minutes)
https://pages.github.com/images/sync-windows@2x.png (10 minutes)
https://pages.github.com/images/theme-chooser@2x.png (10 minutes)
https://pages.github.com/images/user-repo@2x.png (10 minutes)
https://pages.github.com/js/application.js (10 minutes)
https://pages.github.com/js/jquery.js (10 minutes)
https://static.doubleclick.net/instream/ad_status.js (15 minutes)
https://www.google-analytics.com/analytics.js (2 hours)

Your page has 2 blocking script resources and 1 blocking CSS resources. This causes a delay in rendering your page.
Remove render-blocking JavaScript:

https://pages.github.com/js/jquery.js
https://pages.github.com/js/application.js

Optimize CSS Delivery of the following:

https://pages.github.com/css/pages.css

Your page requires additional network round trips to render the above-the-fold content. For best performance, reduce the amount of HTML needed to render above-the-fold content.
The entire HTML response was not sufficient to render the above-the-fold content. This usually indicates that additional resources, loaded after HTML parsing, were required to render above-the-fold content. Prioritize visible content that is needed for rendering above-the-fold by including it directly in the HTML response.

Only about 37% of the final above-the-fold content could be rendered with the full HTML response snapshot:3.

Desktop Resource Breakdown
Total Resources39
Number of Hosts9
Static Resources31
JavaScript Resources8
CSS Resources2

Last tested: 05/31/2017

Mobile
Mobile Usability
83%
Your page does not have a viewport specified. This causes mobile devices to render your page as it would appear on a desktop browser, scaling it down to fit on a mobile screen. Configure a viewport to allow your page to render properly on all devices.
The following text on your page renders in a way that may be difficult for some of your visitors to read. Use legible font sizes to provide a better user experience.
The following text fragments have a small font size. Increase the font size to make them more legible.

. Just edit, p…nges are live. and 1 others render only 7 pixels tall (18 CSS pixels) final.
GitHub repository renders only 7 pixels tall (18 CSS pixels) final.
Pages Help renders only 5 pixels tall (12 CSS pixels) final.
Your browser d…ats available. renders only 5 pixels tall (14 CSS pixels) final.
Click here to…t HTML5 video. renders only 5 pixels tall (14 CSS pixels) final.
User or organization site and 1 others render only 6 pixels tall (15 CSS pixels) final.
Project site renders only 6 pixels tall (15 CSS pixels) final.
is your userna…me) on GitHub. and 4 others render only 7 pixels tall (18 CSS pixels).
create a new repository and 1 others render only 7 pixels tall (18 CSS pixels).
username and 1 others render only 7 pixels tall (18 CSS pixels).
If the first p…get it right. renders only 5 pixels tall (14 CSS pixels).
GitHub for Windows and 1 others render only 6 pixels tall (15 CSS pixels).
GitHub for Mac renders only 6 pixels tall (15 CSS pixels).
Go to the fold…ew repository: and 4 others render only 7 pixels tall (18 CSS pixels).
~ and 5 others render only 7 pixels tall (17 CSS pixels).
$ and 5 others render only 7 pixels tall (17 CSS pixels).
echo &quot;Hello Wo…&quot; &gt; index.html and 8 others render only 7 pixels tall (17 CSS pixels).
username and 2 others render only 7 pixels tall (17 CSS pixels).
.github.io and 1 others render only 7 pixels tall (18 CSS pixels).
username renders only 7 pixels tall (18 CSS pixels).
Want to use yo…lude your URL. and 6 others render only 5 pixels tall (14 CSS pixels).
learn more about GitHub Pages and 3 others render only 5 pixels tall (14 CSS pixels).
Training and 9 others render only 5 pixels tall (12 CSS pixels).
© 2017 and 1 others render only 5 pixels tall (12 CSS pixels).
GitHub renders only 5 pixels tall (12 CSS pixels).

Some of the links/buttons on your webpage may be too small for a user to easily tap on a touchscreen. Consider making these tap targets larger to provide a better user experience.
The following tap targets are close to other nearby tap targets and may need additional spacing around them.

The tap target <a href="https://jekyllrb.com">Jekyll</a> is close to 1 other tap targets.
The tap target <a href="https://status.github.com/">Status</a> and 9 others are close to other tap targets.

Mobile Speed
47%
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 601.7KiB (39% reduction).

Compressing https://pages.github.com/images/theme-chooser@2x.png could save 127.1KiB (32% reduction).
Compressing https://pages.github.com/images/code-editor@2x.png could save 104.1KiB (45% reduction).
Compressing https://pages.github.com/images/commit-edits@2x.png could save 60.6KiB (40% reduction).
Compressing https://pages.github.com/images/setup-in-desktop@2x.png could save 56.2KiB (33% reduction).
Compressing https://pages.github.com/images/source-setting@2x.png could save 53.7KiB (42% reduction).
Compressing https://pages.github.com/images/new-commit-file@2x.png could save 45.4KiB (41% reduction).
Compressing https://pages.github.com/images/new-create-file@2x.png could save 41.4KiB (37% reduction).
Compressing https://pages.github.com/images/launch-theme-chooser@2x.png could save 40.9KiB (44% reduction).
Compressing https://pages.github.com/images/repo-settings@2x.png could save 36.5KiB (41% reduction).
Compressing https://pages.github.com/images/new-index-html@2x.png could save 35.8KiB (49% reduction).

Your page has 2 blocking script resources and 1 blocking CSS resources. This causes a delay in rendering your page.
Remove render-blocking JavaScript:

https://pages.github.com/js/jquery.js
https://pages.github.com/js/application.js

Optimize CSS Delivery of the following:

https://pages.github.com/css/pages.css

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.
Leverage browser caching for the following cacheable resources:

https://pages.github.com/css/octicons.woff (10 minutes)
https://pages.github.com/css/pages.css (10 minutes)
https://pages.github.com/images/code-editor@2x.png (10 minutes)
https://pages.github.com/images/commit-edits@2x.png (10 minutes)
https://pages.github.com/images/dashboard@2x.png (10 minutes)
https://pages.github.com/images/download-arrow@2x.png (10 minutes)
https://pages.github.com/images/download@2x.png (10 minutes)
https://pages.github.com/images/ghfm@2x.png (10 minutes)
https://pages.github.com/images/launch-theme-chooser@2x.png (10 minutes)
https://pages.github.com/images/logo.svg (10 minutes)
https://pages.github.com/images/new-commit-file@2x.png (10 minutes)
https://pages.github.com/images/new-create-file@2x.png (10 minutes)
https://pages.github.com/images/new-index-html@2x.png (10 minutes)
https://pages.github.com/images/repo-settings@2x.png (10 minutes)
https://pages.github.com/images/setup-in-desktop@2x.png (10 minutes)
https://pages.github.com/images/slideshow/bootstrap.png (10 minutes)
https://pages.github.com/images/slideshow/facebookdesign.png (10 minutes)
https://pages.github.com/images/slideshow/yeoman.png (10 minutes)
https://pages.github.com/images/source-setting@2x.png (10 minutes)
https://pages.github.com/images/sync-mac.png (10 minutes)
https://pages.github.com/images/sync-windows@2x.png (10 minutes)
https://pages.github.com/images/theme-chooser@2x.png (10 minutes)
https://pages.github.com/images/user-repo@2x.png (10 minutes)
https://pages.github.com/js/application.js (10 minutes)
https://pages.github.com/js/jquery.js (10 minutes)
https://static.doubleclick.net/instream/ad_status.js (15 minutes)
https://www.google-analytics.com/analytics.js (2 hours)

Your page requires additional network round trips to render the above-the-fold content. For best performance, reduce the amount of HTML needed to render above-the-fold content.
The entire HTML response was not sufficient to render the above-the-fold content. This usually indicates that additional resources, loaded after HTML parsing, were required to render above-the-fold content. Prioritize visible content that is needed for rendering above-the-fold by including it directly in the HTML response.

Only about 33% of the final above-the-fold content could be rendered with the full HTML response snapshot:3.

Mobile Resource Breakdown
Total Resources40
Number of Hosts10
Static Resources32
JavaScript Resources8
CSS Resources2