4.2 sec in total
769 ms
3.2 sec
224 ms
Click here to check amazing Ultratisicovky content. Otherwise, check out these important facts you probably never knew about ultratisicovky.cz
Katalog českých ultratisícovek. Ultratisícovka = ultraprominentní tisícovka = hora s výškou přes 1000 metrů a prominencí přes 100 metrů. Seznamy podle pohoří, žebříčky, slovníček, tabulka pro evidenci...
Visit ultratisicovky.czWe analyzed Ultratisicovky.cz page load time and found that the first response time was 769 ms and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
ultratisicovky.cz performance score
name
value
score
weighting
Value3.8 s
28/100
10%
Value4.3 s
41/100
25%
Value6.1 s
44/100
10%
Value3,200 ms
2/100
30%
Value0
100/100
15%
Value11.8 s
17/100
10%
769 ms
328 ms
23 ms
16 ms
15 ms
Our browser made a total of 123 requests to load all elements on the main page. We found that 13% of them (16 requests) were addressed to the original Ultratisicovky.cz, 24% (29 requests) were made to Maps.googleapis.com and 22% (27 requests) were made to Files.ultratisicovky.cz. The less responsive or slowest element that took the longest time to load (1.6 sec) relates to the external source Files.ultratisicovky.cz.
Page size can be reduced by 626.2 kB (31%)
2.0 MB
1.4 MB
In fact, the total size of Ultratisicovky.cz main page is 2.0 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.1 MB which makes up the majority of the site volume.
Potential reduce by 55.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. This page needs HTML code to be minified as it can gain 10.6 kB, which is 16% 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 55.1 kB or 84% of the original size.
Potential reduce by 26.0 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. Ultratisicovky images are well optimized though.
Potential reduce by 545.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 545.1 kB or 66% of the original size.
Number of requests can be reduced by 42 (37%)
115
73
The browser has sent 115 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ultratisicovky. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
www.ultratisicovky.cz
769 ms
style.css
328 ms
css
23 ms
frontend.package.1-2-189.js
16 ms
obscripts.js
15 ms
analytics.js
20 ms
ga.js
30 ms
collect
27 ms
__utm.gif
33 ms
IconPinU.png
445 ms
red-dot.png
33 ms
Vysok%C3%A1.jpg
684 ms
illustration.png
27 ms
IconXLS.png
432 ms
IconGPX.png
450 ms
IconKML.png
482 ms
bg-patt.jpg
137 ms
bg-patt-light.jpg
243 ms
main-bg.jpg
452 ms
header-line.png
233 ms
header-top-bg-patt.png
233 ms
header-top-bg.jpg
234 ms
fulltext-form-bg.jpg
249 ms
fulltext-form-search-icon.png
357 ms
sys-icon.png
365 ms
box-bg.png
359 ms
%C4%8Cerchov.jpg
679 ms
De%C5%A1tn%C3%A1.jpg
581 ms
Je%C5%99%C3%A1b.jpg
690 ms
Je%C5%A1t%C4%9Bd.jpg
705 ms
Jizera.jpg
738 ms
Kamenec.jpg
820 ms
Kl%C3%ADnovec.jpg
809 ms
Lib%C3%ADn.jpg
809 ms
Lys%C3%A1.jpg
910 ms
Plech%C3%BD.jpg
993 ms
Prad%C4%9Bd.jpg
966 ms
Smrk%20JH.jpg
1145 ms
Smrk%20RH.jpg
1150 ms
Sn%C4%9B%C5%BEka.jpg
1145 ms
Sn%C4%9B%C5%BEn%C3%ADk.jpg
1149 ms
Kle%C5%A5.jpg
1321 ms
Bo%C5%BE%C3%ADdarsk%C3%BD.jpg
1267 ms
Zaje%C4%8D%C3%AD.jpg
1322 ms
%C4%8Cern%C3%A1.jpg
1369 ms
Lu%C4%8Dn%C3%AD.jpg
1417 ms
Vysok%C3%A9%20Kolo.jpg
1391 ms
Boub%C3%ADn.jpg
1584 ms
Hochficht.jpg
1587 ms
Kn%C4%9Bhyn%C4%9B.jpg
1625 ms
Kn%C3%AD%C5%BEec%C3%AD%20stolec.jpg
1587 ms
Smrk%20MB.jpg
1631 ms
yellow-dot.png
33 ms
red.png
34 ms
ms
101 ms
gallery-shadow-960.png
334 ms
gallery-hover.png
363 ms
UyYrYy3ltEffJV9QueSi4ZTvAuddT2xDMbdz0mdLyZY.ttf
71 ms
Q_pTky3Sc3ubRibGToTAYsLtdzs3iyjn_YuT226ZsLU.ttf
110 ms
footerButtonWebnodeHover.png
12 ms
footer-bg-patt.jpg
479 ms
gallery-arrow.png
428 ms
embed
828 ms
rs=ABjfnFW3NcDEAUOJhqBLkb_g7tp8huHPRg
61 ms
css
77 ms
js
81 ms
rs=ABjfnFVj2c6_lUpgxbr93j8J5XcedEcimw
98 ms
rs=ABjfnFVj2c6_lUpgxbr93j8J5XcedEcimw
69 ms
common.js
81 ms
map.js
106 ms
overlay.js
105 ms
157-yellow-dot.png&filter=ff&scale=1.0
151 ms
util.js
150 ms
marker.js
101 ms
geocoder.js
82 ms
controls.js
148 ms
places_impl.js
130 ms
123-red-dot.png&filter=ff&scale=1.0
147 ms
124-red.png&filter=ff&scale=1.0
148 ms
selection_2x-000.png
56 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
129 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
146 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
183 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
211 ms
gen204
44 ms
onion.js
49 ms
openhand_8_8.cur
125 ms
ViewportInfoService.GetViewportInfo
111 ms
stats.js
62 ms
transparent.png
72 ms
mapcnt6.png
44 ms
tmapctrl4.png
67 ms
vt
15 ms
vt
13 ms
vt
90 ms
vt
27 ms
vt
26 ms
vt
34 ms
vt
23 ms
vt
35 ms
vt
37 ms
vt
39 ms
vt
51 ms
vt
56 ms
vt
52 ms
vt
49 ms
vt
53 ms
vt
63 ms
viewer-icons001.png
73 ms
star4.png
80 ms
157-yellow-dot.png&scale=1.0
51 ms
AuthenticationService.Authenticate
52 ms
123-red-dot.png&scale=1.0
18 ms
124-red.png&scale=1.0
19 ms
MyMaps_Icons003.png
22 ms
mymaps_32.png
23 ms
v1_4593b7d7.png
50 ms
google-my-maps-logo-small-001.png
52 ms
kh
65 ms
footerButtonWebnode.png
6 ms
footerButton.png
6 ms
footerButtonHover.png
5 ms
footerBubble.png
6 ms
ultratisicovky.cz accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
ultratisicovky.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
General
Impact
Issue
Detected JavaScript libraries
ultratisicovky.cz SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 Ultratisicovky.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 Ultratisicovky.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.
ultratisicovky.cz
Open Graph description is not detected on the main page of Ultratisicovky. 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: