Report Summary

  • 33

    Performance

    Renders faster than
    53% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 60% of websites

  • 69

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

ltkh.ee

Lääne-Tallinna Keskhaigla: Ühiselt abiks

Page Load Speed

11.4 sec in total

First Response

2.9 sec

Resources Loaded

8.3 sec

Page Rendered

258 ms

ltkh.ee screenshot

About Website

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

Lääne-Tallinna Keskhaigla on rohkem kui 500 voodikohaga ja 1700 töötajaga raviasutus, kus pakume patsientidele kõrgel tasemel nüüdisaegset raviteenust

Visit ltkh.ee

Key Findings

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

Performance Metrics

ltkh.ee performance score

33

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.9 s

11/100

10%

LCP (Largest Contentful Paint)

Value76.1 s

0/100

25%

SI (Speed Index)

Value10.9 s

7/100

10%

TBT (Total Blocking Time)

Value420 ms

66/100

30%

CLS (Cumulative Layout Shift)

Value0.187

66/100

15%

TTI (Time to Interactive)

Value12.5 s

15/100

10%

Network Requests Diagram

www.keskhaigla.ee

2867 ms

wp-emoji-release.min.js

370 ms

4865c135_ai1ec_parsed_css.css

1112 ms

formidablepro.css

583 ms

styles.css

237 ms

Our browser made a total of 109 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Ltkh.ee, 9% (10 requests) were made to Static.xx.fbcdn.net and 6% (6 requests) were made to Cvkeskus.ee. The less responsive or slowest element that took the longest time to load (2.9 sec) relates to the external source Keskhaigla.ee.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.3 MB (46%)

Content Size

2.8 MB

After Optimization

1.5 MB

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

HTML Optimization

-81%

Potential reduce by 95.9 kB

  • Original 118.9 kB
  • After minification 117.2 kB
  • After compression 23.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 95.9 kB or 81% of the original size.

Image Optimization

-4%

Potential reduce by 40.4 kB

  • Original 1.1 MB
  • After minification 1.0 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. Ltkh images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 520.1 kB

  • Original 758.8 kB
  • After minification 705.0 kB
  • After compression 238.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 520.1 kB or 69% of the original size.

CSS Optimization

-74%

Potential reduce by 632.5 kB

  • Original 851.7 kB
  • After minification 782.2 kB
  • After compression 219.3 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. Ltkh.ee needs all CSS files to be minified and compressed as it can save up to 632.5 kB or 74% of the original size.

Requests Breakdown

Number of requests can be reduced by 84 (84%)

Requests Now

100

After Optimization

16

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

Accessibility Review

ltkh.ee accessibility score

85

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

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

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

ltkh.ee best practices score

69

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

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

ltkh.ee SEO score

92

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

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ltkh.ee can be misinterpreted by Google and other search engines. Our service has detected that Estonian is used on the page, and it does not match the claimed English language. Our system also found out that Ltkh.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 Ltkh. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: