6.6 sec in total
506 ms
5.3 sec
747 ms
Welcome to prian.ru homepage info - get ready to check Prian best content for Russia right away, or after learning these important things about prian.ru
Prian.ru – где, как и за сколько купить недвижимость за рубежом. Каталог предложений от компаний и частных лиц, путеводители по рынкам зарубежной недвижимости.
Visit prian.ruWe analyzed Prian.ru page load time and found that the first response time was 506 ms and then it took 6.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
prian.ru performance score
name
value
score
weighting
Value2.6 s
62/100
10%
Value13.6 s
0/100
25%
Value9.9 s
10/100
10%
Value3,200 ms
2/100
30%
Value0.006
100/100
15%
Value14.7 s
8/100
10%
506 ms
269 ms
286 ms
277 ms
278 ms
Our browser made a total of 159 requests to load all elements on the main page. We found that 8% of them (12 requests) were addressed to the original Prian.ru, 43% (68 requests) were made to Static.prian.ru and 10% (16 requests) were made to Content.adriver.ru. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source Static.prian.ru.
Page size can be reduced by 656.9 kB (37%)
1.8 MB
1.1 MB
In fact, the total size of Prian.ru main page is 1.8 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 862.4 kB which makes up the majority of the site volume.
Potential reduce by 76.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 76.0 kB or 78% of the original size.
Potential reduce by 37.3 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. Prian images are well optimized though.
Potential reduce by 158.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 158.6 kB or 43% of the original size.
Potential reduce by 385.0 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. Prian.ru needs all CSS files to be minified and compressed as it can save up to 385.0 kB or 84% of the original size.
Number of requests can be reduced by 98 (65%)
150
52
The browser has sent 150 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Prian. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 54 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.
prian.ru
506 ms
google-fonts.css
269 ms
font-awesome.min.css
286 ms
kotshare.css
277 ms
jquery.ui.core.css
278 ms
jquery.ui.menu.css
287 ms
main.css
596 ms
new_verst.css
397 ms
newone.css
437 ms
jquery.min.js
850 ms
jquery-migrate-1.2.1.js
575 ms
user_dialog.js
759 ms
jquery.ui.core.css
523 ms
jquery.ui.resizable.css
575 ms
jquery.ui.selectable.css
652 ms
jquery.ui.button.css
708 ms
jquery.ui.dialog.css
713 ms
jquery.ui.theme.css
731 ms
forms.css
780 ms
jquery-ui-1.9.2.custom.min.js
1390 ms
adriver.core.2.js
878 ms
gtm_event.js
429 ms
vendor.js
1578 ms
main.js
770 ms
jquery.cookie.js
787 ms
main2.js
865 ms
jquery.kotshare.js
877 ms
banner.js
907 ms
URI.min.js
1210 ms
prian_static.js
1676 ms
article.js
1011 ms
jquery.price_format.1.7.js
1042 ms
conversion.js
38 ms
autoUpdate.adriver.js
275 ms
autoLoad.adriver.js
276 ms
fbds.js
196 ms
gtm.js
61 ms
watch.js
38 ms
activityi;src=4970681;type=invmedia;cat=hldcftjv;ord=3450237044598.907
137 ms
main_prian.jpg
441 ms
top100.cnt
336 ms
w7.gif
337 ms
logo;prian
336 ms
logo.png
137 ms
71_14123225971860559089sx.jpg
148 ms
283_14123226851065231222sx.jpg
139 ms
13672464811417830696sx.gif
143 ms
13672463901787327966sx.gif
290 ms
1367246407675577940sx.gif
272 ms
1367246465316419804sx.gif
272 ms
201604060429071579949639p.jpg
427 ms
20160330134103955363908p.jpg
405 ms
20160323050039843942375p.jpg
414 ms
201604041633541227148095p.jpg
421 ms
20150603110812201132427p.jpg
424 ms
20160329104117440783661p.jpg
468 ms
201603211548441499099298p.jpg
531 ms
20151222161837365355379p.jpg
538 ms
201603221751201816379634p.jpg
552 ms
201601271645111003008591p.jpg
693 ms
20160109042140873303357p.jpg
557 ms
video-left.jpg
602 ms
flags-greece.png
685 ms
flags-cyprus.png
685 ms
flags-turkey.png
688 ms
flags-czech.png
692 ms
flags-spain.png
736 ms
flags-italy.png
794 ms
flags-finland.png
789 ms
flags-france.png
811 ms
flags-croatia.png
829 ms
flags-bulgaria.png
822 ms
flags-latvia.png
881 ms
flags-montenegro.png
926 ms
flags-germany.png
932 ms
flags-usa.png
942 ms
flags-dominican-republic.png
959 ms
fontawesome-webfont.woff
1261 ms
hit;prian
282 ms
flags-thailand.png
894 ms
rtrg
282 ms
22 ms
old.adriver.js
256 ms
searchMeta.adriver.js
272 ms
massLoad.adriver.js
272 ms
getElementsByClassName.js
283 ms
TeaserBlockPrianTaL.site.js
155 ms
TeaserBlockPrianOotM.site.js
281 ms
TeaserBlockPrianTxt.site.js
285 ms
108 ms
user_dialog_new.php
271 ms
gtm_dataLayer.php
256 ms
1459246381209212340p.jpg
790 ms
hit;prian
140 ms
103 ms
checkFlash.adriver.js
259 ms
functions.adriver.js
262 ms
analytics.js
18 ms
collect
7 ms
collect
96 ms
ga-audiences
35 ms
counter2
180 ms
counter2
212 ms
merle.cgi
311 ms
merle.cgi
316 ms
merle.cgi
317 ms
merle.cgi
325 ms
merle.cgi
311 ms
merle.cgi
575 ms
merle.cgi
571 ms
script.js
276 ms
1.html
168 ms
script.js
281 ms
1.html
157 ms
script.js
275 ms
1.html
158 ms
script.js
267 ms
1.html
254 ms
script.js
301 ms
1.html
331 ms
1.js
233 ms
script.js
281 ms
1.html
159 ms
pixel.adriver.js
273 ms
makeFlash.adriver.js
272 ms
checkFB.adriver.js
275 ms
makeImage.adriver.js
272 ms
clickCoord.adriver.js
275 ms
checkOver.adriver.js
533 ms
html.adriver.js
541 ms
pixel
28 ms
adriver-sync
274 ms
AxtcXsBH6G5DUVZqv-nGztg
288 ms
1186729641395172505s.gif
164 ms
0.jpg
300 ms
0.jpg
417 ms
flag_bulg_s.gif
159 ms
0.jpg
302 ms
0.jpg
324 ms
0.jpg
296 ms
1.html
289 ms
11867292191018980241s.gif
156 ms
11867293112091358402s.gif
158 ms
11867291921233590636s.gif
157 ms
0.jpg
283 ms
0.jpg
502 ms
0.jpg
305 ms
sync.cgi
265 ms
sync.cgi
261 ms
sync.cgi
262 ms
sync.cgi
292 ms
sync.cgi
264 ms
event.adriver.js
272 ms
redco_ad_as3.html
994 ms
immotrading.html
837 ms
200x280_Red_Feniks_montenegro.gif
399 ms
sync.cgi
555 ms
runtime.js
23 ms
12 ms
prian.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
<frame> or <iframe> elements do not have a title
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.
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
<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> 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.
prian.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
prian.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 Prian.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 Prian.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.
prian.ru
Open Graph description is not detected on the main page of Prian. 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: