10.9 sec in total
152 ms
10.1 sec
632 ms
Visit olymprealty.ru now to see the best up-to-date Olymprealty content for Russia and also check out these interesting facts you probably never knew about olymprealty.ru
Планируете купить недвижимость в Сочи? Вы поможем вам в этом! На нашем сайте представлено множество вариантов квартир, домов, коттеджей и земельных участков по привлекательной цене. Вся недвижимость С...
Visit olymprealty.ruWe analyzed Olymprealty.ru page load time and found that the first response time was 152 ms and then it took 10.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
olymprealty.ru performance score
name
value
score
weighting
Value3.4 s
38/100
10%
Value10.1 s
0/100
25%
Value14.5 s
1/100
10%
Value1,370 ms
16/100
30%
Value0
100/100
15%
Value14.1 s
9/100
10%
152 ms
5237 ms
36 ms
219 ms
221 ms
Our browser made a total of 177 requests to load all elements on the main page. We found that 72% of them (127 requests) were addressed to the original Olymprealty.ru, 12% (21 requests) were made to Core-renderer-tiles.maps.yandex.net and 5% (9 requests) were made to Api-maps.yandex.ru. The less responsive or slowest element that took the longest time to load (5.2 sec) belongs to the original domain Olymprealty.ru.
Page size can be reduced by 508.8 kB (17%)
3.0 MB
2.5 MB
In fact, the total size of Olymprealty.ru main page is 3.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. 70% of websites need less resources to load. Images take 2.4 MB which makes up the majority of the site volume.
Potential reduce by 282.4 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 282.4 kB or 72% of the original size.
Potential reduce by 213.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. Olymprealty images are well optimized though.
Potential reduce by 2.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 9.6 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. Olymprealty.ru needs all CSS files to be minified and compressed as it can save up to 9.6 kB or 29% of the original size.
Number of requests can be reduced by 53 (33%)
162
109
The browser has sent 162 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Olymprealty. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 37 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
olymprealty.ru
152 ms
olymprealty.ru
5237 ms
css
36 ms
home.css
219 ms
jquery.bxslider.min.css
221 ms
uniform-checkbox.css
220 ms
jquery.fancybox.css
217 ms
jquery.fancybox-buttons.css
257 ms
jquery.fancybox-thumbs.css
429 ms
media_home.css
428 ms
media_main.css
426 ms
main.css
437 ms
jquery-carousel.css
467 ms
jquery.min.js
23 ms
jquery.maskedinput.min.js
501 ms
jquery.yiiactiveform.js
638 ms
JsTrans.min.js
639 ms
dictionary-0f5e9c8910.js
639 ms
modernizr.custom.js
648 ms
googleAnalytics.js
677 ms
jquery.uniform.min.js
710 ms
jquery.dotdotdot-1.5.7-packed.js
848 ms
jquery.cookie.js
850 ms
jquery.easing-1.3.min.js
848 ms
message.js
888 ms
jquery.carousel.js
888 ms
jquery.slimscroll.js
920 ms
jquery.easing.1.3.js
1058 ms
carousel.js
1058 ms
main.js
1062 ms
758 ms
html5.js
1097 ms
email-decode.min.js
601 ms
yandexMetrika.js
910 ms
popup.js
911 ms
bmodal.js
981 ms
small-plugins.js
981 ms
main-functions.js
1002 ms
jquery.alerts.js
1018 ms
home.js
1025 ms
jquery.fancybox.js
1051 ms
jquery.fancybox-buttons.js
1185 ms
jquery.fancybox-media.js
1186 ms
jquery.fancybox-thumbs.js
1187 ms
ga.js
14 ms
__utm.gif
11 ms
combine
781 ms
i-whatsapp.png
102 ms
i-telegram.png
79 ms
logo.png
401 ms
menu-small.png
404 ms
phone-small.png
427 ms
cancel.png
564 ms
controls.png
568 ms
znJsz6Gmsl2MQIhZkT.jpg
1259 ms
IY5US4PWjU8UDUFIBR.jpg
1302 ms
1D5KR9tVc.jpg
617 ms
Po2VNl6oI.jpg
637 ms
s1UlQqXoo.jpg
872 ms
oWFcXQYZQ.jpg
873 ms
icons-sb07f97d6dc.png
875 ms
6byNIGbfm.jpg
891 ms
vazMn5Pj6.jpg
990 ms
r5jYqneGX.jpg
993 ms
w9qV89JcR.jpg
1042 ms
nqWItO9QlLmDlzoRXa.gif
1949 ms
border-after.png
1198 ms
nNpU0TrD8yxgaY64ue.jpg
1198 ms
phone-small-blue.png
1251 ms
N5yTRFf6Ii8nJbmXKq.jpg
1407 ms
FyMvzGsxCvd5HQ7PIi.jpg
1409 ms
arrowleft.png
1462 ms
4feqSlwqz.jpeg
1469 ms
BkAvNjuFq.jpg
1436 ms
1w6JW8Ngj.jpg
1544 ms
i-whatsapp.png
232 ms
i-telegram.png
446 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf
28 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf
55 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf
64 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf
65 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWVAexQ.ttf
66 ms
E8xqAEira.jpg
1538 ms
init.js
151 ms
index.php
792 ms
watch.js
1 ms
WzlEom4Ep.jpg
1526 ms
mAH5WuHmD.jpg
1523 ms
Ma7w716lY.jpg
1552 ms
6SXIxzMpn.jpg
1643 ms
DMeZEn9JX.jpg
1638 ms
k9YLyEP9X.jpg
1666 ms
bundle.js
11 ms
MtaadPJhN.jpg
1534 ms
iRmdyqbDO.jpg
1483 ms
2uw9MVJbN.jpg
1673 ms
b2NY8DniL.jpg
1647 ms
EwQmbuLmH.jpg
1672 ms
dkJXXZLgt.jpg
1671 ms
lxvhYQjMa.jpg
1537 ms
LohM29Tkk.jpg
1597 ms
openapi.c340c125c61ec5745ebb2a98626e46ab.js
292 ms
oZyn1RyoI.jpg
1633 ms
vtFjSIBn4.jpg
1620 ms
ef50ac9e93aaebe3299791c79f277f8e.cur
211 ms
323 ms
3ce22e999d54bb9ca8150a59207f9d3e.cur
342 ms
4965b66fe115b2f2ed500ece66514d86.cur
434 ms
77492cf358d8b12629399322926c93f2.cur
408 ms
DOi6UUt1i.jpeg
1413 ms
U1M8L7bwH.jpg
1434 ms
59JjgV3ld.jpeg
1421 ms
7bfXZi6wH.jpg
1383 ms
tiles
875 ms
rtrg
144 ms
tiles
1040 ms
tiles
1287 ms
tiles
1241 ms
400 ms
tiles
1417 ms
tiles
1269 ms
tiles
1277 ms
tiles
1275 ms
tiles
1438 ms
tiles
1408 ms
tiles
1553 ms
tiles
1412 ms
tiles
1517 ms
tiles
1561 ms
tiles
1599 ms
tiles
1612 ms
tiles
1597 ms
tiles
1766 ms
tiles
1717 ms
tiles
1738 ms
tiles
1870 ms
2c3d90d4e522c1f62b6cf3e59f7a877d.png
578 ms
BbkCuJBqM.jpg
1468 ms
YPoPa67rM.jpg
1484 ms
beDtWHFZa.jpg
1438 ms
inception-7d288965eb52821298d43f862e861cd5d905074b.js
520 ms
F3QiTBnoy.jpeg
1300 ms
arrowright.png
1316 ms
oRgqt6CMXitPuon51E.jpg
1274 ms
PcDkGR5DWebARxxcKp.jpg
1309 ms
9E3uTpcESvXvHzctJp.jpg
1389 ms
lo2wDe8s34ywmEVomF.jpg
1287 ms
jmKpNROaqurxtnLLfc.jpg
1201 ms
mPqV7VilbbHTt7Q2a5.jpg
1165 ms
WqhtDGt6lAIW58kjkQ.jpg
1264 ms
6nxQjsR2hCgn9borW4.jpg
1264 ms
PLWFjDQkuAHfoLmdh2.jpg
1205 ms
m56Yki8kk1jLUDAg7b.jpg
1216 ms
IXNM5pMywsEyW3ifpT.jpg
1226 ms
jXZr16LUu1goF4GFsH.jpg
1214 ms
hlkW4DRgXRbnmjTWBS.jpg
1223 ms
PC7xTExzocV6bAo1Ip.jpg
1160 ms
VIZtxLY8vJTaHGdvDI.jpg
1203 ms
aVzoh3AAPi4zBslDbb.jpg
1112 ms
fn5FWfhdIaXi966Iba.jpg
1226 ms
eRdhaNoNmO5rKrwVwK.jpg
1229 ms
euPeRdbJRweCeCdosW.jpg
1210 ms
NJ4Zsax5nK7dHUFcXz.jpg
1119 ms
8iAgxIF4pIBdcET8cF.jpg
1150 ms
j7wWQQYIRImTYUGkom.jpg
1171 ms
kZkVbIApH2S7TMeMJh.jpg
1228 ms
nAUhtSiewdVgGi49Xj.jpg
1228 ms
MuY2I1QYKlzJoqiZw1.jpg
1209 ms
3q5AlcZ43jkeT4jzrq.jpg
1124 ms
fb.png
1150 ms
telegram.png
1283 ms
vk.png
1349 ms
ok.png
1329 ms
inst.png
1372 ms
youtube.png
1126 ms
select_dropdown.png
1138 ms
star-empty.png
211 ms
olymprealty.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-*] attributes do not match their roles
button, link, and menuitem elements do not have accessible names.
ARIA IDs are not unique
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
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
<html> element does not have a [lang] attribute
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
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.
olymprealty.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
Missing source maps for large first-party JavaScript
olymprealty.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 Olymprealty.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 Olymprealty.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.
olymprealty.ru
Open Graph data is detected on the main page of Olymprealty. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: