5 sec in total
374 ms
3.7 sec
920 ms
Click here to check amazing SANSI content. Otherwise, check out these important facts you probably never knew about sansi.sk
SANSI - firma na výškové práce, natieračské práce a opravy údržby všade tam kde sa iní ľudia nedostanú, vysoká odbornosť, bohaté skúsenosti
Visit sansi.skWe analyzed Sansi.sk page load time and found that the first response time was 374 ms and then it took 4.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
sansi.sk performance score
name
value
score
weighting
Value4.4 s
17/100
10%
Value8.1 s
2/100
25%
Value6.8 s
35/100
10%
Value590 ms
51/100
30%
Value0.04
99/100
15%
Value12.2 s
15/100
10%
374 ms
585 ms
108 ms
257 ms
258 ms
Our browser made a total of 124 requests to load all elements on the main page. We found that 63% of them (78 requests) were addressed to the original Sansi.sk, 19% (24 requests) were made to Fonts.gstatic.com and 4% (5 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Sansi.sk.
Page size can be reduced by 174.6 kB (5%)
3.4 MB
3.2 MB
In fact, the total size of Sansi.sk main page is 3.4 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 3.0 MB which makes up the majority of the site volume.
Potential reduce by 63.6 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 63.6 kB or 80% of the original size.
Potential reduce by 49.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. SANSI images are well optimized though.
Potential reduce by 3.4 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. This website has mostly compressed JavaScripts.
Potential reduce by 57.9 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. Sansi.sk needs all CSS files to be minified and compressed as it can save up to 57.9 kB or 36% of the original size.
Number of requests can be reduced by 69 (77%)
90
21
The browser has sent 90 CSS, Javascripts, AJAX and image requests in order to completely render the main page of SANSI. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 42 to 1 for JavaScripts and from 23 to 1 for CSS and as a result speed up the page load time.
sansi.sk
374 ms
585 ms
js
108 ms
6nqat2crn4
257 ms
bc84177339a06b8ccfbb5ab69.js
258 ms
wp-emoji-release.min.js
161 ms
sgr.css
240 ms
style.min.css
346 ms
foobox.free.min.css
351 ms
style.css
345 ms
styles.css
353 ms
swipebox.min.css
363 ms
css
117 ms
all.min.css
364 ms
style.css
460 ms
elementor-icons.min.css
455 ms
frontend-legacy.min.css
456 ms
frontend.min.css
475 ms
post-895.css
484 ms
all.min.css
484 ms
v4-shims.min.css
565 ms
global.css
564 ms
post-83.css
569 ms
css
157 ms
fontawesome.min.css
588 ms
solid.min.css
592 ms
regular.min.css
605 ms
brands.min.css
674 ms
sgr.js
672 ms
frontend-gtag.min.js
683 ms
jquery.min.js
734 ms
jquery-migrate.min.js
711 ms
jquery.cookie.js
712 ms
script.js
782 ms
jquery.swipebox.min.js
784 ms
underscore.min.js
803 ms
infinite-scroll.pkgd.min.js
828 ms
front.js
838 ms
v4-shims.min.js
845 ms
foobox.free.min.js
933 ms
animations.min.css
892 ms
regenerator-runtime.min.js
912 ms
api.js
149 ms
wp-polyfill.min.js
961 ms
js
68 ms
analytics.js
25 ms
collect
62 ms
collect
53 ms
index.js
812 ms
clarity.js
40 ms
production.min.js
735 ms
index.js
721 ms
wp-embed.min.js
717 ms
webpack.runtime.min.js
714 ms
frontend-modules.min.js
756 ms
waypoints.min.js
745 ms
core.min.js
736 ms
swiper.min.js
793 ms
share-link.min.js
698 ms
dialog.min.js
698 ms
frontend.min.js
728 ms
preloaded-modules.min.js
716 ms
wp-util.min.js
716 ms
frontend.min.js
703 ms
destination
114 ms
Sansi_Header_01.png
715 ms
Sansi_Header_01-300x183.png
406 ms
k2-1024x683.jpg
459 ms
prievoz-4-1024x683.jpg
764 ms
IMG_3835-scaled.jpg
1301 ms
DEV_1.jpg
1080 ms
prokare.png
536 ms
azyl_log.png
567 ms
qualita-logon.png
691 ms
nc_logo.png
692 ms
alinel-1.png
831 ms
swanin.png
832 ms
lezecka-stena-k2-logo-new.jpg
833 ms
logo.png
881 ms
PS_Logo-1.png
938 ms
download-1.png
939 ms
download-2.png
954 ms
download.png
1013 ms
fa-brands-400.woff
1059 ms
fa-brands-400.woff
1090 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCGPrQVIT9d4cw.ttf
277 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCGPrQVIT9d4cw.ttf
292 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCGPrQVIT9d4cw.ttf
291 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtaorCGPrQVIT9d4cw.ttf
292 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvao7CGPrQVIT9d4cw.ttf
293 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpbCGPrQVIT9d4cw.ttf
295 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCGPrQVIT9d4cw.ttf
451 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtapbCGPrQVIT9d4cw.ttf
453 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtzpbCGPrQVIT9d4cw.ttf
448 ms
fa-solid-900.woff
1083 ms
fa-solid-900.woff
1181 ms
fa-regular-400.woff
1083 ms
fa-regular-400.woff
1182 ms
KFOmCnqEu92Fr1Mu7GxPKTU1Kg.ttf
328 ms
KFOlCnqEu92Fr1MmEU9fChc9AMP6lQ.ttf
329 ms
KFOlCnqEu92Fr1MmSU5fChc9AMP6lQ.ttf
328 ms
KFOkCnqEu92Fr1MmgVxGIzcXKMny.ttf
444 ms
KFOlCnqEu92Fr1MmWUlfChc9AMP6lQ.ttf
331 ms
KFOlCnqEu92Fr1MmYUtfChc9AMP6lQ.ttf
331 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w3aX9-p7K4GLs.ttf
333 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w3aX9-p7K4GLs.ttf
332 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w3aX9-p7K4GLs.ttf
709 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w3aX9-p7K4GLs.ttf
333 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw3aX9-p7K4GLs.ttf
333 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw3aX9-p7K4GLs.ttf
334 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw3aX9-p7K4GLs.ttf
647 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw3aX9-p7K4GLs.ttf
535 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw3aX9-p7K4GLs.ttf
783 ms
eicons.woff
1419 ms
conversion_async.js
79 ms
58 ms
57 ms
53 ms
54 ms
78 ms
97 ms
140 ms
140 ms
c.gif
42 ms
sansi.sk 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.
sansi.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
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
sansi.sk SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
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
SK
SK
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Sansi.sk can be misinterpreted by Google and other search engines. Our service has detected that Slovak is used on the page, and it matches the claimed language. Our system also found out that Sansi.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.
sansi.sk
Open Graph description is not detected on the main page of SANSI. 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: