9.4 sec in total
2.7 sec
5.9 sec
740 ms
Click here to check amazing HVO Querido content for Netherlands. Otherwise, check out these important facts you probably never knew about hvoquerido.nl
HVO-Querido ondersteunt mensen in een kwetsbare situatie om opnieuw de regie over hun eigen leven te krijgen en deel uit te maken van de samenleving.
Visit hvoquerido.nlWe analyzed Hvoquerido.nl page load time and found that the first response time was 2.7 sec and then it took 6.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
hvoquerido.nl performance score
name
value
score
weighting
Value9.2 s
0/100
10%
Value27.9 s
0/100
25%
Value23.5 s
0/100
10%
Value16,450 ms
0/100
30%
Value0.383
27/100
15%
Value36.2 s
0/100
10%
2712 ms
27 ms
157 ms
253 ms
172 ms
Our browser made a total of 155 requests to load all elements on the main page. We found that 95% of them (147 requests) were addressed to the original Hvoquerido.nl, 3% (4 requests) were made to Fonts.gstatic.com and 1% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.7 sec) belongs to the original domain Hvoquerido.nl.
Page size can be reduced by 1.2 MB (13%)
8.8 MB
7.6 MB
In fact, the total size of Hvoquerido.nl main page is 8.8 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 7.4 MB which makes up the majority of the site volume.
Potential reduce by 92.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. 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 92.9 kB or 87% of the original size.
Potential reduce by 104.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. HVO Querido images are well optimized though.
Potential reduce by 606.2 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 606.2 kB or 73% of the original size.
Potential reduce by 373.9 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. Hvoquerido.nl needs all CSS files to be minified and compressed as it can save up to 373.9 kB or 85% of the original size.
Number of requests can be reduced by 109 (75%)
145
36
The browser has sent 145 CSS, Javascripts, AJAX and image requests in order to completely render the main page of HVO Querido. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 82 to 1 for JavaScripts and from 29 to 1 for CSS and as a result speed up the page load time.
hvoquerido.nl
2712 ms
css
27 ms
reset.css
157 ms
bootstrap.css
253 ms
bootstrap-responsive.css
172 ms
entypo-icon-font.css
168 ms
style.css
173 ms
jquery.pixelentity.background.css
173 ms
isotope.css
238 ms
jquery.pixelentity.isotope.css
250 ms
jquery.pixelentity.carousel.css
264 ms
jquery.pixelentity.ajaxportfolio.css
264 ms
common.css
266 ms
vario-transitions.css
321 ms
common.css
336 ms
skin.css
333 ms
slider_ui.css
337 ms
animate.min.css
339 ms
slider_captions.css
340 ms
slider_captions_style.css
404 ms
menu.css
415 ms
menu_style.css
417 ms
style.css
498 ms
style_responsive.css
421 ms
style.css
417 ms
styles.css
485 ms
events_manager.css
504 ms
fonts.css
507 ms
tablepress-combined.min.css
506 ms
jquery.js
656 ms
jquery-migrate.min.js
580 ms
jquery.debouncedresize.js
581 ms
core.min.js
581 ms
widget.min.js
583 ms
position.min.js
582 ms
mouse.min.js
663 ms
js
87 ms
sortable.min.js
612 ms
datepicker.min.js
527 ms
menu.min.js
510 ms
autocomplete.min.js
511 ms
resizable.min.js
578 ms
draggable.min.js
586 ms
button.min.js
522 ms
dialog.min.js
501 ms
events-manager.js
503 ms
KmlMapParser.js
584 ms
wp-emoji-release.min.js
569 ms
comment-reply.min.js
575 ms
boot.js
521 ms
jquery.mobile.custom.min.js
513 ms
jquery.pixelentity.utils.browser.js
511 ms
jquery.pixelentity.menu.js
579 ms
jquery.smoothscroll.js
583 ms
waypoints.js
585 ms
jquery.parallax-1.1.3.js
527 ms
jquery.mb.YTPlayer.js
624 ms
style.css
512 ms
jquery.pixelentity.lazyload.js
621 ms
jquery.pixelentity.loadmore.js
619 ms
jquery.theme.utils.js
562 ms
jquery.mousewheel.js
539 ms
jquery.pixelentity.utils.geom.js
536 ms
jquery.pixelentity.utils.preloader.js
536 ms
jquery.pixelentity.utils.transition.js
605 ms
jquery.pixelentity.transform.js
606 ms
jquery.pixelentity.utils.youtube.js
533 ms
froogaloop.js
533 ms
jquery.pixelentity.utils.vimeo.js
532 ms
jquery.pixelentity.video.js
533 ms
jquery.pixelentity.videoPlayer.js
584 ms
jquery.pixelentity.utils.ticker.js
545 ms
jquery.pixelentity.backgroundSlider.js
537 ms
jquery.pixelentity.flare.lightbox.js
535 ms
jquery.pixelentity.simplethumb.js
531 ms
jquery.pixelentity.flare.lightbox.render.gallery.js
533 ms
jquery.pixelentity.flare.lightbox.render.image.js
594 ms
jquery.pixelentity.volo.js
526 ms
jquery.pixelentity.volo.simpleskin.js
522 ms
jquery.pixelentity.volo.captions.js
521 ms
jquery.pixelentity.vario.js
517 ms
jquery.pixelentity.vista.js
525 ms
bootstrap.min.js
511 ms
jquery.pixelentity.widgets.js
514 ms
jquery.pixelentity.widgets.bslinks.js
519 ms
jquery.pixelentity.contactForm.js
516 ms
jquery.pixelentity.widgets.contact.js
517 ms
jquery.pixelentity.widgets.bootstrap.js
522 ms
jquery.isotope.min.js
511 ms
jquery.pixelentity.isotope.js
596 ms
jquery.pixelentity.widgets.isotope.js
596 ms
jquery.pixelentity.widgets.backgroundSlider.js
560 ms
jquery.pixelentity.widgets.volo.js
481 ms
jquery.pixelentity.widgets.carousel.js
482 ms
jquery.pixelentity.newsletter.js
483 ms
jquery.pixelentity.widgets.newsletter.js
481 ms
jquery.pixelentity.widgets.gmap.js
485 ms
jquery.pixelentity.widgets.dynamicBackground.js
486 ms
jquery.pixelentity.widgets.social.facebook.js
485 ms
jquery.pixelentity.widgets.social.twitter.js
488 ms
jquery.pixelentity.widgets.social.pinterest.js
484 ms
jquery.pixelentity.widgets.social.google.js
488 ms
jquery.pixelentity.scroll.js
497 ms
jquery.pixelentity.ajaxportfolio.js
499 ms
jquery.pixelentity.widgets.ajaxportfolio.js
494 ms
u-WUoqrET9fUeobQW7jkRaCWcynf_cDxXwCLxiixG1c.ttf
42 ms
DXI1ORHCpsQm3Vp6mXoaTdqQynqKV_9Plp7mupa0S4g.ttf
72 ms
MTP_ySUJH_bn48VBG8sNStqQynqKV_9Plp7mupa0S4g.ttf
74 ms
k3k702ZOKiLJc3WVjuplzNqQynqKV_9Plp7mupa0S4g.ttf
104 ms
pixelentity.controller.js
484 ms
init.js
511 ms
jquery.form.min.js
486 ms
scripts.js
495 ms
wp-gallery-custom-links.js
492 ms
wp-embed.min.js
492 ms
sourcesanspro-regular-webfont.woff
937 ms
sourcesanspro-semibold-webfont.woff
876 ms
entypo-icon-font.woff
897 ms
sourcesanspro-light-webfont.woff
873 ms
search.png
867 ms
direct_1.png
867 ms
direct_2.png
864 ms
direct_3.png
798 ms
direct_4.png
797 ms
FAQ1.jpg
876 ms
kaart-web.jpg
878 ms
helpen_1.jpg
811 ms
helpen_2.jpg
804 ms
helpen_3.jpg
654 ms
icon_facebook.png
652 ms
icon_twitter.png
653 ms
ga.js
440 ms
hvo_logo1.jpg
123 ms
betondorp-2000x800.jpg
413 ms
moeder-aleppo-2000x800.jpg
576 ms
scheren-2000x800.jpg
904 ms
angelino-2000x800.jpg
477 ms
gezin-01-2000x800.jpg
666 ms
hvoq_hero_jongeren_01.jpg
588 ms
rikken-2000x800.jpg
740 ms
nils-2000x800.jpg
724 ms
volwassen-8-2000x800.jpg
828 ms
zangeres-2000x800.jpg
752 ms
rijswijk-2000x800.jpg
912 ms
jongeren-2-2000x800.jpg
892 ms
flierbosdreef-eritrea-2000x800.jpg
989 ms
muziekschool-2000x800.jpg
917 ms
gezin-02-2000x800.jpg
1074 ms
wasserij-2000x800.jpg
1056 ms
volwassen-6-2000x800.jpg
1069 ms
rijswijk-wuif.jpg
1079 ms
volwassen-10-2000x800.jpg
982 ms
volwassen-11-2000x800.jpg
1132 ms
__utm.gif
38 ms
BebasNeue-webfont.woff
936 ms
hvoquerido.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.
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
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
hvoquerido.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
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
hvoquerido.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 Hvoquerido.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 Hvoquerido.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.
hvoquerido.nl
Open Graph description is not detected on the main page of HVO Querido. 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: