Access auto1.by. Auto1.by - Интернет-портал автозапчастей, аксессуаров и технических жидкостей Автозапчасти в Минске,...

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

29/100

10%

LCP (Largest Contentful Paint)

Value16.2 s

0/100

25%

SI (Speed Index)

Value12.6 s

3/100

10%

TBT (Total Blocking Time)

Value3,840 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.322

36/100

15%

TTI (Time to Interactive)

Value27.7 s

0/100

10%

auto1.by

795 ms

museo-sans.css

415 ms

bootstrap.min.css

519 ms

jquery.plugins.min.css

640 ms

style.min.css

534 ms

Our browser made a total of 125 requests to load all elements on the main page. We found that 80% of them (100 requests) were addressed to the original Auto1.by, 11% (14 requests) were made to Images.auto1.by and 2% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (4.7 sec) belongs to the original domain Auto1.by.

Content Size

2.6 MB

After Optimization

2.1 MB

In fact, the total size of Auto1.by main page is 2.6 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. Images take 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 283.0 kB

Original 355.8 kB
After minification 307.1 kB
After compression 72.8 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 48.7 kB, which is 14% 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 283.0 kB or 80% of the original size.

Image Optimization

-4%

Potential reduce by 51.8 kB

Original 1.3 MB
After minification 1.2 MB

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. Auto1 images are well optimized though.

JavaScript Optimization

-15%

Potential reduce by 102.5 kB

Original 665.9 kB
After minification 665.9 kB
After compression 563.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 102.5 kB or 15% of the original size.

CSS Optimization

-24%

Potential reduce by 80.4 kB

Original 340.4 kB
After minification 303.1 kB
After compression 260.0 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. Auto1.by needs all CSS files to be minified and compressed as it can save up to 80.4 kB or 24% of the original size.

Requests Now

119

After Optimization

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

Accessibility Issues

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.

High

button, link, and menuitem elements do not have accessible names.

High

ARIA IDs are not unique

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.

High

Buttons do not have an accessible name

Low

No form fields have multiple labels

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

These are opportunities to improve the legibility of your content.

High

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

These are opportunities to improve keyboard navigation in your application.

High

Heading elements are not in a sequentially-descending order

These items highlight common accessibility best practices.

High

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

Areas of Improvement

High

Does not use HTTPS

High

Requests the geolocation permission on page load

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

Search Engine Optimization Advices

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

High

Links are not crawlable

Format your HTML in a way that enables crawlers to better understand your app’s content.

High

Image elements do not have [alt] attributes

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/).

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

auto1.by

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

Report Summary

Performance

Accessibility

Best Practices

SEO

Auto1.by - Интернет-портал автозапчастей, аксессуаров и технических жидкостей Автозапчасти в Минске, купить запчасти для автомобиля

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

auto1.by

museo-sans.css

bootstrap.min.css

jquery.plugins.min.css

style.min.css

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

auto1.by

museo-sans.css

bootstrap.min.css

jquery.plugins.min.css

style.min.css

fotorama.css

datatables.min.css

app.css

app.css

jquery.min.js

js

jquery.plugins.min.js

bootstrap.min.js

jstree.min.js

fotorama.js

SharedJs

CustomJs

gtm.js

analytics.js

fbevents.js

BannerOpt_4.png

arrow-pointing-left.svg

close.svg

angle_right.svg

logo.png

operators_logo.png

logo.svg

autospace.png

Instagram_icon.png

vk_icon.png

temot.png

Banner_3.png

banOpt_4.png

ban_3.png

procent.webp

%D1%87%D0%B5%D1%80%D0%BD%D0%B0%D1%8F-%D0%BF%D1%8F%D1%82%D0%BD%D0%B8%D1%86%D0%B0-%D0%BD%D0%B0-%D1%81%D0%B0%D0%B9%D1%82%D0%B5.png

%D0%BA%D0%B0%D1%80%D1%82%D0%B8%D0%BD%D0%BA%D0%B0-%D0%BD%D0%BE%D0%B2%D0%BE%D1%81%D1%82%D0%B8_%D1%82%D0%B5%D0%BA%D0%BD%D0%BE%D1%80%D0%BE%D1%82.png

%D0%B1%D1%80%D0%B5%D0%BD%D0%B4-%D0%B3%D0%BE%D0%B4%D0%B0-2024.png

krauf.png

icon1.png

icon1-hover.png

icon3.png

icon3-hover.png