Access vakantietop20.be. VakantieVeilingen.nl | Veilingsite met de leukste online veilingen

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

73/100

10%

LCP (Largest Contentful Paint)

Value2.7 s

84/100

25%

SI (Speed Index)

Value5.8 s

50/100

10%

TBT (Total Blocking Time)

Value5,720 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.003

100/100

15%

TTI (Time to Interactive)

Value16.7 s

5/100

10%

www.vakantieveilingen.nl

1251 ms

410c78b29b0050e6.css

26 ms

polyfills-c67a75d1b6f99dc8.js

44 ms

webpack-c2b3c555cf65dff7.js

25 ms

framework-314c182fa7e2bf37.js

44 ms

Our browser made a total of 47 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Vakantietop20.be, 38% (18 requests) were made to Images.emesa-static.com. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Vakantieveilingen.nl.

Content Size

1.2 MB

After Optimization

481.6 kB

In fact, the total size of Vakantietop20.be main page is 1.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. 70% of websites need less resources to load. HTML takes 775.0 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 647.2 kB

Original 775.0 kB
After minification 775.0 kB
After compression 127.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 647.2 kB or 84% of the original size.

Image Optimization

-7%

Potential reduce by 26.3 kB

Original 380.0 kB
After minification 353.7 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. Vakantie Top20 images are well optimized though.

Requests Now

After Optimization

The browser has sent 46 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Vakantie Top20. 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 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 keyboard navigation in your application.

High

Heading elements are not in a sequentially-descending order

Areas of Improvement

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

Search Engine Optimization Advices

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

High

Links are not crawlable

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 uses legible font sizes

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 Vakantietop20.be 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 Vakantietop20.be 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 Vakantie Top20. 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: