Tools & Wizards About Us

Report Summary

  • 95

    Performance

    Renders faster than
    93% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 84% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

pieterkonink.com

Pieter Konink – A public notebook about nothing in particular.

Page Load Speed

1.5 sec in total

First Response

233 ms

Resources Loaded

1.2 sec

Page Rendered

79 ms

About Website

Click here to check amazing Pieter Konink content. Otherwise, check out these important facts you probably never knew about pieterkonink.com

Explore the sub-degenerate chaos of a middle-aged man child grappling with aging while clinging to his inner child.

Visit pieterkonink.com

Key Findings

We analyzed Pieterkonink.com page load time and found that the first response time was 233 ms and then it took 1.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.

Performance Metrics

pieterkonink.com performance score

95

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.2 s

79/100

10%

LCP (Largest Contentful Paint)

Value2.3 s

92/100

25%

SI (Speed Index)

Value3.1 s

93/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value2.2 s

99/100

10%

Network Requests Diagram

pieterkonink.com

233 ms

pieter.kon.ink

356 ms

style.min.css

259 ms

view.min.js

272 ms

wp-polyfill-importmap.min.js

318 ms

Our browser made a total of 5 requests to load all elements on the main page. We found that 20% of them (1 request) were addressed to the original Pieterkonink.com, 80% (4 requests) were made to Pieter.kon.ink. The less responsive or slowest element that took the longest time to load (356 ms) relates to the external source Pieter.kon.ink.

Page Optimization Overview & Recommendations

Page size can be reduced by 39.2 kB (60%)

Content Size

65.6 kB

After Optimization

26.4 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Pieterkonink.com main page is 65.6 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only a small number of websites need less resources to load. HTML takes 50.0 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 39.2 kB

  • Original 50.0 kB
  • After minification 49.7 kB
  • After compression 10.9 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 39.2 kB or 78% of the original size.

JavaScript Optimization

-0%

Potential reduce by 24 B

  • Original 13.3 kB
  • After minification 13.3 kB
  • After compression 13.3 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. This website has mostly compressed JavaScripts.

CSS Optimization

-1%

Potential reduce by 16 B

  • Original 2.3 kB
  • After minification 2.3 kB
  • After compression 2.3 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Pieterkonink.com has all CSS files already compressed.

Requests Breakdown

We found no issues to fix!

Requests Now

3

After Optimization

3

  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

pieterkonink.com accessibility score

94

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

pieterkonink.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

pieterkonink.com SEO score

100

Search Engine Optimization Advices

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pieterkonink.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Pieterkonink.com main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

Open Graph data is detected on the main page of PARSED_DOMAIN, but there is no image specified in description. It would be a good idea for the website admin to select a nice image that can properly represent the website in Open Graph data, otherwise the first found image will be taken for this purpose and social media information block will look like this: