6 sec in total
601 ms
4.9 sec
487 ms
Visit proid.cz now to see the best up-to-date ProID content and also check out these interesting facts you probably never knew about proid.cz
Skutečně silná ochrana dat, prostorů a identit. Enterprise řešení pro bezpečnou pracovní identitu, ochranu infrastruktury a kyberbezpečnost v ucelené platformě.
Visit proid.czWe analyzed Proid.cz page load time and found that the first response time was 601 ms and then it took 5.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
proid.cz performance score
name
value
score
weighting
Value5.1 s
9/100
10%
Value6.7 s
7/100
25%
Value10.5 s
7/100
10%
Value2,610 ms
4/100
30%
Value0.125
83/100
15%
Value19.0 s
3/100
10%
601 ms
202 ms
380 ms
343 ms
346 ms
Our browser made a total of 165 requests to load all elements on the main page. We found that 77% of them (127 requests) were addressed to the original Proid.cz, 5% (8 requests) were made to Fonts.gstatic.com and 4% (7 requests) were made to Proid2.piwik.pro. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Proid.cz.
Page size can be reduced by 170.4 kB (6%)
2.8 MB
2.6 MB
In fact, the total size of Proid.cz main page is 2.8 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.7 MB which makes up the majority of the site volume.
Potential reduce by 131.1 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 131.1 kB or 83% of the original size.
Potential reduce by 1.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. ProID images are well optimized though.
Potential reduce by 27.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. This website has mostly compressed JavaScripts.
Potential reduce by 9.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. Proid.cz has all CSS files already compressed.
Number of requests can be reduced by 120 (81%)
148
28
The browser has sent 148 CSS, Javascripts, AJAX and image requests in order to completely render the main page of ProID. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 73 to 1 for JavaScripts and from 49 to 1 for CSS and as a result speed up the page load time.
proid.cz
601 ms
wp-emoji-release.min.js
202 ms
dashicons.min.css
380 ms
extra.min.css
343 ms
styles.css
346 ms
icomoon-the7-font.min.css
347 ms
fontello.min.css
374 ms
js_composer.min.css
545 ms
pum-site-styles.css
461 ms
css
43 ms
main.min.css
642 ms
custom-scrollbar.min.css
463 ms
wpbakery.min.css
490 ms
post-type.min.css
498 ms
css-vars.css
577 ms
custom.css
704 ms
media.css
631 ms
mega-menu.css
619 ms
stripes.css
692 ms
the7-elements-albums-portfolio.css
721 ms
wpml.css
734 ms
post-type-dynamic.css
746 ms
style.css
754 ms
style.min.css
809 ms
slick.min.css
811 ms
icons.css
809 ms
animate.min.css
853 ms
advanced-buttons.min.css
867 ms
content-box.min.css
871 ms
um-crop.css
926 ms
um-modal.css
924 ms
jquery-ui.min.css
934 ms
tipsy.min.css
970 ms
um-raty.min.css
983 ms
fonticons-ii.min.css
993 ms
fonticons-fa.min.css
1047 ms
select2.min.css
1043 ms
7425899.js
66 ms
js
78 ms
api.js
67 ms
um-styles.css
980 ms
um-profile.css
894 ms
um-account.css
766 ms
um-misc.css
771 ms
um-fileupload.css
822 ms
default.css
797 ms
default.date.css
800 ms
css
24 ms
default.time.css
748 ms
simplebar.css
762 ms
um-responsive.css
743 ms
um-old-default.css
784 ms
background-style.min.css
744 ms
jquery.min.js
757 ms
jquery-migrate.min.js
710 ms
language-cookie.js
712 ms
above-the-fold.min.js
703 ms
ultimate-params.min.js
699 ms
custom.min.js
686 ms
slick.min.js
736 ms
jquery-appear.min.js
714 ms
slick-custom.min.js
704 ms
um-gdpr.min.js
712 ms
main.min.js
987 ms
js.cookie.js
892 ms
utm-grabber.js
892 ms
index.js
847 ms
index.js
835 ms
dlm-xhr.min.js
831 ms
js_composer_front.min.js
931 ms
core.min.js
915 ms
pum-site-scripts.js
905 ms
mobile-detect.min.js
922 ms
legacy.min.js
809 ms
jquery-mousewheel.min.js
933 ms
custom-scrollbar.min.js
921 ms
post-type.min.js
927 ms
regenerator-runtime.min.js
919 ms
wp-polyfill.min.js
976 ms
index.js
960 ms
content-box.min.js
958 ms
underscore.min.js
923 ms
wp-util.min.js
927 ms
um-crop.min.js
926 ms
um-modal.min.js
923 ms
um-jquery-form.min.js
921 ms
um-fileupload.js
917 ms
picker.js
972 ms
picker.date.js
980 ms
picker.time.js
953 ms
cs_CZ.js
927 ms
imagesloaded.min.js
938 ms
masonry.min.js
933 ms
jquery.masonry.min.js
987 ms
simplebar.min.js
1004 ms
um-functions.min.js
944 ms
um-responsive.min.js
935 ms
hooks.min.js
931 ms
gtm.js
169 ms
c591de65-d5ee-4b67-b7f5-02777bf0bb5c.js
728 ms
lftracker_v1_YEgkB8lK5nwaep3Z.js
601 ms
icon_digital_identity.png
607 ms
icon_tech_identity.png
673 ms
Asset-2.svg
682 ms
collectedforms.js
375 ms
banner.js
231 ms
conversations-embed.js
373 ms
7425899.js
373 ms
fb.js
372 ms
um-conditional.min.js
776 ms
pxiByp8kv8JHgFVrLEj6Z1xlEN2JQEk.ttf
129 ms
pxiByp8kv8JHgFVrLCz7Z1xlEN2JQEk.ttf
164 ms
pxiByp8kv8JHgFVrLDD4Z1xlEN2JQEk.ttf
264 ms
pxiByp8kv8JHgFVrLGT9Z1xlEN2JQEk.ttf
264 ms
pxiEyp8kv8JHgFVrJJfed3FHGPc.ttf
264 ms
select2.full.min.js
827 ms
cs.js
797 ms
tipsy.min.js
799 ms
i18n.min.js
809 ms
um-raty.min.js
778 ms
um-scripts.min.js
731 ms
um-profile.min.js
818 ms
um-account.min.js
778 ms
ultimate_bg.min.js
809 ms
icomoon-the7-font.ttf
936 ms
proid_black.svg
747 ms
the7-chevron-down.svg
698 ms
the7-chevron-side.svg
859 ms
mockup_phones-1024x800.png
855 ms
recaptcha__en.js
27 ms
cez_logo-1.png
846 ms
kb_logo.png
759 ms
up_logo-1.png
758 ms
fno_logo.png
867 ms
pardubicky_kraj_logo.png
869 ms
vyskov_logo.png
845 ms
Collage_ProID_Mobile_iPhone_android_2024_web.png
1264 ms
bez_nadpisu.png
974 ms
brochure_mockup_organizace.png
961 ms
titulka.mobilni-telefon-iphone-pro-firmy-1.jpg
975 ms
tr-rc.lfeeder.com
113 ms
ppms.js
98 ms
brochure_mockup_02.png
1110 ms
kryptografie-1.jpg
877 ms
brochure_mockup_prumyslovy_podnik.png
1265 ms
logo_proid_white.svg
937 ms
solutions_by_monet_horizontal_grey_dark.png
958 ms
NIS-2_a-novy-zakon.jpg
1098 ms
ppms.php
565 ms
anchor
127 ms
styles__ltr.css
53 ms
recaptcha__en.js
56 ms
2-TaiBnmXCtMzWUZK7LoqXc30IYU9KC_EFLJyzEglQo.js
56 ms
webworker.js
53 ms
logo_48.png
37 ms
KFOmCnqEu92Fr1Mu4mxPKTU1Kg.ttf
8 ms
KFOlCnqEu92Fr1MmEU9fBBc9AMP6lQ.ttf
93 ms
KFOlCnqEu92Fr1MmYUtfBBc9AMP6lQ.ttf
8 ms
recaptcha__en.js
96 ms
ppms.php
92 ms
ppms.php
143 ms
ppms.php
177 ms
ppms.php
169 ms
ppms.php
178 ms
ppms.php
158 ms
proid.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.
[aria-*] attributes do not have valid values
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Image elements do not have [alt] attributes
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
proid.cz best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
proid.cz SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 Proid.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 Proid.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.
proid.cz
Open Graph data is detected on the main page of ProID. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: