Report Summary

  • 39

    Performance

    Renders faster than
    59% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 75% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 88

    SEO

    Google-friendlier than
    66% of websites

adrive.by

Правила дорожного движения Республики Беларусь

Page Load Speed

8.1 sec in total

First Response

1.1 sec

Resources Loaded

6.6 sec

Page Rendered

410 ms

adrive.by screenshot

About Website

Visit adrive.by now to see the best up-to-date Adrive content for Belarus and also check out these interesting facts you probably never knew about adrive.by

Интерактивные Правила дорожного движения Республики Беларусь – электронный вариант ПДД РБ с всплывающими окнами подсказки, Запоминалки и Группировки белорусских Правил, онлайн тестирование и экспресс ...

Visit adrive.by

Key Findings

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

Performance Metrics

adrive.by performance score

39

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

28/100

10%

LCP (Largest Contentful Paint)

Value3.8 s

56/100

25%

SI (Speed Index)

Value6.2 s

43/100

10%

TBT (Total Blocking Time)

Value2,020 ms

7/100

30%

CLS (Cumulative Layout Shift)

Value0.023

100/100

15%

TTI (Time to Interactive)

Value13.5 s

11/100

10%

Network Requests Diagram

adrive.by

1089 ms

adrive.css

492 ms

adrive.png

327 ms

pdd_online.png

328 ms

ADiPDD_b.png

324 ms

Our browser made a total of 34 requests to load all elements on the main page. We found that 82% of them (28 requests) were addressed to the original Adrive.by, 3% (1 request) were made to Tit.by and 3% (1 request) were made to Counter.rambler.ru. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Adrive.by.

Page Optimization Overview & Recommendations

Page size can be reduced by 57.0 kB (36%)

Content Size

156.3 kB

After Optimization

99.3 kB

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

HTML Optimization

-77%

Potential reduce by 45.7 kB

  • Original 59.1 kB
  • After minification 57.7 kB
  • After compression 13.4 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 45.7 kB or 77% of the original size.

Image Optimization

-2%

Potential reduce by 1.5 kB

  • Original 84.3 kB
  • After minification 82.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. Adrive images are well optimized though.

CSS Optimization

-76%

Potential reduce by 9.8 kB

  • Original 12.9 kB
  • After minification 11.5 kB
  • After compression 3.1 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. Adrive.by needs all CSS files to be minified and compressed as it can save up to 9.8 kB or 76% of the original size.

Requests Breakdown

Number of requests can be reduced by 12 (38%)

Requests Now

32

After Optimization

20

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

Accessibility Review

adrive.by accessibility score

90

Accessibility Issues

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

High

[aria-*] attributes do not have valid values

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

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

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

Best Practices

adrive.by best practices score

75

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

adrive.by SEO score

88

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    RU

  • Language Claimed

    N/A

  • Encoding

    WINDOWS-1251

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

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