5.9 sec in total
324 ms
5 sec
553 ms
Welcome to epravo.cz homepage info - get ready to check EPRAVO best content for Czech Republic right away, or after learning these important things about epravo.cz
Váš průvodce pro právo a podnikání (Sbírka zákonů, judikatura, právo, zákony, články, poradny, diskuse, seznam advokátů, judikatura)
Visit epravo.czWe analyzed Epravo.cz page load time and found that the first response time was 324 ms and then it took 5.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
epravo.cz performance score
name
value
score
weighting
Value8.0 s
0/100
10%
Value24.0 s
0/100
25%
Value14.3 s
1/100
10%
Value820 ms
35/100
30%
Value0
100/100
15%
Value17.9 s
4/100
10%
324 ms
1117 ms
109 ms
215 ms
423 ms
Our browser made a total of 109 requests to load all elements on the main page. We found that 56% of them (61 requests) were addressed to the original Epravo.cz, 6% (6 requests) were made to Go.eu.bbelements.com and 5% (5 requests) were made to Bbcdn.go.eu.bbelements.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Epravo.cz.
Page size can be reduced by 186.3 kB (12%)
1.5 MB
1.3 MB
In fact, the total size of Epravo.cz main page is 1.5 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. 60% of websites need less resources to load. Images take 711.3 kB which makes up the majority of the site volume.
Potential reduce by 97.6 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 13.7 kB, which is 11% 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 97.6 kB or 79% of the original size.
Potential reduce by 10.3 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. EPRAVO images are well optimized though.
Potential reduce by 52.4 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. This website has mostly compressed JavaScripts.
Potential reduce by 25.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. Epravo.cz needs all CSS files to be minified and compressed as it can save up to 25.9 kB or 28% of the original size.
Number of requests can be reduced by 54 (53%)
101
47
The browser has sent 101 CSS, Javascripts, AJAX and image requests in order to completely render the main page of EPRAVO. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 36 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
epravo.cz
324 ms
www.epravo.cz
1117 ms
jquery-2.2.4.min.js
109 ms
jquery.simplyscroll.min.js
215 ms
gmap3.js
423 ms
easySlider1.7.js
317 ms
bootstrap.min.js
318 ms
jquery-ui-1.10.4.custom.min.js
530 ms
vimeo-player.js
318 ms
slick.min.js
317 ms
cookieconsent.css
420 ms
cookieconsent.js
428 ms
cookie-manage.js
427 ms
jquery_action.js
428 ms
megamenu.js
525 ms
jquery.simplyscroll.css
525 ms
jquery-ui-1.10.4.custom.css
526 ms
font-awesome.min.css
525 ms
bootstrap.min.css
559 ms
slick.css
628 ms
slick-theme.css
627 ms
style.css
738 ms
css
52 ms
aos.css
51 ms
js
66 ms
js
117 ms
api.js
49 ms
tag.js
601 ms
bb_one2n.js
602 ms
register_modal.css
626 ms
something_in_cart_modal.css
627 ms
bb_one2n.167.65.172.1.js
670 ms
retargeting.js
737 ms
j.php
131 ms
25c2db1d5ce4781d074f248c6.js
352 ms
GdprCmpConsentDataProvider.js
124 ms
BbnautIdDataProvider.js
286 ms
921983550
389 ms
epravo_logo_partner.jpg
182 ms
epravo-e.png
182 ms
imagePreview.php
332 ms
imagePreview.php
336 ms
imagePreview.php
334 ms
imagePreview.php
334 ms
imagePreview.php
435 ms
imagePreview.php
420 ms
imagePreview.php
549 ms
imagePreview.php
607 ms
imagePreview.php
604 ms
imagePreview.php
602 ms
imagePreview.php
682 ms
imagePreview.php
689 ms
imagePreview.php
773 ms
imagePreview.php
849 ms
imagePreview.php
836 ms
imagePreview.php
830 ms
imagePreview.php
1084 ms
imagePreview.php
1088 ms
imagePreview.php
1092 ms
imagePreview.php
1093 ms
imagePreview.php
1093 ms
imagePreview.php
1098 ms
imagePreview.php
1138 ms
imagePreview.php
1179 ms
imagePreview.php
1234 ms
imagePreview.php
1259 ms
imagePreview.php
1287 ms
imagePreview.php
1328 ms
100n.png
1241 ms
recaptcha__en.js
206 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCGPrQ.ttf
135 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpbCGPrQ.ttf
216 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCGPrQ.ttf
218 ms
fontawesome-webfont.woff
1402 ms
render_CatalogBox.php
1449 ms
986 ms
xgemius.js
609 ms
v.gif
133 ms
bbnaut-core-latest.min.js
780 ms
1812818378-1918c3485e2b1bc79898dabca888a8cfa197609a984cbb0c1dbec527d7f7faf6-d
50 ms
bbnaut-lib-2.2.1.min.js
639 ms
429 ms
603 ms
fpdata.js
88 ms
lsget.html
572 ms
b1072151_1.jpg
324 ms
515 ms
L.js
699 ms
b1088238_1.jpg
249 ms
b1088852_1.jpg
457 ms
mazda_urok_balik_vyhod_tiscali_branding_1920x1080_cz_01_vystup.jpg
1058 ms
ajax-loader.gif
273 ms
335 ms
339 ms
335 ms
335 ms
jquery-1.7.min.js
220 ms
easySlider1.7.js
320 ms
135 ms
banner.png
124 ms
ga.js
120 ms
fpdata.js
132 ms
rexdot.js
168 ms
iframe_catalogbox.css
106 ms
f0e4c0acd281fdeaf0255d54471e6b8b%2FAK%20SMARDA.jpg
210 ms
__utm.gif
12 ms
rexdot.js
129 ms
print.css
106 ms
co
609 ms
epravo.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-*] attributes do not match their roles
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
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
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
epravo.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
Page has valid source maps
epravo.cz SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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 Epravo.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 Epravo.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.
epravo.cz
Open Graph data is detected on the main page of EPRAVO. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: