3.4 sec in total
193 ms
3 sec
282 ms
Visit fbto.nl now to see the best up-to-date FBTO content for Netherlands and also check out these interesting facts you probably never knew about fbto.nl
Bij FBTO kun je de verzekeringen aanpassen aan jouw situatie. Verzeker bijvoorbeeld je auto, je spullen of je huis. Lees meer of bereken direct je premie.
Visit fbto.nlWe analyzed Fbto.nl page load time and found that the first response time was 193 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.
fbto.nl performance score
name
value
score
weighting
Value4.1 s
21/100
10%
Value5.3 s
21/100
25%
Value9.9 s
9/100
10%
Value6,340 ms
0/100
30%
Value0
100/100
15%
Value13.2 s
12/100
10%
193 ms
272 ms
322 ms
204 ms
287 ms
Our browser made a total of 66 requests to load all elements on the main page. We found that 82% of them (54 requests) were addressed to the original Fbto.nl, 5% (3 requests) were made to Dev.visualwebsiteoptimizer.com and 5% (3 requests) were made to Tdn.r42tag.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Fbto.nl.
Page size can be reduced by 997.4 kB (42%)
2.4 MB
1.4 MB
In fact, the total size of Fbto.nl main page is 2.4 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. 45% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 28.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. This page needs HTML code to be minified as it can gain 4.2 kB, which is 11% 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 28.3 kB or 77% of the original size.
Potential reduce by 88.3 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. FBTO images are well optimized though.
Potential reduce by 771.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 771.1 kB or 79% of the original size.
Potential reduce by 109.6 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. Fbto.nl needs all CSS files to be minified and compressed as it can save up to 109.6 kB or 85% of the original size.
Number of requests can be reduced by 20 (34%)
59
39
The browser has sent 59 CSS, Javascripts, AJAX and image requests in order to completely render the main page of FBTO. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and as a result speed up the page load time.
fbto.nl
193 ms
www.fbto.nl
272 ms
default.aspx
322 ms
site.css
204 ms
vwo.js
287 ms
modernizr.custom.js
292 ms
TMS_Synovite.js
290 ms
site.vendor.js
878 ms
site.custom.js
371 ms
ReadSpeaker.js
371 ms
store-all.js
402 ms
j.php
92 ms
ca-9-site-160.js
200 ms
readspeaker.png
156 ms
readspeaker_button.png
246 ms
icon-inlog.png
163 ms
fbto-verzekeringen-logo.png
248 ms
callus.png
166 ms
phonesearchBtn-white.png
253 ms
coloredbar.png
271 ms
breadcrumb-arrow.png
267 ms
gototop.png
348 ms
FBTO_Reisverzekering_2016.jpg
750 ms
goicon.png
352 ms
Nota%20declareren_72x72.png
364 ms
Schade_melden_72x72.png
375 ms
Gegevens_wijzigen_72x72.png
449 ms
visualbg-right.png
450 ms
roadtrip-vb.jpg
810 ms
visualbanner-cutout.png
477 ms
goicon-white.png
583 ms
logo_onderling.jpg
582 ms
listitemfull-icon.png
585 ms
fbto-iphone-declaratie.jpg
654 ms
minivakantie-blog.jpg
839 ms
duiken-blog.jpg
847 ms
FBTO_reis_Lr.jpg
883 ms
contact-facebook.png
756 ms
contact-twitter.png
849 ms
contact-googleplus.png
858 ms
contact-youtube.png
908 ms
thuiswinkel_waarborg-web.png
943 ms
wijzer_in_geldzaken_logo-web.png
952 ms
keurmerk-web.png
949 ms
onderdeel-van-achmea.svg
927 ms
frank-regular-webfont.woff
1055 ms
frank-bold-webfont.woff
976 ms
v.gif
24 ms
va-fbc30fe569246b4c14a32b01679c9492.js
14 ms
prod
225 ms
dc.js
70 ms
5cabdb8d3d76.js
26 ms
__utm.gif
12 ms
ga-audiences
95 ms
ReadSpeaker.Styles.css
471 ms
ReadSpeaker.Core.js
515 ms
ReadSpeaker.pub.Config.js
584 ms
tag-permissions-02f01b8b-edd8-45a3-8a61-4922d6ca82ae.js
48 ms
stats
44 ms
x.png
42 ms
frank-light-webfont.woff
197 ms
ReadSpeaker.lib.Facade.adapter.jquery.js
103 ms
ReadSpeaker.Common.Settings.js
108 ms
ReadSpeaker.PlayerAPI.js
106 ms
ReadSpeaker.HL.js
141 ms
ReadSpeaker.ui.js
135 ms
fbto.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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
fbto.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
fbto.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 Fbto.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 Fbto.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.
fbto.nl
Open Graph description is not detected on the main page of FBTO. 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: