7.1 sec in total
535 ms
5.6 sec
894 ms
Welcome to steelline.ru homepage info - get ready to check Steelline best content for Russia right away, or after learning these important things about steelline.ru
Официальный сайт производителя входных металлических дверей «Стальная линия», осуществляем продажу, доставку и установку дверей в Москве.
Visit steelline.ruWe analyzed Steelline.ru page load time and found that the first response time was 535 ms and then it took 6.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
steelline.ru performance score
name
value
score
weighting
Value4.6 s
14/100
10%
Value6.9 s
6/100
25%
Value19.2 s
0/100
10%
Value36,950 ms
0/100
30%
Value0.032
100/100
15%
Value48.6 s
0/100
10%
535 ms
795 ms
133 ms
264 ms
368 ms
Our browser made a total of 172 requests to load all elements on the main page. We found that 70% of them (121 requests) were addressed to the original Steelline.ru, 5% (9 requests) were made to App.comagic.ru and 3% (6 requests) were made to Vk.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Steelline.ru.
Page size can be reduced by 506.9 kB (12%)
4.2 MB
3.7 MB
In fact, the total size of Steelline.ru main page is 4.2 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. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 3.1 MB which makes up the majority of the site volume.
Potential reduce by 388.6 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 55.3 kB, which is 12% 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 388.6 kB or 82% of the original size.
Potential reduce by 37.5 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. Steelline images are well optimized though.
Potential reduce by 19.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. This website has mostly compressed JavaScripts.
Potential reduce by 61.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. Steelline.ru needs all CSS files to be minified and compressed as it can save up to 61.7 kB or 15% of the original size.
Number of requests can be reduced by 94 (61%)
155
61
The browser has sent 155 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Steelline. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 67 to 1 for JavaScripts and from 17 to 1 for CSS and as a result speed up the page load time.
steelline.ru
535 ms
steelline.ru
795 ms
compatibility.css
133 ms
video-js.css
264 ms
popup.css
368 ms
style.css
373 ms
style.css
375 ms
selection-door-block.css
384 ms
style.css
398 ms
style.css
399 ms
style.css
487 ms
main.min.css
623 ms
tttstyles.css
875 ms
catalog.css
653 ms
jquery.fancybox.css
521 ms
ajax.css
524 ms
template_styles.css
607 ms
js
58 ms
core.js
1423 ms
protobuf.js
791 ms
model.js
721 ms
rest.client.js
737 ms
pull.client.js
763 ms
jquery-1.12.4.min.js
1388 ms
core_ls.js
860 ms
ajax.js
1385 ms
currency-core.bundle.js
1387 ms
core_currency.js
1419 ms
pageobject.js
1417 ms
core_window.js
1417 ms
fileman_player.js
1417 ms
video.js
1736 ms
api.js
45 ms
recaptcha_.js
1608 ms
main.min.js
1909 ms
mainn.js
1608 ms
script.js
1607 ms
counts.js
1608 ms
lazy.js
1824 ms
cs.min.js
1382 ms
jquery.actual.min.js
1823 ms
jqModal.js
1706 ms
jquery.fancybox.js
1572 ms
jquery.history.js
1477 ms
jquery.flexslider.js
1490 ms
jquery.validate.min.js
1487 ms
jquery.inputmask.bundle.min.js
1477 ms
jquery.easing.1.3.js
1462 ms
equalize.min.js
1584 ms
jquery.alphanumeric.js
1500 ms
jquery.cookie.js
1464 ms
jquery.plugin.min.js
1460 ms
jquery.countdown.min.js
1375 ms
jquery.countdown-ru.js
1385 ms
jquery.ikSelect.js
1391 ms
sly.js
1371 ms
equalize_ext.js
1358 ms
owl.carousel.min.js
1340 ms
jquery.mmenu.min.js
1313 ms
yaGoals.js
1288 ms
fbevents.js
454 ms
script.js
777 ms
custom.js
870 ms
logo_main.png
866 ms
logo-number1.png
864 ms
loader_4_pvk4ih.js
802 ms
analytics.js
200 ms
ubuntu.woff
841 ms
ubuntumedium.woff
870 ms
ubuntulight.woff
954 ms
ubuntubold.woff
955 ms
ubuntuitalic.woff
1130 ms
2616572528623063
72 ms
ubuntumediumitalic.woff
766 ms
ubuntulightitalic.woff
766 ms
ubuntubolditalic.woff
797 ms
icons_wish.png
815 ms
collect
14 ms
recaptcha__en.js
41 ms
icons_wish.png
725 ms
mailimg.png
733 ms
menu_teploshumo.jpg
803 ms
action-shumka.jpg
733 ms
action-belye.jpg
733 ms
s-termorazrivom.jpg
758 ms
menu_color.jpg
758 ms
4cef0b54289c991d6cd0d8a39e7bf309.png
784 ms
40a12c61f5a663ba774b5c78f2e20b1f.png
800 ms
52483b445b8c922d9791a2492d873956.png
805 ms
4be091e93c319d29c0ff66e4f31be34d.png
759 ms
a2699cf263392b5039a1d2ce0b76f7d0.png
768 ms
d074d278e317aba738866af3942aa073.jpg
787 ms
3e111eef1f70f331d515eb11a64910f7.jpg
789 ms
51d8274e44da570cf4d32a6f82cf3c21.jpg
798 ms
f210939f593e79067f29711cc1311ff8.jpg
785 ms
qfl23fyk0eas6scxj0rn3zegu499ougy.jpg
833 ms
a4e1c60d58d1066a47374af393f09d8c.png
820 ms
back.png
1214 ms
woman.png
801 ms
oxrmpfav0giqjgisb50ev5g0sjuqhw28.jpg
787 ms
7nkvib8kguh006ldgd6hd8fmlwwqad0s.jpg
791 ms
l7i9vefue3saum5ypjnzhh0mihbbxauy.jpg
850 ms
tstf6li281r3n234pu8i3s2z4351m1rv.jpg
835 ms
call.tracker.js
175 ms
04kwbj0zom33buehal58nm8okqqz1wa2.jpg
758 ms
ssruqwip57eebdxavm4dtbxy2bcmeklr.jpg
769 ms
map_large.png
1259 ms
2tonceg0qa8h4xyq2jd7rlafxws2lcv4.jpg
1366 ms
ba.js
317 ms
spread.php
681 ms
spread.php
629 ms
spread.php
677 ms
openapi.js
549 ms
openapi.js
576 ms
code.js
952 ms
openapi.js
617 ms
tag.js
801 ms
init
983 ms
script.js
534 ms
styles.min.css
1231 ms
script.min.js
1469 ms
anchor
41 ms
rivjx96psoxrz6s7tq4mlz5kvbqtfl6o.jpg
997 ms
1jc0k86vwm3pmra7cd4nzq8ep1dpkb4i.jpg
931 ms
12fc6d4ebaa9f62eccb0748316e59dd9.jpg
933 ms
dcd9a708b98b7fe0b3744d61f6d838c5.jpg
1002 ms
158 ms
9e8457487ff5a2c0e8fea54a383d6a9f.jpg
1005 ms
styles__ltr.css
18 ms
recaptcha__en.js
22 ms
fe6f577f50fe151b460e5702516d052c.jpg
1141 ms
752ce089fa9993ed538025ad4024209f.jpg
1316 ms
webworker.js
101 ms
logo_48.png
76 ms
c6071b99caaf20e4bdfbdb9443d478c3.jpg
949 ms
ea057712871c06d42341f646acaade0c.jpg
994 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
29 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
35 ms
KFOlCnqEu92Fr1MmYUtfBBc9.ttf
42 ms
263fd6dc183ef884f0d8eb9a78010e7c.jpg
1093 ms
4ym7daihgpvkfe1ztdp1n0qjg02r53jw.jpg
1095 ms
comagic.widgets.min.js
408 ms
98e141ad9d2833ed19e4f5a0601067c3.jpg
1114 ms
recaptcha__en.js
16 ms
f0be0f74fe5c351b31f0595d8367db2c.jpg
1078 ms
pe50rlgf9tnfsnajmddi2fv5lxqf1xgz.jpg
1137 ms
vb43m4u21nes906vfgt71ixbtvii0mt9.jpg
1135 ms
bx_stat
188 ms
9ich54pgc8lbbq4qrboyi70fl14frd0f.jpg
1129 ms
8pwb7nviprgzhprloao6rwna9o0ouli6.jpg
1178 ms
767 ms
sitephone.min.js
374 ms
sitephone_rack.html
378 ms
sitephone_label.html
379 ms
sitephone_simple.html
404 ms
sitephone.html
410 ms
sitephone_times_options.html
464 ms
arrows.png
1173 ms
footer_subscribe.png
1161 ms
payments.png
1160 ms
vk.png
1142 ms
ok.png
1139 ms
youtube-icon.png
1173 ms
rtrg
128 ms
rtrg
120 ms
rtrg
131 ms
counter
174 ms
advert.gif
702 ms
206 ms
addVisit
398 ms
sync_cookie_image_decide
133 ms
tracker
132 ms
steelline.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
Image elements do not have [alt] attributes
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.
steelline.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
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
steelline.ru SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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 Steelline.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 Steelline.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.
steelline.ru
Open Graph description is not detected on the main page of Steelline. 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: