Access avtofan.ru. , , , , , , -

Report Summary

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

12/100

10%

LCP (Largest Contentful Paint)

Value15.0 s

0/100

25%

SI (Speed Index)

Value17.8 s

0/100

10%

TBT (Total Blocking Time)

Value2,190 ms

6/100

30%

CLS (Cumulative Layout Shift)

Value0.555

13/100

15%

TTI (Time to Interactive)

Value26.0 s

0/100

10%

www.avtofan.ru

729 ms

style.css

314 ms

main.css

476 ms

lightbox.css

317 ms

jquery.js

1027 ms

Our browser made a total of 29 requests to load all elements on the main page. We found that 79% of them (23 requests) were addressed to the original Avtofan.ru, 14% (4 requests) were made to Mc.yandex.ru and 7% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Avtofan.ru.

Content Size

390.6 kB

After Optimization

237.7 kB

In fact, the total size of Avtofan.ru main page is 390.6 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. 20% of websites need less resources to load. Javascripts take 202.8 kB which makes up the majority of the site volume.

HTML Optimization

-70%

Potential reduce by 7.3 kB

Original 10.4 kB
After minification 10.2 kB
After compression 3.1 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 7.3 kB or 70% of the original size.

Image Optimization

-7%

Potential reduce by 12.1 kB

Original 164.7 kB
After minification 152.6 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. Avtofan images are well optimized though.

JavaScript Optimization

-61%

Potential reduce by 124.1 kB

Original 202.8 kB
After minification 189.6 kB
After compression 78.8 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 124.1 kB or 61% of the original size.

CSS Optimization

-75%

Potential reduce by 9.4 kB

Original 12.7 kB
After minification 10.2 kB
After compression 3.2 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. Avtofan.ru needs all CSS files to be minified and compressed as it can save up to 9.4 kB or 75% of the original size.

Requests Now

After Optimization

The browser has sent 27 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Avtofan. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts 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

[aria-hidden="true"] elements contain focusable descendents

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

High

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

High

Form elements do not have associated labels

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 are opportunities to improve the interpretation of your content by users in different locales.

High

<html> element does not have a [lang] attribute

Search Engine Optimization Advices

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

High

Links are not crawlable

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

N/A
Language Claimed

N/A
Encoding

UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Avtofan.ru can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Avtofan.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

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