6.2 sec in total
1.2 sec
4.8 sec
186 ms
Click here to check amazing 602 content. Otherwise, check out these important facts you probably never knew about 602.sk
Jsme Software602
Visit 602.skWe analyzed 602.sk page load time and found that the first response time was 1.2 sec and then it took 5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
602.sk performance score
name
value
score
weighting
Value2.8 s
56/100
10%
Value8.5 s
1/100
25%
Value6.8 s
34/100
10%
Value960 ms
29/100
30%
Value0.307
38/100
15%
Value8.9 s
34/100
10%
1243 ms
1151 ms
127 ms
246 ms
260 ms
Our browser made a total of 86 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original 602.sk, 86% (74 requests) were made to 602.cz and 2% (2 requests) were made to C.imedia.cz. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain 602.sk.
Page size can be reduced by 336.2 kB (22%)
1.6 MB
1.2 MB
In fact, the total size of 602.sk main page is 1.6 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. 30% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 34.7 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 34.7 kB or 79% of the original size.
Potential reduce by 23.2 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. 602 images are well optimized though.
Potential reduce by 160.3 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 160.3 kB or 64% of the original size.
Potential reduce by 118.1 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. 602.sk needs all CSS files to be minified and compressed as it can save up to 118.1 kB or 83% of the original size.
Number of requests can be reduced by 45 (57%)
79
34
The browser has sent 79 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 602. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 21 to 1 for CSS and as a result speed up the page load time.
602.sk
1243 ms
sk
1151 ms
aggregator.css
127 ms
node.css
246 ms
defaults.css
260 ms
system.css
264 ms
system-menus.css
256 ms
user.css
262 ms
content-module.css
256 ms
colorbox_default_style.css
364 ms
ctools.css
374 ms
date.css
378 ms
datepicker.css
379 ms
jquery.timeentry.css
384 ms
filefield.css
380 ms
views_slideshow.css
484 ms
views.css
492 ms
tablefield.css
497 ms
jquery.jcarousel.css
500 ms
skin.css
501 ms
skin.css
502 ms
style.css
959 ms
jquery.min.js
849 ms
drupal.js
620 ms
sk_fadd37830066c5c82b8a895538110244.js
622 ms
jquery.colorbox-min.js
623 ms
colorbox.js
623 ms
colorbox_default_style.js
746 ms
floating_block.js
748 ms
getlocations_colorbox.js
750 ms
jquery.cycle.all.min.js
870 ms
views_slideshow.js
871 ms
googleanalytics.js
880 ms
jquery.jcarousel.pack.js
879 ms
viewscarousel.js
988 ms
script.js
992 ms
SpryTabbedPanels.js
995 ms
retargeting.js
454 ms
conversion.js
24 ms
script.js
1000 ms
analytics.js
141 ms
flag-czech.gif
140 ms
anglicka.png
134 ms
602k_logo.png
132 ms
menubgreal.png
140 ms
limenuactive.png
134 ms
menu-expanded.png
137 ms
menu-leaf.png
251 ms
searchpole.png
262 ms
homepage_doladime_1000x382_SK.jpg
626 ms
home602_LTD_vse_08_4_SK.jpg
508 ms
homepage_syst_1000x382_SK.jpg
517 ms
homepage_workflow_1000x382_SK.jpg
518 ms
homepage_kamen_1000x382_SK.jpg
621 ms
homepage_DMS_1000x382_SK.jpg
758 ms
homepage_ucetni_1000x382_SK.jpg
641 ms
linknews.png
645 ms
sipeckaodjanicky.png
646 ms
fask.png
748 ms
portfolio_0.png
759 ms
seminare_2014_SK.png
768 ms
aplikace_2014_SK.png
771 ms
dotyky_2014_SK.png
775 ms
FS_1_1.png
878 ms
datovky_2014_SK.png
886 ms
ico_rss.jpg
885 ms
youtubeIcoWeb.png
887 ms
ico_linkedin.png
893 ms
ico_twitter.png
896 ms
google_Plus_.png
998 ms
L.js
226 ms
gtm.js
91 ms
retargeting
118 ms
92 ms
loading_animation.gif
907 ms
controls.png
909 ms
clickbutton_on.png
908 ms
clickbutton.png
913 ms
sipkavlevo.png
916 ms
sipkavpravo.png
1020 ms
releway1.ttf
1149 ms
collect
30 ms
54 ms
collect
57 ms
ga-audiences
19 ms
print.css
126 ms
602.sk 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 IDs are not unique
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
No form fields have multiple labels
Image elements do not have [alt] attributes
Form elements do not have associated labels
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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
602.sk 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
Page has valid source maps
602.sk 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
SK
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 602.sk can be misinterpreted by Google and other search engines. Our service has detected that Czech is used on the page, and it does not match the claimed Slovak language. Our system also found out that 602.sk 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.
602.sk
Open Graph description is not detected on the main page of 602. 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: