4.9 sec in total
575 ms
3.9 sec
379 ms
Visit sonar.ru now to see the best up-to-date SONAR content for Russia and also check out these interesting facts you probably never knew about sonar.ru
⚓ Компания SONAR оказывает услуги: Промеры глубин, Инженерные изыскания, Гидрография, Телеметрия, Геодезические работы, Дноуглубление, Навигация, BIM, Геотехнический мониторинг, Площадное и водолазное...
Visit sonar.ruWe analyzed Sonar.ru page load time and found that the first response time was 575 ms and then it took 4.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
sonar.ru performance score
name
value
score
weighting
Value3.8 s
26/100
10%
Value7.4 s
4/100
25%
Value7.0 s
32/100
10%
Value540 ms
54/100
30%
Value0.003
100/100
15%
Value7.1 s
51/100
10%
575 ms
683 ms
261 ms
401 ms
524 ms
Our browser made a total of 101 requests to load all elements on the main page. We found that 89% of them (90 requests) were addressed to the original Sonar.ru, 9% (9 requests) were made to Fonts.gstatic.com and 1% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Sonar.ru.
Page size can be reduced by 209.8 kB (27%)
790.5 kB
580.7 kB
In fact, the total size of Sonar.ru main page is 790.5 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. 60% of websites need less resources to load. Javascripts take 451.9 kB which makes up the majority of the site volume.
Potential reduce by 72.6 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 19.9 kB, which is 22% 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 72.6 kB or 80% of the original size.
Potential reduce by 11 B
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. SONAR images are well optimized though.
Potential reduce by 131.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 131.4 kB or 29% of the original size.
Potential reduce by 5.8 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. Sonar.ru has all CSS files already compressed.
Number of requests can be reduced by 77 (88%)
88
11
The browser has sent 88 CSS, Javascripts, AJAX and image requests in order to completely render the main page of SONAR. 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 28 to 1 for CSS and as a result speed up the page load time.
sonar.ru
575 ms
sonar.ru
683 ms
sonar.ru
261 ms
font-awesome.min.css
401 ms
flexslider.css
524 ms
owl.carousel.min.css
523 ms
owl.theme.default.min.css
531 ms
jquery.fancybox.css
538 ms
theme-elements.css
539 ms
theme-responsive.css
541 ms
print.min.css
653 ms
animate.min.css
655 ms
jquery.mCustomScrollbar.min.css
663 ms
animation_ext.css
670 ms
jquery.onoff.css
668 ms
bootstrap.min.css
809 ms
h1-normal.css
782 ms
ajax.min.css
782 ms
width-3.css
793 ms
font-1.min.css
797 ms
google_font.css
803 ms
style.min.css
911 ms
popup.min.css
912 ms
style.min.css
921 ms
styles.min.css
927 ms
template_styles.min.css
1279 ms
responsive.min.css
1013 ms
colors.min.css
1041 ms
bgcolors.min.css
1040 ms
custom.css
1051 ms
css2
35 ms
h26rzmmcubolaa63kyr23wfii8veqxm3.png
1052 ms
core.min.js
1347 ms
main.polyfill.customevent.min.js
1163 ms
dexie.bitrix.bundle.min.js
1347 ms
core_ls.min.js
1174 ms
core_fx.min.js
1179 ms
core_frame_cache.min.js
1345 ms
jquery-2.1.3.min.min.js
1448 ms
ajax.min.js
1146 ms
pageobject.min.js
1015 ms
core_window.min.js
1044 ms
jquery.actual.min.js
928 ms
browser.js
940 ms
jquery.fancybox.min.js
916 ms
jquery.easing.js
1024 ms
jquery.appear.js
1045 ms
jquery.cookie.js
933 ms
bootstrap.js
935 ms
jquery.flexslider.min.js
930 ms
owl.carousel.min.js
1038 ms
jquery.validate.min.js
1026 ms
ls.unveilhooks.min.js
933 ms
jquery.uniform.min.js
933 ms
jqModal.min.js
927 ms
jquery.autocomplete.min.js
929 ms
jquery-ui.min.js
1024 ms
detectmobilebrowser.js
1025 ms
matchMedia.min.js
932 ms
jquery.waypoints.min.js
931 ms
jquery.counterup.js
927 ms
jquery.alphanumeric.min.js
930 ms
jquery.mobile.custom.touch.min.js
937 ms
jquery.mousewheel-3.0.6.min.js
930 ms
jquery.mCustomScrollbar.min.js
931 ms
jquery.onoff.min.js
921 ms
jquery.autoresize.min.js
920 ms
lazysizes.min.js
822 ms
velocity.min.js
908 ms
scrollTabs.min.js
918 ms
general.js
885 ms
custom.js
750 ms
script.min.js
707 ms
script.min.js
724 ms
7cH1v4okm5zmbvwkAx_sfcEuiD8jvvKcPQ.woff
23 ms
7cH1v4okm5zmbvwkAx_sfcEuiD8jjPKcPQ.woff
47 ms
7cH1v4okm5zmbvwkAx_sfcEuiD8j4PKcPQ.woff
67 ms
7cH1v4okm5zmbvwkAx_sfcEuiD8jPvKcPQ.woff
68 ms
7cH1v4okm5zmbvwkAx_sfcEuiD8jvvOcPQ.woff
67 ms
7cH1v4okm5zmbvwkAx_sfcEuiD8jYPWcPQ.woff
68 ms
7cH1v4okm5zmbvwkAx_sfcEuiD8jWfWcPQ.woff
66 ms
7cH1v4okm5zmbvwkAx_sfcEuiD8jPvWcPQ.woff
65 ms
7cH1v4okm5zmbvwkAx_sfcEuiD8jF_WcPQ.woff
68 ms
script.min.js
818 ms
script.min.js
820 ms
script.min.js
791 ms
script.js
780 ms
script.min.js
791 ms
script.min.js
882 ms
jquery.inputmask.bundle.min.js
813 ms
flexslider-icon.woff
800 ms
fontawesome-webfont.woff
918 ms
9r9guzd5vqoqogkfdbarnxpv2bfil3o9.jpg
938 ms
header_icons.svg
806 ms
darkengradient.png
887 ms
content_icons.svg
828 ms
footer_icons.svg
790 ms
36rgikxlig93sz3bxjj1jt60r0kmp4oj.svg
297 ms
5j42hr2he0m24pbhssnhkpb3r8lwadgs.svg
251 ms
ba.js
281 ms
p1ufdbkvku7dycplunyiny0xzb6hx4sx.svg
142 ms
sonar.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
sonar.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
Page has valid source maps
sonar.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 Sonar.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 Sonar.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.
sonar.ru
Open Graph data is detected on the main page of SONAR. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: