4 sec in total
340 ms
3 sec
596 ms
Welcome to k70.webnode.cz homepage info - get ready to check K 70 Webnode best content for Czech Republic right away, or after learning these important things about k70.webnode.cz
Visit k70.webnode.czWe analyzed K70.webnode.cz page load time and found that the first response time was 340 ms and then it took 3.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
k70.webnode.cz performance score
name
value
score
weighting
Value4.0 s
23/100
10%
Value14.9 s
0/100
25%
Value5.0 s
63/100
10%
Value1,000 ms
27/100
30%
Value0
100/100
15%
Value6.9 s
54/100
10%
340 ms
13 ms
14 ms
16 ms
241 ms
Our browser made a total of 85 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original K70.webnode.cz, 49% (42 requests) were made to Static-cdn1.webnode.com and 12% (10 requests) were made to Files.k70.webnode.cz. The less responsive or slowest element that took the longest time to load (1.9 sec) relates to the external source Files.k70.webnode.cz.
Page size can be reduced by 195.0 kB (44%)
440.7 kB
245.7 kB
In fact, the total size of K70.webnode.cz main page is 440.7 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. 25% of websites need less resources to load. Images take 191.5 kB which makes up the majority of the site volume.
Potential reduce by 37.8 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.9 kB, which is 13% 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 37.8 kB or 81% of the original size.
Potential reduce by 9.0 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. K 70 Webnode images are well optimized though.
Potential reduce by 110.9 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 110.9 kB or 71% of the original size.
Potential reduce by 37.3 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. K70.webnode.cz needs all CSS files to be minified and compressed as it can save up to 37.3 kB or 83% of the original size.
Number of requests can be reduced by 38 (48%)
80
42
The browser has sent 80 CSS, Javascripts, AJAX and image requests in order to completely render the main page of K 70 Webnode. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 5 to 1 for JavaScripts and as a result speed up the page load time.
k70.webnode.cz
340 ms
functions.js
13 ms
style.css
14 ms
frontend.package.1-2-189.js
16 ms
widget-pocasi-i9orfa5ssjipmpm79n6nadab5aed5a
241 ms
counter_1.php
474 ms
analytics.js
37 ms
body.png
20 ms
nov%C3%BD-2.JPG
607 ms
poll.png
40 ms
print.css
8 ms
SDC11179.JPG
1918 ms
chytej_banner_full.gif
553 ms
rbb.JPG
523 ms
obraz000kg-300x240.jpg
603 ms
nov%C3%BD-1.JPG
690 ms
2.JPG
799 ms
P2271525.JPG
826 ms
SDC10488.JPG
866 ms
k2a.JPG
902 ms
pg_b.png
38 ms
pg_t.png
39 ms
masque.png
43 ms
nav_fxt.png
40 ms
nav_fxt_b.png
40 ms
nav_fxt_t.png
42 ms
submit.png
42 ms
box_wb_b.jpg
43 ms
box_wb_t.jpg
43 ms
box_wb_head.jpg
44 ms
brd_poll_l_t.png
46 ms
brd_poll_r_t.png
45 ms
brd_poll_l_b.png
46 ms
brd_poll_r_b.png
47 ms
poll_s.png
46 ms
collect
17 ms
widget-pocasi-i9orfa5ssjipmpm79n6nadab5aed5a
238 ms
counter_1.php
237 ms
sluzba.php
285 ms
calendar.php
319 ms
box_wd_b.jpg
12 ms
loader.gif
243 ms
box_wd_t.jpg
10 ms
box_wd_head.jpg
11 ms
pg_wd_next.png
11 ms
pg_wd_last.png
13 ms
brd_l_t.png
12 ms
brd_r_t.png
12 ms
brd_l_b.png
15 ms
brd_r_b.png
14 ms
box_m_b.jpg
13 ms
box_m_t.jpg
11 ms
ft.png
12 ms
ft_b.png
12 ms
ft_t.png
14 ms
rss.png
14 ms
footerButtonWebnodeHover.png
13 ms
polojasno.png
238 ms
oblacnosdestem.png
238 ms
calendar.php
619 ms
loading.gif
16 ms
loading_poll.gif
19 ms
loading_poll_wd.gif
17 ms
back_h.png
17 ms
counter_1.php
608 ms
brd_l_b_h.png
12 ms
brd_wd_l_b_h.png
14 ms
mi_h.png
12 ms
pg_next_h.png
13 ms
brd_r_t_h.png
11 ms
brd_wd_r_t_h.png
15 ms
pg_last_h.png
15 ms
slideshow_h.png
16 ms
brd_l_t_h.png
11 ms
brd_wd_l_t_h.png
20 ms
next_h.png
20 ms
pg_prev_h.png
19 ms
brd_r_b_h.png
12 ms
brd_wd_r_b_h.png
14 ms
pg_first_h.png
14 ms
prev_h.png
17 ms
footerButtonWebnode.png
17 ms
footerButton.png
17 ms
footerButtonHover.png
18 ms
footerBubble.png
18 ms
k70.webnode.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.
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
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
k70.webnode.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
Browser errors were logged to the console
k70.webnode.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 K70.webnode.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 K70.webnode.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.
k70.webnode.cz
Open Graph description is not detected on the main page of K 70 Webnode. 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: