Tools & Wizards About Us
duinrell.com screenshot

Report Summary

  • 22

    Performance

    Renders faster than
    40% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

duinrell.com

Duinrell Holland - Holiday park and amusement park

Page Load Speed

4.3 sec in total

First Response

214 ms

Resources Loaded

3.2 sec

Page Rendered

841 ms

duinrell.com screenshot

About Website

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

Enjoy fun and relaxation for the whole family! Holiday Park, Amusement Park and Waterpark. Perfectly located near the beach and popular cities.

Visit duinrell.com

Key Findings

We analyzed Duinrell.com page load time and found that the first response time was 214 ms and then it took 4.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

duinrell.com performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

27/100

10%

LCP (Largest Contentful Paint)

Value4.7 s

33/100

25%

SI (Speed Index)

Value8.5 s

17/100

10%

TBT (Total Blocking Time)

Value1,420 ms

15/100

30%

CLS (Cumulative Layout Shift)

Value0.423

23/100

15%

TTI (Time to Interactive)

Value14.0 s

10/100

10%

Network Requests Diagram

duinrell.com

214 ms

duinrell.com

300 ms

www.duinrell.com

531 ms

main_style.css

309 ms

style.css

418 ms

Our browser made a total of 56 requests to load all elements on the main page. We found that 84% of them (47 requests) were addressed to the original Duinrell.com, 4% (2 requests) were made to Plugins.flockler.com and 4% (2 requests) were made to Piwik.easyhandling.nl. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Duinrell.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 208.3 kB (9%)

Content Size

2.4 MB

After Optimization

2.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Duinrell.com main page is 2.4 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. Images take 2.0 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 93.6 kB

  • Original 113.4 kB
  • After minification 107.3 kB
  • After compression 19.8 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 93.6 kB or 83% of the original size.

Image Optimization

-6%

Potential reduce by 114.2 kB

  • Original 2.0 MB
  • After minification 1.9 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. Duinrell images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 277 B

  • Original 186.2 kB
  • After minification 186.2 kB
  • After compression 185.9 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

-0%

Potential reduce by 266 B

  • Original 65.7 kB
  • After minification 65.7 kB
  • After compression 65.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. Duinrell.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 21 (43%)

Requests Now

49

After Optimization

28

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

duinrell.com

duinrell.com

214 ms

duinrell.com

duinrell.com

300 ms

www.duinrell.com

www.duinrell.com

531 ms

main_style.css

main_style.css

309 ms

style.css

style.css

418 ms

conversion.js

conversion.js

87 ms

layer-usps.css

layer-usps.css

415 ms

banners.css

banners.css

412 ms

photo-banner2.css

photo-banner2.css

285 ms

photo-banner1.css

photo-banner1.css

426 ms

KdnRa2

KdnRa2

35 ms

170687d126603f0c53ff7ec6f9505c8a

170687d126603f0c53ff7ec6f9505c8a

119 ms

layer-blog.css

layer-blog.css

490 ms

layer-kiyoh.css

layer-kiyoh.css

523 ms

email-decode.min.js

email-decode.min.js

322 ms

jquery-3.1.1.min.js

jquery-3.1.1.min.js

889 ms

script.js

script.js

888 ms

style.css

style.css

332 ms

piwik.js

piwik.js

886 ms

gtm.js

gtm.js

172 ms

121 ms

logo-duinrell-wassenaar-en.svg

logo-duinrell-wassenaar-en.svg

622 ms

Overnachten%20menu%20banner%20EN.png

Overnachten%20menu%20banner%20EN.png

622 ms

Attractiepark%20menu%20banner%20COM.png

Attractiepark%20menu%20banner%20COM.png

677 ms

Tikipool%20banner%20COM%20.png

Tikipool%20banner%20COM%20.png

674 ms

Ontdek%20duinrell%20menu%20banner%20COM-%282%29.png

Ontdek%20duinrell%20menu%20banner%20COM-%282%29.png

678 ms

vlag-rond-en01.svg

vlag-rond-en01.svg

673 ms

vlag-rond-nl01.svg

vlag-rond-nl01.svg

679 ms

vlag-rond-de01.svg

vlag-rond-de01.svg

674 ms

Icon_earlybook.png

Icon_earlybook.png

920 ms

Premium%20Plus%20Duingalow%20800x533.jpg

Premium%20Plus%20Duingalow%20800x533.jpg

932 ms

Tikibad%20buiten%20fotobanner.jpg

Tikibad%20buiten%20fotobanner.jpg

936 ms

Attracties1.jpg

Attracties1.jpg

921 ms

Ontwerp%20zonder%20titel%20%2832%29.png

Ontwerp%20zonder%20titel%20%2832%29.png

929 ms

Fotobanner%20-%20ontdek%20park%20-%201920x540.jpg

Fotobanner%20-%20ontdek%20park%20-%201920x540.jpg

938 ms

icoontjes%20social.png

icoontjes%20social.png

1222 ms

Amsterdam%20weekend%20weg%20-%20tegel.jpg

Amsterdam%20weekend%20weg%20-%20tegel.jpg

1211 ms

Met%20deze%20tips%20haal%20je%20alles%20uit%20je%20vakantie%201200x800.jpg

Met%20deze%20tips%20haal%20je%20alles%20uit%20je%20vakantie%201200x800.jpg

1234 ms

2%20%281%29.png

2%20%281%29.png

1231 ms

NEW%20Duinrell%20Horizon%20v5_Duinrell%20Horizon%202020%20%5Bnatuur%20-%20kust%20-%20omgeving%5D-%282%29.jpg

NEW%20Duinrell%20Horizon%20v5_Duinrell%20Horizon%202020%20%5Bnatuur%20-%20kust%20-%20omgeving%5D-%282%29.jpg

1227 ms

image.png

image.png

1218 ms

image.png

image.png

1506 ms

Duingalow.png

Duingalow.png

1519 ms

Strand.png

Strand.png

1510 ms

Weer.png

Weer.png

1523 ms

vlag-nl01.svg

vlag-nl01.svg

1524 ms

vlag-en01.svg

vlag-en01.svg

1488 ms

vlag-de01.svg

vlag-de01.svg

1750 ms

rick.svg

rick.svg

1751 ms

sequel-neue-webfont.woff

sequel-neue-webfont.woff

1766 ms

sequel-light-webfont.woff

sequel-light-webfont.woff

1843 ms

embed-carousel_v2.js

embed-carousel_v2.js

17 ms

icons.ttf

icons.ttf

1478 ms

27 ms

kiyoh.png

kiyoh.png

1544 ms

piwik.php

piwik.php

235 ms

Accessibility Review

duinrell.com accessibility score

76

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

ARIA input fields do not have accessible names

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

duinrell.com 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

SEO Factors

duinrell.com SEO score

77

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

duinrell.com

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