4.5 sec in total
1 sec
3.1 sec
330 ms
Welcome to if.no homepage info - get ready to check If best content for Norway right away, or after learning these important things about if.no
If hjelper deg med å velge riktig forsikring. Sjekk pris på forsikring hos Nordens største forsikringsselskap.
Visit if.noWe analyzed If.no page load time and found that the first response time was 1 sec and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
if.no performance score
name
value
score
weighting
Value4.9 s
11/100
10%
Value9.4 s
0/100
25%
Value8.8 s
16/100
10%
Value850 ms
34/100
30%
Value0
100/100
15%
Value12.5 s
14/100
10%
1048 ms
132 ms
162 ms
219 ms
292 ms
Our browser made a total of 44 requests to load all elements on the main page. We found that 9% of them (4 requests) were addressed to the original If.no, 43% (19 requests) were made to Az801830.vo.msecnd.net and 9% (4 requests) were made to Ifhelp2015eu.herokuapp.com. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain If.no.
Page size can be reduced by 566.1 kB (42%)
1.4 MB
793.0 kB
In fact, the total size of If.no main page is 1.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. 35% of websites need less resources to load. Images take 605.8 kB which makes up the majority of the site volume.
Potential reduce by 62.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 62.6 kB or 80% of the original size.
Potential reduce by 22.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. If images are well optimized though.
Potential reduce by 279.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 279.1 kB or 63% of the original size.
Potential reduce by 202.0 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. If.no needs all CSS files to be minified and compressed as it can save up to 202.0 kB or 86% of the original size.
Number of requests can be reduced by 15 (44%)
34
19
The browser has sent 34 CSS, Javascripts, AJAX and image requests in order to completely render the main page of If. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
default.aspx
1048 ms
global-css.arc.min-sha2hOcIxq4hdo6OG2-iZLluhl7XAnw.css
132 ms
moodboard-other-winterboat.min-sha2bWqIq3OvVdCACrLWbIXlVsx9XKg.css
162 ms
global-js.arc.min-sha2Ghin6ptaQcJ6RIHfqxIyDBmE-JY.js
219 ms
webforms-ecmt-v2.min-sha2nmPD6Kz1iD6C_q0O-HI4zHhHj6Y-sha2nmPD6Kz1iD6C_q0O-HI4zHhHj6Y.js
292 ms
wsno.css
363 ms
ifhelp2015require.js
405 ms
419 ms
417 ms
ga.js
108 ms
logo.min-sha2UrlX-5wEsrrV0qRDj5z4xoWgLBo.png
33 ms
moodboard-insurance-car-s300x169.539666993144-sha2bG8OWRLNQHZxwpdiISUjvRm9tnc.jpg
31 ms
moodboard-insurance-home-s300x169.539666993144-sha2Rfr03vg27A7lOKZ_f-ktJtllJJo.jpg
92 ms
moodboard-insurance-travel-s300x169.539666993144-sha2LxIhIamgX1RLHkGhFJjQQfjUN0I.jpg
91 ms
circle-pageteaser-deductable-account-s270x270-sha24jyv770iwKJ50zoYDQn-bI8dvgI.jpg
92 ms
circle-pageteaser-tipsandadvice-s270x270-sha2RKt77g6l8lkfx9YQiq1VGW3ofuw.jpg
165 ms
circle-pageteaser-slowdown-gps-s270x270-sha2vrJffp_YzL5i4bxhT3tvn2Sgpe0.jpg
164 ms
gtm.js
165 ms
moodboard-other-winterboat-s2042x1154-sha2Xb-5uZjknmukd7t0oVHYit1WCgY.jpg
289 ms
OpenSans-Semibold-webfont.min-sha2hTUeNuRDhcG-Qi0AnCmQbDzqNOM.woff
179 ms
OpenSans-Bold-webfont.min-sha22aA4zRmmpEZTJj8-ABysQw6vzA8.woff
180 ms
OpenSans-Regular-webfont.min-sha2nQAMjWCeO46GuB5iuIZbzES1Cdg.woff
158 ms
OpenSans-Light-webfont.min-sha29oAIL4C9mqfq2F3I_W_zhE4Wcu4.woff
159 ms
if-icons.min-sha2hZlQnw1MNvqmbX4TvyIFWoYlKuc.woff
124 ms
__utm.gif
20 ms
GarageGothicForIf-Bold.min-sha2_t95EkYAGZ77yf5xtHVdpfIgPGc.woff
68 ms
HandsomeProForIf-Regular.min-sha2KOSuWWbAB4N9HYXvWqcnVmhvNbA.woff
134 ms
collect
77 ms
speedtrap.js
240 ms
ga-audiences
39 ms
reflectif_bannere_ifno_1501671_940x300_v4.jpg
226 ms
pages
117 ms
getuserinfo
720 ms
100 ms
session.js
682 ms
JavascriptInsert.js
931 ms
ifhelp2015.css
95 ms
ifhelp2015panel.html
188 ms
112 ms
activityi;src=4463930;type=invmedia;cat=xlzirdm1;ord=7669117280747.741
58 ms
fbevents.js
51 ms
__utm.gif
23 ms
108 ms
jsEvent.js
118 ms
if.no accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
button, link, and menuitem elements do not have accessible names.
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
if.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
Detected JavaScript libraries
Page has valid source maps
if.no 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
NO
NO
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise If.no can be misinterpreted by Google and other search engines. Our service has detected that Norwegian is used on the page, and it matches the claimed language. Our system also found out that If.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.
if.no
Open Graph description is not detected on the main page of If. 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: