Tools & Wizards About Us
gocar.by screenshot

Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 67% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

gocar.by

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

Page Load Speed

12.2 sec in total

First Response

577 ms

Resources Loaded

11.1 sec

Page Rendered

494 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 577 ms and then it took 11.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

gocar.by performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

14/100

10%

LCP (Largest Contentful Paint)

Value6.0 s

13/100

25%

SI (Speed Index)

Value10.3 s

8/100

10%

TBT (Total Blocking Time)

Value10,550 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.017

100/100

15%

TTI (Time to Interactive)

Value17.1 s

4/100

10%

Network Requests Diagram

gocar.by

577 ms

www.gocar.by

883 ms

css

744 ms

css

645 ms

bootstrap

900 ms

Our browser made a total of 66 requests to load all elements on the main page. We found that 52% of them (34 requests) were addressed to the original Gocar.by, 15% (10 requests) were made to Vk.com and 12% (8 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (4.9 sec) relates to the external source Vk.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 430.0 kB (32%)

Content Size

1.3 MB

After Optimization

911.1 kB

  • 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. 55% of websites need less resources to load. Images take 980.5 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 46.7 kB

  • Original 57.3 kB
  • After minification 45.7 kB
  • After compression 10.5 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 11.6 kB, which is 20% 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 46.7 kB or 82% of the original size.

Image Optimization

-17%

Potential reduce by 162.3 kB

  • Original 980.5 kB
  • After minification 818.2 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 162.3 kB or 17% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-71%

Potential reduce by 185.7 kB

  • Original 259.8 kB
  • After minification 200.1 kB
  • After compression 74.1 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 185.7 kB or 71% of the original size.

CSS Optimization

-81%

Potential reduce by 35.2 kB

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

Requests Breakdown

Number of requests can be reduced by 32 (52%)

Requests Now

61

After Optimization

29

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 61 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 24 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

gocar.by

gocar.by

577 ms

www.gocar.by

www.gocar.by

883 ms

css

css

744 ms

css

css

645 ms

bootstrap

bootstrap

900 ms

openapi.js

openapi.js

390 ms

jquery

jquery

379 ms

jqueryval

jqueryval

502 ms

jqueryui

jqueryui

1079 ms

bootstrap

bootstrap

392 ms

jquery.placeholder.js

jquery.placeholder.js

501 ms

Layout.js

Layout.js

505 ms

js

js

69 ms

js

js

131 ms

Index.js

Index.js

584 ms

logo-header.png

logo-header.png

156 ms

by.png

by.png

128 ms

mercedes-sprinter-316-cdi-vip-main_135-90.jpg

mercedes-sprinter-316-cdi-vip-main_135-90.jpg

146 ms

Moskva.png

Moskva.png

443 ms

Vilnus.png

Vilnus.png

771 ms

Belostok.png

Belostok.png

771 ms

Varshava.png

Varshava.png

772 ms

Grodno.png

Grodno.png

443 ms

Sankt-piterburg.png

Sankt-piterburg.png

795 ms

mogilev.jpg

mogilev.jpg

772 ms

Polotsk.JPG

Polotsk.JPG

796 ms

Kiev.png

Kiev.png

3530 ms

user-man-driver-72.png

user-man-driver-72.png

794 ms

18591

18591

794 ms

14423

14423

793 ms

user-woman-driver-72.png

user-woman-driver-72.png

1065 ms

all.js

all.js

346 ms

home-search.jpg

home-search.jpg

1320 ms

search-from-plot.png

search-from-plot.png

1026 ms

search-to-plot.png

search-to-plot.png

1022 ms

search-s5f9c2ee11a.png

search-s5f9c2ee11a.png

1024 ms

footer-social-network.png

footer-social-network.png

1198 ms

glyphicons-halflings-regular.woff

glyphicons-halflings-regular.woff

1134 ms

379 ms

xd_arbiter.php

xd_arbiter.php

437 ms

xd_arbiter.php

xd_arbiter.php

1707 ms

upload.gif

upload.gif

3100 ms

ga.js

ga.js

192 ms

watch.js

watch.js

55 ms

common.js

common.js

94 ms

util.js

util.js

331 ms

controls.js

controls.js

171 ms

places_impl.js

places_impl.js

87 ms

widget_like.php

widget_like.php

3171 ms

__utm.gif

__utm.gif

111 ms

like.php

like.php

172 ms

powered-by-google-on-white3.png

powered-by-google-on-white3.png

453 ms

autocomplete-icons.png

autocomplete-icons.png

509 ms

collect

collect

1066 ms

OZhivdPHVp_.js

OZhivdPHVp_.js

1528 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

1643 ms

loader_nav19239_3.js

loader_nav19239_3.js

233 ms

lite.css

lite.css

392 ms

lite.js

lite.js

680 ms

lang3_0.js

lang3_0.js

914 ms

widgets.css

widgets.css

1088 ms

xdm.js

xdm.js

1272 ms

al_like.js

al_like.js

4927 ms

stats.js

stats.js

48 ms

AuthenticationService.Authenticate

AuthenticationService.Authenticate

293 ms

like_widget.png

like_widget.png

218 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

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

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: