7.8 sec in total
2.5 sec
4.7 sec
600 ms
Click here to check amazing Vaillant content for Czech Republic. Otherwise, check out these important facts you probably never knew about vaillant.cz
Řešení vytápění na míru vašim potřebám: ✔ Více než 140 let zkušeností ✔ Německý vývoj → Objevte naše výrobky!
Visit vaillant.czWe analyzed Vaillant.cz page load time and found that the first response time was 2.5 sec and then it took 5.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
vaillant.cz performance score
name
value
score
weighting
Value3.8 s
28/100
10%
Value5.7 s
17/100
25%
Value8.0 s
22/100
10%
Value730 ms
40/100
30%
Value0
100/100
15%
Value15.3 s
7/100
10%
2462 ms
61 ms
1659 ms
554 ms
94 ms
Our browser made a total of 37 requests to load all elements on the main page. We found that 89% of them (33 requests) were addressed to the original Vaillant.cz, 8% (3 requests) were made to Googletagmanager.com and 3% (1 request) were made to Cdn.consentmanager.net. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Vaillant.cz.
Page size can be reduced by 428.4 kB (15%)
2.9 MB
2.5 MB
In fact, the total size of Vaillant.cz main page is 2.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. 45% of websites need less resources to load. Javascripts take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 399.1 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 399.1 kB or 75% of the original size.
Potential reduce by 28.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. Vaillant images are well optimized though.
Potential reduce by 0 B
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.
Potential reduce by 630 B
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. Vaillant.cz has all CSS files already compressed.
Number of requests can be reduced by 4 (13%)
32
28
The browser has sent 32 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Vaillant. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 5 to 1 for JavaScripts and as a result speed up the page load time.
www.vaillant.cz
2462 ms
eb16754db774.js
61 ms
script.min.js
1659 ms
style.min.css
554 ms
gtm.js
94 ms
logo-header-mobile.svg
191 ms
vaillant-logo-272x72-1888261_1.png
406 ms
HP23-312684_01_image_640w_274h.webp
407 ms
HP21-311037_01_image_640w_274h.webp
551 ms
Professionals20-409310_01.eps_image_640w_274h.jpg
749 ms
PEOPLE18-45513_02.eps_image_640w_274h.jpg
760 ms
231214-vaillant-150-teaser-module-eng_image_640w_274h.jpg
692 ms
google_chrome.svg
619 ms
microsoft_edge.svg
592 ms
mozilla_firefox.svg
820 ms
Vaillant16-Book.woff
928 ms
Vaillant16-Light.woff
912 ms
Vaillant16-Demi.woff
1035 ms
Vaillant16-Heavy.woff
1021 ms
blur-background.jpg
839 ms
az-5-let-zaruka.jpg
1204 ms
az-5-let-zaruka_image_640w_360h.jpg
839 ms
whbc19-308901-02_image_640w_427h.jpg
959 ms
hp18-35186-02_image_640w_427h.jpg
1716 ms
vaillant-service_image_640w_427h.webp
945 ms
HP19_309251_01_1_image_640w_360h.jpg
1221 ms
HP23-912509_01.png_image_640w_480h.png
1027 ms
people18-45591-02-neu_image_640w_640h.webp
1248 ms
videoassist_image_640w_640h.jpg
1119 ms
150years-teaser-image_image_640w_640h.jpg
1256 ms
radiator_image_640w_640h.webp
1445 ms
GettyImages-1308582999_image_640w_640h.jpg
1841 ms
control21-308830-02_image_640w_640h.jpg
1412 ms
hp19-108944-02_image_640w_640h-2.jpg
1441 ms
VAI-Logo-SCREEN_Inverted.svg
1523 ms
js
113 ms
js
45 ms
vaillant.cz accessibility score
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
Buttons do not have an accessible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
vaillant.cz best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
vaillant.cz SEO score
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
Document uses legible font sizes
Tap targets are not sized appropriately
CS
CS
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Vaillant.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 Vaillant.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.
vaillant.cz
Open Graph description is not detected on the main page of Vaillant. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: