6.1 sec in total
1.7 sec
4 sec
478 ms
Click here to check amazing Hus content. Otherwise, check out these important facts you probably never knew about hus.no
Sammenlign tilbud fra flere ferdighusleverandører og få en bedre avtale.
Visit hus.noWe analyzed Hus.no page load time and found that the first response time was 1.7 sec and then it took 4.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
hus.no performance score
name
value
score
weighting
Value4.1 s
22/100
10%
Value21.0 s
0/100
25%
Value7.2 s
30/100
10%
Value720 ms
41/100
30%
Value0.006
100/100
15%
Value15.9 s
6/100
10%
1685 ms
22 ms
590 ms
590 ms
1109 ms
Our browser made a total of 91 requests to load all elements on the main page. We found that 52% of them (47 requests) were addressed to the original Hus.no, 7% (6 requests) were made to Pagead2.googlesyndication.com and 7% (6 requests) were made to Tpc.googlesyndication.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Hus.no.
Page size can be reduced by 346.3 kB (53%)
648.7 kB
302.3 kB
In fact, the total size of Hus.no main page is 648.7 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. 50% of websites need less resources to load. Javascripts take 293.4 kB which makes up the majority of the site volume.
Potential reduce by 166.0 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 37.5 kB, which is 20% 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 166.0 kB or 91% of the original size.
Potential reduce by 4.4 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. Hus images are well optimized though.
Potential reduce by 175.0 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 175.0 kB or 60% of the original size.
Potential reduce by 988 B
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. Hus.no needs all CSS files to be minified and compressed as it can save up to 988 B or 71% of the original size.
Number of requests can be reduced by 32 (37%)
86
54
The browser has sent 86 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Hus. 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.
hus.no
1685 ms
swfobject.js
22 ms
exmplmenu_var.js
590 ms
menu_com.js
590 ms
n.gif
1109 ms
fem.gif
1121 ms
bkgrcell.gif
224 ms
hus-husportal.gif
337 ms
unitedkingdom.gif
262 ms
germany.gif
329 ms
spain.gif
376 ms
france.gif
439 ms
238 ms
6577.js
441 ms
ferienlogo.jpg
364 ms
hyttelogo.jpg
391 ms
baatlogo.jpg
370 ms
bilerlogo.jpg
369 ms
hytte-hytteportal.gif
362 ms
selco.gif
969 ms
iechus190x110.gif
465 ms
boligpartner190x110.gif
567 ms
boligpartner140x120.gif
586 ms
boligpartner225x68.gif
470 ms
Blink-Hus-225x68.gif
446 ms
F3.gif
1254 ms
F1.gif
1371 ms
F4.gif
1260 ms
F1-1.gif
373 ms
F1-2.gif
461 ms
vp5.jpg
490 ms
PC160008.JPG
489 ms
varmepumpehus-50.jpg
497 ms
trapp2-mini.jpg
496 ms
bilde_4-tumb.jpg
612 ms
Dcp_1268-mini.jpg
701 ms
trefokus14.gif
613 ms
trefokus9.gif
608 ms
trefokus8.gif
607 ms
trefokus15.gif
579 ms
trefokus6.gif
620 ms
trefokus16.gif
629 ms
trefokus10.gif
636 ms
trefokus12.gif
678 ms
trefokus3.gif
701 ms
trefokus7.gif
730 ms
trefokus17.gif
736 ms
show_ads.js
5 ms
eg_feed.js
741 ms
trefokus2.gif
763 ms
trefokus4.gif
854 ms
vestlandshus140x120.gif
860 ms
norhus_140x600.gif
1121 ms
Norgeshus-140x350.jpg
891 ms
Adform.Bootstrap.js
14 ms
126 ms
boot.js
22 ms
253 ms
172 ms
ca-pub-2482352347094450.js
38 ms
zrt_lookup.html
31 ms
show_ads_impl.js
55 ms
ads
395 ms
Standard
30 ms
osd.js
26 ms
ads
353 ms
13359554.jpg
299 ms
120 ms
jquery.min.js
381 ms
loading.gif
154 ms
ads
160 ms
ga.js
6 ms
__utm.gif
53 ms
m_js_controller.js
71 ms
abg.js
53 ms
googlelogo_color_112x36dp.png
44 ms
10632994980562791078
42 ms
9511053844865311496
109 ms
s
77 ms
x_button_blue2.png
76 ms
favicon
146 ms
nessie_icon_tiamat_white.png
12 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
15 ms
facebox.css
125 ms
facebox.js
117 ms
ajax.ashx
844 ms
tridown.gif
117 ms
tri.gif
134 ms
ui
40 ms
activeview
13 ms
225 ms
hus.no 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
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
hus.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
General
Impact
Issue
Registers an unload listener
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
Issues were logged in the Issues panel in Chrome Devtools
hus.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
NO
N/A
WINDOWS-1252
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hus.no can be misinterpreted by Google and other search engines. Our service has detected that Norwegian 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 Hus.no main page’s claimed encoding is windows-1252. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
hus.no
Open Graph description is not detected on the main page of Hus. 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: