Tools & Wizards About Us
autoprestus.ru screenshot

Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 44% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

autoprestus.ru

Volkswagen АВТОПРЕСТУС — официальный дилер Фольксваген в Москве: купить в автосалоне, цены

Page Load Speed

3.7 sec in total

First Response

478 ms

Resources Loaded

2.8 sec

Page Rendered

413 ms

autoprestus.ru screenshot

About Website

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

АВТОПРЕСТУС – официальный дилер Volkswagen в Москве. Все новые модели Фольксваген можно купить в нашем автосалоне по выгодным ценам. Продажа и сервисное обслуживание автомобилей VW. У нас доступно: ✔К...

Visit autoprestus.ru

Key Findings

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

Performance Metrics

autoprestus.ru performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

18/100

10%

LCP (Largest Contentful Paint)

Value4.7 s

32/100

25%

SI (Speed Index)

Value16.8 s

0/100

10%

TBT (Total Blocking Time)

Value3,070 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.162

72/100

15%

TTI (Time to Interactive)

Value23.0 s

1/100

10%

Network Requests Diagram

autoprestus.ru

478 ms

autoprestus.ru

662 ms

js

65 ms

style.dws.8b523ebe48b98aaa445a.css

707 ms

claim

785 ms

Our browser made a total of 29 requests to load all elements on the main page. We found that 7% of them (2 requests) were addressed to the original Autoprestus.ru, 34% (10 requests) were made to Cdn2.kodixauto.ru and 17% (5 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (807 ms) relates to the external source Mc.yandex.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 94.1 kB (23%)

Content Size

418.1 kB

After Optimization

324.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Autoprestus.ru main page is 418.1 kB. 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 201.4 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 89.4 kB

  • Original 106.1 kB
  • After minification 105.3 kB
  • After compression 16.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 89.4 kB or 84% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 28.8 kB
  • After minification 28.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. Autoprestus images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 1.1 kB

  • Original 201.4 kB
  • After minification 201.4 kB
  • After compression 200.3 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

-4%

Potential reduce by 3.6 kB

  • Original 81.8 kB
  • After minification 81.8 kB
  • After compression 78.3 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. Autoprestus.ru has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 13 (62%)

Requests Now

21

After Optimization

8

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 21 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Autoprestus. 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 as a result speed up the page load time.

Network Requests Diagram

autoprestus.ru

autoprestus.ru

478 ms

autoprestus.ru

autoprestus.ru

662 ms

js

js

65 ms

style.dws.8b523ebe48b98aaa445a.css

style.dws.8b523ebe48b98aaa445a.css

707 ms

claim

claim

785 ms

style.dws.6737ffd078c335c17161.js

style.dws.6737ffd078c335c17161.js

632 ms

vendor.dws.15995fd16d360bd55b63.js

vendor.dws.15995fd16d360bd55b63.js

658 ms

core.dws.2e88099fe438eadb689c.js

core.dws.2e88099fe438eadb689c.js

637 ms

dws.004f4d999f8a20a5e544.js

dws.004f4d999f8a20a5e544.js

657 ms

gtm.js

gtm.js

61 ms

gtm.js

gtm.js

61 ms

65a939b403d379282711d280

65a939b403d379282711d280

628 ms

65a939c1dc27de1f3e866d73

65a939c1dc27de1f3e866d73

634 ms

tag.js

tag.js

807 ms

VWHead-400.woff

VWHead-400.woff

163 ms

VWHead-300.woff

VWHead-300.woff

198 ms

VWHead-700.woff

VWHead-700.woff

163 ms

VWHead-800.woff

VWHead-800.woff

285 ms

Iconfont.woff

Iconfont.woff

197 ms

watch.js

watch.js

4 ms

js

js

80 ms

conversion.js

conversion.js

171 ms

js

js

65 ms

analytics.js

analytics.js

39 ms

72 ms

collect

collect

56 ms

collect

collect

42 ms

35 ms

ga-audiences

ga-audiences

63 ms

Accessibility Review

autoprestus.ru accessibility score

77

Accessibility Issues

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

Buttons do not have an accessible name

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

autoprestus.ru best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

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

autoprestus.ru SEO score

86

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

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

autoprestus.ru

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