13.7 sec in total
1.3 sec
11.3 sec
1.1 sec
Welcome to otolar-centre.ru homepage info - get ready to check Otolar Centre best content for Russia right away, or after learning these important things about otolar-centre.ru
оториноларингологии медицинский исследовательский
Visit otolar-centre.ruWe analyzed Otolar-centre.ru page load time and found that the first response time was 1.3 sec and then it took 12.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
otolar-centre.ru performance score
name
value
score
weighting
Value11.6 s
0/100
10%
Value12.1 s
0/100
25%
Value18.8 s
0/100
10%
Value610 ms
49/100
30%
Value0.398
25/100
15%
Value20.4 s
2/100
10%
1280 ms
525 ms
297 ms
297 ms
443 ms
Our browser made a total of 178 requests to load all elements on the main page. We found that 93% of them (165 requests) were addressed to the original Otolar-centre.ru, 2% (4 requests) were made to Nok.minzdrav.gov.ru and 2% (3 requests) were made to Counter.yadro.ru. The less responsive or slowest element that took the longest time to load (3.2 sec) belongs to the original domain Otolar-centre.ru.
Page size can be reduced by 1.7 MB (24%)
7.0 MB
5.3 MB
In fact, the total size of Otolar-centre.ru main page is 7.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 5.2 MB which makes up the majority of the site volume.
Potential reduce by 106.6 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 106.6 kB or 79% of the original size.
Potential reduce by 516.1 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. Otolar Centre images are well optimized though.
Potential reduce by 694.1 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 694.1 kB or 59% of the original size.
Potential reduce by 350.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. Otolar-centre.ru needs all CSS files to be minified and compressed as it can save up to 350.2 kB or 85% of the original size.
Number of requests can be reduced by 85 (51%)
167
82
The browser has sent 167 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Otolar Centre. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 30 to 1 for JavaScripts and from 41 to 1 for CSS and as a result speed up the page load time.
otolar-centre.ru
1280 ms
calendar-jos.css
525 ms
jcemediabox.css
297 ms
style.css
297 ms
widgetkit-3e9235e9.css
443 ms
bootstrap.css
586 ms
template.css
297 ms
style.css
447 ms
modal.css
443 ms
accordionview.css
738 ms
accordionviewcategorized.css
881 ms
style.css
801 ms
core.js
601 ms
keepalive.js
669 ms
mootools-core.js
1210 ms
mootools-more.js
1329 ms
jquery.min.js
1106 ms
jquery-noconflict.js
1029 ms
jquery-migrate.min.js
1028 ms
calendar.js
1317 ms
calendar-setup.js
1174 ms
punycode.js
1175 ms
validate.js
1397 ms
jcemediabox.js
1481 ms
widgetkit-76908f43.js
1468 ms
engine.mootools.js
1503 ms
modal.js
1665 ms
utilities.js
2058 ms
accordionview.js
1738 ms
iepngfix_tilebg.js
1837 ms
ct-functions.js
1832 ms
ct-bot-detector-wrapper.js
39 ms
ct-external.js
1651 ms
base.css
1825 ms
extensions.css
1957 ms
tools.css
2210 ms
layout.css
1974 ms
api.js
51 ms
menus.css
1865 ms
modules.css
1696 ms
system.css
2026 ms
k2.css
1831 ms
opensans.css
1699 ms
opensans.css
1714 ms
opensans.css
1910 ms
opensans.css
1755 ms
style.css
1706 ms
responsive.css
1707 ms
custom.css
1895 ms
print.css
1686 ms
opensans.css
1644 ms
front.css
1586 ms
responsive.css
1586 ms
warp.js
1476 ms
responsive.js
1475 ms
accordionmenu.js
1420 ms
dropdownmenu.js
1443 ms
template.js
1443 ms
script.js
1693 ms
search.js
1350 ms
lightbox.js
1253 ms
mediaelement-and-player.js
1805 ms
spotlight.js
1272 ms
base.css
752 ms
layout.css
837 ms
menus.css
825 ms
modules.css
846 ms
tools.css
757 ms
responsive.css
740 ms
system.css
738 ms
system.css
749 ms
system-all.css
799 ms
print.css
882 ms
layout.css
290 ms
recaptcha__en.js
98 ms
3_0_D0F0C0FF_D0F0C0FF_0_pageviews
1038 ms
banner1.jpg
1045 ms
1.jpg
1042 ms
logo.png
1039 ms
separator.png
1034 ms
ru_ru.gif
1036 ms
zh.gif
1036 ms
ar_aa.gif
1032 ms
en.gif
1038 ms
%D0%9A%D0%B0%D1%87%D0%B5%D1%81%D1%82%D0%B2%D0%BE_%D0%B8_%D0%B1%D0%B5%D0%B7%D0%BE%D0%BF%D0%B0%D1%81%D0%BD%D0%BE%D1%81%D1%82%D1%8C.png
1069 ms
header-bottom.png
1040 ms
menu-li-active.png
1039 ms
searchbox_magnifier.png
1041 ms
form_input.jpg
1043 ms
s-022019-1.jpg
1702 ms
pdf.png
1041 ms
Skoro.png
1043 ms
08082024of.jpg
1076 ms
08082024.jpeg
1044 ms
07082024.jpg
1297 ms
06082024.jpg
1264 ms
05082014patent.jpg
1478 ms
02082024.jpeg
1518 ms
01082024-0.jpg
1662 ms
31072024.jpg
1762 ms
30072024R.jpg
1878 ms
29072024-p.jpg
1978 ms
26072024D.jpeg
2163 ms
0508otk.jpg
2100 ms
iotog2_%D0%BA%D0%BE%D0%BF%D0%B8%D1%8F.png
2140 ms
v3t.png
2284 ms
%D0%9E%D1%82%D0%B7%D1%8B%D0%B2.png
2492 ms
dayhes_1.jpg
2475 ms
video-icon.png
2454 ms
POMOSH.jpg
2783 ms
News.png
3227 ms
zadat_vopros2.jpg
2925 ms
2
2091 ms
telegram.jpg
2574 ms
watch.js
0 ms
hit
872 ms
OpenSans-Light-webfont.woff
2092 ms
slideshow.js
1899 ms
popup.html
1720 ms
tooltip.html
1868 ms
hit
543 ms
youtube.jpg
2188 ms
VK.png
2015 ms
QR.png
2482 ms
TQR.png
2389 ms
VKQR.png
2312 ms
curv_page-0001.jpg
2379 ms
blood.jpg
2679 ms
03.jpg
2631 ms
RAN.jpg
2660 ms
fmba.jpg
2669 ms
minzdrav.jpg
2858 ms
nfrz.jpg
2884 ms
11.jpg
2903 ms
slishim.png
2557 ms
ROSS_final.jpg
3021 ms
%D0%9D%D0%90%D0%9E.png
2553 ms
hit
135 ms
VOG.jpg
2483 ms
AZ.jpg
2592 ms
Soedinenie.jpg
2551 ms
Rosmed.info.jpg
2505 ms
%D0%A4%D0%9E%D0%9D%D0%94_%D0%9D%D0%B5_%D0%BE%D0%BF%D0%B0%D0%B7%D0%B4%D0%B0%D0%B9.png
2526 ms
%D0%9D%D0%9C%D0%98%D0%A6_%D0%B7%D0%B4%D0%BE%D1%80%D0%BE%D0%B2%D1%8C%D1%8F_%D0%B4%D0%B5%D1%82%D0%B5%D0%B9.jpg
2565 ms
bg2.png
1015 ms
minzdrav_logo_small.png
1164 ms
btn.png
1058 ms
volnc.png
2586 ms
Mediagrupp.jpg
2443 ms
1%D0%BD%D0%B0_%D0%BC%D0%BB%D0%BD.jpg
2451 ms
%D0%94%D0%95%D0%A2%D0%A1%D0%9A%D0%90%D0%AF_%D0%90%D0%A1%D0%A1%D0%9E%D0%A6%D0%98%D0%90%D0%A6%D0%98%D0%AF.jpg
2341 ms
%D0%A1%D0%BE%D1%8E%D0%B7_%D0%B2%D0%B5%D1%82%D0%B5%D1%80%D0%B0%D0%BD%D0%BE%D0%B2_%D0%B3%D0%BE%D1%81%D0%BF%D0%B5%D0%B7%D0%BE%D0%BF%D0%B0%D1%81%D0%BD%D0%BE%D1%81%D1%82%D0%B8.jpg
2638 ms
%D0%A4%D0%A5%D0%93%D0%90%D0%A1%D0%A0_%D0%BB%D0%BE%D0%B3%D0%BE_page-0001.jpg
2463 ms
copyright.jpg
2578 ms
nav.png
2346 ms
hr-dotted.png
2102 ms
mod-dot.png
2248 ms
4.jpg
2253 ms
footer-gradient.png
2367 ms
mid-gradient.png
2198 ms
top.jpg
2330 ms
icon.png
2077 ms
dropdown-bg.png
2352 ms
menu-sep.png
2185 ms
astrahan.png
1980 ms
khabarovsk.png
2021 ms
back-to-top.png
1938 ms
zoom-img.png
1879 ms
s2.jpg
2336 ms
s-022019-3.jpg
2779 ms
s-022019-4.jpg
2618 ms
s-022019-5.jpg
2564 ms
s-022019-6.jpg
2508 ms
s-022019-7.jpg
2815 ms
s-022019-8-1.jpg
1966 ms
ns6.png
1892 ms
ns7.png
1872 ms
s-022019-11-1.jpg
1747 ms
otolar-centre.ru accessibility score
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
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
otolar-centre.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
otolar-centre.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
![]()
RU
![]()
RU
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Otolar-centre.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 Otolar-centre.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.
otolar-centre.ru
Open Graph description is not detected on the main page of Otolar Centre. 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: