5.5 sec in total
827 ms
4.1 sec
531 ms
Visit forens.ru now to see the best up-to-date Forens content for Russia and also check out these interesting facts you probably never knew about forens.ru
Форум сообщества русскоговорящих судебно-медицинских экспертов
Visit forens.ruWe analyzed Forens.ru page load time and found that the first response time was 827 ms and then it took 4.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
forens.ru performance score
name
value
score
weighting
Value2.6 s
64/100
10%
Value12.6 s
0/100
25%
Value10.4 s
8/100
10%
Value1,420 ms
15/100
30%
Value0.647
9/100
15%
Value11.8 s
17/100
10%
827 ms
260 ms
543 ms
397 ms
400 ms
Our browser made a total of 127 requests to load all elements on the main page. We found that 36% of them (46 requests) were addressed to the original Forens.ru, 15% (19 requests) were made to Vk.com and 9% (11 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Forens.ru.
Page size can be reduced by 825.3 kB (69%)
1.2 MB
364.2 kB
In fact, the total size of Forens.ru main page is 1.2 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. 65% of websites need less resources to load. Javascripts take 564.1 kB which makes up the majority of the site volume.
Potential reduce by 200.1 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 43.3 kB, which is 18% 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 200.1 kB or 84% of the original size.
Potential reduce by 23.2 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. Obviously, Forens needs image optimization as it can save up to 23.2 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 436.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 436.5 kB or 77% of the original size.
Potential reduce by 165.4 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.ru needs all CSS files to be minified and compressed as it can save up to 165.4 kB or 83% of the original size.
Number of requests can be reduced by 64 (53%)
120
56
The browser has sent 120 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Forens. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 38 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
forens.ru
827 ms
index.php
260 ms
index.php
543 ms
index.php
397 ms
openapi.js
400 ms
es5-shims.min.js
26 ms
share.js
40 ms
top100.jcn
419 ms
top.js
171 ms
advanced_search.png
530 ms
search_icon.png
319 ms
h_bg.png
528 ms
FRFhl.png
464 ms
FRFhm.png
437 ms
FRFhr.png
436 ms
primary_nav.png
580 ms
icon_quicknav.png
580 ms
useropts_arrow.png
581 ms
cat_minimize.png
702 ms
f_icon.png
700 ms
subforum_stem.png
726 ms
photo-thumb-334.jpg
731 ms
photo-thumb-270.jpg
730 ms
photo-thumb-278.jpg
907 ms
photo-thumb-155.jpg
908 ms
photo-thumb-9.gif
906 ms
default_large.png
907 ms
photo-thumb-1667.jpg
907 ms
photo-thumb-12.gif
1159 ms
logo.png
1052 ms
photo-thumb-352.jpg
1052 ms
photo-thumb-4036.jpg
1052 ms
photo-thumb-268.jpg
1050 ms
photo-thumb-1767.jpg
1140 ms
photo-thumb-2372.jpg
1264 ms
photo-thumb-894.jpg
1157 ms
photo-thumb-52.jpg
1157 ms
new_post.png
1224 ms
photo-thumb-216.jpg
1427 ms
tn_gallery_2431_429_220908.jpg
1263 ms
tn_gallery_9_428_80681.jpg
1290 ms
tn_gallery_9_427_395.jpg
1283 ms
tn_gallery_5810_426_1877004.png
1561 ms
tn_gallery_2431_425_57697.jpg
1424 ms
tn_gallery_5810_424_393668.jpg
1320 ms
upload.gif
168 ms
widget_like.php
290 ms
all.js
197 ms
widget_community.php
308 ms
widgets.js
1023 ms
platform.js
237 ms
watch.js
2 ms
hit
293 ms
top100.scn
135 ms
watch.js
0 ms
frame.html
78 ms
feed.png
1157 ms
es5-shims.min.js
6 ms
frame.js
46 ms
share.php
625 ms
fql.query
299 ms
dk
816 ms
share_count
829 ms
670 ms
index.php
1068 ms
289 ms
cb=gapi.loaded_0
49 ms
cb=gapi.loaded_1
92 ms
page
233 ms
ftlg.png
1140 ms
xd_arbiter.php
224 ms
xd_arbiter.php
417 ms
ftbc.png
1144 ms
loader_nav19239_3.js
212 ms
lite.css
214 ms
lite.js
430 ms
lang3_0.js
320 ms
widgets.css
320 ms
xdm.js
427 ms
al_like.js
428 ms
widget_community.css
408 ms
page.css
528 ms
al_community.js
407 ms
page.js
932 ms
hit
202 ms
postmessageRelay
235 ms
rs=AGLTcCPAqmsHN-Miy-Ef6YL7YJb1UaUfpQ
47 ms
rs=AGLTcCP9IczaT7Rf-UGgqDPBu0TrwouL5A
64 ms
rs=AGLTcCNzjnic12y3JnV5ntUK2Ky0GVxQ-g
112 ms
photo.jpg
227 ms
1077434459-postmessagerelay.js
187 ms
rpc:shindig_random.js
183 ms
rs=AGLTcCNzjnic12y3JnV5ntUK2Ky0GVxQ-g
89 ms
pJeswbKZO4XwVR0035gpgvesZW2xOQ-xsNqO47m55DA.ttf
162 ms
JcQUq3K39RZrUxrrs7pjpwLUuEpTyoUstqEm5AMlJo4.ttf
171 ms
IhuqmeHx65TaW6CiR2l0VALUuEpTyoUstqEm5AMlJo4.ttf
176 ms
like_widget.png
136 ms
rs=AGLTcCNzjnic12y3JnV5ntUK2Ky0GVxQ-g
20 ms
cb=gapi.loaded_0
34 ms
timeline.0eae788bc4fdbe9cd3e72dca3bc26358.js
27 ms
syndication
212 ms
415178000011759616
289 ms
KcSUDdx0EOU.jpg
394 ms
w_logo.png
151 ms
mono_iconset.png
148 ms
timeline.f7130f11be9c2719286897ede16853b9.light.ltr.css
9 ms
timeline.f7130f11be9c2719286897ede16853b9.light.ltr.css
11 ms
tEkLKss2_normal.jpeg
348 ms
arrows10.png
128 ms
jot
25 ms
like_box.php
211 ms
3nB4xc2_6jL.css
93 ms
DHQqLLtVOYz.css
118 ms
SRSW8M763HA.js
166 ms
4uFOsJeWEIM.js
203 ms
y97Ig99UVTs.js
157 ms
KHAtULXOQuz.js
201 ms
10431696_872765832738634_2232661193666401373_n.jpg
138 ms
575435_766094670072418_745030161_n.jpg
124 ms
11149273_1592177524357142_1535079072553731034_n.jpg
173 ms
10354686_10150004552801856_220367501106153455_n.jpg
196 ms
560325_103790473113940_479901970_n.jpg
192 ms
12049314_10206553987001727_3713766783395063699_n.jpg
193 ms
11760194_738061316340174_1838161667395727818_n.jpg
197 ms
12359970_797198443714007_1501529177982233460_n.jpg
197 ms
wL6VQj7Ab77.png
23 ms
1JLnMyDN79z.png
23 ms
forens.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
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
forens.ru best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
forens.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
Tap targets are not sized appropriately
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Forens.ru can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Forens.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.
forens.ru
Open Graph description is not detected on the main page of Forens. 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: