Report Summary

  • 14

    Performance

    Renders faster than
    26% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 83% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    84% of websites

if.fi

Vakuutusyhtiö If vakuuttaa ihmiset ja yritykset | If

Page Load Speed

3.9 sec in total

First Response

487 ms

Resources Loaded

2.3 sec

Page Rendered

1.1 sec

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 487 ms 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

14

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

23/100

10%

LCP (Largest Contentful Paint)

Value10.8 s

0/100

25%

SI (Speed Index)

Value8.1 s

21/100

10%

TBT (Total Blocking Time)

Value2,440 ms

5/100

30%

CLS (Cumulative Layout Shift)

Value0.241

52/100

15%

TTI (Time to Interactive)

Value16.7 s

5/100

10%

Network Requests Diagram

www.if.fi

487 ms

henkiloasiakkaat

364 ms

global-css-header.4b00e9c28017f0489123.css

343 ms

vendor-css.7b5fefab5805a007c8a4.css

356 ms

global-vid-css.5d4f87e20fdd1ce14dfb.css

642 ms

Our browser made a total of 25 requests to load all elements on the main page. We found that 56% of them (14 requests) were addressed to the original If.fi, 28% (7 requests) were made to V.imgi.no and 4% (1 request) were made to Digitalfeedback.euro.confirmit.com. The less responsive or slowest element that took the longest time to load (642 ms) belongs to the original domain If.fi.

Page Optimization Overview & Recommendations

Page size can be reduced by 220.6 kB (6%)

Content Size

3.4 MB

After Optimization

3.2 MB

In fact, the total size of If.fi main page is 3.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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 2.9 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 203.9 kB

  • Original 241.3 kB
  • After minification 184.8 kB
  • After compression 37.4 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 56.5 kB, which is 23% 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 203.9 kB or 85% of the original size.

Image Optimization

-1%

Potential reduce by 15.5 kB

  • Original 2.9 MB
  • After minification 2.9 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

-1%

Potential reduce by 783 B

  • Original 112.1 kB
  • After minification 112.1 kB
  • After compression 111.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

-0%

Potential reduce by 422 B

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

Requests Breakdown

Number of requests can be reduced by 13 (59%)

Requests Now

22

After Optimization

9

The browser has sent 22 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 10 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

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

83

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

Page has valid source maps

SEO Factors

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

    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 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: