Report for mkolarek.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:

Experience6.6

How satisfying the website is likely to be for users.

Marketing2.7

How well marketed, and popular the website is.

Technology8.4

How well designed and built the website is.

Screenshot of mkolarek.github.io

Nibbler tested a sample of 4 pages from this website at 13:35 on 11 Jun 2021 (BST).

Want branded website audits to share with your clients? Learn More

Top priorities for website improvement

  • Consider a leading website analytics solution, such as WebTrends or Google Analytics. (read more)
  • To appear higher in search engine results, consider link building activity as a way to build your search ranking. Be careful though, because incoming links which are obviously artificial are likely to be detected by search engines and could have an adverse effect. (read more)
  • Sign up for a Twitter account and make sure it is linked to from your site. (read more)

Twitter0.0

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

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

0% of pages are optimised for printing

Popularity0.0

  • This website has not yet been ranked by Alexa.
    • If this website is new, this is probably normal. Drive traffic to the website to get an Alexa ranking.

Source: Alexa

Amount of content6.0

Rendering Chart...

  • This website has an average of 160 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.

Amount of content discovered

Server behaviour7.6

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.
  • 2 of the pages of this website follow the best practice of using a permanent (HTTP 301) redirect between URLs with/without trailing slashes. These pages are ideal.
  • There was no website found on http://www.mkolarek.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://mkolarek.github.io on http://www.mkolarek.github.io.

URL format8.5

  • 1 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

Mobile screenshot of mkolarek.github.ioTablet screenshot of mkolarek.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.

Headings8.8

curriculum education experience github mkolarek posts vitae welcome

  • 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

Page titles10.0

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.

Images10.0

100% of images have a clearly defined size

No images are being resized by the browser

  • All images have defined sizes using width and height attributes in the HTML. These attributes are optional, but strongly recommended as they help the browser arrange the page more quickly.

Meta tags10.0

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

mkolarek.github.io | Personal web page of Marko Kolarek.

mkolarek.github.io/

Personal web page of Marko Kolarek.

  • 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
mkolarek.github.io/viewportwidth=device-width, initial-scale=1
mkolarek.github.io/generatorJekyll v3.9.0
mkolarek.github.io/authorMarko Kolarek
mkolarek.github.io/descriptionPersonal web page of Marko Kolarek.
mkolarek.github.io/twitter:cardsummary
mkolarek.github.io/cv/viewportwidth=device-width, initial-scale=1
mkolarek.github.io/cv/generatorJekyll v3.9.0
mkolarek.github.io/cv/authorMarko Kolarek
mkolarek.github.io/cv/descriptionPersonal web page of Marko Kolarek.
mkolarek.github.io/cv/twitter:cardsummary
mkolarek.github.io/about/viewportwidth=device-width, initial-scale=1
mkolarek.github.io/about/generatorJekyll v3.9.0
mkolarek.github.io/about/authorMarko Kolarek
mkolarek.github.io/about/descriptionPersonal web page of Marko Kolarek.
mkolarek.github.io/about/twitter:cardsummary
mkolarek.github.io/.../welcome.htmlviewportwidth=device-width, initial-scale=1
mkolarek.github.io/.../welcome.htmlgeneratorJekyll v3.9.0
mkolarek.github.io/.../welcome.htmlauthorMarko Kolarek
mkolarek.github.io/.../welcome.htmldescriptionHi everyone and welcome (once again) to my personal web page. If you’ve been here before, this is another reset (probably something like the 5th one), but I intend it to be the last one.
mkolarek.github.io/.../welcome.htmltwitter:cardsummary

Meta Tags (http-equiv attribute)

Page URLNameContent
mkolarek.github.io/X-UA-CompatibleIE=edge
mkolarek.github.io/cv/X-UA-CompatibleIE=edge
mkolarek.github.io/about/X-UA-CompatibleIE=edge
mkolarek.github.io/.../welcome.htmlX-UA-CompatibleIE=edge

Freshness10.0

Last updated May 24, 2021

  • It looks like this website was last updated on Monday, 24 May 2021. This is good because visitors perceive up-to-date websites as more credible. Websites that are updated regularly are also spidered by search engines more often.
  • 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
13/05/2021mkolarek.github.io/Body text
24/05/2021mkolarek.github.io/Last modified header
01/11/2020mkolarek.github.io/cv/Body text
01/03/2019mkolarek.github.io/cv/Body text
01/10/2020mkolarek.github.io/cv/Body text
01/10/2018mkolarek.github.io/cv/Body text
01/01/2019mkolarek.github.io/cv/Body text
01/02/2018mkolarek.github.io/cv/Body text
01/09/2018mkolarek.github.io/cv/Body text
01/07/2016mkolarek.github.io/cv/Body text
01/01/2018mkolarek.github.io/cv/Body text
01/09/2015mkolarek.github.io/cv/Body text
01/06/2016mkolarek.github.io/cv/Body text
01/07/2014mkolarek.github.io/cv/Body text
01/06/2015mkolarek.github.io/cv/Body text
01/07/2013mkolarek.github.io/cv/Body text
01/08/2013mkolarek.github.io/cv/Body text
01/09/2012mkolarek.github.io/cv/Body text
01/06/2014mkolarek.github.io/cv/Body text
01/09/2008mkolarek.github.io/cv/Body text
01/06/2012mkolarek.github.io/cv/Body text
24/05/2021mkolarek.github.io/cv/Last modified header
24/05/2021mkolarek.github.io/about/Last modified header
13/05/2021mkolarek.github.io/.../welcome.htmlBody text
24/05/2021mkolarek.github.io/.../welcome.htmlLast modified header
24/05/2021mkolarek.github.io/assets/main.cssLast modified header

Domain agei

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

Fast, branded website audits

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

How does Silktide Prospect 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