Tools & Wizards About Us
freddejonge.nl screenshot

Report Summary

  • 15

    Performance

    Renders faster than
    27% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 74% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

freddejonge.nl

Fred de Jonge | Technical Blog | Solutions I found and share.

Page Load Speed

2.3 sec in total

First Response

228 ms

Resources Loaded

1.8 sec

Page Rendered

222 ms

freddejonge.nl screenshot

About Website

Visit freddejonge.nl now to see the best up-to-date Fred De Jonge content and also check out these interesting facts you probably never knew about freddejonge.nl

My personal tech blog to help other who walk into similar problems and help them towards their solution.

Visit freddejonge.nl

Key Findings

We analyzed Freddejonge.nl page load time and found that the first response time was 228 ms and then it took 2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

freddejonge.nl performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.5 s

14/100

10%

LCP (Largest Contentful Paint)

Value4.5 s

36/100

25%

SI (Speed Index)

Value8.9 s

15/100

10%

TBT (Total Blocking Time)

Value3,600 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.535

14/100

15%

TTI (Time to Interactive)

Value16.2 s

6/100

10%

Network Requests Diagram

freddejonge.nl

228 ms

freddejonge.nl

739 ms

uc.js

21 ms

style.min.css

487 ms

style.min.css

46 ms

Our browser made a total of 38 requests to load all elements on the main page. We found that 39% of them (15 requests) were addressed to the original Freddejonge.nl, 29% (11 requests) were made to C0.wp.com and 8% (3 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (739 ms) belongs to the original domain Freddejonge.nl.

Page Optimization Overview & Recommendations

Page size can be reduced by 234.3 kB (26%)

Content Size

907.6 kB

After Optimization

673.3 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Freddejonge.nl main page is 907.6 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 30% of websites need less resources to load. Javascripts take 639.9 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 123.5 kB

  • Original 151.0 kB
  • After minification 146.8 kB
  • After compression 27.5 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 123.5 kB or 82% of the original size.

JavaScript Optimization

-7%

Potential reduce by 45.4 kB

  • Original 639.9 kB
  • After minification 639.9 kB
  • After compression 594.5 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

-56%

Potential reduce by 65.4 kB

  • Original 116.7 kB
  • After minification 116.0 kB
  • After compression 51.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. Freddejonge.nl needs all CSS files to be minified and compressed as it can save up to 65.4 kB or 56% of the original size.

Requests Breakdown

Number of requests can be reduced by 30 (86%)

Requests Now

35

After Optimization

5

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 35 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fred De Jonge. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

freddejonge.nl

freddejonge.nl

228 ms

freddejonge.nl

freddejonge.nl

739 ms

uc.js

uc.js

21 ms

style.min.css

style.min.css

487 ms

style.min.css

style.min.css

46 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

50 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

54 ms

styles.css

styles.css

203 ms

contact-form-7-main.min.css

contact-form-7-main.min.css

296 ms

pagenavi-css.css

pagenavi-css.css

306 ms

jetpack.css

jetpack.css

53 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

52 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

53 ms

wp-polyfill.min.js

wp-polyfill.min.js

58 ms

hooks.min.js

hooks.min.js

53 ms

i18n.min.js

i18n.min.js

57 ms

i18n-loader.js

i18n-loader.js

309 ms

adsbygoogle.js

adsbygoogle.js

176 ms

adsbygoogle.js

adsbygoogle.js

135 ms

astra-widget-social-profiles.min.css

astra-widget-social-profiles.min.css

212 ms

style.min.js

style.min.js

212 ms

image-cdn.js

image-cdn.js

412 ms

index.js

index.js

411 ms

index.js

index.js

411 ms

url.min.js

url.min.js

2 ms

jp-search.js

jp-search.js

412 ms

w.js

w.js

29 ms

api.js

api.js

56 ms

index.js

index.js

411 ms

e-202410.js

e-202410.js

28 ms

google-translate.min.js

google-translate.min.js

12 ms

element.js

element.js

61 ms

show_ads_impl.js

show_ads_impl.js

442 ms

zrt_lookup_nohtml.html

zrt_lookup_nohtml.html

41 ms

astra.woff

astra.woff

105 ms

g.gif

g.gif

19 ms

recaptcha__en.js

recaptcha__en.js

28 ms

g.gif

g.gif

12 ms

Accessibility Review

freddejonge.nl accessibility score

90

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

<frame> or <iframe> elements do not have a title

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

freddejonge.nl 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

High

Page has valid source maps

SEO Factors

freddejonge.nl SEO score

99

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

High

Tap targets are not sized appropriately

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 Freddejonge.nl 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 Freddejonge.nl 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

freddejonge.nl

Open Graph data is detected on the main page of Fred De Jonge. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: