5.3 sec in total
534 ms
3.7 sec
1 sec
Click here to check amazing Doc Trix content. Otherwise, check out these important facts you probably never knew about doctrix.ru
Платформа разработана на базе open source инструментов и является полноценной заменой зарубежного ПО Open Text, IBM и Microsoft
Visit doctrix.ruWe analyzed Doctrix.ru page load time and found that the first response time was 534 ms and then it took 4.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
doctrix.ru performance score
name
value
score
weighting
Value2.4 s
69/100
10%
Value6.5 s
9/100
25%
Value7.9 s
23/100
10%
Value2,810 ms
3/100
30%
Value0.52
15/100
15%
Value9.3 s
32/100
10%
534 ms
662 ms
123 ms
370 ms
366 ms
Our browser made a total of 90 requests to load all elements on the main page. We found that 96% of them (86 requests) were addressed to the original Doctrix.ru, 2% (2 requests) were made to Bitrix.info and 1% (1 request) were made to Mc.yandex.ru. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Doctrix.ru.
Page size can be reduced by 200.9 kB (23%)
879.4 kB
678.5 kB
In fact, the total size of Doctrix.ru main page is 879.4 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. 50% of websites need less resources to load. Javascripts take 372.4 kB which makes up the majority of the site volume.
Potential reduce by 86.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. This page needs HTML code to be minified as it can gain 42.7 kB, which is 42% 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 86.9 kB or 86% of the original size.
Potential reduce by 36.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. Obviously, Doc Trix needs image optimization as it can save up to 36.3 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 55.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 55.5 kB or 15% of the original size.
Potential reduce by 22.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. Doctrix.ru needs all CSS files to be minified and compressed as it can save up to 22.2 kB or 29% of the original size.
Number of requests can be reduced by 27 (31%)
86
59
The browser has sent 86 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Doc Trix. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 5 to 1 for JavaScripts and as a result speed up the page load time.
doctrix.ru
534 ms
doctrix.ru
662 ms
page_1fd205bd6cfdfe4c2ab2c8cfaba2ce19_v1.css
123 ms
template_84fdea47694ad0543651eb167fa5c92f_v1.css
370 ms
font-awesome.css
366 ms
logo_header_new.svg
445 ms
icon-phone.svg
451 ms
main_top_img_left_orange.png
533 ms
main_top_img_right.png
665 ms
core.min.js
728 ms
template_735809bd031971a92d1d7ed1ec4bf3f1_v1.js
734 ms
page_4c368201b31b0094318e71c20bf27a5d_v1.js
490 ms
ni9jf1ip3xhsn9ar6gfl1r21cnacvu44.webp
659 ms
8n9hntnkob558em4up9z84m1rok3pz8y.webp
611 ms
681c1owfpm0p954je0euuak4vod9qkkd.webp
658 ms
a15ivc7he3kw03k1fr62willkqv029eq.webp
742 ms
my1f04z9s9zgc5b5m6te36kn8ps8w95a.webp
788 ms
i1j7wbyk544an0ohby39jgfdjfwitvjg.webp
790 ms
button-icon-rocket.svg
792 ms
img_skolkovo.svg
850 ms
img_rfrit.svg
1110 ms
img_flag.svg
858 ms
fmn8ktv8585p2g2jird4c11yxzsxjr2s.png
919 ms
logo_sign.svg
925 ms
logo_s.svg
1064 ms
settings.svg
968 ms
rocket.svg
977 ms
charts_blocks2.svg
1053 ms
like.svg
1062 ms
success.svg
1097 ms
on_premise.svg
1107 ms
m1k30crwltqg1dt4m4l0lfp2folhdhez.svg
1186 ms
vg4qcs43uz728ulqvgzxf3k59z3928py.svg
1195 ms
qfk28mcf4fhq4capcpihnjg6jxs6l9tr.svg
1204 ms
wwnf5r7fp07ac9vgx8dexky97lv07057.svg
1213 ms
89dspkn2rjfhr62uh1z5n78hbgsw4a9d.svg
1223 ms
6kn6jdihen1cj795wbmmty71hl42k0z5.svg
1223 ms
vopizny416fpn3nx2vktejslis3lmbdc.png
1314 ms
leok82yfwidsa8dzgbjggbbxdd1hj48v.svg
1210 ms
28bie611cr8pxlh21srwmb6n23c19igy.svg
975 ms
n7ngng8d89lf3cefes17mqqkylwt9dfo.webp
897 ms
r3qck0cd78y9l12fy2gdhvvxaju86x70.webp
900 ms
Inter-Regular.otf
1386 ms
jpkotlz9q3y4zpkscjl0ek4q88hv9os6.webp
960 ms
kgq37pqqjnowfefkofa3m3qgxlrp6ila.webp
928 ms
584glp1iki0slkm9zkkz6o4mw91wnz8y.webp
858 ms
7jmo6j2n8n8pegk6wipset9vs17aaazy.webp
799 ms
qfhln8rjbx0whdx4tdivrzwdqyjs0vc7.webp
814 ms
zl33evmidz57yb0q6mhame7lon1txs3e.webp
924 ms
4o1p1pvzg6ugpc6vw7w8mv9th0zdas2q.webp
845 ms
ba.js
287 ms
tag.js
954 ms
956dilmo1w5au51e0765yb9c8g0s6j5a.svg
848 ms
wjcq0n4pxjbzqu5lxiz57smwy290vd1v.svg
856 ms
og3eamvyta9adrueqkvevfxhq2s8c2tp.svg
800 ms
txm4hwj6q34apo7gej6kemwdvqmchnrr.svg
943 ms
aecsyc1l1c08mmvuun78tsnxcx1ew2xw.svg
942 ms
344si8fa2c7xfd3vf8kmxiriyq3pwlh2.webp
877 ms
7niuzms4ynpw8pp60acslcdrw0l2wc76.webp
869 ms
5sgzs6yhfhp6xpnurkur670837jrf4lw.webp
817 ms
ddk8smjt3ka1kqmohjop611uqahxzca0.webp
891 ms
logo_1c.png
855 ms
logo_astra_linux.png
871 ms
bx_stat
188 ms
logo_r7_office.png
794 ms
logo_my_office.png
789 ms
2y6yi5tvixgz603yne1t3aaa8focfhva.png
859 ms
u86420qzn2ftebepml3opai4tgwpposm.svg
845 ms
6t7w5owx9r25fum7r4p5aavk77wrs056.svg
797 ms
tn2k7l0nser9lzh54yb2gkuneq0kry63.svg
814 ms
icon-arrow-right.svg
795 ms
kuhlxoobkgc8qdk8kvktcpq3szq9eo3r.svg
793 ms
2up8ylhumpltuoddawx9esf8bd8gyoqv.svg
856 ms
o0ljxkiou9j9uc823cucugxp1dn432l1.svg
861 ms
spsudw5u648qnbxkgyo0vcmefmo92818.webp
855 ms
phhq95nlsdvyeiqgph0d0fgps3vixvqe.webp
880 ms
ordkm08hxpwymgig3dhv6gh5ttkenwil.webp
804 ms
g8xl8f8909yey5j3npn7l2qr224kj1b4.webp
797 ms
e5nx12p456ny7rmmbc4j6yp8c4gbz3rd.jpg
849 ms
hr2xxaeih3kp4jtf7l6lc7wvkxp3b0qv.png
860 ms
vts33fnzfho7u1xo32u2t3pe2r4ansr2.jpg
857 ms
fwbai0k6o5m55r7w5c0boair8rxur9uy.webp
796 ms
logos_youtube.png
796 ms
icon-up.svg
794 ms
icon-close.svg
834 ms
icon_arrow_down.svg
838 ms
icon-star.svg
751 ms
section-bg-grey.png
924 ms
i107h9uketofjgc8ojt5rtpubtnq6c0c.webp
800 ms
advert.gif
569 ms
doctrix.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
Image elements do not have [alt] attributes
Links do not have a discernible name
doctrix.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
doctrix.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 Doctrix.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 Doctrix.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.
doctrix.ru
Open Graph data is detected on the main page of Doc Trix. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: