9.3 sec in total
1.1 sec
7.8 sec
394 ms
Welcome to infodoctor.ru homepage info - get ready to check Info Doctor best content for Russia right away, or after learning these important things about infodoctor.ru
Лучшие врачи и клиники Москвы на информационно-медицинском портале «ИнфоДоктор» - 8644 медицинских центра в Москве с отзывами реальных клиентов, ценами, фото
Visit infodoctor.ruWe analyzed Infodoctor.ru page load time and found that the first response time was 1.1 sec and then it took 8.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
infodoctor.ru performance score
name
value
score
weighting
Value2.4 s
72/100
10%
Value2.9 s
80/100
25%
Value4.6 s
71/100
10%
Value310 ms
78/100
30%
Value0.002
100/100
15%
Value7.8 s
44/100
10%
1103 ms
261 ms
396 ms
271 ms
531 ms
Our browser made a total of 127 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Infodoctor.ru, 11% (14 requests) were made to Eu-sonar.sociomantic.com and 6% (8 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (3.1 sec) relates to the external source My1.imgsmail.ru.
Page size can be reduced by 535.8 kB (42%)
1.3 MB
735.0 kB
In fact, the total size of Infodoctor.ru main page is 1.3 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 638.1 kB which makes up the majority of the site volume.
Potential reduce by 85.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. This page needs HTML code to be minified as it can gain 20.9 kB, which is 20% 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 85.5 kB or 81% of the original size.
Potential reduce by 45.5 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. Info Doctor images are well optimized though.
Potential reduce by 318.5 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 318.5 kB or 74% of the original size.
Potential reduce by 86.2 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. Infodoctor.ru needs all CSS files to be minified and compressed as it can save up to 86.2 kB or 87% of the original size.
Number of requests can be reduced by 80 (73%)
109
29
The browser has sent 109 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Info Doctor. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 32 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
px.infodoctor.ru
1103 ms
head.js
261 ms
_main.css
396 ms
_main_dktr.css
271 ms
animate.css
531 ms
jquery.fancybox.css
268 ms
jquery.fancybox-thumbs.css
272 ms
webfont.js
397 ms
loader.js
318 ms
share.js
240 ms
jquery.min.js
32 ms
jquery.maskedinput.min.js
281 ms
jquery.tipsy.js
280 ms
jquery.tabster.js
284 ms
jquery.fancybox.pack.js
532 ms
jquery.fancybox-thumbs.js
416 ms
base64.js
417 ms
all.js
1469 ms
loader.js
344 ms
fonts.css
138 ms
bg.jpg
299 ms
iconza.woff
184 ms
websymbolsligaregular.woff
296 ms
tab1.png
846 ms
tab2.png
978 ms
tab3.png
846 ms
tab5.png
846 ms
manager.png
543 ms
clinics2.png
845 ms
firrma.png
990 ms
rbru.png
986 ms
hopesfears.png
992 ms
appstore.png
987 ms
loading.gif
1230 ms
OpenSans-Regular-webfont.woff
1053 ms
OpenSans-Light-webfont.woff
1051 ms
OpenSans-Semibold-webfont.woff
1054 ms
OpenSans-Bold-webfont.woff
1141 ms
OpenSans-ExtraBold-webfont.woff
1054 ms
all.js
371 ms
grstat
410 ms
api_min.js
640 ms
share.php
139 ms
share_logo.png
321 ms
platform.js
130 ms
cb=gapi.loaded_0
128 ms
cb=gapi.loaded_1
130 ms
sharebutton
200 ms
203 ms
connect.js
767 ms
xd_arbiter.php
272 ms
xd_arbiter.php
600 ms
postmessageRelay
145 ms
rs=AGLTcCP9IczaT7Rf-UGgqDPBu0TrwouL5A
40 ms
rs=AGLTcCONaLyiNnVKL3jJiPNE7nDzR3YYiA
87 ms
vxNK-E6B13CyehuDCmvQvw.woff
167 ms
grlryt2bdKIyfMSOhzd1eA.woff
176 ms
1077434459-postmessagerelay.js
52 ms
rpc:shindig_random.js
49 ms
share_button
453 ms
cb=gapi.loaded_0
7 ms
ga.js
185 ms
watch.js
183 ms
a.php
543 ms
infodoctor-ru
272 ms
221 ms
__utm.gif
60 ms
jquery.js
3060 ms
uber-share.js
1449 ms
20.css
330 ms
share_button.php
112 ms
view
98 ms
dk
186 ms
OZhivdPHVp_.js
609 ms
LVx-xkvaJ0b.png
671 ms
sociomantic
612 ms
UserMatch.ashx
38 ms
sync.cgi
295 ms
rum
82 ms
u.php
91 ms
serve
115 ms
80 ms
pixel
88 ms
usersync
45 ms
Pug
59 ms
483 ms
us.gif
49 ms
info.php
293 ms
tg-03.yieldpartners.com
310 ms
tap.php
13 ms
match
13 ms
sd
58 ms
match
160 ms
rum
40 ms
102 ms
match
205 ms
pixel
49 ms
merge
59 ms
share.3aa457d6.css
657 ms
match
178 ms
match
381 ms
match
95 ms
mapuser
91 ms
match
120 ms
cm.gif
36 ms
match
199 ms
match
92 ms
match
108 ms
match
97 ms
match
94 ms
421383662517445779
120 ms
match
93 ms
match
112 ms
match
93 ms
ok-like-bg-l.png
153 ms
ok-logon.png
305 ms
preloader.gif
475 ms
vertical-pointer-sprite.png
159 ms
mm-rounded.png
157 ms
preloader.gif
158 ms
grstat
311 ms
d525461.gif
1116 ms
code.js
320 ms
counter
162 ms
tracker
195 ms
nr-918.min.js
59 ms
4aa654be27
68 ms
infodoctor.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-hidden="true"] elements contain focusable descendents
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
Image elements do not have [alt] attributes
Links do not have a discernible name
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.
infodoctor.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
infodoctor.ru SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
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 Infodoctor.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 Infodoctor.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.
infodoctor.ru
Open Graph description is not detected on the main page of Info Doctor. 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: