6.9 sec in total
567 ms
5.9 sec
466 ms
Click here to check amazing Stan content for Russia. Otherwise, check out these important facts you probably never knew about stan.su
Производство корпоративной спецодежды с нанесением логотипа. Большой ассортимент текстиля оптом и в розницу с доставкой в Москве, Екатеринбурге, Санкт-Петербурге и Краснодаре.
Visit stan.suWe analyzed Stan.su page load time and found that the first response time was 567 ms and then it took 6.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
stan.su performance score
name
value
score
weighting
Value4.4 s
16/100
10%
Value4.4 s
40/100
25%
Value8.8 s
16/100
10%
Value1,780 ms
10/100
30%
Value0
100/100
15%
Value6.8 s
55/100
10%
567 ms
1241 ms
333 ms
350 ms
340 ms
Our browser made a total of 91 requests to load all elements on the main page. We found that 82% of them (75 requests) were addressed to the original Stan.su, 5% (5 requests) were made to Mc.yandex.ru and 4% (4 requests) were made to Yastatic.net. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Stan.su.
Page size can be reduced by 836.4 kB (36%)
2.3 MB
1.5 MB
In fact, the total size of Stan.su main page is 2.3 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. 50% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 66.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.8 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 66.7 kB or 81% of the original size.
Potential reduce by 200.8 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, Stan needs image optimization as it can save up to 200.8 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 492.5 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 492.5 kB or 70% of the original size.
Potential reduce by 76.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. Stan.su needs all CSS files to be minified and compressed as it can save up to 76.4 kB or 80% of the original size.
Number of requests can be reduced by 43 (49%)
88
45
The browser has sent 88 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Stan. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
stan.su
567 ms
www.stan.su
1241 ms
core.min.css
333 ms
style.css
350 ms
style.css
340 ms
kernel_main.js
1690 ms
template_2c2a929678ea82fa69c38c97c953a228.js
930 ms
main_7.css
873 ms
rocon.js
505 ms
mousehold.js
507 ms
jquery.jcarousel.pack.js
526 ms
jquery.tablesort.js
691 ms
common_01012014.js
990 ms
comm.js
1068 ms
swobject.js
870 ms
jquery.mousewheel-3.0.6.pack.js
1034 ms
jquery.fancybox.js
1189 ms
jquery.fancybox.css
1097 ms
jquery.fancybox-buttons.css
1141 ms
jquery.fancybox-buttons.js
1193 ms
jquery.fancybox-thumbs.css
1233 ms
jquery.fancybox-thumbs.js
1263 ms
jquery.fancybox-media.js
1294 ms
share.js
101 ms
ba.js
163 ms
get_flash_player.gif
34 ms
logo.png
474 ms
body-bg.jpg
351 ms
close-btn.png
158 ms
send-message-btn.png
157 ms
stan_logo_group_of_company.png
178 ms
logo-beta.png
189 ms
b-content.png
187 ms
b-begin.png
311 ms
b-end.png
312 ms
ico-home.gif
348 ms
ico-mail.gif
357 ms
ico-map.gif
356 ms
tab-download.png
466 ms
tab-price.png
466 ms
tab-colors.png
518 ms
b_small_v2_partnership.jpg
508 ms
b_small_v2_kp_generator.jpg
525 ms
b_small_v2_sales-2.png
528 ms
7045348861ae1d452b90d505408a5315.jpg
644 ms
11fe2178818dd53305a4c660e0e0fb75.png
970 ms
90a5fc3987fdbeb4ae80d028f1422ad3.jpg
674 ms
c484af3241c382f5b47711f7854a4eb6.jpg
685 ms
d83a016978f442341fa9aa2022b0d482.jpg
691 ms
02a5fa962584a0c3990dd478ab17d1cf.jpg
899 ms
88c785fbafe7942bf6074cf4a1a980cb.jpg
817 ms
0e23c10fbd7138a0ba8f1ca784614b9e.png
1197 ms
d6f76db354a65f80a382db95c0f08f55.jpg
1023 ms
f6ed07ac469142f967fa2009d1924ea9.jpg
1220 ms
c4889f5f91dfbfda60eb334a2e4fa8c2.jpg
981 ms
9393b402aed6d97e7a6381bd6b9852bb.jpg
1070 ms
094ec9d42c2206dd0b3da097b662891f.jpg
1625 ms
70b877a958026eeb83f3ebe274a2c751.jpg
1306 ms
703db0f1fcf15cf9bfeca740a1457214.jpg
1581 ms
d64f4b0756a891858f8957b6511220c9.jpg
1906 ms
1a1b7c85226659eedef01f2c8be20632.jpg
1580 ms
65fe9e48f4868cac0d2a425ee9d941ab.jpg
2018 ms
2e5daa9246cf864463db0b9239bb180f.jpg
1656 ms
ga.js
72 ms
watch.js
181 ms
b-share-form-button.png
31 ms
b-share-form-button_share__icon.png
29 ms
b-share-icon.png
30 ms
b-share-popup_down__tail.png
28 ms
__utm.gif
15 ms
bx_stat
202 ms
f4372f1cd52c7978c278e1d9b36a222e.jpg
1787 ms
7a738951bf0fe7be5432665e3f7174c7.jpg
2003 ms
243dfe3c8c4914f8ce86c28eb8e610e9.jpg
2000 ms
enter-btn.png
1724 ms
c-bg.png
1879 ms
watch.js
481 ms
c-bottom.png
1773 ms
c-top.png
1791 ms
shadow_septer.png
1848 ms
red-arrow.gif
1874 ms
news-sep.gif
1894 ms
list-marker.gif
1906 ms
pp-win.png
1861 ms
f-line.gif
1864 ms
icons.png
1875 ms
fancybox_overlay.png
1859 ms
fancybox_sprite.png
1895 ms
advert.gif
90 ms
1
92 ms
26812653
91 ms
stan.su 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.
stan.su best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
stan.su 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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Stan.su can be misinterpreted by Google and other search engines. Our service has detected that English 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 Stan.su 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.
stan.su
Open Graph description is not detected on the main page of Stan. 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: