3.1 sec in total
560 ms
2.3 sec
274 ms
Click here to check amazing Jacob Hooy content. Otherwise, check out these important facts you probably never knew about jacob-hooy.com
Gespecialiseerd in kruiden en specerijen. Jacob Hooy beschikt over een zeer groot assortiment van kruiden en specerijen
Visit jacob-hooy.comWe analyzed Jacob-hooy.com page load time and found that the first response time was 560 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
jacob-hooy.com performance score
name
value
score
weighting
Value5.5 s
6/100
10%
Value14.9 s
0/100
25%
Value8.6 s
17/100
10%
Value1,170 ms
21/100
30%
Value0
100/100
15%
Value14.7 s
8/100
10%
560 ms
168 ms
249 ms
751 ms
879 ms
Our browser made a total of 61 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Jacob-hooy.com, 11% (7 requests) were made to Translate.googleapis.com and 5% (3 requests) were made to Gstatic.com. The less responsive or slowest element that took the longest time to load (879 ms) relates to the external source Jacob-hooy.nl.
Page size can be reduced by 370.9 kB (46%)
813.5 kB
442.6 kB
In fact, the total size of Jacob-hooy.com main page is 813.5 kB. 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. Javascripts take 519.4 kB which makes up the majority of the site volume.
Potential reduce by 12.2 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 12.2 kB or 71% of the original size.
Potential reduce by 18.3 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. Jacob Hooy images are well optimized though.
Potential reduce by 316.7 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 316.7 kB or 61% of the original size.
Potential reduce by 23.6 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. Jacob-hooy.com needs all CSS files to be minified and compressed as it can save up to 23.6 kB or 75% of the original size.
Number of requests can be reduced by 31 (52%)
60
29
The browser has sent 60 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Jacob Hooy. 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 7 to 1 for CSS and as a result speed up the page load time.
jacob-hooy.nl
560 ms
style.css
168 ms
fancy.css
249 ms
mootools_1.4.5.js
751 ms
mootools-1.4.0-more.js
879 ms
moofBox-1.0.beta.js
335 ms
tabulator.js
240 ms
element.js
32 ms
header.css
168 ms
middle.css
160 ms
subtemplates.css
247 ms
bottom.css
243 ms
headerBg.jpg
250 ms
headerLogo.jpg
184 ms
headerLoginBg.gif
183 ms
headerLoginInput.gif
87 ms
headerLoginSubmit.gif
86 ms
menuBg.gif
85 ms
menu.gif
415 ms
zoekfunctieInput.gif
184 ms
zoekfunctieSubmit.gif
184 ms
contentBg.gif
249 ms
download.php
254 ms
download.php
258 ms
download.php
259 ms
download.php
334 ms
download.php
502 ms
contentLaatste4BgBottom.gif
326 ms
contentLaatste4BgTop.gif
334 ms
download.php
335 ms
contentLaatste4FotoOverlay.png
405 ms
download.php
496 ms
download.php
503 ms
download.php
424 ms
contentLaatste4LiBottom.gif
484 ms
contentGrootBgBottom.gif
486 ms
contentGrootBgTop.gif
507 ms
download.php
569 ms
fotoHolderOverlay.png
569 ms
textHolderBg.gif
571 ms
download.php
581 ms
contentKleinBgBottom.gif
585 ms
contentKleinBgTop.gif
588 ms
download.php
654 ms
download.php
656 ms
download.php
655 ms
download.php
667 ms
bottomBg.gif
667 ms
translateelement.css
60 ms
main.js
68 ms
ga.js
7 ms
element_main.js
37 ms
__utm.gif
50 ms
translate_24dp.png
30 ms
l
46 ms
googlelogo_color_42x16dp.png
23 ms
googlelogo_color_68x28dp.png
11 ms
cleardot.gif
46 ms
te_ctrl3.gif
13 ms
loading.gif
24 ms
te_bk.gif
10 ms
jacob-hooy.com 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.
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 IDs are not unique
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
<frame> or <iframe> elements do not have a title
Form elements do not have associated labels
Links do not have a discernible name
jacob-hooy.com 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
Missing source maps for large first-party JavaScript
jacob-hooy.com 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
Tap targets are not sized appropriately
NL
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Jacob-hooy.com can be misinterpreted by Google and other search engines. Our service has detected that Dutch is used on the page, and it does not match the claimed English language. Our system also found out that Jacob-hooy.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.
jacob-hooy.com
Open Graph description is not detected on the main page of Jacob Hooy. 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: