Report Summary

  • 27

    Performance

    Renders faster than
    46% of other websites

  • 67

    Accessibility

    Visual factors better than
    that of 32% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

npogeschiedenis.nl

Home - Andere Tijden

Page Load Speed

3.6 sec in total

First Response

333 ms

Resources Loaded

2.7 sec

Page Rendered

559 ms

npogeschiedenis.nl screenshot

About Website

Visit npogeschiedenis.nl now to see the best up-to-date Npogeschiedenis content for Netherlands and also check out these interesting facts you probably never knew about npogeschiedenis.nl

Andere Tijden, het geschiedenisprogramma van de NTR en VPRO met reportages over (bijna) vergeten gebeurtenissen uit de recente geschiedenis.

Visit npogeschiedenis.nl

Key Findings

We analyzed Npogeschiedenis.nl page load time and found that the first response time was 333 ms and then it took 3.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

npogeschiedenis.nl performance score

27

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value9.6 s

0/100

10%

LCP (Largest Contentful Paint)

Value13.8 s

0/100

25%

SI (Speed Index)

Value9.6 s

11/100

10%

TBT (Total Blocking Time)

Value900 ms

31/100

30%

CLS (Cumulative Layout Shift)

Value0.018

100/100

15%

TTI (Time to Interactive)

Value13.6 s

11/100

10%

Network Requests Diagram

npogeschiedenis.nl

333 ms

433 ms

anderetijden.nl

231 ms

jquery.min.js

23 ms

piano-analytics.js

19 ms

Our browser made a total of 55 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Npogeschiedenis.nl, 75% (41 requests) were made to Anderetijden.nl and 11% (6 requests) were made to Images.poms.omroep.nl. The less responsive or slowest element that took the longest time to load (761 ms) relates to the external source Anderetijden.nl.

Page Optimization Overview & Recommendations

Page size can be reduced by 144.8 kB (7%)

Content Size

2.2 MB

After Optimization

2.0 MB

In fact, the total size of Npogeschiedenis.nl main page is 2.2 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 40% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 45.6 kB

  • Original 54.3 kB
  • After minification 49.4 kB
  • After compression 8.7 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 45.6 kB or 84% of the original size.

Image Optimization

-7%

Potential reduce by 77.4 kB

  • Original 1.1 MB
  • After minification 1.0 MB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Npogeschiedenis images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 8.2 kB

  • Original 972.5 kB
  • After minification 972.5 kB
  • After compression 964.2 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

-22%

Potential reduce by 13.6 kB

  • Original 62.1 kB
  • After minification 62.1 kB
  • After compression 48.4 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. Npogeschiedenis.nl needs all CSS files to be minified and compressed as it can save up to 13.6 kB or 22% of the original size.

Requests Breakdown

Number of requests can be reduced by 7 (15%)

Requests Now

47

After Optimization

40

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

Accessibility Review

npogeschiedenis.nl accessibility score

67

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.

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

Form elements do not have associated labels

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

npogeschiedenis.nl best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

npogeschiedenis.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

    NL

  • Language Claimed

    NL

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Npogeschiedenis.nl can be misinterpreted by Google and other search engines. Our service has detected that Dutch is used on the page, and it matches the claimed language. Our system also found out that Npogeschiedenis.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

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