4.1 sec in total
800 ms
2.9 sec
374 ms
Click here to check amazing Hafabra content. Otherwise, check out these important facts you probably never knew about hafabra.nl
Visit hafabra.nlWe analyzed Hafabra.nl page load time and found that the first response time was 800 ms and then it took 3.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
hafabra.nl performance score
name
value
score
weighting
Value3.1 s
47/100
10%
Value7.2 s
5/100
25%
Value6.7 s
36/100
10%
Value30 ms
100/100
30%
Value0.621
10/100
15%
Value5.9 s
65/100
10%
800 ms
95 ms
172 ms
174 ms
175 ms
Our browser made a total of 52 requests to load all elements on the main page. We found that 98% of them (51 requests) were addressed to the original Hafabra.nl, 2% (1 request) were made to Cdn-images.mailchimp.com. The less responsive or slowest element that took the longest time to load (800 ms) belongs to the original domain Hafabra.nl.
Page size can be reduced by 479.3 kB (56%)
853.6 kB
374.3 kB
In fact, the total size of Hafabra.nl main page is 853.6 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. 40% of websites need less resources to load. Javascripts take 491.0 kB which makes up the majority of the site volume.
Potential reduce by 24.8 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 24.8 kB or 81% of the original size.
Potential reduce by 949 B
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. Hafabra images are well optimized though.
Potential reduce by 354.4 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 354.4 kB or 72% of the original size.
Potential reduce by 99.2 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. Hafabra.nl needs all CSS files to be minified and compressed as it can save up to 99.2 kB or 86% of the original size.
Number of requests can be reduced by 42 (86%)
49
7
The browser has sent 49 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Hafabra. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
www.hafabra.nl
800 ms
style.css
95 ms
components.css
172 ms
responsive.css
174 ms
events_manager.css
175 ms
jquery.js
263 ms
jquery-migrate.min.js
184 ms
core.min.js
197 ms
widget.min.js
255 ms
position.min.js
281 ms
mouse.min.js
257 ms
sortable.min.js
284 ms
datepicker.min.js
290 ms
menu.min.js
346 ms
autocomplete.min.js
342 ms
resizable.min.js
350 ms
draggable.min.js
356 ms
button.min.js
382 ms
dialog.min.js
381 ms
events-manager.js
429 ms
supersized.js
433 ms
supersized.shutter.js
435 ms
easing.js
441 ms
sticky.js
472 ms
datepicker.js
475 ms
tweet.js
516 ms
prettyphoto.js
515 ms
form.js
517 ms
validate.js
525 ms
custom.js
561 ms
slim-081711.css
9 ms
comment-reply.min.js
588 ms
wp-embed.min.js
598 ms
wp-emoji-release.min.js
492 ms
OpenSans-Regular-webfont.woff
544 ms
bg-header.png
126 ms
bg-header-container.png
128 ms
icon-twitter.png
126 ms
icon-facebook.png
129 ms
icon-vimeo.png
128 ms
logo-harm-wit-vierkant-01-150x150.png
210 ms
bg-menu.png
184 ms
arrow-prev.png
192 ms
arrow-next.png
205 ms
bg-overlay-pattern.png
205 ms
bg-content.png
282 ms
bg-widget-area-footer.png
283 ms
bg-footer.png
293 ms
bg-a.png
328 ms
OpenSans-CondLight-webfont.woff
518 ms
loading.gif
295 ms
468606_660562660626655_1723209523_o.jpg
795 ms
hafabra.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
hafabra.nl best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
hafabra.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 Hafabra.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 Hafabra.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.
hafabra.nl
Open Graph description is not detected on the main page of Hafabra. 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: