Tools & Wizards About Us
klekari.cz screenshot

Report Summary

  • 47

    Performance

    Renders faster than
    65% of other websites

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

klekari.cz

Webové řešení pro lékaře, doktory a zdravotníky | WebProLékaře.cz - www.webprolekare.cz

Page Load Speed

4.2 sec in total

First Response

510 ms

Resources Loaded

3.3 sec

Page Rendered

351 ms

klekari.cz screenshot

About Website

Welcome to klekari.cz homepage info - get ready to check Klekari best content right away, or after learning these important things about klekari.cz

WebProLékaře.cz - Webové řešení pro lékaře, doktory a zdravotníky. Nabídka tvorby a správy webových stránek se specializací na lékaře, doktory, zdravotníky a oblast medicíny a zdravotnictví.

Visit klekari.cz

Key Findings

We analyzed Klekari.cz page load time and found that the first response time was 510 ms and then it took 3.7 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

klekari.cz performance score

47

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

36/100

10%

LCP (Largest Contentful Paint)

Value14.7 s

0/100

25%

SI (Speed Index)

Value5.3 s

57/100

10%

TBT (Total Blocking Time)

Value70 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0.761

5/100

15%

TTI (Time to Interactive)

Value5.4 s

71/100

10%

Network Requests Diagram

klekari.cz

510 ms

webprolekare.cz

741 ms

css

39 ms

bootstrap.min.css

109 ms

flexslider.css

212 ms

Our browser made a total of 53 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Klekari.cz, 85% (45 requests) were made to Webprolekare.cz and 9% (5 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Webprolekare.cz.

Page Optimization Overview & Recommendations

Page size can be reduced by 3.7 MB (88%)

Content Size

4.2 MB

After Optimization

514.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Klekari.cz main page is 4.2 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. 35% of websites need less resources to load. Images take 4.0 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 25.2 kB

  • Original 30.6 kB
  • After minification 22.0 kB
  • After compression 5.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 8.6 kB, which is 28% 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 25.2 kB or 82% of the original size.

Image Optimization

-91%

Potential reduce by 3.6 MB

  • Original 4.0 MB
  • After minification 345.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, Klekari needs image optimization as it can save up to 3.6 MB or 91% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-1%

Potential reduce by 1.7 kB

  • Original 140.3 kB
  • After minification 140.3 kB
  • After compression 138.6 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

-9%

Potential reduce by 2.4 kB

  • Original 27.6 kB
  • After minification 27.6 kB
  • After compression 25.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. Klekari.cz has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 22 (49%)

Requests Now

45

After Optimization

23

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

klekari.cz

klekari.cz

510 ms

webprolekare.cz

webprolekare.cz

741 ms

css

css

39 ms

bootstrap.min.css

bootstrap.min.css

109 ms

flexslider.css

flexslider.css

212 ms

animations.css

animations.css

297 ms

font-awesome.min.css

font-awesome.min.css

296 ms

jquery.flickr.css

jquery.flickr.css

293 ms

prettyPhoto.css

prettyPhoto.css

293 ms

main.css

main.css

308 ms

modernizr-2.6.2-respond-1.1.0.min.js

modernizr-2.6.2-respond-1.1.0.min.js

315 ms

jquery.js

jquery.js

498 ms

css3-animate-it.js

css3-animate-it.js

395 ms

jquery.flexslider-min.js

jquery.flexslider-min.js

393 ms

jquery.sticky.js

jquery.sticky.js

397 ms

jquery.waitforimages.js

jquery.waitforimages.js

415 ms

jflickrfeed.min.js

jflickrfeed.min.js

418 ms

jquery.prettyPhoto.js

jquery.prettyPhoto.js

496 ms

js

js

70 ms

main.js

main.js

509 ms

pattern.png

pattern.png

190 ms

logo_webprolekare2.png

logo_webprolekare2.png

193 ms

i1.png

i1.png

192 ms

i2.png

i2.png

259 ms

i3.png

i3.png

260 ms

i4.png

i4.png

262 ms

i5.png

i5.png

267 ms

BG1.jpg

BG1.jpg

282 ms

child4.png

child4.png

291 ms

child5.png

child5.png

357 ms

child6.png

child6.png

360 ms

child1.png

child1.png

361 ms

child2.png

child2.png

370 ms

child3.png

child3.png

381 ms

t1.png

t1.png

397 ms

t2.png

t2.png

461 ms

t3.png

t3.png

463 ms

logo_webuju.png

logo_webuju.png

556 ms

webhostuj_logo_tmave.png

webhostuj_logo_tmave.png

471 ms

do_logo.png

do_logo.png

482 ms

vyberem_logo.png

vyberem_logo.png

501 ms

pse_logo.png

pse_logo.png

563 ms

prostezacni_logo.png

prostezacni_logo.png

562 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

22 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

30 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

36 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

40 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf

41 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

726 ms

bg01.png

bg01.png

400 ms

slider2.png

slider2.png

1124 ms

slider1.png

slider1.png

1050 ms

slider3.jpg

slider3.jpg

759 ms

Accessibility Review

klekari.cz accessibility score

68

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.

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

klekari.cz best practices score

83

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

SEO Factors

klekari.cz SEO score

92

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

Language and Encoding

  • Language Detected

    CS

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Klekari.cz can be misinterpreted by Google and other search engines. Our service has detected that Czech 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 Klekari.cz 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

klekari.cz

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