Tools & Wizards About Us
xistore.by screenshot

Report Summary

  • 15

    Performance

    Renders faster than
    27% of other websites

  • 62

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

xistore.by

Первый фирменный магазин умных устройств в Беларуси :: Xistore.by

Page Load Speed

9.9 sec in total

First Response

3.4 sec

Resources Loaded

5.7 sec

Page Rendered

843 ms

xistore.by screenshot

About Website

Welcome to xistore.by homepage info - get ready to check Xistore best content for Belarus right away, or after learning these important things about xistore.by

Купить умные устройства в первом фирменном магазине Xistore в Беларуси. Только оригинальная продукция, первоклассный сервис и забота о каждом клиенте.

Visit xistore.by

Key Findings

We analyzed Xistore.by page load time and found that the first response time was 3.4 sec 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. This domain responded with an error, which can significantly jeopardize Xistore.by rating and web reputation

Performance Metrics

xistore.by performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value9.0 s

0/100

10%

LCP (Largest Contentful Paint)

Value10.0 s

0/100

25%

SI (Speed Index)

Value20.9 s

0/100

10%

TBT (Total Blocking Time)

Value12,640 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.017

100/100

15%

TTI (Time to Interactive)

Value30.6 s

0/100

10%

Network Requests Diagram

xistore.by

3373 ms

xistore.by

1137 ms

css2

34 ms

kernel_main0.css

342 ms

kernel_socialservices0.css

365 ms

Our browser made a total of 42 requests to load all elements on the main page. We found that 90% of them (38 requests) were addressed to the original Xistore.by, 2% (1 request) were made to Fonts.googleapis.com and 2% (1 request) were made to Bitrix.info. The less responsive or slowest element that took the longest time to load (3.4 sec) belongs to the original domain Xistore.by.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.4 MB (65%)

Content Size

2.1 MB

After Optimization

738.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Xistore.by main page is 2.1 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. 45% of websites need less resources to load. HTML takes 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-94%

Potential reduce by 1.3 MB

  • Original 1.3 MB
  • After minification 884.3 kB
  • After compression 77.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. This page needs HTML code to be minified as it can gain 444.3 kB, which is 33% 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 1.3 MB or 94% of the original size.

Image Optimization

-3%

Potential reduce by 4.2 kB

  • Original 164.5 kB
  • After minification 160.3 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. Xistore images are well optimized though.

JavaScript Optimization

-9%

Potential reduce by 22.9 kB

  • Original 250.2 kB
  • After minification 250.2 kB
  • After compression 227.4 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.

CSS Optimization

-26%

Potential reduce by 98.0 kB

  • Original 371.4 kB
  • After minification 367.4 kB
  • After compression 273.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. Xistore.by needs all CSS files to be minified and compressed as it can save up to 98.0 kB or 26% of the original size.

Requests Breakdown

Number of requests can be reduced by 11 (28%)

Requests Now

39

After Optimization

28

  • Images
  • JavaScript
  • CSS

The browser has sent 39 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Xistore. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

xistore.by

xistore.by

3373 ms

xistore.by

xistore.by

1137 ms

css2

css2

34 ms

kernel_main0.css

kernel_main0.css

342 ms

kernel_socialservices0.css

kernel_socialservices0.css

365 ms

page_ebbeba2e0fb9180394c0b6daff5fb9080.css

page_ebbeba2e0fb9180394c0b6daff5fb9080.css

488 ms

template_9e0b3ec337f4a68adbd9d1ccc413ba360.css

template_9e0b3ec337f4a68adbd9d1ccc413ba360.css

827 ms

template_9e0b3ec337f4a68adbd9d1ccc413ba361.css

template_9e0b3ec337f4a68adbd9d1ccc413ba361.css

610 ms

popup.min.css

popup.min.css

450 ms

kernel_main.js

kernel_main.js

470 ms

ajax.min.js

ajax.min.js

477 ms

kernel_socialservices.js

kernel_socialservices.js

561 ms

template_b3b7fc74d29645aefc565cf26122d2ce.js

template_b3b7fc74d29645aefc565cf26122d2ce.js

706 ms

ba.js

ba.js

366 ms

gtm.js

gtm.js

192 ms

Rectangle_photo.png

Rectangle_photo.png

187 ms

logo-white.svg

logo-white.svg

184 ms

3a6e2012de490b50a836730848226652_1206_460_50@x2.jpg

3a6e2012de490b50a836730848226652_1206_460_50@x2.jpg

485 ms

arrow-right.svg

arrow-right.svg

182 ms

b3d26aba35faf832b3920bdaca42d541_78_78_80.png

b3d26aba35faf832b3920bdaca42d541_78_78_80.png

185 ms

c06790675ac9664bb1474f41450eb63c_78_78_80.png

c06790675ac9664bb1474f41450eb63c_78_78_80.png

182 ms

57c03c49c47ec4a32128bea47aa5927d_78_78_80.png

57c03c49c47ec4a32128bea47aa5927d_78_78_80.png

228 ms

1d361aca6770ac99e028e86cd45de98e_78_78_80.png

1d361aca6770ac99e028e86cd45de98e_78_78_80.png

243 ms

6bd14b5b90cb81952fc41dc58cbba42e_78_78_80.png

6bd14b5b90cb81952fc41dc58cbba42e_78_78_80.png

244 ms

5980905c3048b3896ad55f2c8c86ad43_78_78_80.png

5980905c3048b3896ad55f2c8c86ad43_78_78_80.png

244 ms

f92845a5e9eeddc92379971ae764a4dc_78_78_80.png

f92845a5e9eeddc92379971ae764a4dc_78_78_80.png

244 ms

767425bbef915b15a4bed7949aaf3624_78_78_80.png

767425bbef915b15a4bed7949aaf3624_78_78_80.png

338 ms

2dbcdb50ef4aafb74ccbf425041ab8f8.svg

2dbcdb50ef4aafb74ccbf425041ab8f8.svg

345 ms

e4f1195815004901dc9e210409dfc0b7.svg

e4f1195815004901dc9e210409dfc0b7.svg

349 ms

7dd178e0d10889164cccd35e4a1f5056.svg

7dd178e0d10889164cccd35e4a1f5056.svg

357 ms

663d8b18dc9fc812bbc919f837fc2726.svg

663d8b18dc9fc812bbc919f837fc2726.svg

363 ms

e5044be51f97d539128096996258cbde.svg

e5044be51f97d539128096996258cbde.svg

459 ms

c4a7ea967337407386e65d2e034f842a.svg

c4a7ea967337407386e65d2e034f842a.svg

459 ms

loader.svg

loader.svg

466 ms

sprite.svg

sprite.svg

373 ms

xistore_logo_v2_vertical_grayText.svg

xistore_logo_v2_vertical_grayText.svg

397 ms

sprite.svg

sprite.svg

449 ms

font

font

57 ms

bonusCard_new.svg

bonusCard_new.svg

344 ms

xistoreSquircle-logo.svg

xistoreSquircle-logo.svg

117 ms

footer_card_logo_new_v3.png

footer_card_logo_new_v3.png

124 ms

login-sprite.svg

login-sprite.svg

120 ms

Accessibility Review

xistore.by accessibility score

62

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

ARIA toggle fields do not have accessible names

High

[aria-*] attributes do not have valid values

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

High

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

Best Practices

xistore.by best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

xistore.by SEO score

83

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    RU

  • Language Claimed

    RU

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Xistore.by 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 Xistore.by 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.

Social Sharing Optimization

xistore.by

Open Graph description is not detected on the main page of Xistore. 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: