10.5 sec in total
1.9 sec
7.5 sec
1.1 sec
Visit savage.ru now to see the best up-to-date SAVAGE content for Russia and also check out these interesting facts you probably never knew about savage.ru
Новые коллекции стильной женской одежды Savage - купить с доставкой по всей стране
Visit savage.ruWe analyzed Savage.ru page load time and found that the first response time was 1.9 sec and then it took 8.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
savage.ru performance score
name
value
score
weighting
Value6.2 s
3/100
10%
Value11.7 s
0/100
25%
Value24.1 s
0/100
10%
Value4,490 ms
0/100
30%
Value0.002
100/100
15%
Value22.2 s
1/100
10%
1936 ms
2013 ms
48 ms
879 ms
127 ms
Our browser made a total of 109 requests to load all elements on the main page. We found that 79% of them (86 requests) were addressed to the original Savage.ru, 5% (5 requests) were made to Api-maps.yandex.ru and 4% (4 requests) were made to Top-fwz1.mail.ru. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Savage.ru.
Page size can be reduced by 512.7 kB (66%)
773.3 kB
260.6 kB
In fact, the total size of Savage.ru main page is 773.3 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. 55% of websites need less resources to load. HTML takes 333.2 kB which makes up the majority of the site volume.
Potential reduce by 281.4 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 281.4 kB or 84% of the original size.
Potential reduce by 383 B
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, SAVAGE needs image optimization as it can save up to 383 B or 36% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 9.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. This website has mostly compressed JavaScripts.
Potential reduce by 222.0 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. Savage.ru needs all CSS files to be minified and compressed as it can save up to 222.0 kB or 79% of the original size.
Number of requests can be reduced by 43 (44%)
97
54
The browser has sent 97 CSS, Javascripts, AJAX and image requests in order to completely render the main page of SAVAGE. 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 7 to 1 for CSS and as a result speed up the page load time.
savage.ru
1936 ms
savage.ru
2013 ms
gtm.js
48 ms
tracker.js
879 ms
style.css
127 ms
ui.design-tokens.min.css
251 ms
ui.font.opensans.min.css
351 ms
main.popup.bundle.min.css
352 ms
template_c739f775baa17f3d17ad63c88a1b983e_v1.css
363 ms
core.min.js
611 ms
script.js
375 ms
protobuf.min.js
382 ms
model.min.js
466 ms
rest.client.min.js
467 ms
pull.client.min.js
484 ms
main.popup.bundle.min.js
620 ms
index.css
512 ms
index.js
930 ms
mainpage.css
581 ms
mainpage.js
728 ms
template_7c36923af56d420efd0ff091f1b1cb6d_v1.js
639 ms
668 ms
js
59 ms
ba.js
311 ms
full-e375679eab0e00a5e81ddbb027f673d8841bde2c.js
1762 ms
white-logo.svg
130 ms
dropdown-angle-white.svg
129 ms
wishlist.svg
129 ms
wishlist-black.svg
116 ms
personal.svg
118 ms
personal-black.svg
127 ms
basket.svg
231 ms
basket-black.svg
233 ms
go_search.svg
255 ms
ubx4b0ybhxe0c6w6xt96t2gi2uvxzg4j.webp
254 ms
4s7z040jqy8msxk0ml531xsq20rkloqg.webp
374 ms
tz7p2cxsowsqt9errq3xprbs6ox6pf9c.webp
247 ms
8kbwl36zlv9n34qwf0pof7xl2isxcpu2.webp
348 ms
5rv1i23vq3sbvhwswjjzfewnma3tw9oj.webp
463 ms
lbq5rdr49unu5du859p1v0knk1k8lkdv.webp
368 ms
ujx3w217e4xbx9285j572v9scprxa7tx.webp
379 ms
7tn7t35mi8q7dxuxaoz032ndn6nv1d8r.webp
375 ms
c1c5lkk1g2sb6yy7y5buv82ts31g4hel.webp
464 ms
45dzynvhx1x1ta9k88rf8cpi51j1196o.webp
490 ms
t9tjcicb595z4yejm2pa9i6o1885c2su.webp
497 ms
hoscsqn4zukoph0l31kshr3e69ajcyq9.webp
497 ms
n7568a87qyyh4g7zd1owgba61gx6fu9t.webp
629 ms
l54i3rvesr786bactoqidi330uh3zg8p.webp
692 ms
yawx2r70ytmntpuv6pr9l1saizyn9zpb.webp
694 ms
xjfoqo2dfzrtdno3tyrclxrcxm9pgrah.webp
612 ms
e063vfhwpx7kx8l2b2xz53afhsc7y0ob.webp
620 ms
3h100pust382y9x3a7hx3msufwy30agw.webp
738 ms
gm1rer6jpeay7v30koi4xezigz4vkz0j.webp
735 ms
rk5f2y4jhcu3gzt367v8jek4kfy6ac0b.webp
742 ms
11hd0vwwjryo6sk4jl0kj1w50zsx25ao.webp
754 ms
rup8jvjls98zlgj7ksf70ba03esf7h60.webp
810 ms
zs48j8da050wsuy94hllns4p6k9a93n5.webp
811 ms
hjo9s277qwtputkrbd2itd6afxhb1e26.webp
988 ms
link-arrow.svg
858 ms
6ib5yqmll40ujt635tn1wsqkxxlbqn76.webp
988 ms
v%D0%BAontakte.svg
845 ms
FuturaPT-Book.woff
847 ms
FuturaPT-Medium.woff
846 ms
FuturaPT-Light.woff
864 ms
FuturaPT-Demi.woff
884 ms
FuturaPT-Bold.woff
918 ms
pcr1y07xoawd5zxjd3c5hib7dfpmkhmn.webp
1033 ms
tag.js
742 ms
exp.js
693 ms
code.js
637 ms
h6711x1xlettkgrk7leixbrxyfjwidrc.webp
869 ms
3h6dg9o2d7jgazo3f2v2ktrlsorqz5la.webp
874 ms
savage-footer-logo.svg
862 ms
savage-footer-logo-white.svg
877 ms
cookie-close.svg
906 ms
bx_stat
185 ms
q3djgq9ynjhilfzcor5smsjfiwuq03su.webp
1116 ms
7qwvyg42ynatgxutnp4re499ujfclh1i.webp
991 ms
z86panq82sa0m84iuntgx3in2a81azyz.webp
1121 ms
9wcr5gxyo8t4bqrxe1sp2jg36r8lxj8x.webp
1272 ms
pl2rusg7xfrjbna0ulqy42h1v1mx3x9r.webp
1019 ms
pfutrtm40jdztiq0j2e5gwha7awq14c2.webp
1165 ms
kb28en1l3gbfk0n217vzql63tcuih7eq.webp
1143 ms
rw6qbfde62lzc49ndf2j4a73hfzmn1wt.webp
1030 ms
New.png
1086 ms
efngcykj1lz08bzwvzqfxvrvgmcgr0nr.webp
1121 ms
openapi.a2ed73393cad04481c1dfb3f7794921f.js
245 ms
vflzhf87ax3jhetlht7euq1voj87sa3v.webp
1035 ms
Hit.png
1081 ms
yt.svg
1098 ms
yt-black.svg
1046 ms
vk.svg
1047 ms
vk-black.svg
1073 ms
teleg.svg
1070 ms
teleg-black.svg
1086 ms
rtrg
206 ms
dzen.svg
1092 ms
sync-loader.js
940 ms
counter
172 ms
dyn-goal-config.js
248 ms
dzen-black.svg
1206 ms
advert.gif
694 ms
sync_cookie_image_decide
204 ms
grab.cur
142 ms
grabbing.cur
159 ms
help.cur
287 ms
zoom_in.cur
422 ms
1
146 ms
tracker
126 ms
savage.ru 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
Form elements do not have associated labels
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.
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
savage.ru best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
savage.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
RU
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Savage.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 Savage.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.
savage.ru
Open Graph description is not detected on the main page of SAVAGE. 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: