Report Summary

  • 52

    Performance

    Renders faster than
    70% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 75% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

invaabi.ee

Tere tulemast! - Invaabi

Page Load Speed

2.3 sec in total

First Response

434 ms

Resources Loaded

1.7 sec

Page Rendered

161 ms

invaabi.ee screenshot

About Website

Visit invaabi.ee now to see the best up-to-date Invaabi content for Estonia and also check out these interesting facts you probably never knew about invaabi.ee

Visit invaabi.ee

Key Findings

We analyzed Invaabi.ee page load time and found that the first response time was 434 ms and then it took 1.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

invaabi.ee performance score

52

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

45/100

10%

LCP (Largest Contentful Paint)

Value6.2 s

11/100

25%

SI (Speed Index)

Value7.8 s

24/100

10%

TBT (Total Blocking Time)

Value310 ms

78/100

30%

CLS (Cumulative Layout Shift)

Value0.068

96/100

15%

TTI (Time to Interactive)

Value7.6 s

46/100

10%

Network Requests Diagram

avaleht

434 ms

main.css

227 ms

t.js

234 ms

ga.js

39 ms

t.gif

135 ms

Our browser made a total of 29 requests to load all elements on the main page. We found that 93% of them (27 requests) were addressed to the original Invaabi.ee, 7% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (654 ms) belongs to the original domain Invaabi.ee.

Page Optimization Overview & Recommendations

Page size can be reduced by 52.6 kB (26%)

Content Size

199.8 kB

After Optimization

147.2 kB

In fact, the total size of Invaabi.ee main page is 199.8 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. 20% of websites need less resources to load. Images take 147.4 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 10.0 kB

  • Original 13.4 kB
  • After minification 11.3 kB
  • After compression 3.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 2.1 kB, which is 15% 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 10.0 kB or 75% of the original size.

Image Optimization

-16%

Potential reduce by 23.8 kB

  • Original 147.4 kB
  • After minification 123.7 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. Obviously, Invaabi needs image optimization as it can save up to 23.8 kB or 16% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 50 B

  • Original 17.3 kB
  • After minification 17.3 kB
  • After compression 17.2 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

-87%

Potential reduce by 18.8 kB

  • Original 21.7 kB
  • After minification 14.0 kB
  • After compression 2.9 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. Invaabi.ee needs all CSS files to be minified and compressed as it can save up to 18.8 kB or 87% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

28

After Optimization

28

The browser has sent 28 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Invaabi. According to our analytics all requests are already optimized.

Accessibility Review

invaabi.ee accessibility score

90

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

invaabi.ee best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

invaabi.ee SEO score

85

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    ET

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Invaabi.ee can be misinterpreted by Google and other search engines. Our service has detected that Estonian is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Invaabi.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

Open Graph description is not detected on the main page of Invaabi. 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: