3.8 sec in total
297 ms
2.9 sec
607 ms
Welcome to 60.cz homepage info - get ready to check 60 best content for Czech Republic right away, or after learning these important things about 60.cz
60.cz
Visit 60.czWe analyzed 60.cz page load time and found that the first response time was 297 ms and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
60.cz performance score
name
value
score
weighting
Value4.7 s
12/100
10%
Value13.1 s
0/100
25%
Value9.7 s
11/100
10%
Value2,440 ms
5/100
30%
Value0
100/100
15%
Value17.5 s
4/100
10%
297 ms
581 ms
393 ms
398 ms
401 ms
Our browser made a total of 73 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original 60.cz, 68% (50 requests) were made to Cdn.myshoptet.com and 5% (4 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (819 ms) relates to the external source Cdn.myshoptet.com.
Page size can be reduced by 237.4 kB (13%)
1.8 MB
1.6 MB
In fact, the total size of 60.cz main page is 1.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. 70% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.
Potential reduce by 197.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. This page needs HTML code to be minified as it can gain 61.3 kB, which is 27% 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 197.5 kB or 86% of the original size.
Potential reduce by 7.8 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. 60 images are well optimized though.
Potential reduce by 32.1 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.1 kB or 22% of the original size.
Number of requests can be reduced by 37 (59%)
63
26
The browser has sent 63 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 60. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
60.cz
297 ms
www.60.cz
581 ms
source-sans-3.css
393 ms
open-sans.css
398 ms
font-shoptet.css
401 ms
main-11.less.bf7acedcd7f4f5a87780.css
590 ms
368427_7.css
404 ms
LBX-339797.js
29 ms
368427_12.css
404 ms
css
40 ms
css
57 ms
fonts.css
484 ms
slick.css
490 ms
styles.css
612 ms
voltz.css
496 ms
responsive.css
497 ms
js
61 ms
sdk.js
26 ms
jquery-1.11.3.min.js
618 ms
main-3g.js.6dcb879ed3595fa234ac.js
781 ms
datepicker-cs.js
524 ms
rc.js
698 ms
368427_datalayer_7.js
524 ms
368427_7.js
618 ms
shoptet.js
392 ms
368427_datalayer_12.js
617 ms
368427_12.js
697 ms
bundle-v2.js
699 ms
slick.js
697 ms
script.js
697 ms
voltz.js
697 ms
autocomplete.js
25 ms
autocomplete.css
36 ms
60.js
292 ms
recorder.js
252 ms
gjs.php
666 ms
logo_60cz_eshop-2.png
234 ms
folder.svg
250 ms
banner_lodes_sky-fall_random-solo.jpg
408 ms
slamp_veli_aurea_banner.jpg
335 ms
diesel_urban_concrete_25-cluster-room-set_04.jpg
334 ms
kolekce-orbit.jpg
407 ms
flos-kolekce.jpg
406 ms
kolekce-urail.jpg
404 ms
nemo_lighting_serie_drop.jpg
409 ms
slamp_clizia_suspension__mama_non_mama_gold.jpg
819 ms
kolekce-artemide-tolomeo-1.jpg
687 ms
plug_and_shine_paulmann.jpg
598 ms
41784.jpg
499 ms
84076.jpg
499 ms
41106-4.jpg
505 ms
7626-3.jpg
596 ms
patrik.png
695 ms
0316-230-osvetleni-detskeho-pokoje_(1).png
694 ms
shoptetLogo.svg
689 ms
dec-logo.png
639 ms
footer-dec.png
729 ms
sdk.js
28 ms
js
53 ms
js
121 ms
Matter-Regular.woff
652 ms
Matter-Medium.woff
642 ms
Matter-Light.woff
641 ms
Matter-SemiBold.woff
653 ms
Matter-Bold.woff
762 ms
Matter-Heavy.woff
763 ms
shoptet.woff
763 ms
js
122 ms
loader.js
147 ms
trending_queries
99 ms
analytics.js
44 ms
landing
98 ms
collect
4 ms
60.cz accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
ARIA IDs are not unique
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
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
Image elements do not have [alt] attributes
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
List items (<li>) are not contained within <ul> or <ol> parent elements.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
60.cz 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
Browser errors were logged to the console
Page has valid source maps
60.cz SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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 60.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 60.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.
60.cz
Open Graph data is detected on the main page of 60. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: