Tools & Wizards About Us
vika.by screenshot

Report Summary

  • 30

    Performance

    Renders faster than
    50% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

vika.by

Купить шины в Минске. Купить литые диски в Минске. Продажа шин, литых дисков и секреток по низким ценам

Page Load Speed

5 sec in total

First Response

471 ms

Resources Loaded

3.7 sec

Page Rendered

860 ms

vika.by screenshot

About Website

Click here to check amazing Vika content for Belarus. Otherwise, check out these important facts you probably never knew about vika.by

Купить летние шины, зимние шины, всесезонные шины, серкетки, литые диски, шины для внедорожников, шины для микроавтобусов

Visit vika.by

Key Findings

We analyzed Vika.by page load time and found that the first response time was 471 ms and then it took 4.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

vika.by performance score

30

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

58/100

10%

LCP (Largest Contentful Paint)

Value6.5 s

8/100

25%

SI (Speed Index)

Value5.4 s

57/100

10%

TBT (Total Blocking Time)

Value2,020 ms

7/100

30%

CLS (Cumulative Layout Shift)

Value0.099

90/100

15%

TTI (Time to Interactive)

Value12.9 s

13/100

10%

Network Requests Diagram

vika.by

471 ms

vika.by

567 ms

jquery.min.js

30 ms

css

44 ms

style.css

125 ms

Our browser made a total of 30 requests to load all elements on the main page. We found that 50% of them (15 requests) were addressed to the original Vika.by, 17% (5 requests) were made to Api-maps.yandex.ru and 10% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Yastatic.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 167.1 kB (28%)

Content Size

588.1 kB

After Optimization

421.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Vika.by main page is 588.1 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. 20% of websites need less resources to load. Javascripts take 350.5 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 166.4 kB

  • Original 199.5 kB
  • After minification 182.2 kB
  • After compression 33.0 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 166.4 kB or 83% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 4.3 kB
  • After minification 4.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. Vika images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 223 B

  • Original 350.5 kB
  • After minification 350.5 kB
  • After compression 350.3 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

-1%

Potential reduce by 447 B

  • Original 33.9 kB
  • After minification 33.9 kB
  • After compression 33.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. Vika.by has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 15 (71%)

Requests Now

21

After Optimization

6

  • Images
  • JavaScript
  • CSS

The browser has sent 21 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Vika. 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 6 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

vika.by

vika.by

471 ms

vika.by

vika.by

567 ms

jquery.min.js

jquery.min.js

30 ms

css

css

44 ms

style.css

style.css

125 ms

slick.css

slick.css

249 ms

catalog-tires.css

catalog-tires.css

331 ms

home.css

home.css

335 ms

useful-tips.css

useful-tips.css

339 ms

720 ms

app.js

app.js

816 ms

home.js

home.js

482 ms

tag.js

tag.js

950 ms

logo_vikaby.svg

logo_vikaby.svg

119 ms

viber-icon@2x.png

viber-icon@2x.png

115 ms

tg-icon@2x.png

tg-icon@2x.png

113 ms

whatsapp-icon@2x.png

whatsapp-icon@2x.png

119 ms

instagram-icon@2x.png

instagram-icon@2x.png

121 ms

logo_vikaby_footer.svg

logo_vikaby_footer.svg

223 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4kaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4kaVQ.woff

24 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4kaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4kaVQ.woff

42 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4kaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4kaVQ.woff

42 ms

full-d4970f46344c5e9889e597ed64f3cc18926d2def.js

full-d4970f46344c5e9889e597ed64f3cc18926d2def.js

1191 ms

advert.gif

advert.gif

866 ms

grab.cur

grab.cur

149 ms

sync_cookie_image_decide

sync_cookie_image_decide

136 ms

grabbing.cur

grabbing.cur

167 ms

help.cur

help.cur

313 ms

zoom_in.cur

zoom_in.cur

380 ms

sync_cookie_image_decide

sync_cookie_image_decide

154 ms

Accessibility Review

vika.by accessibility score

89

Accessibility Issues

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

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

Heading elements are not in a sequentially-descending order

Best Practices

vika.by best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

vika.by SEO score

98

Search Engine Optimization Advices

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 Vika.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 Vika.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

vika.by

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