8.8 sec in total
496 ms
7.5 sec
807 ms
Welcome to otb37.ru homepage info - get ready to check Otb 37 best content for Russia right away, or after learning these important things about otb37.ru
Обучение по программам: Пожарно технический минимум (ПТМ), Охрана труда, Гражданская Оборона и Чрезвычайные Ситуации (ГО и ЧС), Повышение квалификации педагогических работников, Правила оказания перво...
Visit otb37.ruWe analyzed Otb37.ru page load time and found that the first response time was 496 ms and then it took 8.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
otb37.ru performance score
name
value
score
weighting
Value7.0 s
1/100
10%
Value48.0 s
0/100
25%
Value26.6 s
0/100
10%
Value42,680 ms
0/100
30%
Value0
100/100
15%
Value59.5 s
0/100
10%
496 ms
1004 ms
123 ms
488 ms
470 ms
Our browser made a total of 137 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Otb37.ru, 70% (96 requests) were made to Ab-dpo.ru and 5% (7 requests) were made to Yastatic.net. The less responsive or slowest element that took the longest time to load (4.8 sec) relates to the external source Ab-dpo.ru.
Page size can be reduced by 368.1 kB (33%)
1.1 MB
751.8 kB
In fact, the total size of Otb37.ru main page is 1.1 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. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. CSS take 334.1 kB which makes up the majority of the site volume.
Potential reduce by 244.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 244.9 kB or 74% of the original size.
Potential reduce by 11.5 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. Otb 37 images are well optimized though.
Potential reduce by 65.3 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 65.3 kB or 21% of the original size.
Potential reduce by 46.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. Otb37.ru needs all CSS files to be minified and compressed as it can save up to 46.4 kB or 14% of the original size.
Number of requests can be reduced by 104 (81%)
129
25
The browser has sent 129 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Otb 37. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 27 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
otb37.ru
496 ms
ab-dpo.ru
1004 ms
template_258bf0352c38e75147815ab6db64a053_v1.css
123 ms
core.js
488 ms
jquery-3.3.1.min.js
470 ms
scriptn3.js
474 ms
scriptn.js
364 ms
lazysizes.min.js
365 ms
jquery.cookie.js
380 ms
js
48 ms
ba.js
505 ms
1320848302
850 ms
header.png
293 ms
logotype.png
318 ms
h-email.png
292 ms
region.png
288 ms
phone.png
313 ms
region_.png
316 ms
menu.png
313 ms
close.png
314 ms
menu5.png
304 ms
o3ntw8ljjzv8nmppirv87pf6bjb35ick.png
454 ms
4e1f83f820a27542662eb8110d2bc83e.png
455 ms
0d851117b057e49bf940ee4c27511435.png
453 ms
804ada29f0f72be51579d5b43c0767a7.png
449 ms
4c20ea6966be41fc7f95c78c359bd50c.png
448 ms
769t3esmxwerediii5pbln969bp34mxq.png
447 ms
9a344a3624961dceb4e57c50f2d31184.png
594 ms
dff6ed07111ada7d4ada57c6571b5d84.png
596 ms
76f89c6b346f25827b4b3e4c72971442.png
604 ms
3cec1ccf93401887b0a49adba98a15c1.png
593 ms
238e489bc05d8c91e8b094306fbdaf4e.png
587 ms
897b3a164d29cc692580e4ec90fe9fe8.png
595 ms
d67ae954de15e4b57f79dedcd2ac4b02.png
623 ms
7093d2e7e7b39e7c071f06e90a228565.png
741 ms
9a9bb50a37c00dbaa02213d9ef7baa96.png
739 ms
1397356a85699f9ee01f41e867e2ad64.png
740 ms
77e42478b64280b8c7076ede9b198c80.png
738 ms
35ba0059508f47b5ab940aba19f4cc46.png
737 ms
821c1dad628763a36f1898c45323f969.png
740 ms
1efa3411b3ef8c957dfe44c37ba82e5e.png
859 ms
1602204d28176ea1d18167af1450a255.png
862 ms
16e41bd160951bc37f5a897c8acc47e4.png
855 ms
cfc6c9816e3f57ed59d2aac7043d3943.png
856 ms
be6324afcef33512dc018f1c9e8a9d7a.png
859 ms
5ad49266e107032e7886b659a1a6a0c2.png
845 ms
menu6.png
961 ms
menu8.png
724 ms
menu10.png
732 ms
menu1.png
731 ms
tag.js
1143 ms
loader_14_vsdapn.js
1751 ms
loader_3_cyp6tj.js
973 ms
openapi.js
705 ms
menu2.png
715 ms
menu3.png
713 ms
menu5.svg
934 ms
menu4.png
933 ms
n1411d2mg5x1vlu6v9mxe5wrtp1q2ib8.gif
4777 ms
tb__title.png
930 ms
a0h2pvaojj2yyclrhpbse7yfqwhw58ta.png
840 ms
iframe_api
113 ms
analytics.js
87 ms
bx_stat
208 ms
5cdc0cdbe9c4de69dffb2d170686e69e.png
780 ms
d81c03efa32c605f5232ee18d8b4d8ee.png
918 ms
60924caf5823b4d62c8cf00345bf4d9b.png
920 ms
94c482fa33e942936f8bb73f047ad5c9.png
915 ms
pefxcibdotp9liuhows8upbtapl7v3mq.png
914 ms
ea0dc32234c240429d28914ea30fdacf.png
897 ms
www-widgetapi.js
103 ms
collect
61 ms
7b7973be3e4e2f1e314c7a8e910af374.png
1106 ms
7cd7d749bebcbcf44b91bb762734fedf.png
1106 ms
33be3c104ecede269d1df016bd406b3d.png
1108 ms
f0a9053371f06a706901046576326a2d.png
1101 ms
10e3ba285e76d955991ab75405cd45f0.png
1100 ms
fe64b8adff57d1bb1def308c85af93b6.png
1100 ms
collect
46 ms
a508f2d6f5ebef38e04a04f6585bdff4.png
1074 ms
ga-audiences
111 ms
5425fd31f06a750adc9b3ac548243bc6.png
958 ms
3d6c03674a5b9eb7d3c54bf09b94965d.png
957 ms
94d4b614557323da7c3c38984204aa85.png
958 ms
9c24c292552efe037f55d4d2d6c602bd.png
960 ms
0a989f86c516e11a110f6c6cee838b5e.png
975 ms
7d76e4b6a2bfcf583fcd82964c7105fd.png
979 ms
YSText.css
159 ms
YSTextLoader.js
314 ms
badges.min.css
461 ms
desktop~embedded.css
614 ms
badges.ru.min.js
651 ms
react-with-dom.min.js
578 ms
desktop~embedded.js
587 ms
fd92db2672a5f209ba7e2b8b0f6e29ff.png
865 ms
379d3f13f9e57bb0516ab16dff38f266.png
864 ms
9a8e658d249a34ea0642b4978cdca84d.png
931 ms
f62af4329b32b23cfc1ea32756a1234b.png
976 ms
2e240b10aaca86dd0278587bcd7c3e8a.png
986 ms
arrow-right.png
977 ms
icon-zayavka.png
876 ms
rtrg
232 ms
icon-training.png
926 ms
icon-user.png
967 ms
icon-faq.png
974 ms
icon-info.png
977 ms
icon-shop.svg
970 ms
orig
789 ms
text-light.woff
160 ms
text-regular.woff
161 ms
text-medium.woff
161 ms
text-bold.woff
162 ms
icon-passport.png
830 ms
mini-social-icons.png
860 ms
dzen.png
870 ms
instagram.jpg
866 ms
ok.png
870 ms
call.tracker.js
429 ms
styles.min.css
1132 ms
script.min.js
1695 ms
polyfill.js
369 ms
x0rqf6ulk2oxtmb8oyo2zvz3ibqalo2d.png
798 ms
info.png
838 ms
gift.png
849 ms
93a65e3b61d7b64e0cbfa107ceced4ab.jpg
855 ms
6fc66007102ad0c69810c7cfe44a9373.jpg
840 ms
389b5b4c9690a336978e58f8c270c0b8.jpg
573 ms
cadesign.png
615 ms
app.js
160 ms
advert.gif
692 ms
app.bundle.min.css
342 ms
app.bundle.min.js
694 ms
call.tracker.js
149 ms
sync_cookie_image_decide
136 ms
api.js
71 ms
1
165 ms
recaptcha__en.js
52 ms
otb37.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
Image elements do not have [alt] attributes
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
otb37.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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
Issues were logged in the Issues panel in Chrome Devtools
otb37.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
Tap targets are not sized appropriately
RU
RU
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Otb37.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 Otb37.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.
otb37.ru
Open Graph description is not detected on the main page of Otb 37. 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: