3.7 sec in total
353 ms
3.1 sec
310 ms
Welcome to santx.ru homepage info - get ready to check Santx best content for Russia right away, or after learning these important things about santx.ru
Сантехника от ведущих производителей из Германии, Италии и России по низким ценам в розницу и оптом со склада в Москве. Доставка по всей России.
Visit santx.ruWe analyzed Santx.ru page load time and found that the first response time was 353 ms and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
santx.ru performance score
name
value
score
weighting
Value2.9 s
53/100
10%
Value4.5 s
38/100
25%
Value9.5 s
11/100
10%
Value710 ms
42/100
30%
Value0.008
100/100
15%
Value5.5 s
71/100
10%
353 ms
566 ms
181 ms
185 ms
189 ms
Our browser made a total of 116 requests to load all elements on the main page. We found that 85% of them (99 requests) were addressed to the original Santx.ru, 4% (5 requests) were made to Mc.yandex.ru and 3% (3 requests) were made to Top-fwz1.mail.ru. The less responsive or slowest element that took the longest time to load (933 ms) belongs to the original domain Santx.ru.
Page size can be reduced by 802.9 kB (39%)
2.0 MB
1.2 MB
In fact, the total size of Santx.ru 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 974.0 kB which makes up the majority of the site volume.
Potential reduce by 63.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. This page needs HTML code to be minified as it can gain 10.0 kB, which is 13% 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 63.7 kB or 80% of the original size.
Potential reduce by 37.7 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. Santx images are well optimized though.
Potential reduce by 514.1 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 514.1 kB or 67% of the original size.
Potential reduce by 187.4 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. Santx.ru needs all CSS files to be minified and compressed as it can save up to 187.4 kB or 84% of the original size.
Number of requests can be reduced by 51 (46%)
111
60
The browser has sent 111 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Santx. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 27 to 1 for JavaScripts and from 17 to 1 for CSS and as a result speed up the page load time.
santx.ru
353 ms
www.santx.ru
566 ms
core.min.css
181 ms
core_popup.min.css
185 ms
style.css
189 ms
style.css
191 ms
core.min.js
277 ms
core_popup.min.js
192 ms
reset.css
269 ms
nivo-slider.css
273 ms
slider-theme.css
274 ms
jcarousel.css
273 ms
selectbox.css
293 ms
colorbox.css
358 ms
jquery.bxslider.css
362 ms
style.css
458 ms
uploadify.css
365 ms
add_page.css
366 ms
jquery-1.9.0.min.js
498 ms
jquery.selectbox.min.js
448 ms
jquery.colorbox-min.js
456 ms
jquery.nivo.slider.pack.js
474 ms
jcarousel.js
474 ms
jquery.ui.slider.js
634 ms
jquery.uploadify.min.js
646 ms
jquery.formatter.min.js
548 ms
jquery.bxslider.min.js
550 ms
owl.carousel.css
550 ms
owl.carousel.js
589 ms
site.js
652 ms
eshop.js
652 ms
my.js
653 ms
mediaelement-and-player.min.js
682 ms
videoplayer-setup.js
727 ms
videoplayer-style.css
729 ms
highslide-with-gallery.js
824 ms
highslide.css
735 ms
conversion.js
16 ms
ba.js
166 ms
m_gray.png
97 ms
soc-vk.jpg
96 ms
soc-fb.jpg
95 ms
soc-skype.jpg
100 ms
soc-mail.jpg
99 ms
basket.png
98 ms
kludi.jpg
193 ms
hansgrohe.jpg
375 ms
grohe.jpg
469 ms
fiore_new.jpg
382 ms
kludi_new.jpg
380 ms
idealstandart.jpg
386 ms
margaroli.jpg
376 ms
bagnoe.jpg
649 ms
left-block-montaj.jpg
469 ms
left-block-obzori.jpg
471 ms
left-block-yandex.jpg
473 ms
2dfdf0c5d30909fd5a0b9306b5680c6a.png
477 ms
42a481366a11c67baab1b5e0e17da0f0.png
559 ms
ff7e219ccf69ab4c026d336982c378a9.png
560 ms
glavnaya_sogl_45.png
562 ms
glavnaya_sogl_19_48.png
563 ms
glavnaya_sogl_14_21.png
568 ms
glavnaya_sogl_13_24.png
651 ms
glavnaya_sogl_17.png
652 ms
glavnaya_sogl_15_39.png
653 ms
glavnaya_sogl_40.png
656 ms
glavnaya_sogl_25.png
660 ms
glavnaya_sogl_20.png
738 ms
glavnaya_sogl_17_44.png
742 ms
more-goods.png
743 ms
9072100S002.jpg
836 ms
m_gray1.png
185 ms
watch.js
186 ms
analytics.js
36 ms
code.js
310 ms
headerbg.png
933 ms
logo.png
750 ms
headerphone.png
827 ms
headeremail.png
830 ms
bluebtn.png
831 ms
62 ms
collect
39 ms
bx_stat
246 ms
bottomFavorites.php
792 ms
bottomCompare.php
854 ms
bottomBasket.php
894 ms
headerBasket.php
871 ms
utlab.html
838 ms
42 ms
watch.js
513 ms
searchbtn.png
785 ms
analytics.js
251 ms
counter
154 ms
312 ms
searcharrow.png
654 ms
menu.png
659 ms
bluearrow.png
659 ms
li.png
680 ms
footmap.png
680 ms
footphone.png
614 ms
footwork.png
649 ms
footskype.png
655 ms
footemail.png
656 ms
footdelivery.png
672 ms
gotop.jpg
597 ms
bottom-panel-btn.png
611 ms
bottom-basket.png
648 ms
slider-arrows.png
653 ms
advert.gif
85 ms
1
85 ms
utlab.png
287 ms
552664
86 ms
tracker
154 ms
rounded-white.png
94 ms
zoomout.cur
95 ms
loader.white.gif
97 ms
santx.ru 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
Form elements do not have associated labels
santx.ru best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
santx.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
RU
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Santx.ru can be misinterpreted by Google and other search engines. Our service has detected that Russian is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Santx.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.
santx.ru
Open Graph description is not detected on the main page of Santx. 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: