7.2 sec in total
567 ms
6.4 sec
256 ms
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 567 ms and then it took 6.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
savage.ru performance score
name
value
score
weighting
Value6.5 s
2/100
10%
Value8.0 s
2/100
25%
Value13.9 s
1/100
10%
Value2,630 ms
4/100
30%
Value1
2/100
15%
Value13.8 s
10/100
10%
567 ms
3100 ms
260 ms
262 ms
272 ms
Our browser made a total of 98 requests to load all elements on the main page. We found that 56% of them (55 requests) were addressed to the original Savage.ru, 3% (3 requests) were made to Aprtx.com and 3% (3 requests) were made to X.cnt.my. The less responsive or slowest element that took the longest time to load (3.1 sec) belongs to the original domain Savage.ru.
Page size can be reduced by 575.0 kB (39%)
1.5 MB
905.7 kB
In fact, the total size of Savage.ru main page is 1.5 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. Javascripts take 667.3 kB which makes up the majority of the site volume.
Potential reduce by 43.2 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 43.2 kB or 75% of the original size.
Potential reduce by 34.0 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. SAVAGE images are well optimized though.
Potential reduce by 398.9 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 398.9 kB or 60% of the original size.
Potential reduce by 98.9 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 98.9 kB or 84% of the original size.
Number of requests can be reduced by 51 (58%)
88
37
The browser has sent 88 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 34 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
savage.ru
567 ms
www.savage.ru
3100 ms
reset.css
260 ms
skin.css
262 ms
jquery.fancybox-1.3.1.css
272 ms
style.css
407 ms
core.css
270 ms
style.css
272 ms
core.js
545 ms
core_ajax.js
551 ms
session.js
412 ms
postamat.js
551 ms
script.js
519 ms
jquery.min.js
35 ms
jquery.json-2.4.js
523 ms
jquery.jcarousel.js
678 ms
jquery.fancybox-1.3.1.js
551 ms
jquery.hoverIntent.minified.js
647 ms
script.js
654 ms
jquery.min.js
46 ms
popup_subscribe_150515.css
673 ms
placeholder.js
674 ms
masked.min.js
675 ms
conversion.js
16 ms
top_fon.gif
369 ms
postamat.js
668 ms
dc.js
57 ms
j.php
31 ms
tracking.js
796 ms
mw_left_grad.png
162 ms
mw_right_grad.png
158 ms
logo_1.gif
160 ms
tl.png
158 ms
blank.gif
159 ms
tr.png
152 ms
bl.png
276 ms
br.png
298 ms
dehatex_anons.png
433 ms
button_enter.gif
300 ms
sitemap.gif
299 ms
958_dec.jpg
1285 ms
kurtki_w.jpg
964 ms
kurtki_w.jpg
987 ms
kurtki_m.jpg
1136 ms
kurtki_m.jpg
989 ms
free_ship_mini.jpg
731 ms
free_ship_mini.jpg
1134 ms
menu_about_3.gif
1106 ms
menu_franchise_3.gif
1133 ms
menu_customer_3.gif
1134 ms
menu_im_3.gif
1236 ms
logotypes_transp_people_gray.png
1265 ms
logotypes_transp_lawine_gray.png
1271 ms
03-mastercard-04.png
1272 ms
02-visa-w350-04.png
1273 ms
instagram.png
1362 ms
odnoklassniki.png
1402 ms
facebook.png
1405 ms
vkontakte.png
1406 ms
button_add06.png
1407 ms
gtm.js
68 ms
v.gif
56 ms
menu_sprite.png
1549 ms
retag.js
263 ms
tar.php
323 ms
__utm.gif
24 ms
footer_fon.gif
1408 ms
p5azxmbXX6o
103 ms
watch.js
7 ms
76 ms
r.js
245 ms
2814ca30-51f0-40a9-8b08-8aa2f642dcc3.js
24 ms
WRf4.js
9 ms
101 ms
259 ms
cdm_protocol.js
182 ms
www-embed-player-vfl5foy2V.css
82 ms
www-embed-player.js
123 ms
63 ms
95 ms
256 ms
9aKOW9kHIBrJTB9ONj-e1oyTZuOGlgCE-J5p-KupNmo.js
15 ms
ad_status.js
33 ms
46 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
24 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
27 ms
tag.gif
269 ms
lw.php
229 ms
rle.cgi
297 ms
261 ms
close_new_s.png
1051 ms
dumedia.js
418 ms
nvid.png
400 ms
jsonp
306 ms
lsb
288 ms
146 ms
nvid.png
121 ms
139 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
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.
savage.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
Page has valid source maps
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
Tap targets are not sized appropriately
RU
N/A
WINDOWS-1251
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 neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Savage.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.
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: