Report Summary

  • 26

    Performance

    Renders faster than
    46% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 67% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

if.fi

Vakuutusyhtiö If vakuuttaa ihmiset ja yritykset | If

Page Load Speed

4.5 sec in total

First Response

1.1 sec

Resources Loaded

3 sec

Page Rendered

413 ms

if.fi screenshot

About Website

Click here to check amazing If content for Finland. Otherwise, check out these important facts you probably never knew about if.fi

If vakuutusyhtiö varmistaa, että olet asianmukaisesti vakuutettu. Olemme rinnallasi, kun tarvitset apua.

Visit if.fi

Key Findings

We analyzed If.fi page load time and found that the first response time was 1.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.

Performance Metrics

if.fi performance score

26

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.1 s

9/100

10%

LCP (Largest Contentful Paint)

Value7.7 s

3/100

25%

SI (Speed Index)

Value7.9 s

23/100

10%

TBT (Total Blocking Time)

Value1,330 ms

17/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value11.3 s

19/100

10%

Network Requests Diagram

default.aspx

1053 ms

global-css.arc.min-sha2hOcIxq4hdo6OG2-iZLluhl7XAnw.css

142 ms

moodboard-other-winterboat.min-sha2bWqIq3OvVdCACrLWbIXlVsx9XKg.css

171 ms

global-js.arc.min-sha2Ghin6ptaQcJ6RIHfqxIyDBmE-JY.js

231 ms

webforms-ecmt-v2.min-sha2nmPD6Kz1iD6C_q0O-HI4zHhHj6Y-sha2nmPD6Kz1iD6C_q0O-HI4zHhHj6Y.js

304 ms

Our browser made a total of 40 requests to load all elements on the main page. We found that 10% of them (4 requests) were addressed to the original If.fi, 45% (18 requests) were made to Az801830.vo.msecnd.net and 10% (4 requests) were made to Service.giosg.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain If.fi.

Page Optimization Overview & Recommendations

Page size can be reduced by 614.7 kB (37%)

Content Size

1.7 MB

After Optimization

1.1 MB

In fact, the total size of If.fi 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. 35% of websites need less resources to load. Images take 830.3 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 70.4 kB

  • Original 86.2 kB
  • After minification 78.8 kB
  • After compression 15.9 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 70.4 kB or 82% of the original size.

Image Optimization

-3%

Potential reduce by 23.0 kB

  • Original 830.3 kB
  • After minification 807.2 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.

JavaScript Optimization

-64%

Potential reduce by 376.1 kB

  • Original 587.4 kB
  • After minification 586.0 kB
  • After compression 211.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 376.1 kB or 64% of the original size.

CSS Optimization

-86%

Potential reduce by 145.1 kB

  • Original 168.7 kB
  • After minification 167.6 kB
  • After compression 23.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. If.fi needs all CSS files to be minified and compressed as it can save up to 145.1 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 12 (40%)

Requests Now

30

After Optimization

18

The browser has sent 30 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 as a result speed up the page load time.

Accessibility Review

if.fi accessibility score

87

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

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

Best Practices

if.fi 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.fi SEO score

100

Search Engine Optimization Advices

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

    FI

  • Language Claimed

    FI

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise If.fi can be misinterpreted by Google and other search engines. Our service has detected that Finnish is used on the page, and it matches the claimed language. Our system also found out that If.fi 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

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: