Report Summary

  • 37

    Performance

    Renders faster than
    56% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

kart.by

Автозапчасти в Минске по низким ценам в магазине KART.BY

Page Load Speed

4.9 sec in total

First Response

348 ms

Resources Loaded

4.2 sec

Page Rendered

338 ms

kart.by screenshot

About Website

Visit kart.by now to see the best up-to-date KART content for Belarus and also check out these interesting facts you probably never knew about kart.by

У нас вы сможете купить автозапчасти высокого качества и по низким ценам, подбор запчастей по оригинальным каталогам, доставка по Минску и регионам

Visit kart.by

Key Findings

We analyzed Kart.by page load time and found that the first response time was 348 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

kart.by performance score

37

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

23/100

10%

LCP (Largest Contentful Paint)

Value13.5 s

0/100

25%

SI (Speed Index)

Value6.0 s

47/100

10%

TBT (Total Blocking Time)

Value670 ms

45/100

30%

CLS (Cumulative Layout Shift)

Value0.006

100/100

15%

TTI (Time to Interactive)

Value13.6 s

11/100

10%

Network Requests Diagram

kart.by

348 ms

kart.by

616 ms

jquery.mCustomScrollbar.min.css

80 ms

jquery-ui.min.css

90 ms

jquery.fancybox.min.css

82 ms

Our browser made a total of 40 requests to load all elements on the main page. We found that 48% of them (19 requests) were addressed to the original Kart.by, 15% (6 requests) were made to Cdnjs.cloudflare.com and 5% (2 requests) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Kart.by.

Page Optimization Overview & Recommendations

Page size can be reduced by 262.5 kB (36%)

Content Size

720.0 kB

After Optimization

457.5 kB

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

HTML Optimization

-86%

Potential reduce by 261.6 kB

  • Original 304.5 kB
  • After minification 238.9 kB
  • After compression 42.9 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 65.7 kB, which is 22% 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 261.6 kB or 86% of the original size.

JavaScript Optimization

-0%

Potential reduce by 817 B

  • Original 415.5 kB
  • After minification 415.5 kB
  • After compression 414.6 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.

Requests Breakdown

Number of requests can be reduced by 18 (55%)

Requests Now

33

After Optimization

15

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

Accessibility Review

kart.by accessibility score

88

Accessibility Issues

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.

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

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

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

High

Page has valid source maps

SEO Factors

kart.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 Kart.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 Kart.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

Open Graph data is detected on the main page of KART. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: