Tools & Wizards About Us
taxi.yandex.ee screenshot

Report Summary

  • 29

    Performance

    Renders faster than
    49% of other websites

  • 64

    Accessibility

    Visual factors better than
    that of 29% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

taxi.yandex.ee

Yandex Go — request ride

Page Load Speed

3.8 sec in total

First Response

570 ms

Resources Loaded

3.2 sec

Page Rendered

49 ms

taxi.yandex.ee screenshot

About Website

Visit taxi.yandex.ee now to see the best up-to-date Taxi Yandex content for Russia and also check out these interesting facts you probably never knew about taxi.yandex.ee

This service will help you quickly order an inexpensive official taxi using the site or mobile app. The taxi will arrive in 7 minutes. Pay with cash or card.

Visit taxi.yandex.ee

Key Findings

We analyzed Taxi.yandex.ee page load time and found that the first response time was 570 ms and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

taxi.yandex.ee performance score

29

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

55/100

10%

LCP (Largest Contentful Paint)

Value12.7 s

0/100

25%

SI (Speed Index)

Value13.6 s

2/100

10%

TBT (Total Blocking Time)

Value1,020 ms

26/100

30%

CLS (Cumulative Layout Shift)

Value0.074

95/100

15%

TTI (Time to Interactive)

Value11.9 s

17/100

10%

Network Requests Diagram

taxi.yandex.ee

570 ms

279 ms

lego.a4277664.css

706 ms

@gwc.6689d4c2.css

875 ms

userId.592adde6.css

1032 ms

Our browser made a total of 20 requests to load all elements on the main page. We found that 10% of them (2 requests) were addressed to the original Taxi.yandex.ee, 90% (18 requests) were made to Yastatic.net. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source Yastatic.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 237.7 kB (35%)

Content Size

686.2 kB

After Optimization

448.5 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Taxi.yandex.ee main page is 686.2 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. 20% of websites need less resources to load. Javascripts take 598.5 kB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 26.2 kB

  • Original 37.2 kB
  • After minification 37.0 kB
  • After compression 11.0 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 26.2 kB or 71% of the original size.

JavaScript Optimization

-34%

Potential reduce by 202.2 kB

  • Original 598.5 kB
  • After minification 598.5 kB
  • After compression 396.3 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 202.2 kB or 34% of the original size.

CSS Optimization

-18%

Potential reduce by 9.2 kB

  • Original 50.5 kB
  • After minification 50.5 kB
  • After compression 41.3 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. Taxi.yandex.ee needs all CSS files to be minified and compressed as it can save up to 9.2 kB or 18% of the original size.

Requests Breakdown

Number of requests can be reduced by 16 (89%)

Requests Now

18

After Optimization

2

  • JavaScript
  • CSS

The browser has sent 18 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Taxi Yandex. 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 5 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

taxi.yandex.ee

taxi.yandex.ee

570 ms

279 ms

lego.a4277664.css

lego.a4277664.css

706 ms

@gwc.6689d4c2.css

@gwc.6689d4c2.css

875 ms

userId.592adde6.css

userId.592adde6.css

1032 ms

8565.ed451eb6.css

8565.ed451eb6.css

1118 ms

desktop.a2d668d4.css

desktop.a2d668d4.css

1205 ms

react-with-dom.min.js

react-with-dom.min.js

1313 ms

lego.16018e1a.bundle.js

lego.16018e1a.bundle.js

1108 ms

@gwc.e97e7df8.bundle.js

@gwc.e97e7df8.bundle.js

1140 ms

commonVendors.a4f0bca1.bundle.js

commonVendors.a4f0bca1.bundle.js

1347 ms

userId.14078db4.bundle.js

userId.14078db4.bundle.js

1253 ms

5502.44ba85d5.bundle.js

5502.44ba85d5.bundle.js

1370 ms

2219.895318db.bundle.js

2219.895318db.bundle.js

1300 ms

8565.361f746e.bundle.js

8565.361f746e.bundle.js

1730 ms

5359.95ce3c70.bundle.js

5359.95ce3c70.bundle.js

1536 ms

1743.16d39af6.bundle.js

1743.16d39af6.bundle.js

1487 ms

5650.1e4c38d1.bundle.js

5650.1e4c38d1.bundle.js

1481 ms

9311.db25181d.bundle.js

9311.db25181d.bundle.js

1516 ms

desktop.ce19d860.bundle.js

desktop.ce19d860.bundle.js

1726 ms

Accessibility Review

taxi.yandex.ee accessibility score

64

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

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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

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

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

taxi.yandex.ee best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Requests the geolocation permission on page load

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

taxi.yandex.ee 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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

taxi.yandex.ee

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