Report Summary

  • 92

    Performance

    Renders faster than
    92% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

waarnaartoe.be

Wat zijn de mooiste vakantiebestemmingen in de wereld?

Page Load Speed

1.9 sec in total

First Response

348 ms

Resources Loaded

1.3 sec

Page Rendered

181 ms

waarnaartoe.be screenshot

About Website

Click here to check amazing Waarnaartoe content for Belgium. Otherwise, check out these important facts you probably never knew about waarnaartoe.be

Wil jij op vakantie? Hier lees je over een aantal van de mooiste en fijnste vakantiebestemmingen ter wereld.

Visit waarnaartoe.be

Key Findings

We analyzed Waarnaartoe.be page load time and found that the first response time was 348 ms and then it took 1.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

waarnaartoe.be performance score

92

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.4 s

70/100

10%

LCP (Largest Contentful Paint)

Value2.8 s

83/100

25%

SI (Speed Index)

Value2.9 s

95/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value2.4 s

98/100

10%

Network Requests Diagram

waarnaartoe.be

348 ms

waarnaartoe.be

350 ms

bootstrap.min.css

288 ms

style.css

336 ms

font-awesome.css

35 ms

Our browser made a total of 13 requests to load all elements on the main page. We found that 92% of them (12 requests) were addressed to the original Waarnaartoe.be, 8% (1 request) were made to Netdna.bootstrapcdn.com. The less responsive or slowest element that took the longest time to load (621 ms) belongs to the original domain Waarnaartoe.be.

Page Optimization Overview & Recommendations

Page size can be reduced by 22.9 kB (52%)

Content Size

44.0 kB

After Optimization

21.1 kB

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

HTML Optimization

-79%

Potential reduce by 22.8 kB

  • Original 28.7 kB
  • After minification 18.6 kB
  • After compression 5.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. This page needs HTML code to be minified as it can gain 10.1 kB, which is 35% 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 22.8 kB or 79% of the original size.

Image Optimization

-0%

Potential reduce by 66 B

  • Original 15.3 kB
  • After minification 15.2 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. Waarnaartoe images are well optimized though.

Requests Breakdown

We found no issues to fix!

Requests Now

11

After Optimization

11

The browser has sent 11 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Waarnaartoe. According to our analytics all requests are already optimized.

Accessibility Review

waarnaartoe.be accessibility score

85

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.

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

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

waarnaartoe.be best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

waarnaartoe.be SEO score

100

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

Language and Encoding

  • Language Detected

    NL

  • Language Claimed

    EN

  • Encoding

    UTF-8

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