Tools & Wizards About Us
if.no screenshot

Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 83% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

if.no

If – Nordens ledende forsikringsselskap

Page Load Speed

5.1 sec in total

First Response

646 ms

Resources Loaded

3.7 sec

Page Rendered

770 ms

if.no screenshot

About Website

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.no

Key Findings

We analyzed If.no page load time and found that the first response time was 646 ms and then it took 4.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

if.no performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

13/100

10%

LCP (Largest Contentful Paint)

Value11.6 s

0/100

25%

SI (Speed Index)

Value8.6 s

17/100

10%

TBT (Total Blocking Time)

Value3,630 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.003

100/100

15%

TTI (Time to Interactive)

Value18.8 s

3/100

10%

Network Requests Diagram

www.if.no

646 ms

privat

305 ms

global-css-header.4b00e9c28017f0489123.css

277 ms

vendor-css.7b5fefab5805a007c8a4.css

352 ms

global-vid-css.5d4f87e20fdd1ce14dfb.css

546 ms

Our browser made a total of 35 requests to load all elements on the main page. We found that 37% of them (13 requests) were addressed to the original If.no, 20% (7 requests) were made to Shop.pri.if.no and 20% (7 requests) were made to V.imgi.no. The less responsive or slowest element that took the longest time to load (961 ms) relates to the external source Ifhelp.if.eu.

Page Optimization Overview & Recommendations

Page size can be reduced by 220.4 kB (12%)

Content Size

1.9 MB

After Optimization

1.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of If.no main page is 1.9 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. 55% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 175.0 kB

  • Original 203.9 kB
  • After minification 158.1 kB
  • After compression 28.8 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 45.8 kB, which is 22% 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 175.0 kB or 86% of the original size.

Image Optimization

-1%

Potential reduce by 15.0 kB

  • Original 1.3 MB
  • After minification 1.3 MB

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.

JavaScript Optimization

-9%

Potential reduce by 17.8 kB

  • Original 208.1 kB
  • After minification 208.1 kB
  • After compression 190.3 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. This website has mostly compressed JavaScripts.

CSS Optimization

-7%

Potential reduce by 12.5 kB

  • Original 169.2 kB
  • After minification 169.2 kB
  • After compression 156.7 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 has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 19 (61%)

Requests Now

31

After Optimization

12

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 31 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 8 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

www.if.no

www.if.no

646 ms

privat

privat

305 ms

global-css-header.4b00e9c28017f0489123.css

global-css-header.4b00e9c28017f0489123.css

277 ms

vendor-css.7b5fefab5805a007c8a4.css

vendor-css.7b5fefab5805a007c8a4.css

352 ms

global-vid-css.5d4f87e20fdd1ce14dfb.css

global-vid-css.5d4f87e20fdd1ce14dfb.css

546 ms

global-ids-css.d8344393918a03966e58.css

global-ids-css.d8344393918a03966e58.css

356 ms

btx-css.ac64071c35b8c069eabf.css

btx-css.ac64071c35b8c069eabf.css

346 ms

jquery.min.js

jquery.min.js

508 ms

global-js.6e2217fa9ae0b62d3e80.js

global-js.6e2217fa9ae0b62d3e80.js

446 ms

cart

cart

533 ms

vendor-responsively-lazy-js.3a9678b042ddd0fa16b8.js

vendor-responsively-lazy-js.3a9678b042ddd0fa16b8.js

493 ms

openpages-lazy-background-js.a37a782d7816313ef612.js

openpages-lazy-background-js.a37a782d7816313ef612.js

493 ms

find.js

find.js

37 ms

global-vid-js.b7ee5153ef88d98d1cbf.js

global-vid-js.b7ee5153ef88d98d1cbf.js

396 ms

ai.0.js

ai.0.js

19 ms

vendor.js

vendor.js

252 ms

cart.css

cart.css

416 ms

wsno_global.css

wsno_global.css

419 ms

wsno_ids.css

wsno_ids.css

507 ms

cart.js

cart.js

457 ms

gtm.js

gtm.js

359 ms

980

980

333 ms

2042

2042

311 ms

2042

2042

308 ms

2042

2042

309 ms

400

400

307 ms

400

400

306 ms

400

400

309 ms

IfSans-Variable.woff

IfSans-Variable.woff

310 ms

IfSans-Variable..woff

IfSans-Variable..woff

310 ms

js

js

141 ms

analytics.js

analytics.js

198 ms

ifhelp2015.js

ifhelp2015.js

961 ms

collect

collect

186 ms

landing

landing

79 ms

Accessibility Review

if.no accessibility score

94

Accessibility Issues

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

High

[aria-*] attributes do not match their roles

Best Practices

if.no best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

if.no SEO score

93

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    NO

  • Language Claimed

    NO

  • Encoding

    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.

Social Sharing Optimization

if.no

Open Graph data is detected on the main page of If. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: