4.2 sec in total
988 ms
2.9 sec
297 ms
Visit satori.ru now to see the best up-to-date Satori content for Russia and also check out these interesting facts you probably never knew about satori.ru
Производство, переработка, продажа. Широкий ассортимент щебня в Московском регионе на дробильно-сортировочных комплексах Сатори.
Visit satori.ruWe analyzed Satori.ru page load time and found that the first response time was 988 ms and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
satori.ru performance score
name
value
score
weighting
Value3.1 s
46/100
10%
Value14.3 s
0/100
25%
Value9.5 s
11/100
10%
Value690 ms
43/100
30%
Value0.032
100/100
15%
Value10.4 s
24/100
10%
988 ms
665 ms
947 ms
836 ms
275 ms
Our browser made a total of 76 requests to load all elements on the main page. We found that 79% of them (60 requests) were addressed to the original Satori.ru, 5% (4 requests) were made to Site.yandex.net and 4% (3 requests) were made to Mc.yandex.ru. The less responsive or slowest element that took the longest time to load (988 ms) belongs to the original domain Satori.ru.
Page size can be reduced by 208.9 kB (40%)
525.8 kB
316.9 kB
In fact, the total size of Satori.ru main page is 525.8 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 25% of websites need less resources to load. Javascripts take 301.4 kB which makes up the majority of the site volume.
Potential reduce by 27.5 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 27.5 kB or 73% of the original size.
Potential reduce by 12.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. Satori images are well optimized though.
Potential reduce by 153.0 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 153.0 kB or 51% of the original size.
Potential reduce by 15.8 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. Satori.ru needs all CSS files to be minified and compressed as it can save up to 15.8 kB or 80% of the original size.
Number of requests can be reduced by 39 (54%)
72
33
The browser has sent 72 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Satori. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and as a result speed up the page load time.
satori.ru
988 ms
satori.css
665 ms
jquery.min.js
947 ms
jquery.fancybox.js
836 ms
main.js
275 ms
swf.js
419 ms
watch.js
480 ms
counter_cv.js
458 ms
jquery.fancybox.css
138 ms
ga.js
6 ms
body_bg.gif
137 ms
__utm.gif
12 ms
body2_bg.gif
138 ms
nav_bg.jpg
137 ms
fn_home_act.gif
138 ms
fn_feedback.gif
138 ms
fn_sitemap.gif
135 ms
fn_search.gif
140 ms
menu_bg.jpg
270 ms
all.js
21 ms
m_company.gif
258 ms
m_action.gif
262 ms
m_objects.gif
263 ms
m_vacancy.gif
265 ms
m_contacts.gif
266 ms
img_03.jpg
390 ms
info_bg.jpg
394 ms
slogan_01.gif
395 ms
telephon.jpg
395 ms
arrow_b.gif
397 ms
callback.jpg
397 ms
satori_stat.jpg
645 ms
blocks_bg.gif
518 ms
table_bg.gif
518 ms
img_01.gif
519 ms
building.gif
520 ms
arrow_w2.gif
521 ms
img_02.gif
653 ms
sheben.gif
657 ms
img_03.gif
658 ms
service.gif
658 ms
img_04.gif
659 ms
other.gif
777 ms
div_news_bg.gif
787 ms
title_news.gif
791 ms
arrow_w.gif
792 ms
goszakaz.gif
793 ms
developers-1.gif
793 ms
church.gif
907 ms
jquery.min.js
44 ms
advert.gif
97 ms
cnt
522 ms
hit
263 ms
suggest.js
44 ms
opensearch.js
46 ms
search.png
41 ms
list_ul.gif
817 ms
banner_bg.gif
819 ms
banner_dsk_1.gif
839 ms
banner_title_dsk_2.gif
832 ms
banner_zem_1.gif
831 ms
banner_title_zem_4.gif
932 ms
1
92 ms
div_info2_bg.gif
819 ms
mechty.gif
820 ms
mechty2.gif
832 ms
Postavshik_22.gif
832 ms
SC_logo.gif
834 ms
ST_logo.gif
927 ms
hit
131 ms
eco_cert_znak_1.gif
821 ms
baner_stroykompleksa.jpg
958 ms
copyright_bg.gif
835 ms
counter_bg.gif
834 ms
u9257.83.spylog.com
253 ms
cnt
244 ms
satori.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-hidden="true"] elements contain focusable descendents
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
satori.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
Browser errors were logged to the console
satori.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
WINDOWS-1251
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Satori.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 Satori.ru main page’s claimed encoding is windows-1251. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
satori.ru
Open Graph description is not detected on the main page of Satori. 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: