2.3 sec in total
346 ms
1.7 sec
222 ms
Welcome to xperd.cz homepage info - get ready to check Xperd best content right away, or after learning these important things about xperd.cz
Dušan Pernický is on Facebook. Join Facebook to connect with Dušan Pernický and others you may know. Facebook gives people the power to share and makes...
Visit xperd.czWe analyzed Xperd.cz page load time and found that the first response time was 346 ms and then it took 1.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
xperd.cz performance score
name
value
score
weighting
Value4.5 s
15/100
10%
Value4.7 s
32/100
25%
Value4.5 s
72/100
10%
Value0 ms
100/100
30%
Value0.026
100/100
15%
Value4.5 s
82/100
10%
346 ms
322 ms
38 ms
72 ms
47 ms
Our browser made a total of 68 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Xperd.cz, 60% (41 requests) were made to Static.xx.fbcdn.net and 25% (17 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (736 ms) relates to the external source External.xx.fbcdn.net.
Page size can be reduced by 74.2 kB (43%)
171.5 kB
97.3 kB
In fact, the total size of Xperd.cz main page is 171.5 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. 70% of websites need less resources to load. HTML takes 90.0 kB which makes up the majority of the site volume.
Potential reduce by 67.5 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 67.5 kB or 75% of the original size.
Potential reduce by 6.7 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. Xperd images are well optimized though.
Number of requests can be reduced by 33 (50%)
66
33
The browser has sent 66 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Xperd. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
xperd.cz
346 ms
xperd
322 ms
jri1RqGgcfE.css
38 ms
DY6CRC1i1Bl.css
72 ms
kyEKgjk51ZE.css
47 ms
b_nc0vjtAUF.css
44 ms
xgj7bXhJNEH.css
48 ms
sFTVm4Wm5AN.css
61 ms
VFoZ1f4h99C.css
61 ms
RlvWmF7gpVx.css
55 ms
tSgg1_QsZ29.css
84 ms
q68gy-v_YMF.js
103 ms
event
393 ms
58191_106097126117872_1735237_n.jpg
202 ms
info_24.png
58 ms
safe_image.php
736 ms
FJmpeSpHpjS.js
165 ms
1bNoFZUdlYZ.js
109 ms
_UYztdBNTjs.js
107 ms
1FCa-btixu2.js
110 ms
7BE0CZr3HTs.js
110 ms
RTHSWgdzleR.js
107 ms
Oagsvfb4VWi.js
237 ms
OZFAYTv-ZUg.js
238 ms
N6x5BPT1p97.js
237 ms
LTv6ZK-5zxz.js
243 ms
R_PGrgD5ZlT.js
236 ms
J0ZuTxeV0vD.js
239 ms
Xa8aKOYq3zI.js
250 ms
yBzWdmXwoNV.js
244 ms
IjqSyiwKeaX.js
244 ms
RJ-tBRDclXF.js
249 ms
HgJbVwzBr8E.js
250 ms
67L4LyUDskl.js
342 ms
kAwRfubFq5y.js
342 ms
safe_image.php
702 ms
safe_image.php
708 ms
safe_image.php
705 ms
safe_image.php
708 ms
safe_image.php
704 ms
37018_10151617984432227_139840060_n.jpg
150 ms
580846_10149999285985791_1565762244_n.png
221 ms
1484109_10152152180793249_1742398483_n.jpg
226 ms
12376092_10153727871924593_1935564866391043271_n.jpg
222 ms
1782035_10155115086290424_425679784340173114_n.jpg
220 ms
10955556_10152802034269064_415532451596293656_n.jpg
227 ms
12832412_1720736544876478_6066588953902120252_n.jpg
227 ms
205120_196984827006761_7073091_n.jpg
230 ms
1908290_10152215643194678_695793975911111231_n.png
230 ms
12734116_10153780679381620_4752512759472667993_n.png
227 ms
10382627_10152524764720844_3244405373432255610_n.jpg
231 ms
1009954_845489675466248_1040973764_n.jpg
237 ms
1524829_1376493799271559_1317276323_n.jpg
335 ms
10417741_295368044004278_6025448006269582377_n.jpg
332 ms
12794574_10153298020850653_5330498516415482789_n.jpg
336 ms
22567_317007619736_3962302_n.jpg
329 ms
ZVyMWStefv_.png
236 ms
K00K-UgnsKu.png
331 ms
LOOn0JtHNzb.gif
332 ms
GsNJNwuI-UM.gif
37 ms
jKEcVPZFk-2.gif
36 ms
I6-MnjEovm5.js
8 ms
pQrUxxo5oQp.js
8 ms
Dppan5o6UJu.js
7 ms
8v2_hdH4Nfm.js
19 ms
-Tr757ZEtMP.js
23 ms
A0qdgknEnD5.js
17 ms
-PAXP-deijE.gif
6 ms
xperd.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
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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.
xperd.cz best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Browser errors were logged to the console
xperd.cz SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Page is blocked from indexing
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Xperd.cz can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Xperd.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.
xperd.cz
Open Graph description is not detected on the main page of Xperd. 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: