3.5 sec in total
340 ms
3 sec
147 ms
Visit bof.nl now to see the best up-to-date Bof content for Netherlands and also check out these interesting facts you probably never knew about bof.nl
Bits of Freedom komt op voor internetvrijheid door de online grondrechten op communicatievrijheid en privacy te beschermen.
Visit bof.nlWe analyzed Bof.nl page load time and found that the first response time was 340 ms and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
bof.nl performance score
name
value
score
weighting
Value2.7 s
59/100
10%
Value3.7 s
58/100
25%
Value8.7 s
16/100
10%
Value190 ms
91/100
30%
Value0.443
21/100
15%
Value7.0 s
53/100
10%
340 ms
1110 ms
92 ms
179 ms
262 ms
Our browser made a total of 55 requests to load all elements on the main page. We found that 98% of them (54 requests) were addressed to the original Bof.nl, 2% (1 request) were made to Stats.bof.nl. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Bof.nl.
Page size can be reduced by 371.7 kB (57%)
651.6 kB
279.8 kB
In fact, the total size of Bof.nl main page is 651.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. 30% of websites need less resources to load. Javascripts take 328.0 kB which makes up the majority of the site volume.
Potential reduce by 25.3 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 25.3 kB or 80% of the original size.
Potential reduce by 29.8 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. Obviously, Bof needs image optimization as it can save up to 29.8 kB or 16% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 227.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 227.4 kB or 69% of the original size.
Potential reduce by 89.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. Bof.nl needs all CSS files to be minified and compressed as it can save up to 89.2 kB or 84% of the original size.
Number of requests can be reduced by 30 (59%)
51
21
The browser has sent 51 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Bof. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
bof.nl
340 ms
www.bof.nl
1110 ms
style.css
92 ms
gridiculous.css
179 ms
post_grid.css
262 ms
icms.js
264 ms
styles.css
262 ms
fancybox.css
265 ms
polls-css.css
264 ms
jquery.js
368 ms
jquery-migrate.min.js
346 ms
jquery.fancybox.js
347 ms
share.css
347 ms
share.js
355 ms
jquery.ui.tabs.min.js
366 ms
jquery-ui-custom.css
432 ms
jquery.validate.min.js
434 ms
validation_logic.js
432 ms
jquery.init.js
438 ms
comment-reply.min.js
471 ms
jquery.form.min.js
469 ms
scripts.js
517 ms
polls-js.js
518 ms
wp-embed.min.js
518 ms
mime.css
440 ms
fonts.css
473 ms
bof.png
89 ms
header.png
175 ms
word-donateur.png
91 ms
btn.vacatures.png
89 ms
bof_960-home_03.png
90 ms
menu-left2.png
91 ms
menu-right2.png
176 ms
menu-right.png
175 ms
menu-left.png
178 ms
zoek.png
179 ms
fd98878371cc69e4ebb73867828b80a4.png
332 ms
onder_bg_a.png
256 ms
btn.talent.png
259 ms
ul-bullet-on.png
260 ms
e9d8f3a97d389ca4e3eb1da6f0cb679d-150x150.jpg
256 ms
9396613642_9890ebe3eb_z-150x150.jpg
259 ms
6046509739_65159e9a75_z-150x150.jpg
341 ms
4654483579_a9fefebc94_z-150x150.jpg
342 ms
3675980379_0bf9f9b669_z-150x150.jpg
343 ms
22675905582_915a33aa51_z-150x150.jpg
345 ms
footer.png
344 ms
2footer-4.png
418 ms
2footer-3.png
426 ms
2footer-2.png
427 ms
2footer-1.png
428 ms
DINWeb-Bold.woff
429 ms
DINWebPro-Black.woff
516 ms
piwik.js
899 ms
print.css
89 ms
bof.nl accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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.
bof.nl 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
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
bof.nl 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
Tap targets are not sized appropriately
NL
NL
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Bof.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 Bof.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.
bof.nl
Open Graph description is not detected on the main page of Bof. 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: