10.8 sec in total
387 ms
9.7 sec
740 ms
Click here to check amazing Jacob Hooy content. Otherwise, check out these important facts you probably never knew about jacob-hooy.com
Sinds 1743 bekend om zijn kruiden en specerijen. Jacob Hooy is begonnen met een kruidenkraam op de Amsterdamse Nieuwmarkt.
Visit jacob-hooy.comWe analyzed Jacob-hooy.com page load time and found that the first response time was 387 ms and then it took 10.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
jacob-hooy.com performance score
name
value
score
weighting
Value8.9 s
0/100
10%
Value25.5 s
0/100
25%
Value21.1 s
0/100
10%
Value190 ms
90/100
30%
Value0.001
100/100
15%
Value23.1 s
1/100
10%
387 ms
474 ms
3163 ms
49 ms
52 ms
Our browser made a total of 54 requests to load all elements on the main page. We found that 4% of them (2 requests) were addressed to the original Jacob-hooy.com, 85% (46 requests) were made to Jacob-hooy.nl and 6% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (3.2 sec) relates to the external source Jacob-hooy.nl.
Page size can be reduced by 900.0 kB (10%)
8.7 MB
7.8 MB
In fact, the total size of Jacob-hooy.com main page is 8.7 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. 55% of websites need less resources to load. Images take 8.4 MB which makes up the majority of the site volume.
Potential reduce by 47.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 8.0 kB, which is 14% 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 47.9 kB or 84% of the original size.
Potential reduce by 799.5 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 51.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 51.6 kB or 31% of the original size.
Potential reduce by 1.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. Jacob-hooy.com has all CSS files already compressed.
Number of requests can be reduced by 26 (58%)
45
19
The browser has sent 45 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 17 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
jacob-hooy.com
387 ms
www.jacob-hooy.com
474 ms
jacob-hooy.nl
3163 ms
css2
49 ms
tiny-slider.css
52 ms
6ec2c24286.js
77 ms
style.min.css
100 ms
jacob-hooy-blocks-public.css
194 ms
stekkit-blocks-public.css
254 ms
woocommerce-layout.css
264 ms
woocommerce.css
273 ms
app.css
466 ms
tiny-slider.css
284 ms
awdr_style.css
286 ms
jquery.min.js
447 ms
jquery-migrate.min.js
361 ms
jacob-hooy-blocks-public.js
367 ms
stekkit-blocks-public.js
378 ms
jquery.blockUI.min.js
383 ms
add-to-cart.min.js
449 ms
js.cookie.min.js
457 ms
woocommerce.min.js
618 ms
site_main.js
617 ms
awdr-dynamic-price.js
618 ms
what-input.js
618 ms
foundation.js
758 ms
tiny-slider.js
620 ms
jquery.selectBox.js
620 ms
app.js
620 ms
awdr_pro.js
625 ms
35216-Yerba-Mate.jpg
704 ms
logo.jpg
206 ms
35344-Gember-theezkj-500x500.jpg
152 ms
jacob-hooy-nasikruiden-grof-10510-500x446.jpg
284 ms
1_110_1_1_1_1_1_1_1_1_1_1_1_1_1_1_1_1_1_1_1_1_1_1_1_1_1_1_1_1_1_1_1_1_1_1_2_1_1_1_1_1_1_1_1_1_1_1_1_1_1_1_1_1_1_1_1_1_1_1-500x333.jpg
284 ms
jacob-hooy-passiekruid-21580-500x465.jpg
322 ms
image-2.jpg
576 ms
image-3.jpg
585 ms
image-4.jpg
688 ms
image-5.jpg
680 ms
image-6.jpg
795 ms
00011-Haarlemmer-bruin-gezichts-50-ml-SPF-30-500x500.jpg
667 ms
thumbnail_PHOTO-2023-04-03-12-29-36-500x375.jpg
679 ms
Aantekening-2024-01-22-145912-500x219.jpg
758 ms
70730-Kruidnagel-500x500.jpg
788 ms
image-footer.jpg
945 ms
logo-white.jpg
781 ms
S6uyw4BMUTPHvxk.ttf
32 ms
S6u9w4BMUTPHh7USew8.ttf
63 ms
S6u9w4BMUTPHh6UVew8.ttf
64 ms
fa-brands-400.woff
725 ms
fa-light-300.woff
777 ms
fa-regular-400.woff
821 ms
woocommerce-smallscreen.css
96 ms
jacob-hooy.com 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-*] attributes do not match their roles
[aria-hidden="true"] elements contain focusable descendents
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
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.
jacob-hooy.com 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
Page has valid source maps
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
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 data is detected on the main page of Jacob Hooy. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: