13.1 sec in total
849 ms
11.4 sec
908 ms
Click here to check amazing Endoinfo content for Russia. Otherwise, check out these important facts you probably never knew about endoinfo.ru
Центр эндокринологии в Санкт-Петербурге. Прием эндокринолога, запись к врачу.
Visit endoinfo.ruWe analyzed Endoinfo.ru page load time and found that the first response time was 849 ms and then it took 12.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
endoinfo.ru performance score
name
value
score
weighting
Value4.5 s
15/100
10%
Value4.5 s
37/100
25%
Value9.8 s
10/100
10%
Value2,940 ms
3/100
30%
Value0.001
100/100
15%
Value12.7 s
14/100
10%
849 ms
761 ms
893 ms
765 ms
770 ms
Our browser made a total of 66 requests to load all elements on the main page. We found that 6% of them (4 requests) were addressed to the original Endoinfo.ru, 42% (28 requests) were made to Endoinfo.ru.opt-images.1c-bitrix-cdn.ru and 24% (16 requests) were made to Endoinfo.ru.opt-css.1c-bitrix-cdn.ru. The less responsive or slowest element that took the longest time to load (8.9 sec) relates to the external source Endoinfo.ru.opt-images.1c-bitrix-cdn.ru.
Page size can be reduced by 719.5 kB (26%)
2.8 MB
2.0 MB
In fact, the total size of Endoinfo.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. 35% of websites need less resources to load. Images take 1.7 MB which makes up the majority of the site volume.
Potential reduce by 319.7 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 319.7 kB or 66% of the original size.
Potential reduce by 10.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. Endoinfo images are well optimized though.
Potential reduce by 321.8 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 321.8 kB or 72% of the original size.
Potential reduce by 67.9 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. Endoinfo.ru needs all CSS files to be minified and compressed as it can save up to 67.9 kB or 85% of the original size.
Number of requests can be reduced by 18 (32%)
57
39
The browser has sent 57 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Endoinfo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
endoinfo.ru
849 ms
kernel_main0.css
761 ms
page_79a91a110f4040e3b216848e7e5af18e0.css
893 ms
default_1826f1e079199128ed60f0b1018661b10.css
765 ms
template_6ee50efa94c8c81e1c942cc8ae97621a0.css
770 ms
kernel_main.js
1635 ms
jquery-1.8.3.min.js
942 ms
template_c7e282900bf47a6ab6aaff8b9ce39be5.js
752 ms
page_de848ac4ecba711c77aa5bce76ec79d6.js
773 ms
jquery.sudoSlider.min.js
1683 ms
jquery.mousewheel-3.0.4.pack.js
653 ms
jquery.fancybox-1.3.4.pack.js
654 ms
jquery.fancybox-1.3.4.css
1369 ms
style.css
169 ms
sokr.js
652 ms
header_bg.png
2566 ms
logo_head.png
710 ms
phone_ico.png
888 ms
contacts.png
176 ms
li_services.png
177 ms
h3_bg.png
173 ms
f.jpg
673 ms
g.jpg
674 ms
baz.jpg
680 ms
book.jpg
685 ms
uzi.jpg
6588 ms
eko.jpg
1179 ms
pao.jpg
1179 ms
bakterii.png
4944 ms
advio.png
8856 ms
cent.png
3852 ms
pmz.jpg
2402 ms
11111.jpg
1354 ms
310.jpg
2247 ms
cshitovidnaya_zheleza_u_zhencshin_lechenie.jpg
2398 ms
p_25739_1_gallerybig.jpg
2552 ms
123.jpg
8902 ms
11.jpg
2724 ms
22.jpg
2910 ms
33.jpg
3069 ms
logo.gif
3811 ms
logo-01.jpg
4222 ms
logo-1.gif
4045 ms
ice_medium.gif
4282 ms
eses-logo_5.gif
5368 ms
europeansociety-of-endocrinology-converted.png
5400 ms
ATA288eps.gif
5365 ms
AACE_logo.png
5621 ms
captcha.php
385 ms
318 ms
mini_logo.png
292 ms
ico_microscope2.jpg
292 ms
sidebar_bot.png
294 ms
footer_tel.png
325 ms
footer_bg.png
2553 ms
watch.js
1 ms
watch.js
1 ms
foot_logo.png
482 ms
prev.png
451 ms
next.png
451 ms
1120 ms
combine.xml
3560 ms
ef50ac9e93aaebe3299791c79f277f8e.cur
202 ms
3ce22e999d54bb9ca8150a59207f9d3e.cur
145 ms
4965b66fe115b2f2ed500ece66514d86.cur
318 ms
77492cf358d8b12629399322926c93f2.cur
473 ms
endoinfo.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
button, link, and menuitem elements do not have accessible names.
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
endoinfo.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
endoinfo.ru SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Page is blocked from indexing
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
WINDOWS-1251
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Endoinfo.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 Endoinfo.ru main page’s claimed encoding is windows-1251. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
endoinfo.ru
Open Graph description is not detected on the main page of Endoinfo. 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: