5.7 sec in total
1.6 sec
3.4 sec
667 ms
Click here to check amazing ITlog content. Otherwise, check out these important facts you probably never knew about itlog.cz
Stanislav Jermář - Information Technology Blog
Visit itlog.czWe analyzed Itlog.cz page load time and found that the first response time was 1.6 sec and then it took 4.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
itlog.cz performance score
name
value
score
weighting
Value5.8 s
5/100
10%
Value6.9 s
6/100
25%
Value8.0 s
22/100
10%
Value220 ms
87/100
30%
Value0.185
66/100
15%
Value6.9 s
54/100
10%
1592 ms
352 ms
236 ms
66 ms
331 ms
Our browser made a total of 95 requests to load all elements on the main page. We found that 22% of them (21 requests) were addressed to the original Itlog.cz, 22% (21 requests) were made to Pixel.wp.com and 18% (17 requests) were made to Systemcentercentral.com. The less responsive or slowest element that took the longest time to load (1.6 sec) relates to the external source Systemcentercentral.com.
Page size can be reduced by 601.8 kB (57%)
1.1 MB
462.8 kB
In fact, the total size of Itlog.cz main page is 1.1 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. 40% of websites need less resources to load. Javascripts take 480.3 kB which makes up the majority of the site volume.
Potential reduce by 65.0 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 65.0 kB or 82% of the original size.
Potential reduce by 9.6 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. ITlog images are well optimized though.
Potential reduce by 329.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 329.7 kB or 69% of the original size.
Potential reduce by 197.5 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. Itlog.cz needs all CSS files to be minified and compressed as it can save up to 197.5 kB or 78% of the original size.
Number of requests can be reduced by 70 (75%)
93
23
The browser has sent 93 CSS, Javascripts, AJAX and image requests in order to completely render the main page of ITlog. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 34 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
itlog.cz
1592 ms
wp-emoji-release.min.js
352 ms
sdm_wp_styles.css
236 ms
css
66 ms
genericons.css
331 ms
style.css
441 ms
style.css
220 ms
jetpack.css
568 ms
jquery.js
664 ms
jquery-migrate.min.js
447 ms
sdm_wp_scripts.js
478 ms
script.js
703 ms
devicepx-jetpack.js
6 ms
gprofiles.js
57 ms
wpgroho.js
182 ms
masonry.min.js
225 ms
jquery.masonry.min.js
182 ms
functions.js
181 ms
wp-embed.min.js
180 ms
sharing.js
213 ms
e-201611.js
8 ms
1595 ms
index2.php
507 ms
valid-xhtml10
50 ms
aip.php
353 ms
search-icon.png
118 ms
reg1.png
790 ms
reg2.png
333 ms
loading.gif
113 ms
Genericons.svg
252 ms
8AAnjaY2BgYGQAgosrjpwF0ZcUq9bCaABTzgdAAAA=
12 ms
cookie
364 ms
context
226 ms
hovercard.css
42 ms
services.css
69 ms
share
93 ms
g.gif
27 ms
graph.facebook.com
113 ms
share
92 ms
graph.facebook.com
178 ms
share
97 ms
graph.facebook.com
204 ms
share
98 ms
graph.facebook.com
196 ms
share
98 ms
graph.facebook.com
198 ms
share
92 ms
graph.facebook.com
197 ms
share
136 ms
graph.facebook.com
206 ms
share
130 ms
graph.facebook.com
246 ms
share
137 ms
graph.facebook.com
256 ms
share
140 ms
graph.facebook.com
264 ms
g.gif
20 ms
g.gif
24 ms
g.gif
24 ms
g.gif
24 ms
g.gif
24 ms
g.gif
24 ms
g.gif
24 ms
g.gif
24 ms
g.gif
26 ms
g.gif
26 ms
g.gif
26 ms
g.gif
26 ms
g.gif
26 ms
g.gif
25 ms
g.gif
26 ms
g.gif
27 ms
g.gif
27 ms
g.gif
27 ms
g.gif
26 ms
cimage2.png
280 ms
g.gif
14 ms
118 ms
wp-emoji-release.min.js
12 ms
jquery.js
32 ms
jquery-migrate.min.js
24 ms
feralf-scripts.js
25 ms
tubepress.js
24 ms
jquery.notice.js
25 ms
jquery.bxSlider.js
28 ms
quicktags.min.js
43 ms
crayon.te.min.js
49 ms
bookmarks.js
47 ms
tubepress.css
48 ms
jquery.notice.css
47 ms
jquery.bxslider.css
48 ms
crayon.min.css
53 ms
css
13 ms
jetpack.css
54 ms
w-logo-blue.png
38 ms
itlog.cz accessibility score
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
Buttons do not have an accessible name
Links do not have a discernible name
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.
itlog.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
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
itlog.cz SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 Itlog.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 Itlog.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.
itlog.cz
Open Graph data is detected on the main page of ITlog. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: