Access whoznext.nl. whoznext.nl - This website is for sale!

name

value

score

weighting

FCP (First Contentful Paint)

Value2.1 s

81/100

10%

LCP (Largest Contentful Paint)

Value2.1 s

96/100

25%

SI (Speed Index)

Value4.8 s

66/100

10%

TBT (Total Blocking Time)

Value1,580 ms

12/100

30%

CLS (Cumulative Layout Shift)

Value0.23

54/100

15%

TTI (Time to Interactive)

Value5.4 s

72/100

10%

2277 ms

pt-sans-narrow:n7,n4:all;pt-sans:n4,n7,i4:all.js

119 ms

jquery.min.js

6 ms

wp-modal-login.css

990 ms

default.css

1007 ms

Our browser made a total of 40 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Whoznext.nl, 18% (7 requests) were made to Webfonts.creativecloud.com and 3% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (2.3 sec) relates to the external source Huisvoorbeweging.nl.

Content Size

530.8 kB

After Optimization

270.3 kB

In fact, the total size of Whoznext.nl main page is 530.8 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. 35% of websites need less resources to load. Images take 196.8 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 38.4 kB

Original 49.3 kB
After minification 48.0 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 38.4 kB or 78% of the original size.

Image Optimization

-5%

Potential reduce by 9.3 kB

Original 196.8 kB
After minification 187.5 kB

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. Whoznext images are well optimized though.

JavaScript Optimization

-71%

Potential reduce by 132.9 kB

Original 186.5 kB
After minification 171.9 kB
After compression 53.6 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 132.9 kB or 71% of the original size.

CSS Optimization

-81%

Potential reduce by 79.8 kB

Original 98.2 kB
After minification 79.2 kB
After compression 18.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. Whoznext.nl needs all CSS files to be minified and compressed as it can save up to 79.8 kB or 81% of the original size.

Requests Now

After Optimization

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

Accessibility Issues

These are opportunities to improve the legibility of your content.

High

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

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.

High

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

These items highlight common accessibility best practices.

High

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

Areas of Improvement

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

High

Issues were logged in the Issues panel in Chrome Devtools

Search Engine Optimization Advices

To appear in search results, crawlers need access to your app.

High

Page is blocked from indexing

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/).

High

Document doesn't use legible font sizes

Language and Encoding

Language Detected

EN
Language Claimed

NL
Encoding

UTF-8

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

whoznext.nl

Open Graph description is not detected on the main page of Whoznext. 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:

Report Summary

Performance

Accessibility

Best Practices

SEO

whoznext.nl - This website is for sale! - whoznext Resources and Information.

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram