4.1 sec in total
332 ms
3.6 sec
238 ms
Welcome to proglas.cz homepage info - get ready to check Proglas best content for Czech Republic right away, or after learning these important things about proglas.cz
Web neziskové, nestátní, nekomerční rozhlasové stanice pro celou informovanou rodinu; staví na křesťanských základech. Nevysílá reklamu. Žije z podpory posluchačů.
Visit proglas.czWe analyzed Proglas.cz page load time and found that the first response time was 332 ms and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
proglas.cz performance score
name
value
score
weighting
Value4.2 s
20/100
10%
Value6.4 s
9/100
25%
Value6.5 s
39/100
10%
Value420 ms
66/100
30%
Value0
100/100
15%
Value6.4 s
60/100
10%
332 ms
1312 ms
314 ms
628 ms
210 ms
Our browser made a total of 121 requests to load all elements on the main page. We found that 79% of them (95 requests) were addressed to the original Proglas.cz, 8% (10 requests) were made to Static.xx.fbcdn.net and 7% (8 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Proglas.cz.
Page size can be reduced by 444.5 kB (41%)
1.1 MB
627.3 kB
In fact, the total size of Proglas.cz main page is 1.1 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. 50% of websites need less resources to load. Images take 530.8 kB which makes up the majority of the site volume.
Potential reduce by 53.3 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 53.3 kB or 76% of the original size.
Potential reduce by 53.6 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. Proglas images are well optimized though.
Potential reduce by 237.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 237.7 kB or 67% of the original size.
Potential reduce by 99.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. Proglas.cz needs all CSS files to be minified and compressed as it can save up to 99.9 kB or 86% of the original size.
Number of requests can be reduced by 51 (43%)
119
68
The browser has sent 119 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Proglas. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
proglas.cz
332 ms
www.proglas.cz
1312 ms
lib.js
314 ms
main.css
628 ms
print.css
210 ms
prettyPhoto.css
419 ms
jquery-ui-1.8.14.custom.css
426 ms
jquery-1.7.2.min.js
731 ms
jquery-ui-1.8.16.custom.min.js
729 ms
jquery.cycle.all.min.js
436 ms
jquery.bxSlider.min.js
639 ms
jquery.prettyPhoto.js
532 ms
jscroller2-1.61.js
535 ms
lib.js
639 ms
jquery.ui.core.min.js
637 ms
jquery.ui.datepicker.min.js
767 ms
all.js
159 ms
hqdefault.jpg
115 ms
027499_56_574581.png
307 ms
nav-1.png
110 ms
play.png
108 ms
phones.png
109 ms
029525_59_598243.jpg
109 ms
029506_59_598046.jpg
107 ms
029492_59_597876.jpg
212 ms
029521_59_598215.jpg
214 ms
029036_59_592893.gif
216 ms
019460_59_465206.jpg
318 ms
028728_59_589118.jpg
218 ms
018780_59_457653.jpg
315 ms
022186_59_510832.jpg
316 ms
025106_59_545469.jpg
317 ms
023224_59_523598.jpg
320 ms
018803_59_457943.jpg
411 ms
navi-prev.png
419 ms
navi-next.png
420 ms
018323_57_452580.gif
423 ms
018367_57_453013.gif
424 ms
019611_60_466753.jpg
425 ms
018343_58_452765.gif
511 ms
018317_58_452551.gif
523 ms
018318_58_452563.gif
524 ms
020020.png
524 ms
019818.png
525 ms
019822.png
531 ms
019823.png
611 ms
027412.png
626 ms
019821.png
627 ms
019825.png
627 ms
019820.png
628 ms
020021.png
637 ms
027411.png
711 ms
029436_02_597336.png
803 ms
ga.js
16 ms
029380_67_596726.gif
803 ms
__utm.gif
32 ms
126 ms
xd_arbiter.php
144 ms
xd_arbiter.php
267 ms
022104_68_493367.png
703 ms
022106_68_493393.jpg
703 ms
022107_68_493406.png
703 ms
022105_68_493380.jpg
707 ms
facebook.png
731 ms
like_box.php
199 ms
twitter.png
626 ms
signaly.png
626 ms
youtube.png
626 ms
google.png
637 ms
top-bnnr.png
611 ms
top-menu.png
635 ms
input.png
634 ms
search.png
634 ms
nav-5.png
634 ms
online.png
642 ms
ebiMDO3r-8l.css
177 ms
jGc-59L_9lo.css
219 ms
q68gy-v_YMF.js
299 ms
FJmpeSpHpjS.js
374 ms
0wM5s1Khldu.js
317 ms
1bNoFZUdlYZ.js
317 ms
noty.png
605 ms
top-menu-main.png
631 ms
top-menu-div.png
631 ms
mainmenu-li.png
629 ms
pout-free.png
630 ms
pout-active-blue.png
642 ms
pout-inactive.png
606 ms
articles.png
632 ms
s1.png
632 ms
s2.png
632 ms
bottom-bnnr.png
632 ms
program-all.png
642 ms
mod.png
605 ms
pout-dot.png
633 ms
bnnr-right.png
634 ms
box-blue.png
634 ms
arrow-big-white.png
635 ms
pout-right.png
641 ms
bottom-box.png
605 ms
10505593_1050930271645044_5559664872587966195_n.png
185 ms
215689_141111642626916_1650645_n.jpg
226 ms
1798385_371332449688992_319780468441269174_n.jpg
267 ms
11146610_10202832478172735_177252126352560471_n.jpg
301 ms
1379841_10150004552801901_469209496895221757_n.jpg
302 ms
24356_1154662885024_6642129_n.jpg
347 ms
12803192_431515717039080_1900277244814729883_n.jpg
304 ms
12705672_1049069441798661_8006559513789351863_n.jpg
364 ms
wL6VQj7Ab77.png
68 ms
s7jcwEQH7Sx.png
68 ms
bg-icon.png
558 ms
bottom-box3.png
558 ms
next.png
560 ms
bottom-box2.png
560 ms
vertical.png
578 ms
arrow-white.png
605 ms
more-green.png
630 ms
more-orange.png
631 ms
more-lightblue.png
632 ms
I6-MnjEovm5.js
45 ms
pQrUxxo5oQp.js
80 ms
proglas.cz accessibility score
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
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
proglas.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
Page has valid source maps
proglas.cz SEO score
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 Proglas.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 Proglas.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.
proglas.cz
Open Graph description is not detected on the main page of Proglas. 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: