Tools & Wizards About Us
kating.ee screenshot

Report Summary

  • 32

    Performance

    Renders faster than
    52% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

kating.ee

Kodulehe ja e-poe tegemine ja haldamine, WordPressi juhendid

Page Load Speed

2.3 sec in total

First Response

318 ms

Resources Loaded

1.6 sec

Page Rendered

320 ms

kating.ee screenshot

About Website

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

Kodulehe ja e-poe tegemine Wordpressi platvormile. Vana ning aegunud kodulehe tegemine responsive kujundusega koduleheks. WooCommerce E-poe tegemine.

Visit kating.ee

Key Findings

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

Performance Metrics

kating.ee performance score

32

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.4 s

72/100

10%

LCP (Largest Contentful Paint)

Value10.4 s

0/100

25%

SI (Speed Index)

Value7.5 s

27/100

10%

TBT (Total Blocking Time)

Value1,510 ms

14/100

30%

CLS (Cumulative Layout Shift)

Value0.012

100/100

15%

TTI (Time to Interactive)

Value10.3 s

25/100

10%

Network Requests Diagram

kating.ee

318 ms

kating.ee

559 ms

prettyPhoto.min.css

209 ms

styles.css

312 ms

wpcf7-redirect-frontend.min.css

312 ms

Our browser made a total of 34 requests to load all elements on the main page. We found that 56% of them (19 requests) were addressed to the original Kating.ee, 35% (12 requests) were made to Fonts.gstatic.com and 6% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (746 ms) belongs to the original domain Kating.ee.

Page Optimization Overview & Recommendations

Page size can be reduced by 204.0 kB (72%)

Content Size

282.0 kB

After Optimization

78.0 kB

  • HTML
  • Images

In fact, the total size of Kating.ee main page is 282.0 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. 55% of websites need less resources to load. HTML takes 238.7 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 203.6 kB

  • Original 238.7 kB
  • After minification 236.0 kB
  • After compression 35.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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 203.6 kB or 85% of the original size.

Image Optimization

-1%

Potential reduce by 361 B

  • Original 43.3 kB
  • After minification 43.0 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. Kating images are well optimized though.

Requests Breakdown

Number of requests can be reduced by 11 (58%)

Requests Now

19

After Optimization

8

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

kating.ee

kating.ee

318 ms

kating.ee

kating.ee

559 ms

prettyPhoto.min.css

prettyPhoto.min.css

209 ms

styles.css

styles.css

312 ms

wpcf7-redirect-frontend.min.css

wpcf7-redirect-frontend.min.css

312 ms

style.css

style.css

205 ms

jquery.min.js

jquery.min.js

209 ms

js

js

73 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

315 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

313 ms

api.js

api.js

43 ms

wp-polyfill.min.js

wp-polyfill.min.js

315 ms

lazyload.min.js

lazyload.min.js

314 ms

b71fbc768ffa749019a625e11d959a6a.js

b71fbc768ffa749019a625e11d959a6a.js

746 ms

gtm.js

gtm.js

94 ms

kating-logo-2020.svg

kating-logo-2020.svg

178 ms

kodulehe-tegemine-front-200516.svg

kodulehe-tegemine-front-200516.svg

214 ms

zone-veebimajutus-240226-400x250.jpg

zone-veebimajutus-240226-400x250.jpg

303 ms

ewww-image-optimizer-230726-400x250.jpg

ewww-image-optimizer-230726-400x250.jpg

217 ms

veergude-korrastamine-wordpressis-210528-03-400x250.jpg

veergude-korrastamine-wordpressis-210528-03-400x250.jpg

217 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0C4k.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0C4k.woff

61 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0C4n.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0C4n.ttf

74 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4k.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4k.woff

93 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4n.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4n.ttf

93 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0C4k.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0C4k.woff

94 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0C4n.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0C4n.ttf

93 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1y4k.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1y4k.woff

94 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1y4n.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1y4n.ttf

93 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1y4k.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1y4k.woff

96 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1y4n.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1y4n.ttf

97 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1y4k.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1y4k.woff

97 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1y4n.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1y4n.ttf

120 ms

modules.woff

modules.woff

120 ms

5-stars-210521.png

5-stars-210521.png

110 ms

Accessibility Review

kating.ee accessibility score

86

Accessibility Issues

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.

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

kating.ee best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

kating.ee SEO score

100

Search Engine Optimization Advices

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

kating.ee

Open Graph data is detected on the main page of Kating. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: