4.2 sec in total
316 ms
3.3 sec
551 ms
Click here to check amazing Loc content. Otherwise, check out these important facts you probably never knew about loc.cz
Visit loc.czWe analyzed Loc.cz page load time and found that the first response time was 316 ms and then it took 3.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
loc.cz performance score
name
value
score
weighting
Value4.2 s
19/100
10%
Value4.3 s
41/100
25%
Value5.3 s
58/100
10%
Value10 ms
100/100
30%
Value0.126
83/100
15%
Value4.2 s
85/100
10%
316 ms
620 ms
137 ms
222 ms
231 ms
Our browser made a total of 155 requests to load all elements on the main page. We found that 74% of them (115 requests) were addressed to the original Loc.cz, 10% (15 requests) were made to Maps.google.com and 6% (10 requests) were made to Maps.gstatic.com. The less responsive or slowest element that took the longest time to load (749 ms) belongs to the original domain Loc.cz.
Page size can be reduced by 663.6 kB (29%)
2.3 MB
1.6 MB
In fact, the total size of Loc.cz main page is 2.3 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 85.9 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 29.8 kB, which is 30% 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 85.9 kB or 88% of the original size.
Potential reduce by 73.5 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. Loc images are well optimized though.
Potential reduce by 450.8 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 450.8 kB or 60% of the original size.
Potential reduce by 53.4 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. Loc.cz needs all CSS files to be minified and compressed as it can save up to 53.4 kB or 84% of the original size.
Number of requests can be reduced by 36 (25%)
146
110
The browser has sent 146 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Loc. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 29 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
loc.cz
316 ms
www.loc.cz
620 ms
tipsy.css
137 ms
flexslider.css
222 ms
jquery.fancybox-1.3.4.css
231 ms
css
25 ms
base.css
223 ms
dark.css
228 ms
media.queries.css
231 ms
my.css
257 ms
jquery-1.7.1.min.js
453 ms
html5shiv.js
346 ms
jquery.tipsy.js
338 ms
jquery.mobilemenu.js
342 ms
jquery.infieldlabel.js
344 ms
jquery.fancybox-1.3.4.pack.js
363 ms
jquery.easing-1.3.pack.js
444 ms
js
20 ms
jquery.css-rorate-scale.js
488 ms
jquery.quicksand.js
487 ms
jquery.twitter.js
488 ms
jquery.flexslider-min.js
492 ms
jquery.ui.totop.min.js
560 ms
jquery.nav.min.js
558 ms
scrolio.js
559 ms
cookieconsent.min.js
5 ms
dark-stripe.png
165 ms
logo.png
165 ms
image.png
169 ms
image.png
203 ms
image.png
170 ms
image.png
205 ms
image.png
262 ms
image.png
263 ms
image.png
309 ms
image.png
310 ms
image.png
310 ms
image.png
306 ms
image.png
350 ms
image.png
351 ms
image.png
397 ms
image.png
394 ms
image.png
394 ms
image.png
397 ms
image.png
474 ms
image.png
451 ms
image.png
519 ms
image.png
493 ms
image.png
502 ms
image.png
524 ms
image.png
564 ms
image.png
589 ms
image.png
606 ms
image.png
610 ms
image.png
627 ms
image.png
633 ms
image.png
672 ms
image.png
696 ms
image.png
714 ms
image.png
718 ms
image.png
749 ms
ga.js
50 ms
common.js
13 ms
map.js
13 ms
util.js
13 ms
geocoder.js
12 ms
image.png
672 ms
StaticMapService.GetMapImage
134 ms
__utm.gif
71 ms
onion.js
48 ms
openhand_8_8.cur
31 ms
AuthenticationService.Authenticate
234 ms
GeocodeService.Search
102 ms
foundation-icons-general.woff
623 ms
foundation-icons-social.woff
649 ms
image.png
668 ms
ViewportInfoService.GetViewportInfo
81 ms
stats.js
26 ms
controls.js
20 ms
image.png
630 ms
image.png
670 ms
image.png
659 ms
transparent.png
30 ms
css
53 ms
image.png
643 ms
image.png
658 ms
google4.png
47 ms
marker.js
39 ms
mapcnt6.png
41 ms
sv5.png
42 ms
image.png
632 ms
image.png
643 ms
image.png
672 ms
image.png
681 ms
tmapctrl.png
19 ms
cb_scout5.png
36 ms
tmapctrl4.png
18 ms
imgs8.png
19 ms
vt
20 ms
vt
19 ms
vt
27 ms
vt
26 ms
vt
26 ms
vt
19 ms
vt
26 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
14 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
15 ms
Hgo13k-tfSpn0qi1SFdUfT8E0i7KZn-EPnyo3HZu7kw.woff
24 ms
d-6IYplOFocCacKzxwXSOD8E0i7KZn-EPnyo3HZu7kw.woff
23 ms
image.png
661 ms
image.png
676 ms
image.png
657 ms
image.png
663 ms
image.png
691 ms
image.png
695 ms
spotlight-poi.png
14 ms
image.png
667 ms
image.png
660 ms
image.png
663 ms
image.png
664 ms
image.png
677 ms
image.png
681 ms
image.png
662 ms
image.png
653 ms
image.png
660 ms
image.png
664 ms
image.png
676 ms
image.png
689 ms
image.png
684 ms
image.png
660 ms
image.png
665 ms
image.png
666 ms
image.png
687 ms
image.png
681 ms
image.png
671 ms
image.png
659 ms
image.png
662 ms
image.png
667 ms
image.png
683 ms
image.png
670 ms
image.png
672 ms
image.png
662 ms
image.png
663 ms
image.png
663 ms
image.png
669 ms
image.png
662 ms
image.png
671 ms
image.png
663 ms
image.png
656 ms
image.png
669 ms
image.png
670 ms
image.png
663 ms
image.png
685 ms
image.png
668 ms
dark-bottom.css
3 ms
loc.cz accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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.
loc.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
loc.cz 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
N/A
CS
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Loc.cz can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is Czech. Our system also found out that Loc.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.
loc.cz
Open Graph description is not detected on the main page of Loc. 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: