10.2 sec in total
742 ms
9.1 sec
346 ms
Click here to check amazing X5 content for Russia. Otherwise, check out these important facts you probably never knew about x5.ru
Visit x5.ruWe analyzed X5.ru page load time and found that the first response time was 742 ms and then it took 9.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
x5.ru performance score
name
value
score
weighting
Value2.6 s
64/100
10%
Value3.7 s
57/100
25%
Value5.9 s
49/100
10%
Value370 ms
71/100
30%
Value0
100/100
15%
Value5.5 s
70/100
10%
742 ms
504 ms
369 ms
515 ms
686 ms
Our browser made a total of 77 requests to load all elements on the main page. We found that 75% of them (58 requests) were addressed to the original X5.ru, 13% (10 requests) were made to Google.com and 5% (4 requests) were made to Gstatic.com. The less responsive or slowest element that took the longest time to load (5.2 sec) belongs to the original domain X5.ru.
Page size can be reduced by 1.8 MB (17%)
10.5 MB
8.7 MB
In fact, the total size of X5.ru main page is 10.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. 60% of websites need less resources to load. Images take 8.1 MB which makes up the majority of the site volume.
Potential reduce by 98.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 13.7 kB, which is 11% 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 98.6 kB or 82% of the original size.
Potential reduce by 65.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. X5 images are well optimized though.
Potential reduce by 1.1 MB
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 1.1 MB or 72% of the original size.
Potential reduce by 470.6 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. X5.ru needs all CSS files to be minified and compressed as it can save up to 470.6 kB or 75% of the original size.
Number of requests can be reduced by 32 (46%)
70
38
The browser has sent 70 CSS, Javascripts, AJAX and image requests in order to completely render the main page of X5. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
www.x5.ru
742 ms
en
504 ms
corev15.css
369 ms
style.css
515 ms
brand-style.css
686 ms
jquery-1.11.2.min.js
1197 ms
init.js
1396 ms
ScriptResource.axd
1008 ms
blank.js
647 ms
ScriptResource.axd
793 ms
x5changes.js
817 ms
modernizr.2.8.3.min.js
926 ms
detectizr.min.js
1384 ms
x5searchstyle.css
949 ms
WebResource.axd
1060 ms
jquery-migrate-1.2.1.min.js
991 ms
owl.carousel.min.js
1054 ms
idangerous.swiper.min.js
1102 ms
jquery.magnific-popup.min.js
1246 ms
default.js
1197 ms
jquery.mask.min.js
1244 ms
api.js
38 ms
favicon.ico
216 ms
spcommon.png
214 ms
logo.png
212 ms
searchresultui.png
214 ms
dollar.png
214 ms
pokupateli.png
215 ms
magaziny.png
296 ms
logo-01.jpg
297 ms
logo-01-sm.jpg
496 ms
logo-02.jpg
297 ms
logo-02-sm.jpg
300 ms
logo-03.jpg
300 ms
logo-03-sm.jpg
833 ms
logo-white.png
503 ms
2F433E_1_0.woff
468 ms
logo-orange.png
436 ms
icons-s2c2bbc4f9d.png
441 ms
header-homepage-01.jpg
2083 ms
header-homepage-02.jpg
2468 ms
header-homepage-03.jpg
1457 ms
header-homepage-04.jpg
2423 ms
03.jpg
821 ms
swipe01b.png
4221 ms
2F433E_0_0.woff
1211 ms
2F433E_2_0.woff
1482 ms
swipe02a.png
4751 ms
recaptcha__en.js
157 ms
analytics.js
136 ms
sp.init.js
1596 ms
clientrenderer.js
1734 ms
ScriptResx.ashx
2012 ms
774 ms
swipe01b.png
3464 ms
swipe02a.png
5202 ms
collect
38 ms
anchor
33 ms
anchor
46 ms
anchor
41 ms
anchor
48 ms
anchor
47 ms
anchor
46 ms
anchor
46 ms
initstrings.js
2331 ms
styles__ltr.css
25 ms
3S-QlPMSNPmZHIC0k0XLHhyc4Z2xiLseOE2qhpfcAp0.js
117 ms
webworker.js
116 ms
logo_48.png
54 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
195 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
196 ms
recaptcha__en.js
85 ms
Stock_Index_Up.png
1787 ms
strings.js
540 ms
core.js
775 ms
search.clientcontrols.js
393 ms
corev15.css
158 ms
x5.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
Image elements do not have [alt] attributes
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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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.
x5.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
Missing source maps for large first-party JavaScript
x5.ru SEO score
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise X5.ru can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that X5.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.
x5.ru
Open Graph description is not detected on the main page of X5. 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: