8.4 sec in total
463 ms
6.8 sec
1.1 sec
Click here to check amazing Preo content for Russia. Otherwise, check out these important facts you probably never knew about preo.ru
Реабилитационный центр «Преодоление» — первый в России специализированный круглосуточный стационар европейского уровня для пациентов с тяжелыми ограничениями в передвижении и самообслуживании вследств...
Visit preo.ruWe analyzed Preo.ru page load time and found that the first response time was 463 ms and then it took 7.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
preo.ru performance score
name
value
score
weighting
Value3.2 s
44/100
10%
Value10.5 s
0/100
25%
Value10.1 s
9/100
10%
Value290 ms
80/100
30%
Value0.818
4/100
15%
Value12.3 s
15/100
10%
463 ms
603 ms
363 ms
577 ms
580 ms
Our browser made a total of 112 requests to load all elements on the main page. We found that 90% of them (101 requests) were addressed to the original Preo.ru, 2% (2 requests) were made to Fonts.googleapis.com and 2% (2 requests) were made to Vk.com. The less responsive or slowest element that took the longest time to load (1.9 sec) relates to the external source Vk.com.
Page size can be reduced by 173.8 kB (6%)
2.8 MB
2.7 MB
In fact, the total size of Preo.ru main page is 2.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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 2.4 MB which makes up the majority of the site volume.
Potential reduce by 47.3 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 10.0 kB, which is 18% 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 47.3 kB or 85% of the original size.
Potential reduce by 72.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. Preo images are well optimized though.
Potential reduce by 43.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 43.6 kB or 13% of the original size.
Potential reduce by 10.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. Preo.ru needs all CSS files to be minified and compressed as it can save up to 10.6 kB or 13% of the original size.
Number of requests can be reduced by 60 (56%)
108
48
The browser has sent 108 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Preo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 40 to 1 for JavaScripts and from 22 to 1 for CSS and as a result speed up the page load time.
preo.ru
463 ms
preo.ru
603 ms
bootstrap.css
363 ms
font.css
577 ms
responsive.css
580 ms
camera.css
615 ms
style.css
511 ms
flexslider.css
543 ms
owl.carousel.css
526 ms
owl.theme.css
630 ms
font-awesome.css
783 ms
cherry-plugin.css
786 ms
styles.css
685 ms
main-style.css
1037 ms
magnific-popup.css
737 ms
css
78 ms
css
92 ms
common.css
745 ms
unit.css
906 ms
veil.css
844 ms
evo.css
858 ms
slick.css
891 ms
highslide.css
893 ms
jquery-1.11.3.min.js
1196 ms
jquery.easing.1.3.js
981 ms
jquery.elastislide.js
1006 ms
jquery-migrate-1.2.1.min.js
1014 ms
swfobject.js
1010 ms
modernizr.js
1101 ms
jflickrfeed.js
1151 ms
custom.js
1121 ms
bootstrap.min.js
1133 ms
jquery.form.min.js
1140 ms
slick.js
1389 ms
common-dist.js
1786 ms
common.js
1369 ms
highslide-with-gallery.js
1369 ms
highslide.js
1371 ms
jquery.mobile.customized.min.js
1373 ms
wnew.js
604 ms
banner.css
1631 ms
jquery.validate.min.js
1395 ms
additional-methods.min.js
1280 ms
messages_ru.js
1270 ms
comment-reply.min.js
1257 ms
jquery.flexslider-min.js
1416 ms
cherry-plugin.js
1411 ms
jquery.form.min.js
1377 ms
scripts_site.js
1373 ms
superfish.js
1319 ms
jquery.mobilemenu.js
1263 ms
jquery.magnific-popup.min.js
1256 ms
tmstickup.js
1222 ms
device.min.js
1218 ms
jquery.zaccordion.min.js
1276 ms
camera.min.js
1262 ms
jquery.debouncedresize.js
1227 ms
jquery.ba-resize.min.js
1223 ms
jquery.isotope.js
1214 ms
loadmetrics.js
1266 ms
openapi.js
1939 ms
body.jpg
1912 ms
preo-n-logo.jpg
1900 ms
icc-adres.jpg
1901 ms
icc-phone.jpg
1899 ms
phone-31.jpg
1909 ms
burg10.jpg
1897 ms
p-b-02k72-8g-8-0.jpg
1914 ms
p-reabilitaciya-insult.jpg
1914 ms
p-_sm_1118.jpg
1910 ms
p-b-548g5a-0o-5015-8b0f8o.jpg
1853 ms
p-g5-5-73-20o-b-02.jpg
1815 ms
p-f.jpg
1846 ms
p-c-38o.jpg
1816 ms
p-image.png
1878 ms
m-shurezkodavlenie.jpg
1484 ms
m-ozokervpreo.jpg
1449 ms
m-novtechexo.jpg
1448 ms
ll-photo-min.jpg
1444 ms
1.jpg
1442 ms
2.jpg
1254 ms
3.jpg
1290 ms
vk.png
1251 ms
main_tail.gif
1279 ms
content_tail.gif
1282 ms
search.png
1282 ms
ajax.php
335 ms
img_4088.jpg
263 ms
rtrg
139 ms
5-a-0o.jpg
124 ms
metrics.js
124 ms
ch-2-54-0b-l528g-a-515452k-.-.1.jpg
349 ms
custom.png
120 ms
zoomout.cur
118 ms
loader.white.gif
126 ms
gtm.js
58 ms
tag.js
910 ms
analytics.js
81 ms
018-5b.jpg
128 ms
collect
34 ms
1219014318_imgp8648.jpg
242 ms
ekzoskelet-3_1500x1000.jpg
139 ms
59-d878-38o-68-o-a-89.jpg
130 ms
5.jpg
408 ms
6.jpg
134 ms
advert.gif
588 ms
7.jpg
125 ms
8.jpg
144 ms
9.jpg
124 ms
10.jpg
131 ms
sync_cookie_image_decide
132 ms
12.jpg
123 ms
preo.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
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
Image elements do not have [alt] attributes
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
preo.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
preo.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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Preo.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 Preo.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.
preo.ru
Open Graph data is detected on the main page of Preo. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: