9.5 sec in total
1 sec
7.3 sec
1.2 sec
Click here to check amazing M 2 content for Russia. Otherwise, check out these important facts you probably never knew about m2.ru
Поиск и покупка недвижимости в Москве. База объявлений об аренде и продаже квартир на m2.ru. Проверка и безопасная сделка с недвижимостью. Экосистема «Метр квадратный».
Visit m2.ruWe analyzed M2.ru page load time and found that the first response time was 1 sec and then it took 8.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
m2.ru performance score
name
value
score
weighting
Value2.9 s
53/100
10%
Value8.3 s
2/100
25%
Value14.6 s
1/100
10%
Value9,270 ms
0/100
30%
Value0.001
100/100
15%
Value35.5 s
0/100
10%
1021 ms
1562 ms
150 ms
152 ms
1088 ms
Our browser made a total of 83 requests to load all elements on the main page. We found that 4% of them (3 requests) were addressed to the original M2.ru, 48% (40 requests) were made to Cdn.m2.ru and 14% (12 requests) were made to Top-fwz1.mail.ru. The less responsive or slowest element that took the longest time to load (2.5 sec) relates to the external source Cdn.m2.ru.
Page size can be reduced by 573.1 kB (31%)
1.9 MB
1.3 MB
In fact, the total size of M2.ru main page is 1.9 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. Javascripts take 781.8 kB which makes up the majority of the site volume.
Potential reduce by 418.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 418.0 kB or 88% of the original size.
Potential reduce by 0 B
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.
Potential reduce by 124.4 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 124.4 kB or 16% of the original size.
Potential reduce by 30.8 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. M2.ru needs all CSS files to be minified and compressed as it can save up to 30.8 kB or 23% of the original size.
Number of requests can be reduced by 56 (73%)
77
21
The browser has sent 77 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 24 to 1 for JavaScripts and as a result speed up the page load time.
m2.ru
1021 ms
m2.ru
1562 ms
gtm.js
150 ms
gtm.js
152 ms
styles.e045cdd384a61d0eb133.css
1088 ms
6192ce4b72fe244cfa2a3091bef72149.jpeg
1416 ms
react.production.min.js
821 ms
react-dom.production.min.js
1021 ms
mobx.umd.min.js
1120 ms
mobx-react.umd.js
1192 ms
react-router-dom.min.js
1197 ms
axios.min.js
1207 ms
bundle.tracing.replay.min.js
1347 ms
index.min.js
1326 ms
vtblife-axios.min.js
1213 ms
workbox-window.prod.umd.js
1314 ms
polyfill-a335067d781ab74ef99b.js
1458 ms
app-df6a4ddafb2aaa59cd74.js
2146 ms
framework-23f0d0ded1e6762f2a40.js
1332 ms
webpack-runtime-b14fdaa482b6e039da2a.js
1328 ms
d005bbee57e42f15cc0aca0a7c01fa33.svg
1462 ms
ec178151b5451fcc8cd9d9e6299b5601.svg
1464 ms
0213b29318b16c168d31b10164a56b4e.svg
1465 ms
5e17b351d1c004e7f21cff69af3fb002.svg
1512 ms
c82aac45ae620bf3f0c5eff1a191ccc6.svg
1618 ms
af1a92cf9a55fb02ea3948122adc8cf9.svg
1622 ms
8ca1391747febee0336e998019aecc1e.svg
1620 ms
50196274da57e702f2c6f6503db00295.svg
1624 ms
3bd44bdb88741c629e127d9e586c2eec.svg
1626 ms
de2d1b49aa7b36e42886c159c31c77d6.svg
1649 ms
7f99dd8e52fdf4281897a2dfeffd9c53.svg
1690 ms
604dc67fbbf9cdf06fc4a545f77ace6c.svg
2181 ms
25981f3748b7925c23fa1d346488c3dc.svg
2204 ms
922d5e6a263984b7386ad13c598acaf3.svg
1735 ms
0ac718e4e17c9ad7f8f4e7e1fc130ada.svg
1767 ms
acf385f8d54f8e8c04cef9bf90c88676.svg
1809 ms
a186b01636e63192b1f8a3ca61de1f3a.svg
1867 ms
2ff0a65ac2f1db9d61ea33f2740bf955.svg
1886 ms
9382509eaec42541270f1f5fa5818a01.jpeg
1947 ms
ef97725afa607ab64b7d3cf453acdc2a.jpeg
2016 ms
f0ac6cbae5972d7b9bc09e4e2f36ffa6.jpeg
2013 ms
18dbfa139152841e117eb5fa56ee656a.jpeg
2101 ms
e6c3e6fd3743725eda1fcd61d80f3b8e.jpeg
2177 ms
6aae1391542a0aefb78b1677fead0968.jpeg
2215 ms
cef863eef0bc55bc9ee18a89ff3ab86a.jpeg
2342 ms
470890caf65d301f3b7fb7175153994d.jpeg
2515 ms
c1ca83273963eeb674fb92a549d4f9e5.svg
2264 ms
3ac324d9b1f16e11bbf65604e0f29390.svg
2305 ms
65bb95104f58ba398b6e1128d4a065e5.svg
2356 ms
destination
107 ms
tag.js
879 ms
styles.e045cdd384a61d0eb133.css
956 ms
rle.cgi
149 ms
m2logo.svg
1338 ms
ALS_Hauss-Regular.woff
1262 ms
ALS_Hauss-Medium.woff
1207 ms
0ea3dfd4b27570e4f80f79c4465a2644.svg
1141 ms
advert.gif
321 ms
sync_cookie_image_decide
133 ms
1
129 ms
sync_cookie_image_check
157 ms
rle.cgi
132 ms
code.js
836 ms
widget.js
750 ms
m2.ru.js
787 ms
56439838
137 ms
openapi.a2ed73393cad04481c1dfb3f7794921f.js
253 ms
rtrg
146 ms
rtrg
281 ms
spevent
538 ms
sync-loader.js
852 ms
counter
166 ms
dyn-goal-config.js
271 ms
counter
386 ms
counter
406 ms
counter
411 ms
counter
413 ms
tracker
429 ms
tracker
437 ms
tracker
509 ms
tracker
545 ms
tracker
548 ms
tracking.gif
124 ms
m2.ru accessibility score
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
Buttons do not have an accessible name
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
m2.ru best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
m2.ru SEO score
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
Document uses legible font sizes
Tap targets are not sized appropriately
RU
RU
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise M2.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 M2.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.
m2.ru
Open Graph data is detected on the main page of M 2. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: