4 sec in total
212 ms
2 sec
1.8 sec
Welcome to fbr.dk homepage info - get ready to check Fbr best content right away, or after learning these important things about fbr.dk
Se uvildige og videnskabelige test af produkter og services. Som medlem støtter du vores kamp for dine rettigheder som forbruger.
Visit fbr.dkWe analyzed Fbr.dk page load time and found that the first response time was 212 ms and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
fbr.dk performance score
name
value
score
weighting
Value0.6 s
100/100
10%
Value0.6 s
100/100
25%
Value0.7 s
100/100
10%
Value0 ms
100/100
30%
Value0.01
100/100
15%
Value0.6 s
100/100
10%
212 ms
238 ms
178 ms
281 ms
205 ms
Our browser made a total of 45 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Fbr.dk, 80% (36 requests) were made to Taenk.dk and 13% (6 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Taenk.dk.
Page size can be reduced by 220.7 kB (13%)
1.7 MB
1.5 MB
In fact, the total size of Fbr.dk main page is 1.7 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. 50% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.
Potential reduce by 20.6 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 20.6 kB or 74% of the original size.
Potential reduce by 27.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. Fbr images are well optimized though.
Potential reduce by 104.9 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 104.9 kB or 68% of the original size.
Potential reduce by 67.8 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. Fbr.dk needs all CSS files to be minified and compressed as it can save up to 67.8 kB or 81% of the original size.
Number of requests can be reduced by 9 (21%)
43
34
The browser has sent 43 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fbr. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 5 to 1 for JavaScripts and as a result speed up the page load time.
fbr.dk
212 ms
taenk.dk
238 ms
css_a1969a336d8aebd4dbdbfda352f73187.css
178 ms
js_725cddadd3811cb2bca33b2b2122e9b2.js
281 ms
js_12b797ecc5ea4d3a62c3120bcff91b33.js
205 ms
site-logo.png
154 ms
paaskeb1339.jpg
1152 ms
rystepudser-test-800x387.jpg
154 ms
vask-top800x.jpg
293 ms
precious_bean_bargain_by_0009.jpg
190 ms
led-graa-skaerm800x.jpg
297 ms
tv_i_fbrt-farver_-_800x387_-_istock_000006293326_medium.jpg
473 ms
streamingulovlig800x387.jpg
391 ms
taenkpenge_0008_redigeret.jpg
459 ms
hus_stigende_bidragssatser_800x387_-_istock_000043395980_medium.jpg
436 ms
madvaerkstedet_har-du-taenkt_web_lokalmad.jpg
460 ms
insurance_stop.jpg
682 ms
bedemand_web.jpg
611 ms
11nyemaerker.jpg
641 ms
vw-snyd-med-biler.jpg
736 ms
minedagligvarer.jpg
663 ms
minepenge.jpg
786 ms
mitdigitaleliv.jpg
732 ms
mithjem.jpg
757 ms
kemiluppen.jpg
776 ms
taenkkemi.png
824 ms
passagerpulsen.jpg
825 ms
passagerpulsen.png
846 ms
gaeldsraadgivning.jpg
968 ms
gaeldsraadgivningen.png
871 ms
fbrt169forside.jpg
1015 ms
tp37_forside.jpg
1015 ms
newsletter.png
940 ms
gtm.js
128 ms
icomoon.woff
820 ms
analytics.js
40 ms
popup_html_info.html
809 ms
menu-expanded.png
842 ms
linkid.js
28 ms
collect
86 ms
collect
46 ms
collect
38 ms
css_c3d954ec3b77bcdcd25b156c92cc68e0.css
90 ms
collect
11 ms
collect
11 ms
fbr.dk accessibility score
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Image elements do not have [alt] attributes
Links do not have a discernible name
fbr.dk best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
fbr.dk SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
DA
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fbr.dk can be misinterpreted by Google and other search engines. Our service has detected that Danish is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Fbr.dk 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.
fbr.dk
Open Graph description is not detected on the main page of Fbr. 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: