7.5 sec in total
561 ms
4.1 sec
2.7 sec
Welcome to uro-info.ru homepage info - get ready to check Uro Info best content for Russia right away, or after learning these important things about uro-info.ru
Всё об аденоме простаты, ГМП, цистите и простатите. Ответы на вопросы о затруднениях при мочеиспускании. Профессиональные термины в доступном изложении.
Visit uro-info.ruWe analyzed Uro-info.ru page load time and found that the first response time was 561 ms and then it took 6.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
uro-info.ru performance score
name
value
score
weighting
Value2.3 s
74/100
10%
Value2.3 s
93/100
25%
Value8.4 s
18/100
10%
Value1,920 ms
8/100
30%
Value0.024
100/100
15%
Value7.0 s
53/100
10%
561 ms
773 ms
141 ms
285 ms
412 ms
Our browser made a total of 103 requests to load all elements on the main page. We found that 88% of them (91 requests) were addressed to the original Uro-info.ru, 4% (4 requests) were made to Top-fwz1.mail.ru and 2% (2 requests) were made to Bitrix.info. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Uro-info.ru.
Page size can be reduced by 282.6 kB (11%)
2.6 MB
2.3 MB
In fact, the total size of Uro-info.ru main page is 2.6 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. 60% of websites need less resources to load. Images take 2.2 MB which makes up the majority of the site volume.
Potential reduce by 126.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. This page needs HTML code to be minified as it can gain 22.7 kB, which is 15% 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 126.7 kB or 85% of the original size.
Potential reduce by 140.0 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. Uro Info images are well optimized though.
Potential reduce by 2.4 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. This website has mostly compressed JavaScripts.
Potential reduce by 13.5 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. Uro-info.ru needs all CSS files to be minified and compressed as it can save up to 13.5 kB or 21% of the original size.
Number of requests can be reduced by 21 (21%)
99
78
The browser has sent 99 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Uro Info. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
uro-info.ru
561 ms
uro-info.ru
773 ms
style.css
141 ms
style.css
285 ms
slick.css
412 ms
slick-theme.css
417 ms
fm.revealator.jquery.css
419 ms
jquery.fancybox.min.css
428 ms
select2.min.css
427 ms
template_styles.css
570 ms
logo.png
547 ms
womanTriangle.svg
555 ms
manTriangle.svg
557 ms
jquery-3.6.1.min.js
705 ms
slick.min.js
690 ms
app.js
689 ms
axios.min.js
690 ms
fm.revealator.jquery.js
691 ms
jquery.fancybox.min.js
718 ms
select2.min.js
724 ms
script.js
813 ms
nq381gp4vbb7b.js
983 ms
icon-1.png
825 ms
icon-2.png
830 ms
icon-3.png
845 ms
icon-4.png
844 ms
icon-5.png
848 ms
icon-6.png
1001 ms
qyfesepog5gmsdsfyjidsc96gexkspk1.jpg
1138 ms
vjo1s3y5m83h1udrkbtg7j1e1wk18jdc.png
1139 ms
t2rhgua4dbygint7mvaiegrq60ybk0xj.jpg
1001 ms
ntlsd819j7ih83r97i1uytdn6x14p6rt.jpg
1126 ms
yv6j1t9rj93rzvi43yf81db12poi95p8.jpg
1128 ms
uhb1gxynqe6kc6ccbjcijv7zq7297syx.png
1272 ms
ph3lbpj2cvsg0s7dalv9ioblo2wcirn0.png
1143 ms
5jbmgs7vp01okrl3v2d8kjb1qyzyng2c.png
1267 ms
t5acumb6nkbivlovo0uighmvrwxxibvd.png
1409 ms
25ggado0iq0qgk4x1otkjf1y65z2bq7s.png
1276 ms
bzuncun3rezv6by075sxkbcrom25zsry.jpg
1417 ms
t8db4dmt7hawqbwpd3mym3r27xtkr2xb.jpg
1155 ms
znym5xo267jwxfnq751b5ckglx9w9nkp.jpg
1134 ms
g8geegt19s7t5nk5arbf3pzfh0tz8gx1.jpg
1010 ms
3np00e3zwnc2gkb0zr9wzy14zrcec9ny.jpg
1011 ms
gjqrebqwezx4ibosxzn198hzcnlddqml.jpg
1018 ms
glqdydkar96052ip9es3wwnoh1h9md1w.png
1272 ms
yrlciljc7hgggdg84bjg0bzltfvqczk1.jpg
1133 ms
wzz5a5dehr2fk0zvxonrtb79is4fb43k.jpg
1010 ms
ne855yllhed81cr93nq2p1hrrp7vfpa4.jpg
1012 ms
vengglb9snyj4g0l8o1uxhh1yq0vbbu0.jpg
1148 ms
Roboto-Regular.ttf
1142 ms
iovrkj3olqc08zcu168dy0mtuiwoou7a.jpg
1133 ms
lb28gjskij5k3mvn628oxdc6ed85nnzx.jpg
1004 ms
eidek02io5hfx60hdc9bbp2u0auzqkma.jpg
1043 ms
q85vq7g2y4ik2dg4e15ney1lblmvly1e.jpg
1142 ms
n2zxjur8mdkg61n36g6uqb9c1s3h7w2s.jpg
1119 ms
138u6lamcpewz69q17zxjj2g1hqpk4zd.jpg
1110 ms
hf4zf7hjvw6ugrr6vhaldah04h31day1.jpg
1118 ms
ba.js
282 ms
code.js
773 ms
tag.js
884 ms
gtm.js
50 ms
ope2b48bpy81uvzq8h7ns3deut50ho2k.jpg
1034 ms
0y0iwm9wrpb3ydz1un0ldrm1myfc62um.jpg
1133 ms
r2o3n9nuaxgjuu36qqaek5isxm4qs2fo.jpg
1144 ms
nqivwhct7iojkq0znoqbam0e2cvig9hq.jpg
1131 ms
pq7r1lqdjwhrhd26yafz27elylorgagc.jpg
1134 ms
uve8dwsjcsz7umnse6ygf3vwjklc135o.jpg
1136 ms
uou4i69fclpddk4b7xg4iqqurd2ujf4z.jpg
994 ms
iqsc6gujp0oop35ixf3pbz2s0cugacfo.jpg
1093 ms
bx_stat
189 ms
mgrnerrpnmg0l6i12fad9xxj5ajfw9hj.jpg
989 ms
recedeviryushiy_czestit.jpg
988 ms
play.png
980 ms
0-_1_.jpg
983 ms
0-_2_.jpg
991 ms
screenshot_68_1_.jpg
964 ms
screenshot_at_mar_15_17_34_28.jpg
982 ms
home_video_bg.jpg
980 ms
screenshot_42_1_.jpg
972 ms
snimok_ekrana_ot_2020_12_04_15_18_43.jpg
853 ms
snimok_ekrana_ot_2020_12_04_15_22_44.jpg
865 ms
snimok_ekrana_ot_2020_12_04_15_24_50.jpg
958 ms
snimok_ekrana_ot_2020_12_04_15_23_31.jpg
980 ms
snimok_ekrana_ot_2020_12_04_15_24_14.jpg
980 ms
snimok_ekrana_ot_2020_12_04_15_17_09.jpg
972 ms
logo-footer.png
853 ms
spoiler.svg
865 ms
subscribe-title.png
949 ms
sync-loader.js
795 ms
counter
140 ms
dyn-goal-config.js
256 ms
leave-modal-1.jpg
848 ms
leave-modal-2.jpg
846 ms
sprite-menu.png
845 ms
star-active.svg
808 ms
rpj-icon.svg
824 ms
advert.gif
559 ms
sprite_st.png
851 ms
star.svg
848 ms
star-st1.png
844 ms
subscribe-button.svg
840 ms
1
143 ms
tracker
129 ms
uro-info.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
Links do not have a discernible name
uro-info.ru best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
uro-info.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
RU
RU
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Uro-info.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 Uro-info.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.
uro-info.ru
Open Graph description is not detected on the main page of Uro Info. 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: