7.4 sec in total
459 ms
6.5 sec
400 ms
Click here to check amazing SEMOData content. Otherwise, check out these important facts you probably never knew about semodata.cz
Řešíme problémy s informačními technologiemi, Optimalizujeme systémy, Navrhujeme efektivní řešení na míru, Zdarma Vám vyhodnotíme současný stav a navrhneme řešení, Naše řešení nabízí neomezený počet p...
Visit semodata.czWe analyzed Semodata.cz page load time and found that the first response time was 459 ms and then it took 6.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
semodata.cz performance score
name
value
score
weighting
Value4.9 s
10/100
10%
Value11.4 s
0/100
25%
Value7.0 s
33/100
10%
Value180 ms
91/100
30%
Value0
100/100
15%
Value8.3 s
40/100
10%
459 ms
560 ms
380 ms
5 ms
308 ms
Our browser made a total of 130 requests to load all elements on the main page. We found that 59% of them (77 requests) were addressed to the original Semodata.cz, 15% (19 requests) were made to Google.com and 10% (13 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain Semodata.cz.
Page size can be reduced by 922.8 kB (54%)
1.7 MB
771.6 kB
In fact, the total size of Semodata.cz main page is 1.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. 55% of websites need less resources to load. Javascripts take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 22.4 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 22.4 kB or 75% of the original size.
Potential reduce by 11.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. SEMOData images are well optimized though.
Potential reduce by 754.7 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 754.7 kB or 69% of the original size.
Potential reduce by 133.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. Semodata.cz needs all CSS files to be minified and compressed as it can save up to 133.9 kB or 85% of the original size.
Number of requests can be reduced by 54 (45%)
121
67
The browser has sent 121 CSS, Javascripts, AJAX and image requests in order to completely render the main page of SEMOData. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
semodata.cz
459 ms
www.semodata.cz
560 ms
bootstrap.css
380 ms
bootstrap-glyphicons.css
5 ms
main.css
308 ms
jquery.min.js
6 ms
jquery.hoverIntent.js
314 ms
bootstrap.js
335 ms
jquery.anchor.js
342 ms
jquery.cycle.all.js
340 ms
jquery.jcarousel.js
696 ms
skin.css
690 ms
clearbox.js
685 ms
tiny_mce.js
1077 ms
config.js
687 ms
cookieconsent.min.js
6 ms
cb_style.css
160 ms
cb_config.js
322 ms
cb_language.js
345 ms
cb_core.js
565 ms
bg_page.png
310 ms
bg_top.png
314 ms
logo.png
329 ms
hrp.jpg
512 ms
prg.jpg
514 ms
webapl.jpg
898 ms
dashboard.jpg
1359 ms
divadelni-intranet.jpg
677 ms
firemni-intranet.jpg
980 ms
web-knihovna.jpg
979 ms
CPOK.jpg
1007 ms
NDM.jpg
1199 ms
ridera.jpg
1226 ms
sodexo.jpg
1250 ms
sipka.png
1312 ms
glyphicons-halflings-regular.woff
16 ms
glyphicons-halflings-regular.woff
1502 ms
1.png
1525 ms
2.png
1542 ms
3.png
1642 ms
maps
92 ms
ga.js
8 ms
__utm.gif
16 ms
rot_l_outer.gif
1565 ms
prev_outer.gif
1738 ms
pause_outer.gif
1757 ms
start_outer.gif
1778 ms
next_outer.gif
1805 ms
rot_r_outer.gif
1886 ms
loading.gif
2075 ms
close.png
2080 ms
blank.gif
2079 ms
prev.png
2182 ms
next.png
2200 ms
pause.png
2377 ms
start.png
2399 ms
s_topleft.png
2395 ms
s_top.png
2401 ms
s_topright.png
2605 ms
s_left.png
2612 ms
embed
425 ms
s_right.png
2569 ms
s_btmleft.png
2605 ms
s_btm.png
2597 ms
s_btmright.png
2399 ms
btm_dl.gif
2565 ms
js
60 ms
init_embed.js
42 ms
btm_max.gif
2405 ms
common.js
59 ms
map.js
71 ms
google4.png
102 ms
overlay.js
102 ms
util.js
100 ms
onion.js
102 ms
search_impl.js
99 ms
stats.js
116 ms
openhand_8_8.cur
62 ms
ViewportInfoService.GetViewportInfo
76 ms
ViewportInfoService.GetViewportInfo
55 ms
kh
144 ms
transparent.png
60 ms
controls.js
27 ms
btm_next.gif
2387 ms
ViewportInfoService.GetViewportInfo
81 ms
css
116 ms
entity11.png
75 ms
vt
124 ms
vt
132 ms
vt
111 ms
vt
128 ms
vt
115 ms
vt
112 ms
vt
150 ms
vt
181 ms
vt
162 ms
vt
162 ms
vt
173 ms
vt
166 ms
vt
168 ms
vt
203 ms
vt
189 ms
vt
196 ms
vt
197 ms
vt
212 ms
btm_prev.gif
2295 ms
btm_rot_l.gif
2294 ms
mapcnt6.png
35 ms
tmapctrl.png
24 ms
btm_rot_r.gif
2263 ms
QHD8zigcbDB8aPfIoaupKOvvDin1pK8aKteLpeZ5c0A.ttf
24 ms
RxZJdnzeo3R5zSexge8UUSZ2oysoEQEeKwjgmXLRnTc.ttf
36 ms
Hgo13k-tfSpn0qi1SFdUfSZ2oysoEQEeKwjgmXLRnTc.ttf
48 ms
d-6IYplOFocCacKzxwXSOCZ2oysoEQEeKwjgmXLRnTc.ttf
48 ms
AuthenticationService.Authenticate
18 ms
no_flash.gif
2226 ms
no_html.gif
2218 ms
no_iframe.gif
2269 ms
no_image.gif
2259 ms
no_inner.gif
2256 ms
no_quicktime.gif
2204 ms
no_winmedia.gif
2197 ms
no_winmediaavi.gif
2265 ms
no_winmediamp3.gif
2184 ms
no_winmediampg.gif
2237 ms
no_winmediawav.gif
2225 ms
no_winmediawma.gif
2218 ms
no_winmediawmv.gif
2266 ms
no_youtube.gif
2277 ms
dark-bottom.css
4 ms
semodata.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
Form elements do not have associated labels
Links do not have a discernible name
semodata.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
semodata.cz SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
robots.txt is not valid
EN
CS
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Semodata.cz can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Czech language. Our system also found out that Semodata.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.
semodata.cz
Open Graph description is not detected on the main page of SEMOData. 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: