5.9 sec in total
898 ms
4.7 sec
374 ms
Welcome to vitstore.com homepage info - get ready to check Vitstore best content for Netherlands right away, or after learning these important things about vitstore.com
Vitalize is dé specialist op het gebied van voedingssupplementen, vitamines en mineralen. Producten van hoogwaardige kwaliteit voor de beste prijzen.
Visit vitstore.comWe analyzed Vitstore.com page load time and found that the first response time was 898 ms and then it took 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.
vitstore.com performance score
name
value
score
weighting
Value3.8 s
28/100
10%
Value7.1 s
5/100
25%
Value10.7 s
7/100
10%
Value1,490 ms
14/100
30%
Value0
100/100
15%
Value20.3 s
2/100
10%
898 ms
374 ms
435 ms
184 ms
359 ms
Our browser made a total of 160 requests to load all elements on the main page. We found that 90% of them (144 requests) were addressed to the original Vitstore.com, 3% (4 requests) were made to Bekendbij.postnl.nl and 3% (4 requests) were made to Bat.bing.com. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Vitstore.com.
Page size can be reduced by 1.3 MB (28%)
4.6 MB
3.3 MB
In fact, the total size of Vitstore.com main page is 4.6 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. 60% of websites need less resources to load. Images take 3.1 MB which makes up the majority of the site volume.
Potential reduce by 905.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. This page needs HTML code to be minified as it can gain 458.3 kB, which is 47% 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 905.7 kB or 94% of the original size.
Potential reduce by 202.1 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. Vitstore images are well optimized though.
Potential reduce by 5.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. This website has mostly compressed JavaScripts.
Potential reduce by 164.7 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. Vitstore.com needs all CSS files to be minified and compressed as it can save up to 164.7 kB or 89% of the original size.
Number of requests can be reduced by 136 (86%)
159
23
The browser has sent 159 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Vitstore. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 137 to 1 for JavaScripts and as a result speed up the page load time.
www.vitstore.com
898 ms
6075c27d4c15397848e1aa519e0a3c9b.min.css
374 ms
all.css
435 ms
require.min.js
184 ms
requirejs-min-resolver.min.js
359 ms
mixins.min.js
359 ms
requirejs-config.min.js
359 ms
ec.min.js
359 ms
ec4.min.js
387 ms
main.min.js
387 ms
optimize.js
46 ms
deobfuscator.min.js
404 ms
v2
33 ms
instant.min.js
401 ms
gtm.js
118 ms
retrieve-widget.html
447 ms
2024_Homepage_3Luik_banners_Links2.png
402 ms
2024_juli_Homepage_3Luik_banners_Midden.png
589 ms
2024_juli_Homepage_3Luik_banners_Rechts.png
313 ms
Yoran.png
135 ms
hotjar-386959.js
106 ms
sqzl.js
159 ms
bat.js
53 ms
common.min.js
104 ms
dataPost.min.js
104 ms
bootstrap.min.js
155 ms
form-key-provider.min.js
197 ms
app.min.js
196 ms
mage-translation-dictionary.min.js
246 ms
webpimages.min.js
286 ms
lazysizes.min.js
287 ms
responsive.min.js
328 ms
theme.min.js
337 ms
translate.min.js
378 ms
storage-wrapper.min.js
379 ms
mage.min.js
414 ms
jquery.min.js
419 ms
5222170.js
11 ms
5222170
217 ms
modules.6c69b5997f314810cfe8.js
12 ms
domReady.min.js
337 ms
template.min.js
372 ms
confirm.min.js
373 ms
widget.min.js
410 ms
jquery-mixin.min.js
413 ms
aHR0cHM6Ly93d3cudml0c3RvcmUuY29tL21lZGlhL2Jhbm5lcnMvMjAyNF9Ib21lcGFnZV9iYW5uZXJfSnVuaV9GdWxsV2l0aDEucG5n.png
972 ms
aHR0cHM6Ly93d3cudml0c3RvcmUuY29tL21lZGlhL2Jhbm5lcnMvMjAyNF9Ib21lcGFnZV9iYW5uZXJfSnVuaV9EZXNrdG9wMy5wbmc.png
1004 ms
aHR0cHM6Ly93d3cudml0c3RvcmUuY29tL3N0YXRpYy92ZXJzaW9uMjAyNDA3MTUwODA1NTYvZnJvbnRlbmQvVml0c3RvcmUvZGVmYXVsdC9ubF9OTC9pbWFnZXMvbG9nby5zdmc.svg
433 ms
aHR0cHM6Ly93d3cudml0c3RvcmUuY29tL21lZGlhL3d5c2l3eWcvY29udGFjdF9wYWdpbmFfaWNvbmVuMi5wbmc.png
469 ms
aHR0cHM6Ly93d3cudml0c3RvcmUuY29tL21lZGlhL3d5c2l3eWcvY29udGFjdF9wYWdpbmFfaWNvbmVuLnBuZw.png
468 ms
aHR0cHM6Ly93d3cudml0c3RvcmUuY29tL21lZGlhL3d5c2l3eWcvZm9vdGVyX2JldGFhbGljb25lbi5wbmc.png
473 ms
394f97d55f1f2cf8c900.js
24 ms
main.min.js
512 ms
bootstrap.min.js
548 ms
types.min.js
501 ms
layout.min.js
505 ms
aHR0cHM6Ly93d3cudml0c3RvcmUuY29tL21lZGlhL3d5c2l3eWcvY29udGFjdF9wYWdpbmFfaWNvbmVuNC5wbmc.png
589 ms
text.min.js
579 ms
0.7.41
60 ms
modernizr-webp.min.js
534 ms
tabs.min.js
495 ms
matchMedia.min.js
516 ms
smart-keyboard-handler.min.js
578 ms
style.css
374 ms
widget.js
272 ms
35f5bc6c
13 ms
underscore.min.js
536 ms
js.storage.min.js
536 ms
magebirdpopup.php
664 ms
modal.min.js
536 ms
version.min.js
496 ms
wrapper.min.js
502 ms
scripts.min.js
439 ms
knockout.min.js
412 ms
knockout-es5.min.js
413 ms
main.min.js
495 ms
registry.min.js
492 ms
engine.min.js
494 ms
bootstrap.min.js
496 ms
observable_array.min.js
501 ms
bound-nodes.min.js
517 ms
console-logger.min.js
581 ms
logo-postnl-outline.svg
93 ms
tabs.min.js
463 ms
collapsible.min.js
469 ms
js-translation.json
468 ms
jquery.cookie.min.js
374 ms
modal-popup.html
302 ms
modal-slide.html
369 ms
modal-custom.html
370 ms
key-codes.min.js
371 ms
core.min.js
372 ms
z-index.min.js
375 ms
validation.min.js
290 ms
knockout-repeat.min.js
273 ms
knockout-fast-foreach.min.js
274 ms
arrays.min.js
274 ms
compare.min.js
277 ms
misc.min.js
277 ms
objects.min.js
298 ms
strings.min.js
367 ms
template.min.js
365 ms
observable_source.min.js
365 ms
renderer.min.js
371 ms
resizable.min.js
372 ms
i18n.min.js
388 ms
scope.min.js
456 ms
range.min.js
455 ms
mage-init.min.js
455 ms
keyboard.min.js
458 ms
optgroup.min.js
459 ms
after-render.min.js
479 ms
autoselect.min.js
545 ms
datepicker.min.js
546 ms
outer_click.min.js
546 ms
fadeVisible.min.js
549 ms
collapsible.min.js
549 ms
staticChecked.min.js
564 ms
simple-checked.min.js
564 ms
bind-html.min.js
564 ms
tooltip.min.js
561 ms
color-picker.min.js
563 ms
events.min.js
563 ms
local.min.js
564 ms
logger.min.js
562 ms
entry-factory.min.js
564 ms
console-output-handler.min.js
563 ms
formatter.min.js
563 ms
message-pool.min.js
562 ms
levels-pool.min.js
563 ms
logger-utils.min.js
563 ms
keycode.min.js
563 ms
safe-active-element.min.js
560 ms
unique-id.min.js
563 ms
cookie-wrapper.min.js
562 ms
data.min.js
564 ms
disable-selection.min.js
563 ms
focusable.min.js
562 ms
form.min.js
560 ms
ie.min.js
562 ms
labels.min.js
559 ms
jquery-patch.min.js
563 ms
plugin.min.js
564 ms
safe-blur.min.js
563 ms
scroll-parent.min.js
562 ms
tabbable.min.js
565 ms
validation.min.js
564 ms
class.min.js
563 ms
async.min.js
564 ms
loader.min.js
565 ms
tooltip.html
466 ms
spectrum.min.js
468 ms
tinycolor.min.js
472 ms
moment.min.js
396 ms
entry.min.js
462 ms
js.cookie.min.js
369 ms
jquery.validate.min.js
181 ms
dom-observer.min.js
95 ms
bindings.min.js
96 ms
jquery.metadata.min.js
95 ms
vitstore.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
[role]s do not have all required [aria-*] attributes
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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
vitstore.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
Issues were logged in the Issues panel in Chrome Devtools
vitstore.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 Vitstore.com 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 Vitstore.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.
vitstore.com
Open Graph description is not detected on the main page of Vitstore. 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: