Report Summary

  • 10

    Performance

    Renders faster than
    23% of other websites

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

m-2.ru

m-2.ru - Портал поиска недвижимости и готового бизнеса

Page Load Speed

11.6 sec in total

First Response

545 ms

Resources Loaded

10.2 sec

Page Rendered

842 ms

m-2.ru screenshot

About Website

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

m-2.ru - Ресурс о поиске недвижимости и готового бизнеса. База объявлений по недвижимости. Каталог по готовому бизнесу. Подбор объектов по городам, цене, классу и прочим параметрам. Частные объявления...

Visit m-2.ru

Key Findings

We analyzed M-2.ru page load time and found that the first response time was 545 ms and then it took 11.1 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

m-2.ru performance score

10

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.1 s

3/100

10%

LCP (Largest Contentful Paint)

Value26.8 s

0/100

25%

SI (Speed Index)

Value17.1 s

0/100

10%

TBT (Total Blocking Time)

Value20,290 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.197

63/100

15%

TTI (Time to Interactive)

Value41.4 s

0/100

10%

Network Requests Diagram

m-2.ru

545 ms

fiolaestate.ru

751 ms

css

36 ms

application-6e58b71a8242d5e012079af78e2024986893aef5c16adf90278932a02c77ea96.css

1667 ms

232 ms

Our browser made a total of 55 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original M-2.ru, 24% (13 requests) were made to Fiolaestate.ru and 18% (10 requests) were made to Api-maps.yandex.ru. The less responsive or slowest element that took the longest time to load (4.8 sec) relates to the external source Fiolaestate.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 3.2 MB (60%)

Content Size

5.3 MB

After Optimization

2.1 MB

In fact, the total size of M-2.ru main page is 5.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. 45% of websites need less resources to load. Javascripts take 3.5 MB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 280.5 kB

  • Original 367.3 kB
  • After minification 367.1 kB
  • After compression 86.8 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 280.5 kB or 76% of the original size.

Image Optimization

-2%

Potential reduce by 15.1 kB

  • Original 951.3 kB
  • After minification 936.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. M 2 images are well optimized though.

JavaScript Optimization

-70%

Potential reduce by 2.5 MB

  • Original 3.5 MB
  • After minification 3.5 MB
  • After compression 1.0 MB

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 2.5 MB or 70% of the original size.

CSS Optimization

-85%

Potential reduce by 380.3 kB

  • Original 449.4 kB
  • After minification 447.8 kB
  • After compression 69.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. M-2.ru needs all CSS files to be minified and compressed as it can save up to 380.3 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 11 (25%)

Requests Now

44

After Optimization

33

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

Accessibility Review

m-2.ru accessibility score

68

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

button, link, and menuitem elements do not have accessible names.

High

[role]s do not have all required [aria-*] attributes

High

[aria-*] attributes do not have valid values

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

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

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

High

Form elements do not have associated labels

High

Links do not have a discernible name

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

m-2.ru 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

User Experience

Impact

Issue

High

Serves images with low resolution

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

m-2.ru SEO score

86

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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

High

Tap targets are not sized appropriately

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 M-2.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 M-2.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

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