Tools & Wizards About Us
v-h.cz screenshot

Report Summary

  • 51

    Performance

    Renders faster than
    69% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 88% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

v-h.cz

V-H Limousines and Vans s.r.o.

Page Load Speed

5.4 sec in total

First Response

441 ms

Resources Loaded

4.7 sec

Page Rendered

245 ms

v-h.cz screenshot

About Website

Visit v-h.cz now to see the best up-to-date V H content and also check out these interesting facts you probably never knew about v-h.cz

V-H Limousines and Vans s.r.o.

Visit v-h.cz

Key Findings

We analyzed V-h.cz page load time and found that the first response time was 441 ms and then it took 4.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

v-h.cz performance score

51

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.9 s

11/100

10%

LCP (Largest Contentful Paint)

Value7.5 s

4/100

25%

SI (Speed Index)

Value9.9 s

10/100

10%

TBT (Total Blocking Time)

Value160 ms

94/100

30%

CLS (Cumulative Layout Shift)

Value0.018

100/100

15%

TTI (Time to Interactive)

Value7.6 s

47/100

10%

Network Requests Diagram

v-h.cz

441 ms

v-h.cz

469 ms

www.v-h.cz

434 ms

www.v-h.cz

2075 ms

style.css

544 ms

Our browser made a total of 35 requests to load all elements on the main page. We found that 60% of them (21 requests) were addressed to the original V-h.cz, 34% (12 requests) were made to Fonts.gstatic.com and 6% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain V-h.cz.

Page Optimization Overview & Recommendations

Page size can be reduced by 178.7 kB (29%)

Content Size

609.6 kB

After Optimization

430.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of V-h.cz main page is 609.6 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. Javascripts take 196.1 kB which makes up the majority of the site volume.

HTML Optimization

-92%

Potential reduce by 137.1 kB

  • Original 149.6 kB
  • After minification 135.5 kB
  • After compression 12.5 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 137.1 kB or 92% of the original size.

Image Optimization

-1%

Potential reduce by 2.2 kB

  • Original 151.7 kB
  • After minification 149.4 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. V H images are well optimized though.

JavaScript Optimization

-10%

Potential reduce by 20.4 kB

  • Original 196.1 kB
  • After minification 196.1 kB
  • After compression 175.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. This website has mostly compressed JavaScripts.

CSS Optimization

-17%

Potential reduce by 19.0 kB

  • Original 112.2 kB
  • After minification 112.2 kB
  • After compression 93.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. V-h.cz needs all CSS files to be minified and compressed as it can save up to 19.0 kB or 17% of the original size.

Requests Breakdown

Number of requests can be reduced by 5 (29%)

Requests Now

17

After Optimization

12

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

v-h.cz

v-h.cz

441 ms

v-h.cz

v-h.cz

469 ms

www.v-h.cz

www.v-h.cz

434 ms

www.v-h.cz

www.v-h.cz

2075 ms

style.css

style.css

544 ms

css

css

35 ms

css

css

53 ms

logo-v-h-limvans.png

logo-v-h-limvans.png

326 ms

jsminBottom.js

jsminBottom.js

995 ms

divider.png

divider.png

124 ms

cz.svg

cz.svg

122 ms

arrLang.png

arrLang.png

218 ms

liBefore.png

liBefore.png

216 ms

bg-usp.jpg

bg-usp.jpg

530 ms

footerBg.jpg

footerBg.jpg

535 ms

prejit.svg

prejit.svg

327 ms

phone.svg

phone.svg

326 ms

envelope.svg

envelope.svg

328 ms

facebookW.svg

facebookW.svg

436 ms

twitterW.svg

twitterW.svg

438 ms

instagramW.svg

instagramW.svg

439 ms

iconfnt.otf

iconfnt.otf

482 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCGPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCGPrQ.ttf

23 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCGPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCGPrQ.ttf

31 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCGPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCGPrQ.ttf

53 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpbCGPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpbCGPrQ.ttf

61 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCGPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCGPrQ.ttf

61 ms

KtkpALCRZonmalTgyPmRfvWi.ttf

KtkpALCRZonmalTgyPmRfvWi.ttf

61 ms

Ktk0ALCRZonmalTgyPmRfs1WwETX.ttf

Ktk0ALCRZonmalTgyPmRfs1WwETX.ttf

61 ms

Ktk0ALCRZonmalTgyPmRfs0OwUTX.ttf

Ktk0ALCRZonmalTgyPmRfs0OwUTX.ttf

91 ms

Ktk0ALCRZonmalTgyPmRfs1qwkTX.ttf

Ktk0ALCRZonmalTgyPmRfs1qwkTX.ttf

91 ms

Ktk0ALCRZonmalTgyPmRfs16x0TX.ttf

Ktk0ALCRZonmalTgyPmRfs16x0TX.ttf

79 ms

Ktk0ALCRZonmalTgyPmRfs0exkTX.ttf

Ktk0ALCRZonmalTgyPmRfs0exkTX.ttf

79 ms

Ktk0ALCRZonmalTgyPmRfs0CxUTX.ttf

Ktk0ALCRZonmalTgyPmRfs0CxUTX.ttf

78 ms

icons.woff

icons.woff

613 ms

Accessibility Review

v-h.cz accessibility score

96

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

Links do not have a discernible name

Best Practices

v-h.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

High

Missing source maps for large first-party JavaScript

SEO Factors

v-h.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

    CS

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise V-h.cz can be misinterpreted by Google and other search engines. Our service has detected that Czech is used on the page, and it matches the claimed language. Our system also found out that V-h.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

v-h.cz

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