4 sec in total
458 ms
3.2 sec
308 ms
Click here to check amazing Duinrell content for Germany. Otherwise, check out these important facts you probably never knew about duinrell.de
Ferienpark und Campingplatz an der Küste. Mit mehr als 40 Attraktionen und dem Tikibad-Wasserpark gibt es für Jung und Alt viel zu tun und zu erleben!
Visit duinrell.deWe analyzed Duinrell.de page load time and found that the first response time was 458 ms and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
duinrell.de performance score
name
value
score
weighting
Value2.2 s
78/100
10%
Value10.3 s
0/100
25%
Value8.5 s
18/100
10%
Value2,790 ms
3/100
30%
Value0.499
16/100
15%
Value13.9 s
10/100
10%
458 ms
263 ms
606 ms
533 ms
176 ms
Our browser made a total of 60 requests to load all elements on the main page. We found that 88% of them (53 requests) were addressed to the original Duinrell.de, 3% (2 requests) were made to Dev.visualwebsiteoptimizer.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Duinrell.de.
Page size can be reduced by 773.2 kB (26%)
3.0 MB
2.2 MB
In fact, the total size of Duinrell.de main page is 3.0 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. 40% of websites need less resources to load. Images take 2.1 MB which makes up the majority of the site volume.
Potential reduce by 176.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 176.8 kB or 93% of the original size.
Potential reduce by 44.0 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. Duinrell images are well optimized though.
Potential reduce by 376.5 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 376.5 kB or 70% of the original size.
Potential reduce by 175.9 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.de needs all CSS files to be minified and compressed as it can save up to 175.9 kB or 89% of the original size.
Number of requests can be reduced by 7 (12%)
58
51
The browser has sent 58 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 8 to 1 for JavaScripts and as a result speed up the page load time.
www.duinrell.de
458 ms
global.php
263 ms
jquery.js
606 ms
complete_js.php
533 ms
jquery.cookie.js
176 ms
jquery.cookiecuttr.js
179 ms
cookiecuttr.css
179 ms
ga-settings.js
281 ms
conversion.js
14 ms
j.php
7 ms
ga.js
58 ms
yellowBg.gif
96 ms
logo.png
95 ms
yellowMenu.png
215 ms
redMenu.png
94 ms
blueMenu.png
175 ms
lgreenMenu.png
173 ms
dgreenMenu.png
255 ms
greyMenu.png
173 ms
nl.gif
175 ms
de.gif
261 ms
en.gif
259 ms
e8bdd463f38672d6b818157ee3b41601.png
945 ms
0ffe263a9c94103a1208d997c2b189e8.png
1020 ms
9369ad1480eec123e205db39de78dffc.png
1017 ms
6052796e211c9c33321d65b420440466.png
1015 ms
64936db5b516f0537a53d6f57f7ef222.jpg
600 ms
fa199f04ec85dcf3b2b84d6e416c8249.jpg
511 ms
6e79cb0c7471f3bbcff01ca76dafc153.jpg
680 ms
b6152a83dba489318ecb52a6b7adc021.jpg
687 ms
e4fd00440bbb44e2f91a7c7a195fcd31.jpg
767 ms
e82f72e9904ad713442f349e666794df.jpg
775 ms
6f96223868d917be8c916103945425f8.jpg
853 ms
f5db184ffcadc9299685ca46d6a6e5c9.jpg
862 ms
251351b1b1ff651a2ccab0fc505d0aca.jpg
940 ms
brochure-de.png
1034 ms
facebook-18x18.png
1025 ms
v.gif
41 ms
yellowSubmit.png
1022 ms
boekBg.png
1092 ms
553bf5ef09675bb96145fae227661fa0.jpg
1053 ms
boekSubmit.png
1057 ms
__utm.gif
78 ms
rondje-rood01.png
1027 ms
rondje-wit01.png
1033 ms
rondje-blauw01.png
1036 ms
rondje-dgroen01.png
1102 ms
rondje-groen01.png
1103 ms
smallBg.png
1106 ms
rondknop01.png
1110 ms
mediumBg.png
1119 ms
virtueel-rondkijken02_01.png
1117 ms
74 ms
virtueel-rondkijken02_02.png
1524 ms
virtueel-rondkijken02_03.png
1109 ms
parkBox-top.png
1112 ms
arrow.png
1114 ms
30 ms
footerBg.gif
1087 ms
ui-bg_highlight-soft_100_eeeeee_1x100.png
1047 ms
duinrell.de accessibility score
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
[aria-hidden="true"] elements contain focusable descendents
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
duinrell.de best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
duinrell.de SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
robots.txt is not valid
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
Document uses legible font sizes
Tap targets are not sized appropriately
DE
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Duinrell.de can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it does not match the claimed English language. Our system also found out that Duinrell.de 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.
duinrell.de
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: