11.8 sec in total
795 ms
10.7 sec
359 ms
Click here to check amazing Auto1 content for Belarus. Otherwise, check out these important facts you probably never knew about auto1.by
Официальный поставщик в РБ. Тел: 7301. Огромный ассортимент и отличное качество. Удобные каталоги оригинальных автозапчастей по vin и их заменителей. Бесплатная доставка. Скидки
Visit auto1.byWe analyzed Auto1.by page load time and found that the first response time was 795 ms and then it took 11 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
auto1.by performance score
name
value
score
weighting
Value3.7 s
29/100
10%
Value16.2 s
0/100
25%
Value12.6 s
3/100
10%
Value3,840 ms
1/100
30%
Value0.322
36/100
15%
Value27.7 s
0/100
10%
795 ms
415 ms
519 ms
640 ms
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.
Page size can be reduced by 485.7 kB (19%)
2.6 MB
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.
Potential reduce by 283.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. 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.
Potential reduce by 51.8 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. Auto1 images are well optimized though.
Potential reduce by 70.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 70.5 kB or 11% of the original size.
Potential reduce by 80.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. 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.
Number of requests can be reduced by 21 (18%)
119
98
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.
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
fotorama.css
545 ms
datatables.min.css
1004 ms
app.css
889 ms
app.css
1114 ms
jquery.min.js
1033 ms
js
57 ms
jquery.plugins.min.js
1015 ms
bootstrap.min.js
1016 ms
jstree.min.js
1277 ms
fotorama.js
1408 ms
SharedJs
1345 ms
CustomJs
1490 ms
gtm.js
51 ms
analytics.js
232 ms
fbevents.js
200 ms
BannerOpt_4.png
999 ms
arrow-pointing-left.svg
495 ms
close.svg
525 ms
angle_right.svg
1363 ms
logo.png
1493 ms
operators_logo.png
1047 ms
logo.svg
1214 ms
autospace.png
1171 ms
Instagram_icon.png
1061 ms
vk_icon.png
1416 ms
temot.png
1428 ms
Banner_3.png
1368 ms
banOpt_4.png
1218 ms
ban_3.png
1590 ms
procent.webp
2033 ms
%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
1471 ms
%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
2362 ms
%D0%B1%D1%80%D0%B5%D0%BD%D0%B4-%D0%B3%D0%BE%D0%B4%D0%B0-2024.png
1715 ms
krauf.png
1744 ms
icon1.png
1488 ms
icon1-hover.png
1504 ms
icon3.png
1669 ms
icon3-hover.png
1811 ms
icon2.png
1887 ms
icon2-hover.png
1892 ms
icon7.png
1981 ms
icon7-hover.png
2140 ms
icon6.png
2143 ms
icon6-hover.png
2234 ms
icon5.png
2286 ms
icon5-hover.png
2286 ms
icon8.png
2380 ms
icon8-hover.png
2832 ms
icon4.png
3733 ms
icon4-hover.png
2625 ms
icon9.png
2631 ms
icon9-hover.png
2674 ms
icon10.png
3201 ms
icon10-hover.png
3012 ms
7245724523.png
2188 ms
MuseoSansRegular.woff
3267 ms
MuseoSansBold.woff
3277 ms
6738357653.png
2724 ms
collect
14 ms
glyphicons-halflings-regular.woff
3057 ms
icon11.png
3057 ms
icon11-hover.png
4146 ms
icon12.png
3200 ms
icon12-hover.png
3230 ms
loader_4_psqk9q.js
1087 ms
watch.js
241 ms
geolocate
294 ms
8357423724578345.png
1657 ms
2572473746.png
1901 ms
237246535.png
1983 ms
getquantity
2965 ms
search.svg
2982 ms
map.svg
3062 ms
phone.svg
2943 ms
basket.svg
2810 ms
flag.svg
2961 ms
smartphone-call.svg
3081 ms
preimushestva_1.svg
3018 ms
preimushestva_4.svg
4212 ms
preimushestva_2.svg
3189 ms
call.tracker.js
708 ms
styles.min.css
1012 ms
script.min.js
1132 ms
preimushestva_3.svg
3151 ms
preimushestva_5.svg
3021 ms
preimushestva_6.svg
3086 ms
getquantity
3222 ms
getcount
3250 ms
icon14.png
3054 ms
icon14-hover.png
3221 ms
icon16.png
4242 ms
icon16-hover.png
3282 ms
icon17.png
3336 ms
icon17-hover.png
3329 ms
details.svg
3317 ms
truck_icon.png
3362 ms
truck_icon_2.png
3399 ms
pc_icon.png
3239 ms
pc_icon_2.png
4286 ms
wsd_info_logo.png
3177 ms
wsd_thumb_logo_s.png
3153 ms
icon13.png
3123 ms
icon13-hover.png
3398 ms
01.png
3422 ms
02.png
3191 ms
03.png
3357 ms
04.png
3412 ms
05.png
4654 ms
14.png
3186 ms
06.png
3346 ms
07.png
3393 ms
08.png
3434 ms
09.png
3358 ms
10.png
3415 ms
11.png
3465 ms
12.png
3462 ms
15.png
3546 ms
arrow_left.svg
3385 ms
arrow_right.svg
3665 ms
arrow-down.svg
3391 ms
auto1.by accessibility score
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
button, link, and menuitem elements do not have accessible names.
ARIA IDs are not unique
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
Buttons do not have an accessible name
No form fields have multiple labels
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
auto1.by best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Requests the geolocation permission on page load
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
auto1.by SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
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
Document uses legible font sizes
Tap targets are not sized appropriately
RU
RU
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.
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: