5 sec in total
362 ms
4.3 sec
367 ms
Visit produktfakta.no now to see the best up-to-date Produktfakta content for Norway and also check out these interesting facts you probably never knew about produktfakta.no
ProduktFakta, Leverandørdatabasen for bygg- og anleggsbransjen
Visit produktfakta.noWe analyzed Produktfakta.no page load time and found that the first response time was 362 ms and then it took 4.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
produktfakta.no performance score
name
value
score
weighting
Value5.6 s
5/100
10%
Value25.0 s
0/100
25%
Value10.4 s
8/100
10%
Value2,460 ms
4/100
30%
Value0.001
100/100
15%
Value23.5 s
1/100
10%
362 ms
363 ms
124 ms
240 ms
241 ms
Our browser made a total of 157 requests to load all elements on the main page. We found that 79% of them (124 requests) were addressed to the original Produktfakta.no, 3% (5 requests) were made to Boa.aecinfo.com and 3% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Produktfakta.no.
Page size can be reduced by 353.0 kB (19%)
1.8 MB
1.5 MB
In fact, the total size of Produktfakta.no main page is 1.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. 60% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.
Potential reduce by 50.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 50.3 kB or 79% of the original size.
Potential reduce by 93.5 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. Produktfakta images are well optimized though.
Potential reduce by 129.5 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 129.5 kB or 57% of the original size.
Potential reduce by 79.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. Produktfakta.no needs all CSS files to be minified and compressed as it can save up to 79.6 kB or 86% of the original size.
Number of requests can be reduced by 54 (36%)
150
96
The browser has sent 150 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Produktfakta. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
produktfakta.no
362 ms
www.produktfakta.no
363 ms
docu.css
124 ms
docunet_stats.js
240 ms
utilities.js
241 ms
Common.js
239 ms
jQuery.js
364 ms
carousel.js
241 ms
jquery-ui.css
242 ms
autocomplete.css
358 ms
css
26 ms
jquery.min.js
28 ms
jquery.cookie.js
360 ms
jquery-ui.min.js
46 ms
analytics.js
21 ms
atrk.js
81 ms
widgets.js
7 ms
print.css
140 ms
sdk.js
99 ms
docu_pageview.gif
773 ms
gtm.js
78 ms
vanpee-banner1.jpg
847 ms
bransjenytt_topleft.jpg
654 ms
bransjenytt_bottomright.jpg
628 ms
bflive336x280.jpg
630 ms
byggfakta_336x280.jpg
628 ms
BgHeader8.png
623 ms
pf_logo_left_new4.png
268 ms
SearchTextBox.png
146 ms
magnifier.png
146 ms
ButtonSearch3.png
150 ms
1_om_oss.png
248 ms
2_kontakt.png
268 ms
3_nyhetsbrv.png
271 ms
4_nyheter.png
272 ms
5_stat.png
377 ms
6_kat.png
382 ms
keymail_banner_eksempel_final3_small.png
505 ms
front.jpg
387 ms
logo_tb.jpg
387 ms
tb.jpg
499 ms
grohe_logo_tb.jpg
502 ms
tb.jpg
508 ms
logotb.jpg
507 ms
front.jpg
627 ms
flexigulv_logo_tb.jpg
621 ms
th85795.jpg
623 ms
deco_logo_tb.jpg
627 ms
EPICbyINR-100x150.jpg
629 ms
181.png
739 ms
front.jpg
740 ms
tb.jpg
743 ms
tb.jpg
748 ms
th353394.jpg
747 ms
front2.jpg
749 ms
logotb.jpg
857 ms
front2.jpg
865 ms
logo_tb.png
864 ms
tb.jpg
868 ms
logo_tb.jpg
869 ms
tb.jpg
870 ms
collect
22 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
19 ms
DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf
20 ms
MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf
21 ms
EInbV5DfGHOiMmvb1Xr-honF5uFdDttMLvmWuJdhhgs.ttf
20 ms
collect
78 ms
atrk.gif
71 ms
450 ms
test.png
212 ms
150 ms
xd_arbiter.php
84 ms
xd_arbiter.php
149 ms
logo_tb.JPG
850 ms
front.jpg
843 ms
lilleronning_logo_tb.jpg
840 ms
front.jpg
843 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
47 ms
follow_button.b9740740e0bcf9b0657c5b11bd4388da.no.html
17 ms
biokjemi_logo_tb.jpg
744 ms
front3.jpg
731 ms
logo_new_tb.jpg
834 ms
tb2.jpg
835 ms
artiteq_logo_tb.jpg
836 ms
like.php
68 ms
qeKvIRsJabD.js
139 ms
LVx-xkvaJ0b.png
154 ms
front2.jpg
854 ms
jot
84 ms
logotb.jpg
729 ms
tb.jpg
729 ms
aritco_logo_tb.jpg
832 ms
tb.jpg
727 ms
logotb2.jpg
723 ms
front.jpg
730 ms
hesselberg_logo_tb.jpg
725 ms
front.jpg
830 ms
213 ms
norfax_logo_tb.jpg
726 ms
front.jpg
726 ms
logotb.jpg
2384 ms
front.jpg
727 ms
logo_tb.jpg
726 ms
front.jpg
830 ms
logo_ny_tb.jpg
724 ms
facebook.png
723 ms
twitter.png
726 ms
linkedin.png
725 ms
nito2.png
828 ms
byggenorge2.png
834 ms
byggfakta2.png
727 ms
norgebygges2.png
725 ms
vvs2.png
727 ms
polyflor2.png
827 ms
deco2.png
832 ms
aiwell2.png
832 ms
hesselberg2.png
732 ms
betomur2.png
728 ms
byggma3.png
831 ms
forbo2.png
833 ms
sika2.png
832 ms
imi_hydronic.png
835 ms
10_print.png
733 ms
empty.gif
833 ms
12_fav.png
837 ms
13_email.png
834 ms
Bransjenytt_front_banner.png
1095 ms
a10.png
733 ms
list.png
832 ms
docu_summaryview.gif
1168 ms
docu_summaryview.gif
1165 ms
docu_summaryview.gif
841 ms
docu_summaryview.gif
944 ms
docu_summaryview.gif
852 ms
docu_summaryview.gif
950 ms
docu_summaryview.gif
962 ms
docu_summaryview.gif
975 ms
docu_summaryview.gif
1062 ms
docu_summaryview.gif
972 ms
docu_summaryview.gif
984 ms
docu_summaryview.gif
1046 ms
docu_summaryview.gif
1041 ms
docu_summaryview.gif
1063 ms
docu_summaryview.gif
971 ms
docu_summaryview.gif
982 ms
docu_summaryview.gif
1045 ms
docu_summaryview.gif
1038 ms
docu_summaryview.gif
1060 ms
docu_summaryview.gif
972 ms
docu_summaryview.gif
983 ms
docu_summaryview.gif
1044 ms
docu_summaryview.gif
1040 ms
docu_summaryview.gif
1063 ms
footer_bg.jpg
1094 ms
11_pdf.png
983 ms
ui-bg_flat_75_ffffff_40x100.png
1046 ms
docu_small.css
121 ms
produktfakta.no accessibility score
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
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
[id] attributes on active, focusable elements are not unique
Heading elements are not in a sequentially-descending order
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
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
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.
produktfakta.no 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
Page has valid source maps
produktfakta.no SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
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
NO
DA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Produktfakta.no can be misinterpreted by Google and other search engines. Our service has detected that Norwegian is used on the page, and it does not match the claimed Danish language. Our system also found out that Produktfakta.no 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.
produktfakta.no
Open Graph description is not detected on the main page of Produktfakta. 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: