Report Summary

  • 17

    Performance

    Renders faster than
    33% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 39% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

kv.ee

Kinnisvara KV.EE - Kinnisvara pakkumised - korterid majad maad äripinnad. 

Page Load Speed

8.1 sec in total

First Response

448 ms

Resources Loaded

7.1 sec

Page Rendered

616 ms

kv.ee screenshot

About Website

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

Eesti Esimene Kinnisvaraportaal

Visit kv.ee

Key Findings

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

Performance Metrics

kv.ee performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

16/100

10%

LCP (Largest Contentful Paint)

Value19.4 s

0/100

25%

SI (Speed Index)

Value13.5 s

2/100

10%

TBT (Total Blocking Time)

Value10,340 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value20.0 s

2/100

10%

Network Requests Diagram

kv.ee

448 ms

www.kv.ee

679 ms

kinnisvaraportaal-kv-ee.postimees.ee

752 ms

kv2.min.css

335 ms

kv2.min.js

539 ms

Our browser made a total of 130 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Kv.ee, 36% (47 requests) were made to R1.kv.ee and 25% (33 requests) were made to Files.kv.ee. The less responsive or slowest element that took the longest time to load (1.5 sec) relates to the external source F2.pmo.ee.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.5 MB (42%)

Content Size

3.6 MB

After Optimization

2.1 MB

In fact, the total size of Kv.ee main page is 3.6 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. 60% of websites need less resources to load. Images take 1.8 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 93.3 kB

  • Original 109.1 kB
  • After minification 86.1 kB
  • After compression 15.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 22.9 kB, which is 21% 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 93.3 kB or 86% of the original size.

Image Optimization

-11%

Potential reduce by 190.7 kB

  • Original 1.8 MB
  • After minification 1.6 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. Obviously, KV needs image optimization as it can save up to 190.7 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-67%

Potential reduce by 879.8 kB

  • Original 1.3 MB
  • After minification 1.3 MB
  • After compression 429.1 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 879.8 kB or 67% of the original size.

CSS Optimization

-83%

Potential reduce by 323.4 kB

  • Original 390.6 kB
  • After minification 385.5 kB
  • After compression 67.2 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. Kv.ee needs all CSS files to be minified and compressed as it can save up to 323.4 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 64 (52%)

Requests Now

122

After Optimization

58

The browser has sent 122 CSS, Javascripts, AJAX and image requests in order to completely render the main page of KV. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for JavaScripts and as a result speed up the page load time.

Accessibility Review

kv.ee accessibility score

73

Accessibility Issues

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

Buttons do not have an accessible name

High

Links do not have a discernible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

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 IDs are not unique

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

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

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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

kv.ee SEO score

82

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 doesn't use legible font sizes

High

Tap targets are not sized appropriately

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 Kv.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 Kv.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 KV. 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: