Tools & Wizards About Us
perevoz.by screenshot

Report Summary

  • 61

    Performance

    Renders faster than
    76% of other websites

  • 64

    Accessibility

    Visual factors better than
    that of 29% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

perevoz.by

© Perevoz.by | Сервис поиска частных перевозчиков и спецтехники

Page Load Speed

4.7 sec in total

First Response

502 ms

Resources Loaded

4 sec

Page Rendered

202 ms

perevoz.by screenshot

About Website

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

Сайт предоставляет услуги всех видов частных автомобильных перевозок и аренды автомобильной техники. Транспортные услуги перевозчиков по Беларуси и странам СНГ.

Visit perevoz.by

Key Findings

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

Performance Metrics

perevoz.by performance score

61

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.4 s

72/100

10%

LCP (Largest Contentful Paint)

Value5.9 s

14/100

25%

SI (Speed Index)

Value4.4 s

74/100

10%

TBT (Total Blocking Time)

Value160 ms

93/100

30%

CLS (Cumulative Layout Shift)

Value0.194

63/100

15%

TTI (Time to Interactive)

Value7.1 s

52/100

10%

Network Requests Diagram

perevoz.by

502 ms

perevoz.by

503 ms

www.perevoz.by

994 ms

style.css

122 ms

main.css

246 ms

Our browser made a total of 43 requests to load all elements on the main page. We found that 98% of them (42 requests) were addressed to the original Perevoz.by, 2% (1 request) were made to Mc.yandex.ru. The less responsive or slowest element that took the longest time to load (994 ms) belongs to the original domain Perevoz.by.

Page Optimization Overview & Recommendations

Page size can be reduced by 243.2 kB (15%)

Content Size

1.6 MB

After Optimization

1.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Perevoz.by 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. 40% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 103.8 kB

  • Original 114.9 kB
  • After minification 60.0 kB
  • After compression 11.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. This page needs HTML code to be minified as it can gain 54.9 kB, which is 48% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 103.8 kB or 90% of the original size.

Image Optimization

-6%

Potential reduce by 81.7 kB

  • Original 1.3 MB
  • After minification 1.2 MB

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. Perevoz images are well optimized though.

JavaScript Optimization

-12%

Potential reduce by 25.7 kB

  • Original 213.5 kB
  • After minification 212.6 kB
  • After compression 187.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 25.7 kB or 12% of the original size.

CSS Optimization

-60%

Potential reduce by 32.0 kB

  • Original 53.7 kB
  • After minification 27.9 kB
  • After compression 21.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. Perevoz.by needs all CSS files to be minified and compressed as it can save up to 32.0 kB or 60% of the original size.

Requests Breakdown

Number of requests can be reduced by 20 (56%)

Requests Now

36

After Optimization

16

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

perevoz.by

perevoz.by

502 ms

perevoz.by

perevoz.by

503 ms

www.perevoz.by

www.perevoz.by

994 ms

style.css

style.css

122 ms

main.css

main.css

246 ms

icons.css

icons.css

456 ms

hystmodal.css

hystmodal.css

342 ms

myicons.css

myicons.css

351 ms

chiefslider.css

chiefslider.css

355 ms

float-label.css

float-label.css

364 ms

jquery-ui.css

jquery-ui.css

367 ms

jquery-ui-timepicker-addon.css

jquery-ui-timepicker-addon.css

454 ms

func.js

func.js

467 ms

sjquery.js

sjquery.js

473 ms

jquery.jcarousel.min.js

jquery.jcarousel.min.js

485 ms

ajaxInput.js

ajaxInput.js

487 ms

avto.js

avto.js

567 ms

top-menu2.js

top-menu2.js

567 ms

jquery-3.3.1.js

jquery-3.3.1.js

817 ms

hystmodal.full.js

hystmodal.full.js

617 ms

chiefcarousel.js

chiefcarousel.js

617 ms

chiefcarousel-mouse-click.js

chiefcarousel-mouse-click.js

617 ms

no-scroll-slider.js

no-scroll-slider.js

676 ms

chiefslider.dev.js

chiefslider.dev.js

677 ms

logo-big.png

logo-big.png

348 ms

m_avto673076de02_1647.jpg

m_avto673076de02_1647.jpg

515 ms

m_avto27272665aa_40.jpg

m_avto27272665aa_40.jpg

350 ms

m_avto84961437b5_399.jpg

m_avto84961437b5_399.jpg

446 ms

m_avtode14f7d9ae_11.jpg

m_avtode14f7d9ae_11.jpg

561 ms

m_avto7b63912baf_2004.jpg

m_avto7b63912baf_2004.jpg

480 ms

m_avto2634c0fd3f_1996.jpg

m_avto2634c0fd3f_1996.jpg

609 ms

m_avto68a7163cb2_1990.jpg

m_avto68a7163cb2_1990.jpg

524 ms

m_avto144c4e6336_1987.jpg

m_avto144c4e6336_1987.jpg

561 ms

m_avtodb22678726_1986.jpg

m_avtodb22678726_1986.jpg

598 ms

m_avtob10853bb37_1982.jpg

m_avtob10853bb37_1982.jpg

875 ms

m_avto96aee861ff_16.jpg

m_avto96aee861ff_16.jpg

764 ms

sprinter.jpg

sprinter.jpg

787 ms

OpenSans.ttf

OpenSans.ttf

742 ms

HelveticaNeue.woff

HelveticaNeue.woff

670 ms

road-webp-min.webp

road-webp-min.webp

587 ms

fa-solid-900.woff

fa-solid-900.woff

487 ms

fa-regular-400.woff

fa-regular-400.woff

538 ms

tag.js

tag.js

950 ms

Accessibility Review

perevoz.by accessibility score

64

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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.

Best Practices

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

perevoz.by SEO score

92

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

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

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Perevoz.by can be misinterpreted by Google and other search engines. Our service has detected that Russian is used on the page, and it does not match the claimed English language. Our system also found out that Perevoz.by 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

perevoz.by

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