1.8 sec in total
359 ms
1.3 sec
178 ms
Click here to check amazing Weeghals content. Otherwise, check out these important facts you probably never knew about weeghals.nl
Visit weeghals.nlWe analyzed Weeghals.nl page load time and found that the first response time was 359 ms and then it took 1.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.
weeghals.nl performance score
name
value
score
weighting
Value3.6 s
31/100
10%
Value6.2 s
11/100
25%
Value5.5 s
55/100
10%
Value340 ms
74/100
30%
Value0
100/100
15%
Value4.9 s
78/100
10%
359 ms
263 ms
348 ms
176 ms
265 ms
Our browser made a total of 34 requests to load all elements on the main page. We found that 94% of them (32 requests) were addressed to the original Weeghals.nl, 3% (1 request) were made to Fonts.googleapis.com and 3% (1 request) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (615 ms) belongs to the original domain Weeghals.nl.
Page size can be reduced by 335.1 kB (33%)
1.0 MB
692.4 kB
In fact, the total size of Weeghals.nl main page is 1.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. 30% of websites need less resources to load. Images take 806.4 kB which makes up the majority of the site volume.
Potential reduce by 13.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.3 kB, which is 66% 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 13.9 kB or 89% of the original size.
Potential reduce by 173.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. Obviously, Weeghals needs image optimization as it can save up to 173.2 kB or 21% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 111.0 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 111.0 kB or 68% of the original size.
Potential reduce by 37.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. Weeghals.nl needs all CSS files to be minified and compressed as it can save up to 37.0 kB or 86% of the original size.
Number of requests can be reduced by 10 (31%)
32
22
The browser has sent 32 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Weeghals. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and as a result speed up the page load time.
weeghals.nl
359 ms
style.css
263 ms
jquery.min.js
348 ms
ddsmoothmenu.js
176 ms
cufon-yui.js
265 ms
TitilliumText22L_Rg_400-TitilliumText22L_Rg_700.font.js
265 ms
contentslider.js
177 ms
jcarousellite_1.0.1.js
265 ms
jquery.easing.1.1.js
267 ms
jquery.fancybox-1.3.1.js
363 ms
lightbox.js
362 ms
jquery.infinite-carousel.js
365 ms
css
24 ms
slider.js
370 ms
topbg.jpg
95 ms
logo.png
93 ms
bannerbg.jpg
93 ms
shopnow.png
93 ms
slidebg.png
95 ms
weeghalswww008.jpg
264 ms
banner2.png
615 ms
weeghalswww010.jpg
352 ms
banner1.png
526 ms
leftarrow.png
181 ms
rightarrow1.png
181 ms
slider_left_arrow.png
234 ms
slider_navbg.png
234 ms
slider_right_arrow.png
315 ms
whitebg.jpg
325 ms
contentbg.jpg
325 ms
bottomsecbg.jpg
401 ms
footerlistimg.png
404 ms
slider_hover.png
414 ms
9k-RPmcnxYEPm8CNFsH2gg.woff
10 ms
weeghals.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
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
weeghals.nl 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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
weeghals.nl SEO score
NL
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Weeghals.nl can be misinterpreted by Google and other search engines. Our service has detected that Dutch is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Weeghals.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.
weeghals.nl
Open Graph description is not detected on the main page of Weeghals. 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: