Tools & Wizards About Us
if.ee screenshot

Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

if.ee

If Kindlustus – Sulle, Sinu perele ja ettevõttele | If.ee

Page Load Speed

3.7 sec in total

First Response

567 ms

Resources Loaded

2.7 sec

Page Rendered

446 ms

if.ee screenshot

About Website

Welcome to if.ee homepage info - get ready to check If best content for Estonia right away, or after learning these important things about if.ee

If Kindlustus on Sinu kõrval. Tee liikluskindlustus, reisikindlustus, kaskokindlustus, kodukindlustus, õnnetusjuhtumikindlustus ja lemmikloomakindlustus.

Visit if.ee

Key Findings

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

Performance Metrics

if.ee performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.5 s

6/100

10%

LCP (Largest Contentful Paint)

Value15.2 s

0/100

25%

SI (Speed Index)

Value9.6 s

11/100

10%

TBT (Total Blocking Time)

Value2,140 ms

6/100

30%

CLS (Cumulative Layout Shift)

Value0.143

78/100

15%

TTI (Time to Interactive)

Value17.9 s

3/100

10%

Network Requests Diagram

www.if.ee

567 ms

eraklient

271 ms

global-css-header.4b00e9c28017f0489123.css

248 ms

vendor-css.7b5fefab5805a007c8a4.css

348 ms

global-vid-css.5d4f87e20fdd1ce14dfb.css

905 ms

Our browser made a total of 23 requests to load all elements on the main page. We found that 61% of them (14 requests) were addressed to the original If.ee, 17% (4 requests) were made to V.imgi.no and 9% (2 requests) were made to Dev.visualwebsiteoptimizer.com. The less responsive or slowest element that took the longest time to load (905 ms) belongs to the original domain If.ee.

Page Optimization Overview & Recommendations

Page size can be reduced by 213.5 kB (44%)

Content Size

489.9 kB

After Optimization

276.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of If.ee main page is 489.9 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. 30% of websites need less resources to load. CSS take 199.5 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 118.9 kB

  • Original 143.5 kB
  • After minification 111.5 kB
  • After compression 24.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. This page needs HTML code to be minified as it can gain 32.0 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 118.9 kB or 83% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 15.5 kB
  • After minification 15.5 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

-17%

Potential reduce by 22.7 kB

  • Original 131.4 kB
  • After minification 131.4 kB
  • After compression 108.7 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 22.7 kB or 17% of the original size.

CSS Optimization

-36%

Potential reduce by 72.0 kB

  • Original 199.5 kB
  • After minification 199.5 kB
  • After compression 127.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.ee needs all CSS files to be minified and compressed as it can save up to 72.0 kB or 36% of the original size.

Requests Breakdown

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

Requests Now

20

After Optimization

7

  • Images
  • JavaScript
  • CSS

The browser has sent 20 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.

Network Requests Diagram

www.if.ee

www.if.ee

567 ms

eraklient

eraklient

271 ms

global-css-header.4b00e9c28017f0489123.css

global-css-header.4b00e9c28017f0489123.css

248 ms

vendor-css.7b5fefab5805a007c8a4.css

vendor-css.7b5fefab5805a007c8a4.css

348 ms

global-vid-css.5d4f87e20fdd1ce14dfb.css

global-vid-css.5d4f87e20fdd1ce14dfb.css

905 ms

global-ids-css.d8344393918a03966e58.css

global-ids-css.d8344393918a03966e58.css

496 ms

btx-css.ac64071c35b8c069eabf.css

btx-css.ac64071c35b8c069eabf.css

415 ms

jquery.min.js

jquery.min.js

654 ms

global-js.6e2217fa9ae0b62d3e80.js

global-js.6e2217fa9ae0b62d3e80.js

402 ms

dropdown-calltoaction-block-js.ac7c2a091e1790930185.js

dropdown-calltoaction-block-js.ac7c2a091e1790930185.js

494 ms

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

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

546 ms

expandables-js.70a3f3a715edec3fe6f0.js

expandables-js.70a3f3a715edec3fe6f0.js

577 ms

find.js

find.js

37 ms

global-vid-js.b7ee5153ef88d98d1cbf.js

global-vid-js.b7ee5153ef88d98d1cbf.js

547 ms

ai.0.js

ai.0.js

169 ms

j.php

j.php

204 ms

gtm.js

gtm.js

302 ms

400

400

163 ms

400

400

166 ms

400

400

169 ms

980

980

119 ms

IfSans-Variable.woff

IfSans-Variable.woff

246 ms

v.gif

v.gif

86 ms

Accessibility Review

if.ee accessibility score

85

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

ARIA IDs are not unique

Best Practices

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

    ET

  • Language Claimed

    ET

  • Encoding

    UTF-8

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

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: