Nibbler SEO audit for roine.github.io

Overall7.1

The overall score for this website.

Accessibility9.2

How accessible the website is to mobile and disabled users.

The following tests contribute to this score:

Experience5.9

How satisfying the website is likely to be for users.

The following tests contribute to this score:

Marketing3.4

How well marketed, and popular the website is.

The following tests contribute to this score:

Technology8.4

How well designed and built the website is.

The following tests contribute to this score:

Nibbler tested a sample of 5 pages from this website at 00:04 on 11 Apr 2024 (BST).

Want white-label SEO audits to share with your clients?

Top priorities for website improvement

  • Consider a leading website analytics solution, such as WebTrends or Google Analytics. (read more)
  • Consider updating this website regularly with new content. (read more)
  • Consider the amount of text on this website and increase it if appropriate. (read more)

Twitter0.0

Help

This website does not appear to be associated with a Twitter account.

  • This website did not contain a link to Twitter.
    • Sign up for a Twitter account and make sure it is linked to from your site.

Analytics0.0

Help

0% of pages use analytics

No Analytics SolutionNo

  • None of this website is using any recognised analytics software. It is still possible to gather a great deal of information from webserver logs, however complete visitor analysis requires client-side Javascript or an image not found here.
    • Consider a leading website analytics solution, such as WebTrends or Google Analytics.
  • Note that this test can only detect recognised analytics solutions. If an analytics solution is new, obscure or used in a non-standard way (e.g. it has been customised) it may not be detected.

Printability0.0

Help

0% of pages are optimised for printing

Media specific CSS detected

Freshness0.4

Help

Last updated March 22, 2019

  • It looks like this website was last updated on Friday, 22 March 2019. This is bad because visitors may dismiss this website as outdated. Websites that are not updated regularly are also spidered by search engines less often.
    • Consider updating this website regularly with new content.
  • To find this information we used the last modified dates reported by this website's server in addition to looking for dates written on each page.

All dates found

DateFileSource
24/01/2019roine.github.io/Body text
23/01/2019roine.github.io/Body text
17/01/2019roine.github.io/Body text
20/12/2018roine.github.io/Body text
04/09/2018roine.github.io/Body text
26/08/2018roine.github.io/Body text
22/08/2018roine.github.io/Body text
15/08/2018roine.github.io/Body text
13/08/2018roine.github.io/Body text
22/03/2019roine.github.io/Last modified header
22/03/2019roine.github.io/about/Last modified header
24/01/2019roine.github.io/.../keep-same-url-in-now-sh.htmlBody text
22/03/2019roine.github.io/.../keep-same-url-in-now-sh.htmlLast modified header
24/01/2019roine.github.io/tag/tilBody text
23/01/2019roine.github.io/tag/tilBody text
17/01/2019roine.github.io/tag/tilBody text
20/12/2018roine.github.io/tag/tilBody text
22/03/2019roine.github.io/tag/tilLast modified header
22/03/2019roine.github.io/.../shell-calendar.pngLast modified header
22/03/2019roine.github.io/.../elm-debug-format.pngLast modified header
22/03/2019roine.github.io/assets/main.cssLast modified header
22/03/2019roine.github.io/assets/syntax.cssLast modified header

Amount of content4.9

Help

Rendering Chart...

  • This website has an average of 260 words per page. The amount of content on a website has been shown to correlate with its search engine ranking.
    • Consider the amount of text on this website and increase it if appropriate.
  • 2 pages of this website have very little content (20 words or less).
    • Ensure all pages have a sufficient amount of content.

Amount of content discovered

Server behaviour7.4

Help

Yes404 page

YesCompression

  • This website handles missing pages correctly by sending a 404 HTTP status code.
  • This website was served with GZIP encoding. This is very good because it reduces the loading time of a web page.
  • One page of this website follows the best practice of using a permanent (HTTP 301) redirect between its URL with/without a trailing slash. This page is ideal.
  • Adding or removing a trailing slash to 2 of the URLs of this site returns an error page (404). This is OK as no content is being duplicated, but visitors might try browsing to the pages of this website with or without a trailing slash. Ideally, the alternate URL should redirect to the correct page.
  • There was no website found on http://www.roine.github.io. This is bad, as visitors might presume they can visit this website by visiting that address.
    • Put a permanent (HTTP 301) redirect to http://roine.github.io on http://www.roine.github.io.

URL format7.6

Help

  • 2 URLs include a file extension.
    • Avoid use of file extensions wherever possible. File extensions appear at the end of web addresses, and have several negative effects. They make the address harder to remember or type (particularly for non-technical users), and can reveal the underlying technology of the website making it very slightly more vulnerable to hackers. They also tie the implementation of the website to a specific technology, which can make subsequent migration of URLs difficult. Consider URL rewriting as an effective and transparent means of creating appropriate URLs.

      Page extensions

Mobile8.6

Help

Mobile screenshot of roine.github.ioTablet screenshot of roine.github.io
  • All of this website appears to be optimised for viewing on a mobile phone (using CSS media queries) but it is not optimised for tablet viewing. It is important to make sure your content is optimised for a wide range of devices as a growing percentage of web browsing is done on phones and tablets.

Media specific CSS detected

Headings9.0

Help

alias argument browser building calendar command common ditched element empty errors file format fragment hash it's javascript keep kind last list message model parsing part pretty previous react requires return reuse roine same shell solved some timestamp touch update wrap

  • All pages were found to use defined headings. This is excellent as it allows visitors and search engines to summarise the content of webpages quickly. Correctly defined headings aid accessibility and are particularly important for search engine optimisation.
  • Some pages did not define headings correctly. The H1 tag should be used for the most top-level heading, with H2 being used for sub-headings and H3 for further sub-headings and so-on. Not conforming to this convention may confuse visitors.
    • Ensure that headings are defined in a semantically correct way, i.e. always start with a H1 tag. This is used to summarise the page content. Further tags (H2, H3, H4 etc) are meant to summarise and partition sections within the content.

Page headings detail

URLHeadingLevel
roine.github.io/Wrap with an elementH2
roine.github.io/Return a list (requires a key)H2
roine.github.io/Use Fragment (16.2.0+)H2
roine.github.io/Use empty tag (some kind of alias for Fragment)H2
roine.github.io/RoineH2
roine.github.io/Keep same URL in now.shH3
roine.github.io/touch to update a file timestampH3
roine.github.io/Pretty format ELM model in browserH3
roine.github.io/Empty Tag in ReactH3
roine.github.io/Reuse last argument from previous commandH3
roine.github.io/Calendar in shellH3
roine.github.io/MessageH3
roine.github.io/Building a calendar UI in ELM - Part 2H3
roine.github.io/Building a calendar UI in ELM - Part 1H3
roine.github.io/How to use hash parsing in ELM 0.19H3
roine.github.io/Common errors in Javascript and how it's solved in ELMH3
roine.github.io/Why I ditched JS for ELMH3
roine.github.io/about/AboutH1
roine.github.io/about/RoineH2
roine.github.io/.../keep-same-url-in-now-sh.htmlKeep same URL in now.shH1
roine.github.io/.../keep-same-url-in-now-sh.htmlRoineH2
roine.github.io/tag/now.sh404H1
roine.github.io/tag/now.shRoineH2
roine.github.io/tag/tilTag: tilH1
roine.github.io/tag/tilWrap with an elementH2
roine.github.io/tag/tilReturn a list (requires a key)H2
roine.github.io/tag/tilUse Fragment (16.2.0+)H2
roine.github.io/tag/tilUse empty tag (some kind of alias for Fragment)H2
roine.github.io/tag/tilRoineH2
roine.github.io/tag/tilKeep same URL in now.shH3
roine.github.io/tag/tiltouch to update a file timestampH3
roine.github.io/tag/tilPretty format ELM model in browserH3
roine.github.io/tag/tilEmpty Tag in ReactH3
roine.github.io/tag/tilReuse last argument from previous commandH3
roine.github.io/tag/tilCalendar in shellH3

Internal links9.6

Help

Page titles10.0

Help

100% of pages have defined titles

0% of page titles are weak

  • All pages were found to use page titles appropriately. Page titles appear in search results and at the top of the browser's window when visiting the site. Appropriate page titles are particularly important for search engine optimisation.

Page titles

Images10.0

Help

0% of images have a clearly defined size

No images are being resized by the browser

Meta tags10.0

Help

This is how this website will look in Google search listings:

Roine | Tech blog

roine.github.io/

Tech blog

  • All pages were found to include a meta description. This is good because search engines (like Google) show this text in search result pages.

Meta Tags (name attribute)

Page URLNameContent
roine.github.io/viewportwidth=device-width, initial-scale=1
roine.github.io/generatorJekyll v3.7.4
roine.github.io/descriptionTech blog
roine.github.io/about/viewportwidth=device-width, initial-scale=1
roine.github.io/about/generatorJekyll v3.7.4
roine.github.io/about/descriptionTech blog
roine.github.io/.../keep-same-url-in-now-sh.htmlviewportwidth=device-width, initial-scale=1
roine.github.io/.../keep-same-url-in-now-sh.htmlgeneratorJekyll v3.7.4
roine.github.io/.../keep-same-url-in-now-sh.htmldescriptionIn the world of static file hosting there are plenty of solutions. I picked now.sh. It’s free, easy to use and works well. I have had one problem with now.sh so far, it creates a new URL everytime you push. It’s a feature that I dont need in some cases, here’s how to solve. Put this in package.json: { "scripts": { "deploy": "now && now alias && now remove YOUR_APP_NAME --safe -y" } } Replace YOUR_APP_NAME by the name of your app. Then go to your now.json and add/change: "name": "YOUR_APP_NAME", "alias": "YOUR_UNIQUE_SUBDOMAIN.now.sh", Replace YOUR_UNIQUE_SUBDOMAIN by your unique subdomain. Just run yarn deploy.
roine.github.io/tag/now.shviewportwidth=device-width, initial-scale=1
roine.github.io/tag/now.shgeneratorJekyll v3.7.4
roine.github.io/tag/now.shdescriptionTech blog
roine.github.io/tag/tilviewportwidth=device-width, initial-scale=1
roine.github.io/tag/tilgeneratorJekyll v3.7.4
roine.github.io/tag/tildescriptionTech blog

Meta Tags (http-equiv attribute)

Page URLNameContent
roine.github.io/X-UA-CompatibleIE=edge
roine.github.io/about/X-UA-CompatibleIE=edge
roine.github.io/.../keep-same-url-in-now-sh.htmlX-UA-CompatibleIE=edge
roine.github.io/tag/now.shX-UA-CompatibleIE=edge
roine.github.io/tag/tilX-UA-CompatibleIE=edge

Popularityi

Help

  • Sorry, it was not possible to determine the popularity for this website.

Source: Ahrefs

Domain agei

Help

  • Sorry, we cannot check the domain age of .github.io websites.

Fast, branded website audits

Insites creates professional website reports that can be shared with your clients.

How does Insites compare?

Tests 17 fixed tests 50+ testsCovers SEO, SEM, Google My Business, reviews, social media and much more
Add your brandingNoYes
Export & shareNoPDF & link
Lead generationNoEmbed on your site
Competitor auditsNoYes
Test as a batchNoYes
Integrations + APINoYes
Multi-lingualNo20+ languages
Try it free