4.5 sec in total
401 ms
3.9 sec
157 ms
Welcome to parts66.ru homepage info - get ready to check Parts 66 best content for Russia right away, or after learning these important things about parts66.ru
Купить запчасти в магазине автозапчастей по низким ценам в Екатеринбурге, Кургане и Челябинске автозапчасти для иномарок вы можете на Parts66.ru
Visit parts66.ruWe analyzed Parts66.ru page load time and found that the first response time was 401 ms and then it took 4.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
parts66.ru performance score
name
value
score
weighting
Value5.9 s
4/100
10%
Value17.1 s
0/100
25%
Value14.1 s
1/100
10%
Value2,100 ms
7/100
30%
Value0
100/100
15%
Value26.1 s
0/100
10%
401 ms
1408 ms
283 ms
205 ms
206 ms
Our browser made a total of 111 requests to load all elements on the main page. We found that 88% of them (98 requests) were addressed to the original Parts66.ru, 5% (6 requests) were made to Mc.yandex.ru and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Parts66.ru.
Page size can be reduced by 1.0 MB (68%)
1.5 MB
473.4 kB
In fact, the total size of Parts66.ru main page is 1.5 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. 50% of websites need less resources to load. Javascripts take 864.7 kB which makes up the majority of the site volume.
Potential reduce by 91.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 26.6 kB, which is 24% 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 91.9 kB or 83% of the original size.
Potential reduce by 221.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. Obviously, Parts 66 needs image optimization as it can save up to 221.3 kB or 53% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 622.7 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 622.7 kB or 72% of the original size.
Potential reduce by 76.5 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. Parts66.ru needs all CSS files to be minified and compressed as it can save up to 76.5 kB or 83% of the original size.
Number of requests can be reduced by 46 (46%)
100
54
The browser has sent 100 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Parts 66. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
parts66.ru
401 ms
www.parts66.ru
1408 ms
main.css
283 ms
ar2.css
205 ms
rcorners.css
206 ms
parts66.css
288 ms
dc3c.css
202 ms
error-success.css
277 ms
MooDialog.css
294 ms
slide_menu.css
293 ms
fonts.css
292 ms
mootools.js
465 ms
mootools-more.js
660 ms
lib.common.js
393 ms
jquery-1.11.min.js
586 ms
advanced.select.js
391 ms
cf.js
394 ms
jquery-1.11.3.min.js
682 ms
Overlay.js
488 ms
MooDialog.js
492 ms
MooDialog.Fx.js
556 ms
MooDialog.Alert.js
583 ms
MooDialog.Error.js
588 ms
slide_menu.js
650 ms
noconflict.js
677 ms
jquery.transform2d.js
680 ms
md5.js
683 ms
share.js
20 ms
jquery-ui.js
11 ms
dc3c.css
547 ms
11444382059.png
106 ms
11444576010.png
109 ms
11444576243.png
108 ms
11444578437.png
108 ms
11448515566.png
105 ms
11444578464.png
107 ms
11444578492.png
188 ms
11444578512.png
188 ms
11444578532.png
193 ms
11444578556.png
195 ms
11444578586.png
197 ms
11444578599.png
200 ms
11448515609.png
280 ms
11448515674.png
282 ms
11448515694.png
286 ms
11444578699.png
288 ms
11448544736.png
291 ms
11448515716.png
295 ms
11444578806.png
374 ms
11444578849.png
376 ms
11448544765.png
381 ms
11444578867.png
383 ms
11444578881.png
386 ms
11444578893.png
393 ms
11448515733.png
466 ms
11444578943.png
466 ms
11444578956.png
476 ms
11444579989.png
478 ms
11444580014.png
479 ms
11449058243.png
492 ms
11444580036.png
559 ms
11444580054.png
561 ms
11444580070.png
570 ms
11444580085.png
573 ms
11444580106.png
576 ms
11444580127.png
584 ms
hit
264 ms
analytics.js
32 ms
watch.js
625 ms
b-share-icon.png
17 ms
watch.js
179 ms
collect
25 ms
myriad-set-pro_text.woff
841 ms
myriad-set-pro_medium.woff
840 ms
myriad-set-pro_thin.woff
759 ms
myriad-set-pro_ultralight.woff
764 ms
myriad-set-pro_semibold.woff
869 ms
myriad-set-pro_bold.woff
883 ms
collect
65 ms
11444580145.png
787 ms
11444580161.png
787 ms
11444580177.png
844 ms
11444580194.png
844 ms
11444580216.png
860 ms
11444580352.png
861 ms
watch.js
584 ms
11444580373.png
781 ms
11444580387.png
798 ms
11449060280.png
845 ms
11448544831.png
849 ms
11448544839.png
861 ms
avtozapchasti.jpg
956 ms
zapchasti_dla_inomarok.jpg
782 ms
vk.png
799 ms
visa_110x38.png
841 ms
logo1.png
845 ms
submit.png
862 ms
menu-fon.png
862 ms
loading-search.gif
807 ms
bc-t.png
851 ms
bc-r.png
846 ms
bc-b.png
864 ms
bc-l.png
866 ms
bc-tl.png
859 ms
bc-tr.png
807 ms
bc-bl.png
849 ms
bc-br.png
844 ms
news.png
864 ms
advert.gif
280 ms
1
84 ms
26812653
85 ms
parts66.ru accessibility score
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
<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.
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
ARIA IDs are not unique
parts66.ru best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
Issues were logged in the Issues panel in Chrome Devtools
parts66.ru 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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Parts66.ru can be misinterpreted by Google and other search engines. Our service has detected that Russian is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Parts66.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.
parts66.ru
Open Graph description is not detected on the main page of Parts 66. 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: