Tools & Wizards About Us
gocar.by screenshot

Report Summary

  • 37

    Performance

    Renders faster than
    56% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 66% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

gocar.by

Попутчик и попутчики на авто: сайт поиска попутчиков, объявлений, обсуждения - Попутчики и попутки Беларусь GoCar.by

Page Load Speed

5.3 sec in total

First Response

542 ms

Resources Loaded

4.5 sec

Page Rendered

208 ms

gocar.by screenshot

About Website

Click here to check amazing Go Car content for Belarus. Otherwise, check out these important facts you probably never knew about gocar.by

Удобный поиск попутки. Попутчик может выбрать несколько попуток из списка и упорядочить их по цене. Быстрое создание поездки. Альтернативный маршрут. Уведомление по почте. Рейтинг водителей.Оставить о...

Visit gocar.by

Key Findings

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

Performance Metrics

gocar.by performance score

37

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.2 s

8/100

10%

LCP (Largest Contentful Paint)

Value6.5 s

9/100

25%

SI (Speed Index)

Value8.1 s

21/100

10%

TBT (Total Blocking Time)

Value590 ms

50/100

30%

CLS (Cumulative Layout Shift)

Value0.017

100/100

15%

TTI (Time to Interactive)

Value12.2 s

15/100

10%

Network Requests Diagram

gocar.by

542 ms

www.gocar.by

829 ms

css

404 ms

css

619 ms

bootstrap

890 ms

Our browser made a total of 55 requests to load all elements on the main page. We found that 56% of them (31 requests) were addressed to the original Gocar.by, 16% (9 requests) were made to St6-21.vk.com and 11% (6 requests) were made to Vk.com. The less responsive or slowest element that took the longest time to load (922 ms) belongs to the original domain Gocar.by.

Page Optimization Overview & Recommendations

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

Content Size

1.3 MB

After Optimization

1.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-81%

Potential reduce by 50.6 kB

  • Original 62.7 kB
  • After minification 51.9 kB
  • After compression 12.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 10.8 kB, which is 17% 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 50.6 kB or 81% of the original size.

Image Optimization

-18%

Potential reduce by 168.9 kB

  • Original 958.9 kB
  • After minification 790.0 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, Go Car needs image optimization as it can save up to 168.9 kB or 18% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-19%

Potential reduce by 28.0 kB

  • Original 145.9 kB
  • After minification 141.7 kB
  • After compression 117.9 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 28.0 kB or 19% of the original size.

CSS Optimization

-32%

Potential reduce by 50.7 kB

  • Original 156.1 kB
  • After minification 156.1 kB
  • After compression 105.4 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. Gocar.by needs all CSS files to be minified and compressed as it can save up to 50.7 kB or 32% of the original size.

Requests Breakdown

Number of requests can be reduced by 30 (60%)

Requests Now

50

After Optimization

20

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

gocar.by

gocar.by

542 ms

www.gocar.by

www.gocar.by

829 ms

css

css

404 ms

css

css

619 ms

bootstrap

bootstrap

890 ms

select2.min.css

select2.min.css

28 ms

select2-bootstrap.min.css

select2-bootstrap.min.css

543 ms

jquery

jquery

683 ms

jqueryval

jqueryval

556 ms

jqueryui

jqueryui

685 ms

bootstrap

bootstrap

683 ms

jquery.placeholder.js

jquery.placeholder.js

609 ms

Layout.js

Layout.js

694 ms

select2.min.js

select2.min.js

17 ms

Index.js

Index.js

733 ms

openapi.318ba3d5a50b8d6990cb0284cb0e0963.js

openapi.318ba3d5a50b8d6990cb0284cb0e0963.js

254 ms

logo-header.png

logo-header.png

154 ms

by.png

by.png

154 ms

Moskva.png

Moskva.png

276 ms

Vilnus.png

Vilnus.png

136 ms

Belostok.png

Belostok.png

248 ms

Varshava.png

Varshava.png

273 ms

Grodno.png

Grodno.png

259 ms

Sankt-piterburg.png

Sankt-piterburg.png

275 ms

mogilev.jpg

mogilev.jpg

274 ms

Polotsk.JPG

Polotsk.JPG

371 ms

Kiev.png

Kiev.png

387 ms

user-man-driver-72.png

user-man-driver-72.png

409 ms

35757

35757

413 ms

36489

36489

922 ms

user-woman-driver-72.png

user-woman-driver-72.png

411 ms

all.js

all.js

99 ms

home-search.jpg

home-search.jpg

452 ms

footer-social-network.png

footer-social-network.png

471 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

474 ms

ga.js

ga.js

32 ms

watch.js

watch.js

25 ms

all.js

all.js

21 ms

__utm.gif

__utm.gif

23 ms

44 ms

collect

collect

30 ms

upload.gif

upload.gif

128 ms

widget_like.php

widget_like.php

309 ms

loader_nav21095490942_3.js

loader_nav21095490942_3.js

297 ms

lite.93f44416.css

lite.93f44416.css

612 ms

lang3_2.js

lang3_2.js

685 ms

c3d11fba.475e3ac7.js

c3d11fba.475e3ac7.js

499 ms

vkui.6d5e2dae.css

vkui.6d5e2dae.css

657 ms

xdm.js

xdm.js

524 ms

widgets.d2d14ebe.css

widgets.d2d14ebe.css

533 ms

al_like.js

al_like.js

533 ms

base.ec2ae8ae.css

base.ec2ae8ae.css

631 ms

lite.bcf10ece3464fec8b554bde483fa2494.js

lite.bcf10ece3464fec8b554bde483fa2494.js

308 ms

like_widget.png

like_widget.png

89 ms

upload.gif

upload.gif

79 ms

Accessibility Review

gocar.by accessibility score

87

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

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

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

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

Best Practices

gocar.by best practices score

83

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

SEO Factors

gocar.by SEO score

100

Search Engine Optimization Advices

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

    N/A

  • Encoding

    UTF-8

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

gocar.by

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