3.9 sec in total
530 ms
3 sec
365 ms
Welcome to forens-med.ru homepage info - get ready to check Forens Med best content for Russia right away, or after learning these important things about forens-med.ru
Сообщество русскоговорящих судебно-медицинских экспертов. Форум, библиотека, программы, фото, справочник организаций.
Visit forens-med.ruWe analyzed Forens-med.ru page load time and found that the first response time was 530 ms and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
forens-med.ru performance score
name
value
score
weighting
Value2.0 s
84/100
10%
Value2.0 s
97/100
25%
Value4.2 s
77/100
10%
Value450 ms
63/100
30%
Value0.093
91/100
15%
Value6.4 s
60/100
10%
530 ms
546 ms
132 ms
7 ms
12 ms
Our browser made a total of 124 requests to load all elements on the main page. We found that 10% of them (13 requests) were addressed to the original Forens-med.ru, 10% (13 requests) were made to Vk.com and 8% (10 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (969 ms) relates to the external source Share.yandex.net.
Page size can be reduced by 414.6 kB (52%)
793.7 kB
379.0 kB
In fact, the total size of Forens-med.ru main page is 793.7 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 65% of websites need less resources to load. Javascripts take 511.1 kB which makes up the majority of the site volume.
Potential reduce by 76.9 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 76.9 kB or 72% of the original size.
Potential reduce by 9.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. Forens Med images are well optimized though.
Potential reduce by 285.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 285.5 kB or 56% of the original size.
Potential reduce by 42.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. Forens-med.ru needs all CSS files to be minified and compressed as it can save up to 42.9 kB or 81% of the original size.
Number of requests can be reduced by 65 (55%)
118
53
The browser has sent 118 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Forens Med. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 51 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
forens-med.ru
530 ms
www.forens-med.ru
546 ms
st.css
132 ms
es5-shims.min.js
7 ms
share.js
12 ms
openapi.js
379 ms
top.js
259 ms
all.js
15 ms
tn_gallery_2431_429_220908.jpg
525 ms
watch.js
483 ms
sdk.js
160 ms
cycounter
279 ms
tn_gallery_9_428_80681.jpg
537 ms
tn_gallery_9_427_395.jpg
537 ms
tn_gallery_5810_426_1877004.png
679 ms
tn_gallery_2431_425_57697.jpg
584 ms
tn_gallery_5810_424_393668.jpg
585 ms
hd_left.png
135 ms
hd_center.png
277 ms
hd_right.png
286 ms
frforum.gif
284 ms
logotype.gif
285 ms
ftlg.png
297 ms
jquery.min.js
35 ms
suggest.js
33 ms
opensearch.js
38 ms
search.png
35 ms
punycode.js
5 ms
126 ms
xd_arbiter.php
160 ms
xd_arbiter.php
302 ms
upload.gif
167 ms
platform.js
95 ms
widget_community.php
433 ms
widgets.js
121 ms
ftbgd.png
163 ms
ftbc.png
165 ms
top100.js
275 ms
hit
301 ms
code.js
267 ms
frame.html
29 ms
svg.js
39 ms
frame.html
39 ms
es5-shims.min.js
13 ms
frame.js
16 ms
share.php
638 ms
fql.query
125 ms
844 ms
dk
762 ms
share_count
762 ms
share
100 ms
fql.query
153 ms
969 ms
cb=gapi.loaded_0
44 ms
cb=gapi.loaded_1
61 ms
page
159 ms
counter2
312 ms
page.php
141 ms
timeline.1b43d11859b7663a2225b885f87704a5.js
247 ms
postmessageRelay
84 ms
watch.js
260 ms
PGVGVQG1jIH.css
316 ms
_rx8naC75Dy.js
430 ms
t-KLv3gqZy0.js
446 ms
p7Z63Zqb4Op.js
524 ms
advert.gif
274 ms
rs=AGLTcCP3O_7Lv6wPM9DLZp_DouM8Z1J9hQ
34 ms
rs=AGLTcCNVayw58ATXmq5na_KkaQDUov7ewA
62 ms
rs=AGLTcCM1zGB0tce4KBfbpglG9Po-DywOAg
81 ms
api.js
163 ms
core:rpc:shindig.random:shindig.sha1.js
173 ms
2536007149-postmessagerelay.js
200 ms
counter
191 ms
top100.scn
413 ms
photo.jpg
229 ms
rs=AGLTcCM1zGB0tce4KBfbpglG9Po-DywOAg
68 ms
grlryt2bdKIyfMSOhzd1eA.woff
135 ms
d-QWLnp4didxos_6urzFtg.woff
136 ms
vxNK-E6B13CyehuDCmvQvw.woff
150 ms
syndication
186 ms
521794230931320833
232 ms
loader_nav19127_3.js
151 ms
lite.css
153 ms
lite.js
517 ms
lang3_0.js
271 ms
widget_community.css
271 ms
xdm.js
271 ms
al_community.js
297 ms
rs=AGLTcCM1zGB0tce4KBfbpglG9Po-DywOAg
29 ms
1
84 ms
3247129
85 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
28 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
57 ms
tEkLKss2_normal.jpeg
306 ms
10431696_872765832738634_2232661193666401373_n.jpg
250 ms
575435_766094670072418_745030161_n.jpg
289 ms
11760194_738061316340174_1838161667395727818_n.jpg
329 ms
10354686_10150004552801856_220367501106153455_n.jpg
365 ms
12541112_659103907562961_8487730720894332714_n.jpg
367 ms
12592406_237280726603189_7542962373613443461_n.jpg
368 ms
wL6VQj7Ab77.png
99 ms
CSXXCvknpgK.png
99 ms
KcSUDdx0EOU.jpg
268 ms
XogbMPMLOsc.jpg
399 ms
-F9w7PtgONY.jpg
401 ms
9k61yrCNkno.jpg
407 ms
qgteaz6x49o.jpg
395 ms
vL90nkbx7Us.jpg
281 ms
575TuUa8xug.jpg
408 ms
XO0S9h0UlbA.jpg
398 ms
jaCzgflLARI.jpg
273 ms
yI3MkCxQQTU.jpg
283 ms
_CYroh3_GVA.jpg
274 ms
Tred7ddr6XY.jpg
411 ms
d87Y69vbUIQ.jpg
408 ms
camera_50.png
141 ms
w_logo.png
137 ms
jot
26 ms
R9a_DtVRZgv.js
44 ms
cUDgRFxaoIk.js
44 ms
0JBr1QHp8Gi.js
41 ms
kDOzhTr2W91.js
82 ms
arrows10.png
132 ms
tracker
161 ms
forens-med.ru accessibility score
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
forens-med.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
Page has valid source maps
forens-med.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
WINDOWS-1251
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Forens-med.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 Forens-med.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.
forens-med.ru
Open Graph data is detected on the main page of Forens Med. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: