Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

wtf.nl

Opmerkelijk | NU - Het laatste nieuws het eerst op NU.nl

Page Load Speed

8.5 sec in total

First Response

807 ms

Resources Loaded

7.1 sec

Page Rendered

618 ms

wtf.nl screenshot

About Website

Click here to check amazing Wtf content for Netherlands. Otherwise, check out these important facts you probably never knew about wtf.nl

Visit wtf.nl

Key Findings

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

Performance Metrics

wtf.nl performance score

0

Network Requests Diagram

www.wtf.nl

807 ms

8fd6990c722a.css

262 ms

5309502130ec.js

355 ms

625 ms

ac5232e3513b.js

311 ms

Our browser made a total of 139 requests to load all elements on the main page. We found that 14% of them (20 requests) were addressed to the original Wtf.nl, 51% (71 requests) were made to Bin.snmmd.nl and 7% (10 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.6 sec) relates to the external source Bin.snmmd.nl.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.1 MB (44%)

Content Size

2.6 MB

After Optimization

1.4 MB

In fact, the total size of Wtf.nl main page is 2.6 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. 55% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 238.6 kB

  • Original 268.5 kB
  • After minification 195.4 kB
  • After compression 30.0 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. This page needs HTML code to be minified as it can gain 73.1 kB, which is 27% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 238.6 kB or 89% of the original size.

Image Optimization

-4%

Potential reduce by 41.3 kB

  • Original 1.1 MB
  • After minification 1.1 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. Wtf images are well optimized though.

JavaScript Optimization

-70%

Potential reduce by 699.7 kB

  • Original 1.0 MB
  • After minification 1.0 MB
  • After compression 307.0 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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 699.7 kB or 70% of the original size.

CSS Optimization

-85%

Potential reduce by 166.3 kB

  • Original 195.5 kB
  • After minification 193.4 kB
  • After compression 29.2 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. Wtf.nl needs all CSS files to be minified and compressed as it can save up to 166.3 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 40 (31%)

Requests Now

129

After Optimization

89

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

SEO Factors

wtf.nl SEO score

0

Language and Encoding

  • Language Detected

    NL

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wtf.nl can be misinterpreted by Google and other search engines. Our service has detected that Dutch is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Wtf.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 description is not detected on the main page of Wtf. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: