5 sec in total
401 ms
3.7 sec
894 ms
Welcome to krim.move.su homepage info - get ready to check Krim Move best content for Russia right away, or after learning these important things about krim.move.su
Главная страница портала о недвижимости Move.Ru: база объектов недвижимости Москвы и области, новости, статьи, риэлторы, агентства и многое другое.
Visit krim.move.suWe analyzed Krim.move.su page load time and found that the first response time was 401 ms and then it took 4.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
krim.move.su performance score
name
value
score
weighting
Value5.5 s
6/100
10%
Value7.5 s
4/100
25%
Value6.9 s
34/100
10%
Value820 ms
35/100
30%
Value0.001
100/100
15%
Value14.5 s
9/100
10%
401 ms
666 ms
636 ms
661 ms
367 ms
Our browser made a total of 154 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Krim.move.su, 50% (77 requests) were made to Krim.move.ru and 8% (12 requests) were made to Vk.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Krim.move.ru.
Page size can be reduced by 898.0 kB (44%)
2.0 MB
1.1 MB
In fact, the total size of Krim.move.su main page is 2.0 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 785.8 kB which makes up the majority of the site volume.
Potential reduce by 179.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 179.8 kB or 82% of the original size.
Potential reduce by 13.0 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. Krim Move images are well optimized though.
Potential reduce by 457.8 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 457.8 kB or 71% of the original size.
Potential reduce by 247.4 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. Krim.move.su needs all CSS files to be minified and compressed as it can save up to 247.4 kB or 64% of the original size.
Number of requests can be reduced by 59 (40%)
147
88
The browser has sent 147 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Krim 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 24 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
krim.move.su
401 ms
krim.move.ru
666 ms
bb85034d1b707682dd91d22a4a3705e5.css
636 ms
ed3480f975a5a97e5994e179ebd63853.js
661 ms
openapi.js
367 ms
f3dd71182ecfe2c1a5a3d159e9c36fc5.js
281 ms
conversion.js
26 ms
SmartCallBack.js
595 ms
autoUpdate.adriver.js
281 ms
gtm.js
93 ms
1454312904.jpg
469 ms
1067.gif
319 ms
logo_ru.png
138 ms
icon-search.png
157 ms
arr4.png
138 ms
14579380724.jpg
272 ms
i1.jpg
271 ms
i2.jpg
274 ms
i3.jpg
293 ms
i4v2.png
291 ms
i5v2.png
294 ms
label1.png
452 ms
label2.png
453 ms
440x90-1.jpg
454 ms
440x90-2.jpg
455 ms
240x400.jpg
540 ms
top.png
457 ms
down.png
506 ms
shadow3.png
510 ms
240x180-1.jpg
519 ms
ic6.jpg
531 ms
arr8.png
559 ms
ic1.jpg
635 ms
arr9.png
638 ms
ic2.jpg
650 ms
ic3.jpg
663 ms
ic4.png
808 ms
1455182256.jpg
829 ms
nd_1458309983.jpg
888 ms
nd_1458297903.jpg
764 ms
nd_1458296118.jpg
778 ms
nd_1458295993.jpg
927 ms
nd_1458290180.jpg
914 ms
nd_1458287332.jpg
914 ms
nd_1458287213.jpg
942 ms
nd_1458286695.jpg
1095 ms
nd_1458286611.jpg
1031 ms
d59fa5451f7a5f325aecaa1202bbaa2f.jpg
455 ms
1132e442597b752d8ef7fea82fd492bc.jpg
460 ms
1449471531.jpg
459 ms
b36f87c8a0e657f9c98de4f7bf452df1.JPG
462 ms
f51f9ff0fc1e90fc4653b5d2cfb1de0b.jpg
474 ms
e248f9fe4ce6e32a3f554c82b52807b5.jpg
587 ms
1454061900.jpg
585 ms
5f4cf4dcbf43059d7c83f2a5b14fd1bc.jpg
589 ms
1441013117.jpg
593 ms
1454912629.jpg
593 ms
1456727140.jpg
739 ms
nd_1458224247.jpg
1018 ms
analytics.js
17 ms
56bb59547c869.png
952 ms
collect
20 ms
avatar100.jpg
935 ms
139270800888.jpg
934 ms
collect
93 ms
ga-audiences
73 ms
135954725797.jpg
880 ms
136196357444.jpg
886 ms
240x180-2.jpg
906 ms
upload.gif
185 ms
widget_community.php
280 ms
old.adriver.js
275 ms
prev.png
908 ms
rle.cgi
283 ms
next.png
927 ms
rle.cgi
278 ms
rle.cgi
281 ms
rle.cgi
298 ms
rle.cgi
535 ms
rle.cgi
540 ms
141089709536.jpg
949 ms
hit;Move
258 ms
118 ms
230 ms
likebox.php
236 ms
37 ms
847 ms
5515a20b21221.jpeg
828 ms
552375b109dd9.jpeg
886 ms
56ab8fb037f3f.jpeg
887 ms
141742313723.jpg
902 ms
56ea63b423cf6.jpeg
871 ms
56e3d172cdbdf.jpeg
898 ms
56ceba03ede44.png
907 ms
554c7eda354d5.jpeg
903 ms
56c1d2168b6cf.jpeg
922 ms
erle.cgi
291 ms
loader_nav19188_3.js
128 ms
lite.css
128 ms
lite.js
489 ms
lang3_0.js
250 ms
widget_community.css
248 ms
xdm.js
258 ms
al_community.js
266 ms
rle.cgi
286 ms
140913375235.jpg
933 ms
checkFlash.adriver.js
270 ms
functions.adriver.js
273 ms
hit;Move
131 ms
410ucuAGgaJ.css
182 ms
tSbl8xBI27R.css
226 ms
q68gy-v_YMF.js
306 ms
FJmpeSpHpjS.js
378 ms
0wM5s1Khldu.js
304 ms
1bNoFZUdlYZ.js
303 ms
651 ms
140741713040.jpg
877 ms
142658412782.jpg
897 ms
130165355139.jpg
900 ms
133784234248.jpg
899 ms
130165776931.jpg
840 ms
141873195926.jpg
847 ms
141490878875.jpg
840 ms
142467654166.jpg
835 ms
script.js
272 ms
142745211884.jpg
790 ms
soc1.jpg
776 ms
soc2.jpg
810 ms
soc3.jpg
832 ms
soc4.jpg
840 ms
11028021_802331863184901_4489279686225624156_n.jpg
175 ms
11028021_802325309852223_8728834000079259031_n.jpg
213 ms
1520623_761915090537914_7218876866317580425_n.jpg
266 ms
1926773_702298059821518_2116976347_n.jpg
339 ms
12670259_110135719372197_2747512994142586376_n.jpg
342 ms
1185377_423117157804717_2064212635_n.jpg
340 ms
12729162_110028266052762_5647578756626874435_n.jpg
342 ms
10624664_1520771964876599_5139531418090982465_n.jpg
339 ms
wL6VQj7Ab77.png
47 ms
s7jcwEQH7Sx.png
81 ms
145793940986.jpg
1017 ms
house-bg.png
769 ms
gjxod9KGrDE.jpg
362 ms
HywdcPXqEI8.jpg
269 ms
m6ljt6zs2Hk.jpg
377 ms
ExZ7N05w98k.jpg
362 ms
nyjufZJqkBI.jpg
376 ms
camera_50.png
122 ms
w_logo.png
121 ms
footer.png
739 ms
35_960-400.jpg
673 ms
555 ms
I6-MnjEovm5.js
43 ms
pQrUxxo5oQp.js
82 ms
krim.move.su 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
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.
krim.move.su 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
krim.move.su 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
N/A
WINDOWS-1251
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Krim.move.su can be misinterpreted by Google and other search engines. Our service has detected that Russian is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Krim.move.su main page’s claimed encoding is windows-1251. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
krim.move.su
Open Graph description is not detected on the main page of Krim Move. 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: