Tools & Wizards About Us
aw.by screenshot

Report Summary

  • 51

    Performance

    Renders faster than
    69% of other websites

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 73

    SEO

    Google-friendlier than
    31% of websites

aw.by

Автомобильный информационный портал - AW.BY

Page Load Speed

3.3 sec in total

First Response

840 ms

Resources Loaded

2.3 sec

Page Rendered

199 ms

aw.by screenshot

About Website

Welcome to aw.by homepage info - get ready to check AW best content for Belarus right away, or after learning these important things about aw.by

Автомобильный информационный портал - AW.BY. Объявления о продаже, покупке, обмене авто новых и б/у, запчастей на авторынке Беларуси. Фото, отзывы, авто-новости

Visit aw.by

Key Findings

We analyzed Aw.by page load time and found that the first response time was 840 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

aw.by performance score

51

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

66/100

10%

LCP (Largest Contentful Paint)

Value8.5 s

1/100

25%

SI (Speed Index)

Value4.4 s

73/100

10%

TBT (Total Blocking Time)

Value470 ms

61/100

30%

CLS (Cumulative Layout Shift)

Value0.027

100/100

15%

TTI (Time to Interactive)

Value8.5 s

38/100

10%

Network Requests Diagram

aw.by

840 ms

style.css

178 ms

highslide.css

181 ms

script.js

182 ms

highslide.js

361 ms

Our browser made a total of 32 requests to load all elements on the main page. We found that 81% of them (26 requests) were addressed to the original Aw.by, 6% (2 requests) were made to Google-analytics.com and 6% (2 requests) were made to Code.jivosite.com. The less responsive or slowest element that took the longest time to load (840 ms) belongs to the original domain Aw.by.

Page Optimization Overview & Recommendations

Page size can be reduced by 120.0 kB (59%)

Content Size

204.3 kB

After Optimization

84.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Aw.by main page is 204.3 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. 30% of websites need less resources to load. Images take 98.2 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 36.1 kB

  • Original 46.5 kB
  • After minification 45.3 kB
  • After compression 10.3 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 36.1 kB or 78% of the original size.

Image Optimization

-54%

Potential reduce by 52.7 kB

  • Original 98.2 kB
  • After minification 45.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. Obviously, AW needs image optimization as it can save up to 52.7 kB or 54% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-2%

Potential reduce by 513 B

  • Original 22.4 kB
  • After minification 22.4 kB
  • After compression 21.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. This website has mostly compressed JavaScripts.

CSS Optimization

-82%

Potential reduce by 30.6 kB

  • Original 37.2 kB
  • After minification 31.4 kB
  • After compression 6.6 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. Aw.by needs all CSS files to be minified and compressed as it can save up to 30.6 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 7 (23%)

Requests Now

30

After Optimization

23

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 30 CSS, Javascripts, AJAX and image requests in order to completely render the main page of AW. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

aw.by

aw.by

840 ms

style.css

style.css

178 ms

highslide.css

highslide.css

181 ms

script.js

script.js

182 ms

highslide.js

highslide.js

361 ms

jquery.min.js

jquery.min.js

368 ms

models.js

models.js

277 ms

bg.jpg

bg.jpg

93 ms

decor.png

decor.png

102 ms

top_bg.png

top_bg.png

93 ms

content_bg.png

content_bg.png

100 ms

logo.png

logo.png

204 ms

zap.gif

zap.gif

382 ms

menubg.gif

menubg.gif

205 ms

menubg2.jpg

menubg2.jpg

205 ms

sidebar.png

sidebar.png

205 ms

4.png

4.png

206 ms

gradient.png

gradient.png

268 ms

13529s.jpg

13529s.jpg

268 ms

bottom_bg.png

bottom_bg.png

247 ms

zap4.gif

zap4.gif

248 ms

zap3.gif

zap3.gif

254 ms

analytics.js

analytics.js

28 ms

rfZFWOwycf

rfZFWOwycf

207 ms

up.png

up.png

319 ms

collect

collect

14 ms

js

js

60 ms

rfZFWOwycf

rfZFWOwycf

424 ms

counter2

counter2

129 ms

rounded-white.png

rounded-white.png

504 ms

zoomout.cur

zoomout.cur

502 ms

loader.white.gif

loader.white.gif

499 ms

Accessibility Review

aw.by accessibility score

68

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

Best Practices

aw.by best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

aw.by SEO score

73

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

High

Document uses plugins

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 doesn't use legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    RU

  • Language Claimed

    RU

  • Encoding

    WINDOWS-1251

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Aw.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 Aw.by 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.

Social Sharing Optimization

aw.by

Open Graph data is detected on the main page of AW. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: