14.3 sec in total
1.9 sec
11.6 sec
762 ms
Welcome to svicky.net homepage info - get ready to check Svicky best content for Czech Republic right away, or after learning these important things about svicky.net
Nabízíme veškeré komponenty pro výrobu svíček, mýdel i jiných hobbytechnik.
Visit svicky.netWe analyzed Svicky.net page load time and found that the first response time was 1.9 sec and then it took 12.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
svicky.net performance score
name
value
score
weighting
Value3.5 s
35/100
10%
Value4.1 s
46/100
25%
Value5.6 s
52/100
10%
Value90 ms
99/100
30%
Value0.077
95/100
15%
Value4.7 s
80/100
10%
1918 ms
415 ms
581 ms
286 ms
292 ms
Our browser made a total of 105 requests to load all elements on the main page. We found that 77% of them (81 requests) were addressed to the original Svicky.net, 10% (10 requests) were made to Static.xx.fbcdn.net and 6% (6 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (3.4 sec) belongs to the original domain Svicky.net.
Page size can be reduced by 702.7 kB (35%)
2.0 MB
1.3 MB
In fact, the total size of Svicky.net main page is 2.0 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. 45% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 41.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 41.0 kB or 75% of the original size.
Potential reduce by 146.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. Obviously, Svicky needs image optimization as it can save up to 146.0 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 292.8 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 292.8 kB or 73% of the original size.
Potential reduce by 222.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. Svicky.net needs all CSS files to be minified and compressed as it can save up to 222.9 kB or 88% of the original size.
Number of requests can be reduced by 31 (30%)
102
71
The browser has sent 102 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Svicky. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
www.svicky.net
1918 ms
jquery-ui.css
415 ms
page18_36.css
581 ms
page18_49.css
286 ms
slimbox.css
292 ms
slide.css
337 ms
jquery.js
2309 ms
jquery-ui-min.js
888 ms
jquery.slides.min.js
437 ms
onload.js
490 ms
common.js
560 ms
slimbox2.js
593 ms
scrollbutton.js
667 ms
jquery.cycle2.min.js
705 ms
menu1.js
721 ms
retargeting.js
328 ms
pix.gif
147 ms
img523c5fb3a5ce2.png
171 ms
img52aecc8addb5e.jpg
2408 ms
img4ebce837e7f0b.png
151 ms
img4f0c2bfeecf1f.png
345 ms
img4ebcea393e24a.png
182 ms
img4e8c32d9743ed.png
311 ms
img544d53bbcb62c.jpg
439 ms
img544d53dbd7c91.jpg
464 ms
img544d466067c81.jpg
1066 ms
img5593aa51cb26b.jpg
830 ms
img5593abb9ef6af.jpg
698 ms
img55e839ee09173.jpg
962 ms
img544d43e2ecbf5.jpg
814 ms
img52b1c92dc71ea.png
1015 ms
img52b1c88f4bd76.png
1306 ms
img52b1c9606809a.png
1290 ms
img52b1c93c0ec58.png
1428 ms
img52b1c9748f5f7.jpg
1169 ms
img52b1c97d3fabe.jpg
1406 ms
img55a7ccf1d0a13.jpg
2087 ms
img532efc45c5084.jpg
1737 ms
img52b1c91a302e7.png
2637 ms
img52b1c8d9604bd.jpg
1714 ms
img52b1c92fdac63.jpg
1579 ms
img5407385e0439a.jpg
1731 ms
img52b1c8ac47a52.jpg
1878 ms
img52b1c94a0101e.png
2030 ms
img53778292e0748.jpg
2034 ms
img52b1c8e419ea6.jpg
2777 ms
img52b1c8d03596d.jpg
2175 ms
img56aebfb6b1e4e.jpg
2180 ms
img52b1c95bc8765.png
2895 ms
img52b1c956ee517.png
2458 ms
img5496d868ecc2e.jpg
2615 ms
img52b1c8bc1e3ee.jpg
2990 ms
all.js
269 ms
retargeting
167 ms
img52b1c8b6ef15f.jpg
2496 ms
img52b1c911569d4.png
2760 ms
img52b1c90cd5e66.jpg
2742 ms
img545f9dfc3ced5.jpg
2756 ms
60 ms
img52b1c8c410bfa.jpg
2773 ms
xd_arbiter.php
246 ms
xd_arbiter.php
442 ms
img52b1c904ade70.png
3236 ms
img52b1c8a3f12ef.jpg
2620 ms
img52b1c8be6c395.jpg
2751 ms
img532f0e74272ae.jpg
2535 ms
img52b1c9490c6ef.jpg
2326 ms
img540736d5aaeb0.jpg
2378 ms
img55aa1ad7a9b08.png
3352 ms
img52b1c9306b3c1.png
3241 ms
img52b1c8ecbe151.png
2282 ms
img52b1c9372d97b.jpg
2197 ms
img52b1c933b02ad.png
2826 ms
img52b1c8936326c.jpg
2188 ms
img52b1c88fac143.jpg
2106 ms
img52b1c90c1a130.png
2216 ms
img52b1c8d8a118e.jpg
2092 ms
img554b309068753.jpg
2558 ms
img4b55b55e4b5de.png
2056 ms
img4b55b55dea6f2.png
2081 ms
img4ebce9f446faf.png
2061 ms
page18_41.css
293 ms
page18_45.css
149 ms
page18_46.css
148 ms
page18_47.css
148 ms
page18_48.css
147 ms
page18_50.css
147 ms
xd_arbiter.php
139 ms
like_box.php
99 ms
ebiMDO3r-8l.css
280 ms
jGc-59L_9lo.css
349 ms
q68gy-v_YMF.js
486 ms
hHAUS9q05ns.js
616 ms
0wM5s1Khldu.js
485 ms
1bNoFZUdlYZ.js
507 ms
529399_463541783665822_1116389466_n.jpg
351 ms
254660_257784377574898_887138_n.jpg
416 ms
10387629_453755834832940_2955911127808714640_n.jpg
486 ms
12541089_10205230722438130_8523722195055723218_n.jpg
554 ms
12801671_1693916304222687_1451353378860392555_n.jpg
555 ms
12592206_1056076224434051_8432582576585733301_n.jpg
554 ms
wL6VQj7Ab77.png
74 ms
s7jcwEQH7Sx.png
73 ms
I6-MnjEovm5.js
69 ms
pQrUxxo5oQp.js
71 ms
svicky.net 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
Links do not have a discernible name
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.
svicky.net 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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
svicky.net 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 doesn't use legible font sizes
CS
CS
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Svicky.net 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 Svicky.net 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.
svicky.net
Open Graph description is not detected on the main page of Svicky. 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: