6.5 sec in total
965 ms
5.3 sec
243 ms
Click here to check amazing Prins Wijn content. Otherwise, check out these important facts you probably never knew about prinswijn.nl
Prins Wijn - Gespecialiseerde Wijnhandel Den Haag. Jouw bijzondere wijnwinkel voor witte wijn, rode wijn, rosé, Champagne. Persoonlijk Wijnadvies. Wijnproeverijen.
Visit prinswijn.nlWe analyzed Prinswijn.nl page load time and found that the first response time was 965 ms and then it took 5.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
prinswijn.nl performance score
name
value
score
weighting
Value4.8 s
12/100
10%
Value9.9 s
1/100
25%
Value10.5 s
8/100
10%
Value860 ms
34/100
30%
Value0.161
73/100
15%
Value12.7 s
14/100
10%
965 ms
519 ms
268 ms
658 ms
245 ms
Our browser made a total of 76 requests to load all elements on the main page. We found that 89% of them (68 requests) were addressed to the original Prinswijn.nl, 3% (2 requests) were made to Facebook.com and 3% (2 requests) were made to Staticxx.facebook.com. The less responsive or slowest element that took the longest time to load (2.9 sec) belongs to the original domain Prinswijn.nl.
Page size can be reduced by 304.9 kB (13%)
2.3 MB
2.0 MB
In fact, the total size of Prinswijn.nl main page is 2.3 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. 25% of websites need less resources to load. Images take 1.9 MB which makes up the majority of the site volume.
Potential reduce by 20.6 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 20.6 kB or 76% of the original size.
Potential reduce by 14.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. Prins Wijn images are well optimized though.
Potential reduce by 186.6 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 186.6 kB or 68% of the original size.
Potential reduce by 83.5 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. Prinswijn.nl needs all CSS files to be minified and compressed as it can save up to 83.5 kB or 82% of the original size.
Number of requests can be reduced by 43 (58%)
74
31
The browser has sent 74 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Prins Wijn. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and from 25 to 1 for CSS and as a result speed up the page load time.
prinswijn.nl
965 ms
widgetkit-bd795161.css
519 ms
nsb.css
268 ms
mootools.js
658 ms
caption.js
245 ms
jquery.js
695 ms
widgetkit-98984b99.js
415 ms
all.js
269 ms
base.css
443 ms
layout.css
444 ms
menus.css
599 ms
modules.css
610 ms
tools.css
611 ms
system.css
735 ms
extensions.css
768 ms
custom.css
789 ms
red.css
821 ms
chunkfive.css
881 ms
chunkfive.css
923 ms
style.css
857 ms
print.css
900 ms
chunkfive.css
947 ms
warp.js
982 ms
accordionmenu.js
995 ms
dropdownmenu.js
1018 ms
template.js
1034 ms
search.js
1084 ms
base.css
484 ms
layout.css
519 ms
menus.css
520 ms
modules.css
532 ms
tools.css
561 ms
system.css
612 ms
system.css
714 ms
system-all.css
697 ms
lightbox.js
855 ms
mediaelement-and-player.js
911 ms
spotlight.js
776 ms
26 ms
print.css
547 ms
prinswijn_pms342_normal.png
123 ms
toolbar.png
290 ms
searchbox.png
289 ms
facebook_aqu_32.png
549 ms
twitter_aqu_32.png
743 ms
google_aqu_32.png
766 ms
logoPrinsWijn.gif
362 ms
home_app01.png
967 ms
home_app02.png
980 ms
home_app03.png
951 ms
home_app04.png
967 ms
home_app05.png
1075 ms
home_app06.png
1191 ms
home_app07.png
1287 ms
home_app08.png
1398 ms
home_app09.png
1399 ms
home_app10.png
1398 ms
home_app11.png
1492 ms
home_app12.png
1693 ms
favico.gif
1502 ms
header_bg.jpg
2274 ms
header.jpg
2905 ms
menu_dropdown_active.png
1612 ms
nav.png
1711 ms
xd_arbiter.php
215 ms
xd_arbiter.php
419 ms
main.jpg
1623 ms
arrow.png
1777 ms
footer.png
1792 ms
totop_scroller.png
1805 ms
searchbox_results.png
1830 ms
Chunkfive-webfont.woff
1961 ms
slideset.js
1988 ms
like.php
91 ms
qeKvIRsJabD.js
494 ms
LVx-xkvaJ0b.png
555 ms
prinswijn.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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
prinswijn.nl best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
prinswijn.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 Prinswijn.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 Prinswijn.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.
prinswijn.nl
Open Graph description is not detected on the main page of Prins Wijn. 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: