12.6 sec in total
333 ms
11.4 sec
880 ms
Click here to check amazing KDU content for Czech Republic. Otherwise, check out these important facts you probably never knew about kdu.cz
Visit kdu.czWe analyzed Kdu.cz page load time and found that the first response time was 333 ms and then it took 12.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
kdu.cz performance score
name
value
score
weighting
Value12.8 s
0/100
10%
Value13.1 s
0/100
25%
Value19.0 s
0/100
10%
Value650 ms
46/100
30%
Value0.291
41/100
15%
Value17.7 s
4/100
10%
333 ms
381 ms
207 ms
14 ms
453 ms
Our browser made a total of 157 requests to load all elements on the main page. We found that 62% of them (97 requests) were addressed to the original Kdu.cz, 13% (21 requests) were made to Pbs.twimg.com and 4% (6 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (8.2 sec) belongs to the original domain Kdu.cz.
Page size can be reduced by 2.4 MB (14%)
16.7 MB
14.3 MB
In fact, the total size of Kdu.cz main page is 16.7 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. 80% 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 15.0 MB which makes up the majority of the site volume.
Potential reduce by 62.2 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 62.2 kB or 74% of the original size.
Potential reduce by 1.1 MB
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. KDU images are well optimized though.
Potential reduce by 828.0 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 828.0 kB or 72% of the original size.
Potential reduce by 364.1 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. Kdu.cz needs all CSS files to be minified and compressed as it can save up to 364.1 kB or 83% of the original size.
Number of requests can be reduced by 73 (49%)
150
77
The browser has sent 150 CSS, Javascripts, AJAX and image requests in order to completely render the main page of KDU. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 40 to 1 for JavaScripts and from 30 to 1 for CSS and as a result speed up the page load time.
kdu.cz
333 ms
domu
381 ms
GetResource.ashx
207 ms
jquery.min.js
14 ms
jquery-bxslider.css
453 ms
jquery.bxslider.min.js
617 ms
kdu-forum.css
358 ms
meanmenu.css
359 ms
jquery.meanmenu.js
515 ms
jquery-easing.js
455 ms
plugins.js
530 ms
modernizr.js
532 ms
sly.js
728 ms
datepicker.css
589 ms
jquery-ui-1.10.4.custom.min.js
888 ms
kdu-maps.css
642 ms
js
55 ms
marker-with-label.js
656 ms
markerclusterer.js
712 ms
kdu-maps.js
716 ms
jquery-selectbox.css
762 ms
jquery.selectbox-0.2.js
784 ms
jquery-mousewheel-3-0-6-pack.js
337 ms
jquery-fancybox.js
832 ms
jquery-fancybox.css
461 ms
jquery-fancybox-thumbs.css
346 ms
jquery-fancybox-thumbs.js
465 ms
prettyPhoto.css
833 ms
jquery-prettyPhoto.js
840 ms
kdu-gallery.css
880 ms
jquery-timers-1-2.js
897 ms
jquery-galleryview-3-0-dev.js
949 ms
main-gallery-script.js
962 ms
pux-ajax.js
941 ms
kdu-csl.js
1065 ms
kdu-csl-main-page.js
1024 ms
WebResource.axd
915 ms
GetResource.ashx
954 ms
ScriptResource.axd
969 ms
ScriptResource.axd
975 ms
kdu-breadcrumbs.css
936 ms
kdu-searchbox.css
1434 ms
kdu-checkbox.css
1434 ms
kdu-cols-layout.css
1725 ms
kdu-main-nav.css
1439 ms
kdu.css
1805 ms
kdu-persons.css
1822 ms
kdu-gallery.css
1293 ms
kdu-news.css
1557 ms
kdu-related-items.css
1508 ms
kdu-datetime.css
1538 ms
kdu-partners.css
1647 ms
css
23 ms
common.js
22 ms
util.js
71 ms
marker.js
70 ms
Uprchlici.aspx
4340 ms
Veda.aspx
6337 ms
Zemedelstvi.aspx
5823 ms
Kultura.aspx
321 ms
PB_INT.PNG.aspx
1276 ms
MK-deska-mala_104.jpg.aspx
4789 ms
Jurecka2.jpg.aspx
371 ms
Daniel-Herman-se-setkal-s-velvyslancem-SRN.JPG.aspx
558 ms
Vicepremier-Belobradek-jednal-v-Bruselu-s-eurokomisarem-pro-vyzkum-vedu-a-inovace-Moedasem.jpg.aspx
636 ms
Bartosek11.jpg.aspx
1255 ms
Jurecka4.jpg.aspx
1365 ms
Vicepremier-Belobradek-a-predseda-rakouske-Rady-pro-vyzkum-Androsch-po-zasedani-RVVI.jpg.aspx
1409 ms
Herman3.jpg.aspx
1478 ms
Osobni-blog-Pavla-Belobradka.aspx
1548 ms
Osobni-blog-Vita-Ulrycha.aspx
2027 ms
Osobni-blog-Jana-Bartoska.aspx
4017 ms
Osobni-blog-Daniela-Hermana.aspx
2161 ms
Osobni-blog-Jaroslava-Klasky.aspx
2424 ms
Osobni-blog-Pavly-Golasowske.aspx
3602 ms
Osobni-blog-Ivana-Gabala.aspx
4728 ms
Osobni-blog-Miluse-Horske.aspx
4157 ms
Osobni-blog-Jiriho-Carbola.aspx
4321 ms
Osobni-blog-Vaclava-Hampla.aspx
4526 ms
Osobni-blog-Zdenka-Papouska.aspx
8159 ms
Osobni-blog-Michaely-Sojdrove.aspx
4663 ms
Osobni-blog-Pavla-Svobody.aspx
4799 ms
Osobni-blog-Zdechovsky.aspx
4861 ms
Osobni-blog-Ondreje-Zavodskeho.aspx
5692 ms
Osobni-blog-Petra-Vyslouzila.aspx
6469 ms
Osobni-blog-Simona-Hellera.aspx
6511 ms
Osobni-blog-Vladimira-Hanacka.aspx
5843 ms
Osobni-blog-Cyrila-Svobody.aspx
6180 ms
Osobni-blog-Petra-Jurcika.aspx
7200 ms
logo-white.png
6543 ms
sdk.js
15 ms
header-background.jpg
6474 ms
logo.png
6593 ms
widgets.js
143 ms
k3k702ZOKiLJc3WVjuplzNqQynqKV_9Plp7mupa0S4g.ttf
96 ms
MTP_ySUJH_bn48VBG8sNStqQynqKV_9Plp7mupa0S4g.ttf
96 ms
u-WUoqrET9fUeobQW7jkRaCWcynf_cDxXwCLxiixG1c.ttf
95 ms
count.js
93 ms
178 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
143 ms
ndU78UvEfHc
89 ms
xd_arbiter.php
28 ms
xd_arbiter.php
47 ms
LogHits
6463 ms
search.png
6299 ms
www-embed-player-vflfNyN_r.css
69 ms
www-embed-player.js
94 ms
syndication
116 ms
482109115167019008
286 ms
Lrq7Jibxdtv2QOPyDSqncpDfQFNs3PE6SoUrUNh2GTU.js
57 ms
ad_status.js
55 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
39 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
41 ms
hp-button-facebook-26.png
6112 ms
hp-button-rss-26.png
6146 ms
proxy.jpg
82 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
33 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
72 ms
kyLcAlvV_normal.jpg
131 ms
3bcQtvwd_normal.jpeg
48 ms
Cecko_normal.JPG
51 ms
60zHQnFg_normal.jpeg
88 ms
SKv3W0_-_normal.jpg
124 ms
_5ueMW-o_normal.jpeg
50 ms
MTIy5li6_normal.jpeg
138 ms
s-kzLKDn_normal.jpeg
137 ms
KfUcqwH7_normal.jpeg
55 ms
4plVRVYu_normal.jpg
57 ms
--_wVzfC_normal.jpg
59 ms
zKgq833w_normal.jpeg
61 ms
CdiLdiWXIAAHI1p.jpg:large
138 ms
Cdg5BWeXEAAiw-z.jpg
173 ms
CdLpQz3W0AAIHMf.jpg
176 ms
CdLbb81WEAA7H_Q.jpg
151 ms
CdGw2PJWEAAwr7d.png
138 ms
CdBqdO5UYAEZ4J3.jpg
176 ms
CdB3E_VUsAEA7lJ.jpg
172 ms
Cc80CJ4UYAAUSI4.jpg
199 ms
CcEPmI1WIAILQxh.jpg:small
183 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
150 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
174 ms
proxy.jpg
98 ms
link_v1_e64f66f5650df987d97cc5f00c4cb5987f367028.svg
43 ms
hp-button-twitter-26.png
5526 ms
hp-button-zpravodaj-26.png
5515 ms
jot.html
29 ms
sly-slider-prev.png
5997 ms
sly-slider-next.png
5959 ms
arrow-right-blue.png
5892 ms
menu-arrow-down.png
5824 ms
menu-submenu-arrow-up.png
5447 ms
arrow-right-white.png
5698 ms
arrow-left-white.png
5438 ms
bx_loader.gif
4268 ms
stats.js
3 ms
AuthenticationService.Authenticate
215 ms
print.css
110 ms
kdu.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
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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
kdu.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
Missing source maps for large first-party JavaScript
Issues were logged in the Issues panel in Chrome Devtools
kdu.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
CS
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Kdu.cz can be misinterpreted by Google and other search engines. Our service has detected that Czech is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Kdu.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.
kdu.cz
Open Graph description is not detected on the main page of KDU. 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: