6.1 sec in total
945 ms
4.9 sec
278 ms
Visit auto.59.ru now to see the best up-to-date Auto 59 content for Russia and also check out these interesting facts you probably never knew about auto.59.ru
Работа в Перми - более 200 новых вакансий и резюме каждый день на 59.ru
Visit auto.59.ruWe analyzed Auto.59.ru page load time and found that the first response time was 945 ms and then it took 5.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
auto.59.ru performance score
name
value
score
weighting
Value1.9 s
86/100
10%
Value5.4 s
20/100
25%
Value5.7 s
50/100
10%
Value200 ms
90/100
30%
Value0
100/100
15%
Value4.6 s
81/100
10%
945 ms
895 ms
894 ms
915 ms
439 ms
Our browser made a total of 114 requests to load all elements on the main page. We found that 3% of them (3 requests) were addressed to the original Auto.59.ru, 51% (58 requests) were made to I.sdska.ru and 7% (8 requests) were made to Reklama.ngs.ru. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source I.sdska.ru.
Page size can be reduced by 808.5 kB (51%)
1.6 MB
765.7 kB
In fact, the total size of Auto.59.ru main page is 1.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. 50% of websites need less resources to load. Javascripts take 690.0 kB which makes up the majority of the site volume.
Potential reduce by 91.7 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 91.7 kB or 80% of the original size.
Potential reduce by 145.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, Auto 59 needs image optimization as it can save up to 145.3 kB or 22% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 474.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 474.7 kB or 69% of the original size.
Potential reduce by 96.7 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. Auto.59.ru needs all CSS files to be minified and compressed as it can save up to 96.7 kB or 81% of the original size.
Number of requests can be reduced by 67 (61%)
109
42
The browser has sent 109 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Auto 59. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 40 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.
auto.59.ru
945 ms
jquery-1.9.1.min.js
895 ms
jquery-1.8.3.min.js
894 ms
jquery.js
915 ms
jquery.xdomainrequest.min.js
439 ms
png.css
440 ms
popup_passport.css
442 ms
styles.css
741 ms
d_common.css
746 ms
d.css
751 ms
jquery.smartbanner.css
928 ms
widgets_common.css
928 ms
widgets.css
929 ms
news_d.css
1044 ms
news_common.css
1046 ms
styles.css
1048 ms
styles.css
1049 ms
widgets.css
1052 ms
pt_serif.css
1053 ms
common.js
1196 ms
sdb.js
1205 ms
jquery.cookie.js
1203 ms
api.js
1652 ms
jquery.waypoints.js
1211 ms
fotorama-4.4.2.js
1356 ms
fotorama.waypoints.js
1346 ms
dohcohT2.js
596 ms
popup.js
1348 ms
ngs-place.js
1348 ms
startpage.js
1356 ms
browser_detect.js
1497 ms
google_charts.js
1500 ms
jquery.smartbanner.js
1500 ms
jquery.multi-ddm.js
1507 ms
scroll.js
1509 ms
dropdown.js
1670 ms
update_browser.js
1681 ms
poll.js
1255 ms
jquery.jcmcarousel.js
1387 ms
x.gif
154 ms
analytics.js
21 ms
boomerang-0.9.1401865982.js
156 ms
top100.cnt
251 ms
2-z13-fd05220a-eaed-4f52-9433-c28cf2ed4c0d.jpg
440 ms
2-z19-7eade24e-55f9-4832-aa67-6a6dfa59de94.jpg
441 ms
2-z32-5da2aee4-0587-4a63-8a84-b52c0b3a8144.jpg
887 ms
2-z25-3de5028e-dc72-40f3-b843-9f5e5085e88f.jpg
441 ms
2-z28-28e9251d-77d3-4cb2-8aec-f5f0c35d84ab.jpg
463 ms
2-z30-c51f36f2-65a1-48d2-8415-550881b6f47d.jpg
441 ms
2-z10-edc97dee-cc43-4cd6-873d-99ef359bdbef.jpg
449 ms
banner-88x31-rambler-gray2.gif
382 ms
logo
266 ms
logo.59.png
155 ms
6.png
156 ms
logo.auto.59.ru.png
159 ms
video.png
157 ms
rugion-logo-white.png
159 ms
rn-logo-white.png
300 ms
18plus_bottom.png
305 ms
203 ms
collect
11 ms
202 ms
p_common.css
154 ms
hit;59
260 ms
59
263 ms
59
264 ms
watch.js
167 ms
watch.js
478 ms
tcounter.js
257 ms
service_icons_simple.gif
155 ms
220 ms
watch.js
401 ms
202 ms
bg_auto.gif
155 ms
2-z8-c2ed986a-3997-40d9-97c9-510f0e72284d.png
903 ms
2-z15-7ec624d3-f5b4-4f8e-8ecd-38b9e175cfbe.png
741 ms
2-z31-678d8e9e-f6d2-47de-9239-6665d278a2d1.png
729 ms
2-z18-92d80dc4-3167-4b75-97f3-52dc19bebeda.png
889 ms
2-z14-9ec08e99-2fca-4e7d-aa5f-2b2a01bb8499.png
625 ms
2-z12-11399646-8a73-48d7-bcc5-1fd4f05b3dc3.jpg
551 ms
2-z23-a6215e05-8dbf-4f18-b36c-258f303fda71.jpg
587 ms
2-z17-18a43f8b-ffa8-4367-b0d4-1ece34bc4d89.png
730 ms
2-z11-7a548721-fd82-4dab-9912-0bbe8230135f.jpg
724 ms
2-z33-2d398320-d00c-4209-b740-e16a9af38ade.png
724 ms
2-z20-4a65b929-8b8b-4591-8bd4-016f39cebef3.png
720 ms
2-z7-ec6b5e76-7c01-4019-b937-0c59ab01e85e.png
734 ms
2-z15-d6cb83da-0187-4d8e-bb61-645c1f64c5cd.png
727 ms
2-z15-a1431611-5bca-4818-8ac2-098ace1f808b.png
734 ms
2-z15-c57561ea-1811-487a-bb90-2d4363304625.png
755 ms
bg_search.gif
156 ms
button.png
155 ms
2-z18-027edc1f-ed40-4ce9-9e8c-08d1418effd5.png
736 ms
2-z8-3b161890-2a1d-47cf-9098-f56973eb2243.png
756 ms
2-z8-0457f6de-4a15-444a-a91a-557539588638.png
926 ms
2-z32-0968482a-2a42-4e28-ac7a-37e4a836149f.png
160 ms
2-z14-7c2da798-3f7c-4d86-a0ff-fb8ceb607161.jpg
610 ms
search-arrow.png
154 ms
bg_red_button.gif
154 ms
title-bull.png
154 ms
line.png
266 ms
201 ms
advert.gif
236 ms
423625521
257 ms
1
126 ms
202 ms
31583963
91 ms
31639928
92 ms
bg_button.gif
155 ms
service_icons.png
311 ms
203 ms
Widget_Login
167 ms
705 ms
sprite_button.png
154 ms
checkauth.php
782 ms
auto.59.ru 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
[aria-*] attributes do not match their roles
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
auto.59.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
auto.59.ru SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
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
EN
N/A
WINDOWS-1251
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Auto.59.ru can be misinterpreted by Google and other search engines. Our service has detected that English 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 Auto.59.ru main page’s claimed encoding is windows-1251. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
auto.59.ru
Open Graph description is not detected on the main page of Auto 59. 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: