5.8 sec in total
943 ms
4.5 sec
333 ms
Welcome to landkey.ru homepage info - get ready to check Landkey best content for Russia right away, or after learning these important things about landkey.ru
Загородная недвижимость в коттеджных поселках от компании Лэндкей
Visit landkey.ruWe analyzed Landkey.ru page load time and found that the first response time was 943 ms and then it took 4.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
landkey.ru performance score
name
value
score
weighting
Value3.9 s
24/100
10%
Value5.7 s
16/100
25%
Value5.0 s
64/100
10%
Value420 ms
66/100
30%
Value0.037
100/100
15%
Value8.0 s
42/100
10%
943 ms
117 ms
178 ms
388 ms
584 ms
Our browser made a total of 111 requests to load all elements on the main page. We found that 64% of them (71 requests) were addressed to the original Landkey.ru, 10% (11 requests) were made to Vk.com and 6% (7 requests) were made to Api-maps.yandex.ru. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Landkey.ru.
Page size can be reduced by 1.7 MB (63%)
2.7 MB
1.0 MB
In fact, the total size of Landkey.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. 65% of websites need less resources to load. Javascripts take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 546.5 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 546.5 kB or 80% of the original size.
Potential reduce by 73.8 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. Obviously, Landkey needs image optimization as it can save up to 73.8 kB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 885.6 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 885.6 kB or 68% of the original size.
Potential reduce by 217.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. Landkey.ru needs all CSS files to be minified and compressed as it can save up to 217.1 kB or 83% of the original size.
Number of requests can be reduced by 62 (66%)
94
32
The browser has sent 94 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Landkey. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 41 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
landkey.ru
943 ms
css
117 ms
core.css
178 ms
styles.css
388 ms
core.js
584 ms
core_ajax.js
431 ms
json2.min.js
388 ms
core_ls.js
432 ms
session.js
443 ms
normalize.css
559 ms
style.css
687 ms
media.css
626 ms
mCustomScrollbar.css
634 ms
prettyPhoto.css
636 ms
bootstrap-datepicker.css
683 ms
swiper.min.css
708 ms
jquery-1.9.1.min.js
850 ms
jquery.pixel-perfecter.js
717 ms
placeholder.js
727 ms
368 ms
yaMaps.js
807 ms
modernizr.js
809 ms
prettyPhoto.js
832 ms
mCustomScrollbar.js
863 ms
bootstrap-datepicker.js
863 ms
ion.rangeSlider.min.js
985 ms
owl.carousel.min.js
986 ms
jquery.tinycarousel.js
1011 ms
contact.js
1012 ms
waypoints.min.js
1014 ms
swiper.min.js
1198 ms
main.js
1150 ms
openapi.js
600 ms
conversion.js
113 ms
795 ms
ba.js
186 ms
combine.xml
678 ms
watch.js
121 ms
topbar.gif
175 ms
el_bg_search.png
172 ms
i_search.png
142 ms
logo.png
173 ms
callme_border.png
173 ms
topmenu_wrap.gif
173 ms
2835da3a9e01b8141e01eb6b11df1b05.png
877 ms
ab972870f5c0742a8c411a6833e6c025.png
599 ms
a3b954ec0dad5e71163066ec1b0d48e8.png
879 ms
mob_logo.png
279 ms
homes_bg.png
1087 ms
i_metro.png
295 ms
captcha.php
1102 ms
captcha.php
1155 ms
owl_left.png
1335 ms
owl_right.png
981 ms
socs_box.png
1005 ms
Zd2E9abXLFGSr9G3YK2MsNbQxvdFQproHqwx84HIuqM.ttf
17 ms
b9QBgL0iMZfDSpmcXcE8nH2Kqn9Vte1TGXY0ojLIJME.ttf
33 ms
b9QBgL0iMZfDSpmcXcE8nOXJWfeCXjwsU1ch6Jnjz-M.ttf
34 ms
Gorki-Lend-2.html
1098 ms
arrow_left.png
1098 ms
arrow_right.png
1103 ms
upload.gif
134 ms
widget_community.php
318 ms
bg_family.gif
1695 ms
black_50.png
1125 ms
i_check.png
1198 ms
client.js
296 ms
watch.js
8 ms
analytics.js
56 ms
122 ms
watch.js
0 ms
watch.js
0 ms
watch.js
43 ms
bx_stat
320 ms
collect
46 ms
collect
172 ms
162 ms
5ec1456b9dd5.png
933 ms
ccaae231c5d4.jpg
934 ms
loader_nav19239_3.js
159 ms
lite.css
413 ms
lite.js
551 ms
lang3_0.js
418 ms
widget_community.css
419 ms
xdm.js
418 ms
al_community.js
444 ms
3627ebf74f72.png
811 ms
8da0a38e0cd3.png
887 ms
ef50ac9e93aaebe3299791c79f277f8e.cur
147 ms
3ce22e999d54bb9ca8150a59207f9d3e.cur
198 ms
4965b66fe115b2f2ed500ece66514d86.cur
335 ms
77492cf358d8b12629399322926c93f2.cur
469 ms
bc8a53462ce8.png
637 ms
34d7ab1434b4e33a24fd47eaf03dcb76.gif
646 ms
5fb528c60f3c5a2d31e5fd7b68655339.png
672 ms
app3.js
889 ms
1d1dd6f3b0a5.png
675 ms
03f5f242dbc3.png
756 ms
79477806ff13.png
758 ms
KC6lCUjgumo.jpg
322 ms
w_logo.png
163 ms
jquery-2.0.3.min.js
775 ms
jquery-2.1.1.min.js
627 ms
jquery-ui.min.css
475 ms
jquery-ui.min.js
703 ms
jquery.ui.touch-punch.min.js
627 ms
KolorTools.min.js
626 ms
KolorBootstrap.js
681 ms
Gorki-Lend-2.js
1049 ms
69960.js
151 ms
widget-ui-3.js
318 ms
landkey.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
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
landkey.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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
landkey.ru SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
RU
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Landkey.ru 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 Landkey.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.
landkey.ru
Open Graph description is not detected on the main page of Landkey. 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: