Tools & Wizards About Us
rostov.2gis.ru screenshot

Report Summary

  • 32

    Performance

    Renders faster than
    52% of other websites

  • 61

    Accessibility

    Visual factors better than
    that of 27% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 93

    SEO

    Google-friendlier than
    84% of websites

rostov.2gis.ru

Карта Ростова-на-Дону: улицы, дома и организации города — 2ГИС

Page Load Speed

4.8 sec in total

First Response

542 ms

Resources Loaded

4.1 sec

Page Rendered

128 ms

rostov.2gis.ru screenshot

About Website

Visit rostov.2gis.ru now to see the best up-to-date Rostov 2 Gis content for Russia and also check out these interesting facts you probably never knew about rostov.2gis.ru

Подробная карта Ростова-на-Дону с детализацией до дома: поиск по адресу + телефоны, отзывы, фото, часы работы фирм + удобный поиск проезда на авто и городском транспорте

Visit rostov.2gis.ru

Key Findings

We analyzed Rostov.2gis.ru page load time and found that the first response time was 542 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

rostov.2gis.ru performance score

32

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.8 s

5/100

10%

LCP (Largest Contentful Paint)

Value5.8 s

15/100

25%

SI (Speed Index)

Value9.0 s

14/100

10%

TBT (Total Blocking Time)

Value840 ms

34/100

30%

CLS (Cumulative Layout Shift)

Value0.013

100/100

15%

TTI (Time to Interactive)

Value12.8 s

13/100

10%

Network Requests Diagram

rostov.2gis.ru

542 ms

rostov

1854 ms

desktop.css

1457 ms

mausoleum.css

310 ms

logo_rostov.svg

337 ms

Our browser made a total of 15 requests to load all elements on the main page. We found that 7% of them (1 request) were addressed to the original Rostov.2gis.ru, 60% (9 requests) were made to 2gis.ru and 13% (2 requests) were made to Maps.api.2gis.ru. The less responsive or slowest element that took the longest time to load (1.9 sec) relates to the external source 2gis.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.8 MB (66%)

Content Size

2.7 MB

After Optimization

930.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Rostov.2gis.ru main page is 2.7 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. 20% of websites need less resources to load. CSS take 1.7 MB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 344.0 kB

  • Original 478.2 kB
  • After minification 472.5 kB
  • After compression 134.2 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 344.0 kB or 72% of the original size.

Image Optimization

-4%

Potential reduce by 16.7 kB

  • Original 453.6 kB
  • After minification 436.9 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. Rostov 2 Gis images are well optimized though.

JavaScript Optimization

-60%

Potential reduce by 32.0 kB

  • Original 52.9 kB
  • After minification 52.9 kB
  • After compression 20.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 32.0 kB or 60% of the original size.

CSS Optimization

-81%

Potential reduce by 1.4 MB

  • Original 1.7 MB
  • After minification 1.7 MB
  • After compression 338.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. Rostov.2gis.ru needs all CSS files to be minified and compressed as it can save up to 1.4 MB or 81% of the original size.

Requests Breakdown

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

Requests Now

10

After Optimization

7

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

rostov.2gis.ru

rostov.2gis.ru

542 ms

rostov

rostov

1854 ms

desktop.css

desktop.css

1457 ms

mausoleum.css

mausoleum.css

310 ms

logo_rostov.svg

logo_rostov.svg

337 ms

loader.js

loader.js

269 ms

mausoleum.js

mausoleum.js

138 ms

browsers.jpg

browsers.jpg

135 ms

close.gif

close.gif

159 ms

SuisseIntl-CondBold.woff

SuisseIntl-CondBold.woff

139 ms

SuisseIntl-Cond.woff

SuisseIntl-Cond.woff

411 ms

544 ms

analytics.js

analytics.js

21 ms

watch.js

watch.js

19 ms

collect

collect

20 ms

Accessibility Review

rostov.2gis.ru accessibility score

61

Accessibility Issues

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

Image elements do not have [alt] attributes

High

<object> elements do not have alternate text

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

rostov.2gis.ru best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

rostov.2gis.ru SEO score

93

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

    RU

  • Encoding

    UTF-8

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

rostov.2gis.ru

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