7.5 sec in total
587 ms
5.8 sec
1.1 sec
Click here to check amazing Move content for Russia. Otherwise, check out these important facts you probably never knew about move.ru
Главная страница портала о недвижимости Move.Ru: база объектов недвижимости Москвы и области, новости, статьи, риэлторы, агентства и многое другое.
Visit move.ruWe analyzed Move.ru page load time and found that the first response time was 587 ms and then it took 6.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
move.ru performance score
name
value
score
weighting
Value8.3 s
0/100
10%
Value17.7 s
0/100
25%
Value12.8 s
2/100
10%
Value1,720 ms
10/100
30%
Value0.239
52/100
15%
Value24.2 s
0/100
10%
587 ms
1014 ms
59 ms
774 ms
921 ms
Our browser made a total of 152 requests to load all elements on the main page. We found that 4% of them (6 requests) were addressed to the original Move.ru, 53% (81 requests) were made to Static-data.move.ru and 18% (27 requests) were made to Analytics.move.ru. The less responsive or slowest element that took the longest time to load (2.6 sec) relates to the external source Static-data.move.ru.
Page size can be reduced by 595.5 kB (16%)
3.7 MB
3.1 MB
In fact, the total size of Move.ru main page is 3.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. 55% of websites need less resources to load. Images take 2.3 MB which makes up the majority of the site volume.
Potential reduce by 456.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. This page needs HTML code to be minified as it can gain 178.4 kB, which is 35% 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 456.2 kB or 91% of the original size.
Potential reduce by 69.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. Move images are well optimized though.
Potential reduce by 49.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. This website has mostly compressed JavaScripts.
Potential reduce by 19.5 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. Move.ru has all CSS files already compressed.
Number of requests can be reduced by 91 (71%)
128
37
The browser has sent 128 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Move. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
move.ru
587 ms
move.ru
1014 ms
js
59 ms
b46a9395302b5a954445bc36469bc283.css
774 ms
9efa8d939417680eb28fc2d2cf566a40.css
921 ms
ab346d42d9aff5e59e2027a00425606f.css
1534 ms
bd42a5cad47ba4b9f7688e66c1c6e3de.css
1137 ms
44cc779adf80202dfacfc0d2db4be8dd.css
1152 ms
d5a1ec6172e4b1e77780a557a70bd797.css
1154 ms
9598aca5f1d3a45ed0f9338927512468.css
1166 ms
839ec38af79cbe71c962e9e72c579dd8.css
1163 ms
6d796de329b0fff9a0ba1c127e5e513f.js
1257 ms
3582c0c7be4e2d7a5ce58f69c5ae17d6.js
1278 ms
fbb3fe2f3c1a9154abc6c920dbbdb6e5.js
1281 ms
0509fb4d1196b894854c126bcb973146.js
1292 ms
994f34517c3afa0dd2c015bf891652f8.js
1295 ms
49d19226db47dbd5a5a09c8d4e72f4d4.js
1644 ms
a58292a527798dc9c1e107565f7a0b3c.js
1778 ms
0766e5d70259507a8f01d8a19a46b730.js
1422 ms
4372c2d88430e147192d8ace4913dfc2.js
1427 ms
a66493df74f5e0320564013e0ddb6722.js
1424 ms
point.svg
1548 ms
na-button.png
1553 ms
geo-marker.svg
1556 ms
imp.gif
563 ms
pixel.php
731 ms
nd_6649051650880.jpeg
854 ms
pixel.php
743 ms
pixel.php
782 ms
pixel.php
750 ms
pixel.php
833 ms
pixel.php
861 ms
pixel.php
917 ms
pixel.php
886 ms
pixel.php
940 ms
pixel.php
926 ms
nd_6648d76dd5dad.jpeg
1054 ms
menu_pin.svg
1644 ms
advertisement.svg
1670 ms
03d570a58dfd4dfb5a10f2668c5e198d.jpg
1947 ms
d8aea510c92171383d343200bf8ff36c.png
1682 ms
f939d424248883ce6c8a38e29675bb3d.png
1759 ms
ed960a68a6d18e1308e8b9c1037224e0.jpeg
2277 ms
bfc3b52c3a1d8a8cbad1babbcae7b25e.jpeg
1972 ms
381959af8784ef5359d8bd0016f249a6.jpeg
1947 ms
501f0ee1dc2c2fd9e4194032363babfc.jpeg
2034 ms
logo_mra.png
1947 ms
819b2fb49e864d2851297416824ccf5c.jpeg
2080 ms
646e29fcba83404a3408f2e5ffddd05c.jpeg
2558 ms
6ba2f87e77295883cdaab0d2790e875e.jpeg
2037 ms
c145473fa79f9597398ea6263839ed99.jpeg
2105 ms
7d6460b5d40bfa80c610fa545eb6110c.jpeg
2423 ms
imp.gif
580 ms
imp.gif
578 ms
imp.gif
584 ms
imp.gif
586 ms
imp.gif
647 ms
imp.gif
659 ms
imp.gif
682 ms
imp.gif
686 ms
imp.gif
689 ms
imp.gif
692 ms
whatsapp-button-icon.svg
265 ms
imp.gif
459 ms
context.js
870 ms
imp.gif
636 ms
imp.gif
634 ms
imp.gif
653 ms
imp.gif
658 ms
imp.gif
663 ms
imp.gif
665 ms
imp.gif
736 ms
imp.gif
758 ms
imp.gif
759 ms
imp.gif
762 ms
imp.gif
452 ms
imp.gif
453 ms
imp.gif
465 ms
imp.gif
466 ms
imp.gif
508 ms
imp.gif
557 ms
pixel.php
840 ms
pixel.php
910 ms
pixel.php
932 ms
pixel.php
915 ms
pixel.php
929 ms
pixel.php
988 ms
pixel.php
991 ms
pixel.php
1055 ms
pixel.php
1059 ms
pixel.php
1072 ms
pixel.php
1078 ms
pixel.php
1173 ms
pixel.php
1141 ms
pixel.php
1199 ms
pixel.php
1202 ms
pixel.php
1221 ms
pixel.php
1226 ms
483cb4373502ce277df5614ed11d376c.css
1397 ms
cfe5e5feb0f2d47683da65fa14edfb3e.css
1296 ms
57b20467da4fff8e5b886e68146742c5.css
1107 ms
353dc84cd39dcb4758486dd4245db735.js
1173 ms
ccf832eaa12178229356c25caf9f4194.js
1199 ms
58087ef6408e27d8f91d19f4517d83e2.js
1214 ms
f8773c04ddd7090dfc8766f8b255b32c.js
1246 ms
b73034eefff60a9e33e90c19919d3a87.js
1196 ms
e94f874f5bdef3694b8f6520da5ca617.js
1228 ms
20215c4e41676cd54aa042dd9432bcd7.js
1233 ms
dabe2742485e3ed3e96263de8b171d82.jpeg
1553 ms
2c681c163a1fdb0021f2c1b83d338b72.jpeg
1354 ms
96346f76c5097b9fe57ded12bf1887f6.jpeg
1186 ms
cfd05cce70d98a54c7c1f8c4de0d64d4.jpeg
1353 ms
7e3cd4a93cb1af8eb0863e427432cc3b.jpeg
1227 ms
571a7403e7bcf500ba37e60ada9aaa99.jpeg
1619 ms
6cf1df10244922814ecba4d115bd9bb8.jpeg
1483 ms
b96ad715ff692c42d01698ee52b792a1.jpeg
1313 ms
2fe17f1a160332bc5f97fe23d18af1c9.jpeg
1253 ms
879711f423f2e9a6e665afd3e9f3629f.jpeg
1288 ms
6f865da6f567d274e33979fef097a4bf.jpeg
1316 ms
b64e2740f1409a2ab2b5e96b81ad6501.jpg
1374 ms
agency_1000139270.png
1299 ms
16+.svg
1303 ms
index.html
173 ms
loading.gif
1157 ms
search-form.jpg
1485 ms
pattern.png
140 ms
320x90.jpg
146 ms
SFProDisplay-Regular.woff
1516 ms
SFProDisplay-Medium.woff
1620 ms
g9Z+msuD5IAewAAAAABAAAAANWkJwgAAAAAxPARLgAAAADVAVL0
2 ms
hit;Move
656 ms
gtm.js
40 ms
SFProDisplay-Ultralight.woff
1557 ms
watch.js
4 ms
SFProDisplay-Light.woff
1581 ms
SFProDisplay-Thin.woff
1665 ms
SFProDisplay-Semibold.woff
1890 ms
SFProDisplay-Bold.woff
1913 ms
SFProDisplay-Black.woff
1871 ms
SFProDisplay-Heavy.woff
1808 ms
Gilroy-Regular.woff
1515 ms
Gilroy-Medium.woff
1642 ms
Gilroy-Light.woff
1629 ms
Gilroy-UltraLight.woff
1802 ms
Gilroy-Thin.woff
1848 ms
Gilroy-Semibold.woff
1701 ms
Gilroy-Bold.woff
1774 ms
Gilroy-Extrabold.woff
1773 ms
Gilroy-Heavy.woff
1759 ms
Gilroy-Black.woff
1748 ms
openapi.a2ed73393cad04481c1dfb3f7794921f.js
257 ms
rtrg
142 ms
move.ru accessibility score
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
ARIA input fields do not have accessible names
[role]s do not have all required [aria-*] attributes
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
[role]s are not contained by their required parent element
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
List items (<li>) are not contained within <ul> or <ol> parent elements.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
move.ru best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
move.ru SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
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 Move.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 Move.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.
move.ru
Open Graph data is detected on the main page of Move. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: