3.9 sec in total
653 ms
3 sec
279 ms
Click here to check amazing Frendo content. Otherwise, check out these important facts you probably never knew about frendo.cz
Visit frendo.czWe analyzed Frendo.cz page load time and found that the first response time was 653 ms and then it took 3.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
frendo.cz performance score
name
value
score
weighting
Value3.5 s
35/100
10%
Value4.5 s
37/100
25%
Value6.0 s
46/100
10%
Value110 ms
98/100
30%
Value0.228
55/100
15%
Value3.8 s
89/100
10%
653 ms
136 ms
335 ms
260 ms
257 ms
Our browser made a total of 77 requests to load all elements on the main page. We found that 96% of them (74 requests) were addressed to the original Frendo.cz, 1% (1 request) were made to Ajax.googleapis.com and 1% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Frendo.cz.
Page size can be reduced by 526.3 kB (50%)
1.0 MB
519.1 kB
In fact, the total size of Frendo.cz main page is 1.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. 35% of websites need less resources to load. Images take 403.3 kB which makes up the majority of the site volume.
Potential reduce by 30.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 4.6 kB, which is 12% 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 30.9 kB or 82% of the original size.
Potential reduce by 34.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. Frendo images are well optimized though.
Potential reduce by 287.6 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 287.6 kB or 72% of the original size.
Potential reduce by 173.8 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. Frendo.cz needs all CSS files to be minified and compressed as it can save up to 173.8 kB or 85% of the original size.
Number of requests can be reduced by 43 (57%)
75
32
The browser has sent 75 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Frendo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and from 27 to 1 for CSS and as a result speed up the page load time.
frendo.cz
653 ms
style.css
136 ms
typo.css
335 ms
modal.css
260 ms
system.css
257 ms
general.css
254 ms
addons.css
246 ms
layout.css
251 ms
template.css
479 ms
usertools.css
367 ms
css3.css
368 ms
mega.css
369 ms
k2.css
608 ms
typo.css
443 ms
layout.css
482 ms
template.css
600 ms
css3.css
486 ms
mega.css
554 ms
mod_jacontentslider.css
604 ms
mod_jaslideshowlite.css
603 ms
k2.css
610 ms
typo.css
665 ms
template.css
716 ms
mega.css
715 ms
mod_jacontentslider.css
717 ms
mod_jaslideshowlite.css
720 ms
mootools-core.js
1084 ms
core.js
778 ms
mootools-more.js
1409 ms
script.js
831 ms
modal.js
832 ms
jquery.min.js
51 ms
k2.noconflict.js
845 ms
k2.js
906 ms
caption.js
952 ms
core.js
958 ms
mega.js
960 ms
css
24 ms
ja_contentslider.js
1045 ms
script.js
984 ms
system.css
835 ms
bd.png
119 ms
logo.png
119 ms
mainnav-bg.png
121 ms
grad.png
113 ms
home.png
147 ms
arrow3.png
120 ms
mega-line.gif
225 ms
menu-icon2.png
234 ms
readmore-hover.png
232 ms
menu-icon1.png
258 ms
menu-icon5.png
257 ms
sl-2_950_350.jpg
381 ms
sl-3_950_350.jpg
446 ms
sl-1_950_350.jpg
491 ms
story-icon1.png
399 ms
story-icon2.png
399 ms
story-icon5.png
401 ms
story-icon3.png
498 ms
web1_220_165.png
527 ms
web3_220_165.png
749 ms
web4_220_165.png
633 ms
web5_220_165.png
666 ms
web6_220_165.png
724 ms
icon-search.png
609 ms
slide-mask.png
625 ms
slide-prev.gif
748 ms
slide-next.gif
757 ms
g46X4VH_KHOWAAa-HpnGPi3USBnSvpkopQaUR-2r7iU.ttf
12 ms
icon-module1.png
741 ms
icon-module2.png
753 ms
icon-module3.png
813 ms
icon-module4.png
839 ms
readmore.png
854 ms
bc-lr.png
833 ms
icon-home.png
817 ms
slideloading.gif
814 ms
frendo.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
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
Form elements do not have associated labels
frendo.cz best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
frendo.cz SEO score
CS
CS
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Frendo.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 Frendo.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.
frendo.cz
Open Graph description is not detected on the main page of Frendo. 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: