Report Summary

  • 7

    Performance

    Renders faster than
    22% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 89

    SEO

    Google-friendlier than
    67% of websites

kava.ee

Populaarsed | Telekava | KAVA.ee

Page Load Speed

4.8 sec in total

First Response

476 ms

Resources Loaded

4 sec

Page Rendered

329 ms

kava.ee screenshot

About Website

Click here to check amazing KAVA content for Estonia. Otherwise, check out these important facts you probably never knew about kava.ee

Suurim telekava internetis. Üle 160 erineva kanali. ETV, Kanal2, TV3, TV6. Vali avalehele lemmikkanalid ja jaga häid saateid sõpradega! Filmid, sarjad, sport!

Visit kava.ee

Key Findings

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

Performance Metrics

kava.ee performance score

7

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

13/100

10%

LCP (Largest Contentful Paint)

Value11.5 s

0/100

25%

SI (Speed Index)

Value11.9 s

4/100

10%

TBT (Total Blocking Time)

Value2,810 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.399

25/100

15%

TTI (Time to Interactive)

Value17.2 s

4/100

10%

Network Requests Diagram

kava.ee

476 ms

www.kava.ee

1153 ms

bootstrap.min.css

9 ms

styles_screen.min.css

48 ms

migration.css

45 ms

Our browser made a total of 80 requests to load all elements on the main page. We found that 9% of them (7 requests) were addressed to the original Kava.ee, 51% (41 requests) were made to Cdn.tvstart.com and 6% (5 requests) were made to Cdnjs.cloudflare.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Kava.ee.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.9 MB (74%)

Content Size

3.9 MB

After Optimization

1.0 MB

In fact, the total size of Kava.ee main page is 3.9 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. 70% of websites need less resources to load. CSS take 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-91%

Potential reduce by 671.8 kB

  • Original 737.9 kB
  • After minification 477.4 kB
  • After compression 66.0 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 260.4 kB, which is 35% 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 671.8 kB or 91% of the original size.

Image Optimization

-4%

Potential reduce by 20.5 kB

  • Original 546.7 kB
  • After minification 526.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. KAVA images are well optimized though.

JavaScript Optimization

-78%

Potential reduce by 999.1 kB

  • Original 1.3 MB
  • After minification 966.1 kB
  • After compression 284.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 999.1 kB or 78% of the original size.

CSS Optimization

-90%

Potential reduce by 1.2 MB

  • Original 1.3 MB
  • After minification 1.3 MB
  • After compression 126.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. Kava.ee needs all CSS files to be minified and compressed as it can save up to 1.2 MB or 90% of the original size.

Requests Breakdown

Number of requests can be reduced by 32 (43%)

Requests Now

74

After Optimization

42

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

Accessibility Review

kava.ee accessibility score

77

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 progressbar elements do not have accessible names.

High

ARIA IDs are not unique

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

<frame> or <iframe> elements do not have a title

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.

Best Practices

kava.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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

kava.ee SEO score

89

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 Kava.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 Kava.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 data is detected on the main page of KAVA. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: