3.2 sec in total
417 ms
2.6 sec
174 ms
Visit pkr.cz now to see the best up-to-date Pkr content and also check out these interesting facts you probably never knew about pkr.cz
REALITY KRKONOŠE
Visit pkr.czWe analyzed Pkr.cz page load time and found that the first response time was 417 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
pkr.cz performance score
name
value
score
weighting
Value4.0 s
22/100
10%
Value9.5 s
0/100
25%
Value9.4 s
12/100
10%
Value0 ms
100/100
30%
Value0.268
46/100
15%
Value9.9 s
27/100
10%
417 ms
731 ms
88 ms
98 ms
290 ms
Our browser made a total of 57 requests to load all elements on the main page. We found that 98% of them (56 requests) were addressed to the original Pkr.cz, 2% (1 request) were made to Googleadservices.com. The less responsive or slowest element that took the longest time to load (924 ms) belongs to the original domain Pkr.cz.
Page size can be reduced by 114.1 kB (22%)
517.0 kB
402.9 kB
In fact, the total size of Pkr.cz main page is 517.0 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 40% of websites need less resources to load. Images take 309.5 kB which makes up the majority of the site volume.
Potential reduce by 28.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 5.7 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 28.9 kB or 84% of the original size.
Potential reduce by 52.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. Obviously, Pkr needs image optimization as it can save up to 52.8 kB or 17% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 20.3 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 20.3 kB or 15% of the original size.
Potential reduce by 12.2 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. Pkr.cz needs all CSS files to be minified and compressed as it can save up to 12.2 kB or 31% of the original size.
Number of requests can be reduced by 33 (61%)
54
21
The browser has sent 54 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pkr. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
pkr.cz
417 ms
www.pkr.cz
731 ms
conversion_async.js
88 ms
format.css
98 ms
boxes.css
290 ms
modules.css
194 ms
thickbox.css
197 ms
lightbox.css
196 ms
slider.css
199 ms
date.css
197 ms
globals.js.php
323 ms
header.js
295 ms
main.js
295 ms
ajax.js
295 ms
elements.js
296 ms
swfobject.js
384 ms
hover.js
386 ms
jquery-1.7.min.js
585 ms
lib_realityass.js
432 ms
loader_texty.js
433 ms
jquery.ui.js
516 ms
ui.tabs.js
478 ms
loader_hp-tabs.js
479 ms
jquery.slider.js
486 ms
loader_slider.js
484 ms
loader_ankety.js
575 ms
jquery.scrollTo.js
575 ms
jquery.form.js
583 ms
jquery.custom.js
600 ms
MainMenu.js
610 ms
jquery.finally.init.js
670 ms
body.jpg
381 ms
main_cont.gif
303 ms
top.jpg
671 ms
logo2.png
303 ms
logo.png
402 ms
li.png
370 ms
en.png
369 ms
cz.png
377 ms
li_top2.gif
385 ms
li_top.gif
464 ms
vloz_nab.jpg
464 ms
tn_top_filename_16985.jpg
474 ms
tn_top_filename_16803.jpeg
482 ms
tn_top_filename_16797.jpg
495 ms
tn_top_filename_16604.jpg
653 ms
tn_top_filename_13511.jpg
558 ms
tn_top_filename_12595.jpg
570 ms
tn_top_filename_17009.bmp
868 ms
tn_top_filename_13228.jpg
591 ms
tn_top_filename_16606.jpg
747 ms
h3-left.png
666 ms
li.gif
657 ms
submit.gif
718 ms
ubuntu-r-webfont.woff
924 ms
vloz_pop.jpg
689 ms
print_css.css
99 ms
pkr.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.
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
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
pkr.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
pkr.cz SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
CS
CS
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pkr.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 Pkr.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.
pkr.cz
Open Graph description is not detected on the main page of Pkr. 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: