Tools & Wizards About Us

Report Summary

  • 25

    Performance

    Renders faster than
    44% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

kuzparts.ru

Интернет-магазин KuzParts.ru автозапчасти, запчасти для иномарок, каталог запчастей в Новокузнецк (Главный офис)

Page Load Speed

22.1 sec in total

First Response

696 ms

Resources Loaded

21 sec

Page Rendered

363 ms

About Website

Visit kuzparts.ru now to see the best up-to-date Kuz Parts content for Russia and also check out these interesting facts you probably never knew about kuzparts.ru

Интернет магазин запчастей для иномарок и автомобилей. Покупайте автозапчасти по выгодным ценам. Выгодное предложение в Новокузнецк (Главный офис)

Visit kuzparts.ru

Key Findings

We analyzed Kuzparts.ru page load time and found that the first response time was 696 ms and then it took 21.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.

Performance Metrics

kuzparts.ru performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.9 s

0/100

10%

LCP (Largest Contentful Paint)

Value8.9 s

1/100

25%

SI (Speed Index)

Value10.5 s

7/100

10%

TBT (Total Blocking Time)

Value830 ms

35/100

30%

CLS (Cumulative Layout Shift)

Value0.14

78/100

15%

TTI (Time to Interactive)

Value10.8 s

22/100

10%

Network Requests Diagram

kuzparts.ru

696 ms

kuzparts.ru

5916 ms

application_system-23be795b4c57a95c001f17b41d38e483a2c1c16d6ee8aafc703cec25729326a5.js

16240 ms

watch.js

1 ms

application_system-4081f5e6d82a901148b26a36accfce7af54df700516e72ce18d0c5e192c5d646.css

10793 ms

Our browser made a total of 17 requests to load all elements on the main page. We found that 65% of them (11 requests) were addressed to the original Kuzparts.ru, 12% (2 requests) were made to Google-analytics.com and 12% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (16.2 sec) belongs to the original domain Kuzparts.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 530.4 kB (41%)

Content Size

1.3 MB

After Optimization

761.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Kuzparts.ru main page is 1.3 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. 25% of websites need less resources to load. HTML takes 642.5 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 530.0 kB

  • Original 642.5 kB
  • After minification 599.0 kB
  • After compression 112.5 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 530.0 kB or 82% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 44.0 kB
  • After minification 44.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. Kuz Parts images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 364 B

  • Original 443.9 kB
  • After minification 443.9 kB
  • After compression 443.5 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

-0%

Potential reduce by 0 B

  • Original 161.4 kB
  • After minification 161.4 kB
  • After compression 161.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. Kuzparts.ru has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 3 (25%)

Requests Now

12

After Optimization

9

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

kuzparts.ru accessibility score

76

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 input fields do not have accessible names

High

ARIA IDs are not unique

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

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

Form elements do not have associated labels

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

kuzparts.ru best practices score

67

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

User Experience

Impact

Issue

High

Serves images with low resolution

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

kuzparts.ru SEO score

90

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

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 Kuzparts.ru 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 Kuzparts.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.

Social Sharing Optimization

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