5.5 sec in total
1.4 sec
3.9 sec
150 ms
Visit dateq.nl now to see the best up-to-date DATEQ content and also check out these interesting facts you probably never knew about dateq.nl
Visit dateq.nlWe analyzed Dateq.nl page load time and found that the first response time was 1.4 sec and then it took 4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
dateq.nl performance score
name
value
score
weighting
Value7.4 s
1/100
10%
Value7.9 s
3/100
25%
Value10.5 s
8/100
10%
Value940 ms
30/100
30%
Value0.076
95/100
15%
Value12.9 s
13/100
10%
1442 ms
172 ms
186 ms
186 ms
261 ms
Our browser made a total of 41 requests to load all elements on the main page. We found that 93% of them (38 requests) were addressed to the original Dateq.nl, 5% (2 requests) were made to Fonts.gstatic.com and 2% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Dateq.nl.
Page size can be reduced by 389.5 kB (36%)
1.1 MB
701.2 kB
In fact, the total size of Dateq.nl main page is 1.1 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. 35% of websites need less resources to load. Images take 600.2 kB which makes up the majority of the site volume.
Potential reduce by 17.7 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 17.7 kB or 78% of the original size.
Potential reduce by 6.8 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. DATEQ images are well optimized though.
Potential reduce by 132.1 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.1 kB or 67% of the original size.
Potential reduce by 233.0 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. Dateq.nl needs all CSS files to be minified and compressed as it can save up to 233.0 kB or 86% of the original size.
Number of requests can be reduced by 28 (74%)
38
10
The browser has sent 38 CSS, Javascripts, AJAX and image requests in order to completely render the main page of DATEQ. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
www.dateq.nl
1442 ms
language-selector.css
172 ms
styles.css
186 ms
woocommerce-layout.css
186 ms
woocommerce.css
261 ms
layout.css
187 ms
style.css
434 ms
layout.css
257 ms
woocommerce.css
345 ms
prettyPhoto.css
348 ms
jquery.js
522 ms
jquery-migrate.min.js
344 ms
third-party.js
347 ms
general.js
431 ms
jquery.flexslider-min.js
444 ms
featured-slider.js
445 ms
testimonials.js
444 ms
css
24 ms
default.css
517 ms
shortcodes.css
517 ms
custom.css
518 ms
jquery.form.min.js
493 ms
scripts.js
495 ms
add-to-cart.min.js
526 ms
jquery.blockUI.min.js
527 ms
woocommerce.min.js
528 ms
jquery.cookie.min.js
529 ms
cart-fragments.min.js
528 ms
sitepress.js
530 ms
wp-emoji-release.min.js
514 ms
background.png
145 ms
logo2.png
164 ms
ico-search.png
166 ms
tess_banner1.jpg
232 ms
ONDERDELEN-002_980x300.png
579 ms
DE-TROTS-VAN-DATEQ_980x300-.png
702 ms
v0SdcGFAl2aezM9Vq_aFTQ.ttf
5 ms
zJY4gsxBiSo5L7tNutxFNg.ttf
8 ms
www.dateq.nl
694 ms
woocommerce-smallscreen.css
89 ms
bg_direction_nav.png
89 ms
dateq.nl accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Links do not have a discernible name
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.
dateq.nl best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
dateq.nl SEO score
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
NL
NL
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Dateq.nl 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 Dateq.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.
dateq.nl
Open Graph description is not detected on the main page of DATEQ. 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: