2.9 sec in total
337 ms
2.3 sec
285 ms
Click here to check amazing Kronium content for Czech Republic. Otherwise, check out these important facts you probably never knew about kronium.cz
Kvalitní výkonné LED svítilny a čelovky Fenix. Vhodné pro pohyb v přírodě, policisty, cyklisty, myslivce, rybáře i pro použití v domácnosti
Visit kronium.czWe analyzed Kronium.cz page load time and found that the first response time was 337 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
kronium.cz performance score
name
value
score
weighting
Value3.6 s
33/100
10%
Value9.5 s
0/100
25%
Value6.0 s
46/100
10%
Value1,840 ms
9/100
30%
Value0.054
98/100
15%
Value11.6 s
18/100
10%
337 ms
306 ms
20 ms
115 ms
212 ms
Our browser made a total of 57 requests to load all elements on the main page. We found that 84% of them (48 requests) were addressed to the original Kronium.cz, 5% (3 requests) were made to Google-analytics.com and 2% (1 request) were made to Static.hotjar.com. The less responsive or slowest element that took the longest time to load (744 ms) belongs to the original domain Kronium.cz.
Page size can be reduced by 495.0 kB (45%)
1.1 MB
603.3 kB
In fact, the total size of Kronium.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. 50% of websites need less resources to load. Images take 485.6 kB which makes up the majority of the site volume.
Potential reduce by 75.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. This page needs HTML code to be minified as it can gain 18.9 kB, which is 22% 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 75.5 kB or 87% of the original size.
Potential reduce by 20.9 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. Kronium images are well optimized though.
Potential reduce by 287.0 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 287.0 kB or 71% of the original size.
Potential reduce by 111.7 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. Kronium.cz needs all CSS files to be minified and compressed as it can save up to 111.7 kB or 90% of the original size.
Number of requests can be reduced by 11 (20%)
54
43
The browser has sent 54 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Kronium. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and as a result speed up the page load time.
kronium.cz
337 ms
index.php
306 ms
analytics.js
20 ms
main.css
115 ms
jslibrary.js
212 ms
jquery-1.8.1.min.js
330 ms
jquery-ui-1.8.23.custom.min.js
216 ms
jquery.easing.js
217 ms
jquery.mousewheel.js
287 ms
jquery.ui.touch-punch.min.js
225 ms
jQAllRangeSliders-min.js
319 ms
main.js
327 ms
ec.js
10 ms
sprites.css
209 ms
hotjar-159276.js
113 ms
1496-12.png
213 ms
background.jpg
213 ms
sprites.png
212 ms
fenix-rc40v2.jpg
112 ms
fenix-e35uev2.jpg
113 ms
fenix-tk09v2.jpg
114 ms
fenix-rc09ti.jpg
109 ms
fenix-hl60r.jpg
214 ms
fenix-18650-3500.jpg
218 ms
fenix-pd32xpl.jpg
219 ms
fenix-bc21r.jpg
220 ms
fenix-e99.jpg
316 ms
fenix-CL05-modra.jpg
318 ms
fenix-LD09V2.jpg
319 ms
fenix-E15XPG2.jpg
325 ms
fenix-E25UE.jpg
327 ms
fenix-FD40.jpg
327 ms
fenix-HL35.jpg
421 ms
fenix-RC20.jpg
422 ms
fenix_tk35uev2.jpg
424 ms
fenix-arex1.jpg
432 ms
fenix-E20V2.jpg
432 ms
fenix-HL05-blue.jpg
434 ms
fenix-pd35TAC.jpg
525 ms
fenix-uc30.jpg
526 ms
fenix-HL50-00.jpg
529 ms
fenix-tk22v3.jpg
537 ms
bezpecnostni-penezenka1.jpg
644 ms
fenix-tk75v3set26.jpg
647 ms
fenix-bc30set3500.jpg
629 ms
ipc-1.jpg
636 ms
panasonic-eneloop-tropical.jpg
635 ms
fenix-hp30silver-set26.jpg
643 ms
fenix-pd40-set2.jpg
735 ms
fkt-ipc1l.jpg
741 ms
voltcraft-charge-manager-420.jpg
744 ms
free-shipping.png
715 ms
collect
33 ms
collect
71 ms
modules-1f5c71aea63f8df71401422ed80fbe5f.js
39 ms
ga-audiences
36 ms
visit-data
202 ms
kronium.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 input fields do not have accessible names
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
Links do not have a discernible name
kronium.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
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
kronium.cz SEO score
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
CS
CS
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Kronium.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 Kronium.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.
kronium.cz
Open Graph description is not detected on the main page of Kronium. 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: