4.1 sec in total
353 ms
3.5 sec
225 ms
Visit zavesy.com now to see the best up-to-date Zavesy content and also check out these interesting facts you probably never knew about zavesy.com
japonské steny, rímske rolety, záclony, závesy, kožušinové deky, hliníkové kolajničky
Visit zavesy.comWe analyzed Zavesy.com page load time and found that the first response time was 353 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.
zavesy.com performance score
name
value
score
weighting
Value5.9 s
4/100
10%
Value9.6 s
0/100
25%
Value7.5 s
26/100
10%
Value280 ms
81/100
30%
Value0.034
100/100
15%
Value8.2 s
41/100
10%
353 ms
412 ms
892 ms
107 ms
211 ms
Our browser made a total of 81 requests to load all elements on the main page. We found that 81% of them (66 requests) were addressed to the original Zavesy.com, 4% (3 requests) were made to Google.com and 2% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Zavesy.com.
Page size can be reduced by 233.5 kB (4%)
5.4 MB
5.2 MB
In fact, the total size of Zavesy.com main page is 5.4 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. Images take 5.1 MB which makes up the majority of the site volume.
Potential reduce by 46.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 46.5 kB or 84% of the original size.
Potential reduce by 151.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. Zavesy images are well optimized though.
Potential reduce by 32.4 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 32.4 kB or 13% of the original size.
Potential reduce by 2.9 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. Zavesy.com needs all CSS files to be minified and compressed as it can save up to 2.9 kB or 13% of the original size.
Number of requests can be reduced by 26 (35%)
75
49
The browser has sent 75 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Zavesy. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
zavesy.com
353 ms
zavesy.com
412 ms
www.zavesy.com
892 ms
jquery-ui.min.css
107 ms
default.css
211 ms
screen.css
309 ms
responsive.css
310 ms
slicknav.css
307 ms
js
61 ms
jquery-1.10.2.min.js
444 ms
jquery.countdown.min.js
323 ms
jquery-ui.min.js
563 ms
plugins.js
442 ms
jquery.slicknav.min.js
441 ms
core.js
442 ms
countdown.js
442 ms
homepage.js
511 ms
prettyPhoto.css
512 ms
jquery.prettyPhoto.js
513 ms
conversion_async.js
89 ms
conversion.js
90 ms
js
74 ms
analytics.js
20 ms
collect
12 ms
collect
71 ms
ga-audiences
256 ms
ptsans-regular.woff
312 ms
ga.js
119 ms
084927-1107%20b.jpg
509 ms
085970-1009%20b.jpg
313 ms
041100-0105a.jpg
216 ms
054562-1105%20b.jpg
313 ms
bg-middle.jpg
126 ms
bg-top.jpg
223 ms
logo.png
320 ms
ico-phone.png
331 ms
ico-person.png
406 ms
ico-cart.png
409 ms
button-red-bg.png
409 ms
res-menu.png
423 ms
cz.gif
438 ms
search-bg.png
509 ms
search-separator.png
511 ms
button-white-bg.png
512 ms
baner3.jpg
527 ms
baner%20www.jpg
653 ms
banner1.jpg
1015 ms
baner2.jpg
1140 ms
baner%20sk%20ostr%C3%A1.jpg
714 ms
hotove-zaclony-41082-kyra.jpg
613 ms
panelovy-zaves-84109-poesia.jpg
632 ms
termo-zavesy-85425-wolly.jpg
723 ms
rimske-rolety-91497.jpg
735 ms
vitrazkove-zaclony-54562-zayra.jpg
760 ms
zaclona-schmidt-48102.jpg
816 ms
dekoracny-zaves-neutex-69501-globale.jpg
826 ms
apart-67101-zaclony-online.jpg
839 ms
dekoracny-zaves-neutex-04501-satina.jpg
868 ms
zaclona-metraz-schmidt-25174.jpg
917 ms
bottom-3-bg.png
927 ms
bottom-3-pig.png
943 ms
bottom-3-leaf.png
976 ms
bottom-3-truck.png
1020 ms
platform.js
112 ms
126 ms
__utm.gif
21 ms
bg-footer.png
908 ms
collect
12 ms
ga-audiences
97 ms
20 ms
20_rokov.png
835 ms
10_rokov.png
865 ms
mnozstevna.png
814 ms
vyrocna.png
814 ms
ico-fb.png
823 ms
r_byvanie_sk.png
834 ms
bg-box-bottom.png
866 ms
bg-box-gradient.png
816 ms
icostar-new.png
819 ms
ui-bg_flat_75_ffffff_40x100.png
828 ms
slider-handle.png
823 ms
zavesy.com 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
Form elements do not have associated labels
Links do not have a discernible name
zavesy.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
zavesy.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
![]()
SK
![]()
SK
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Zavesy.com can be misinterpreted by Google and other search engines. Our service has detected that Slovak is used on the page, and it matches the claimed language. Our system also found out that Zavesy.com 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.
zavesy.com
Open Graph description is not detected on the main page of Zavesy. 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: