5.9 sec in total
560 ms
4.9 sec
430 ms
Visit sanner.ru now to see the best up-to-date SANNER content for Russia and also check out these interesting facts you probably never knew about sanner.ru
DELUXE
Visit sanner.ruWe analyzed Sanner.ru page load time and found that the first response time was 560 ms and then it took 5.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
sanner.ru performance score
name
value
score
weighting
Value2.4 s
72/100
10%
Value8.7 s
2/100
25%
Value5.8 s
51/100
10%
Value950 ms
30/100
30%
Value0.042
99/100
15%
Value11.5 s
19/100
10%
560 ms
295 ms
194 ms
189 ms
190 ms
Our browser made a total of 83 requests to load all elements on the main page. We found that 96% of them (80 requests) were addressed to the original Sanner.ru, 2% (2 requests) were made to Bitrix.info and 1% (1 request) were made to Mc.yandex.ru. The less responsive or slowest element that took the longest time to load (3.4 sec) belongs to the original domain Sanner.ru.
Page size can be reduced by 496.5 kB (12%)
4.0 MB
3.5 MB
In fact, the total size of Sanner.ru main page is 4.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 3.4 MB which makes up the majority of the site volume.
Potential reduce by 107.9 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 63.5 kB, which is 53% 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 107.9 kB or 91% of the original size.
Potential reduce by 54.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. SANNER images are well optimized though.
Potential reduce by 262.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 262.3 kB or 72% of the original size.
Potential reduce by 71.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. Sanner.ru needs all CSS files to be minified and compressed as it can save up to 71.7 kB or 84% of the original size.
Number of requests can be reduced by 42 (54%)
78
36
The browser has sent 78 CSS, Javascripts, AJAX and image requests in order to completely render the main page of SANNER. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and from 17 to 1 for CSS and as a result speed up the page load time.
sanner.ru
560 ms
jquery.js
295 ms
addtobasket.js
194 ms
jquery.maskedinput.min.js
189 ms
to-top.js
190 ms
scrollTo.js
191 ms
core.min.css
196 ms
core_popup.min.css
281 ms
style.css
283 ms
style.css
285 ms
style.css
284 ms
style.css
312 ms
style.css
383 ms
style.css
382 ms
style.css
383 ms
style.css
387 ms
style.css
388 ms
style.css
389 ms
style.css
473 ms
style.css
475 ms
template_styles.css
488 ms
core.min.js
971 ms
core_popup.min.js
480 ms
webdebug.ruble.a.css
486 ms
script.js
564 ms
script.js
570 ms
script.js
573 ms
script.js
580 ms
script.js
581 ms
script.js
655 ms
script.js
658 ms
jquery.mousewheel-3.0.4.pack.js
669 ms
jquery.fancybox-1.3.4.pack.js
680 ms
fancybox-init.js
680 ms
jquery.fancybox-1.3.4.css
747 ms
jquery.carouFredSel-6.0.4-packed.js
839 ms
jcarousellite_1.0.1.pack.js
684 ms
script.js
596 ms
ba.js
172 ms
logo.png
103 ms
header-search.png
100 ms
search-icon.png
100 ms
slider.png
910 ms
slide.jpg
3432 ms
slide-plank.png
104 ms
aveo-new-generation.jpg
506 ms
foto.jpg
2605 ms
my%20nature.jpg
514 ms
Amadea.jpg
528 ms
back.jpg
598 ms
left-menu-open.png
609 ms
331.jpg
726 ms
1.jpg
693 ms
hit.png
709 ms
1.jpg
786 ms
1.jpg
802 ms
1.jpg
827 ms
1.jpg
877 ms
l1i1116092618228_2.jpg
941 ms
i%20(3).jpg
922 ms
sale.png
971 ms
121827.jpg
1324 ms
GROHE%20Eurosmart%20117922.jpg
1140 ms
1.jpg
1239 ms
1.jpg
1276 ms
1.jpg
1336 ms
1%D0%B3%D0%BE.jpg
1449 ms
new.png
1371 ms
noimage.jpg
1431 ms
noimage.jpg
1429 ms
LAGARD%20Auguste%20black.jpg
1463 ms
LAGARD%20vella%20black.jpg
1533 ms
1%D0%B2.jpg
1615 ms
footer-logo.png
1545 ms
watch.js
49 ms
to-top.png
1468 ms
shadow.png
1537 ms
slider-pager.png
1549 ms
shadow.png
1555 ms
HelveticaNeueCyr-Thin.otf
1710 ms
bx_stat
243 ms
HelveticaNeueCyr-Roman.otf
1227 ms
ruble.woff
1237 ms
sanner.ru 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
Links do not have a discernible name
sanner.ru 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
Registers an unload listener
Detected JavaScript libraries
Browser errors were logged to the console
sanner.ru 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
RU
RU
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Sanner.ru can be misinterpreted by Google and other search engines. Our service has detected that Russian is used on the page, and it matches the claimed language. Our system also found out that Sanner.ru 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.
sanner.ru
Open Graph description is not detected on the main page of SANNER. 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: