25.3 sec in total
1.1 sec
23.4 sec
827 ms
Welcome to eholot.su homepage info - get ready to check EHOLOT best content right away, or after learning these important things about eholot.su
Мы продаем эхолоты для владельцев всех типов судов.
Visit eholot.suWe analyzed Eholot.su page load time and found that the first response time was 1.1 sec and then it took 24.2 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
eholot.su performance score
name
value
score
weighting
Value2.5 s
66/100
10%
Value8.7 s
1/100
25%
Value5.5 s
54/100
10%
Value340 ms
74/100
30%
Value0.062
97/100
15%
Value6.1 s
63/100
10%
1117 ms
871 ms
439 ms
117 ms
501 ms
Our browser made a total of 82 requests to load all elements on the main page. We found that 23% of them (19 requests) were addressed to the original Eholot.su, 43% (35 requests) were made to I.siteapi.org and 10% (8 requests) were made to Img.youtube.com. The less responsive or slowest element that took the longest time to load (19.7 sec) relates to the external source I.siteapi.org.
Page size can be reduced by 386.9 kB (11%)
3.7 MB
3.3 MB
In fact, the total size of Eholot.su main page is 3.7 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. 55% of websites need less resources to load. Images take 3.2 MB which makes up the majority of the site volume.
Potential reduce by 61.2 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 61.2 kB or 79% of the original size.
Potential reduce by 33.4 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. EHOLOT images are well optimized though.
Potential reduce by 43.6 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 43.6 kB or 42% of the original size.
Potential reduce by 248.6 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. Eholot.su needs all CSS files to be minified and compressed as it can save up to 248.6 kB or 83% of the original size.
Number of requests can be reduced by 17 (23%)
74
57
The browser has sent 74 CSS, Javascripts, AJAX and image requests in order to completely render the main page of EHOLOT. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
eholot.su
1117 ms
styles-b44644b630.css
871 ms
styles-42dcca927f.css
439 ms
jquery-ui.css
117 ms
fancybox-0021db7606.css
501 ms
plugins-71827fa78d.css
590 ms
utils-7262e770f6.css
1469 ms
translate.js
673 ms
jquery.min.js
208 ms
jquery-ui.min.js
233 ms
global_libraries-3ef0d10230.js
1414 ms
site_library-b64e6223b8.js
1461 ms
global-db95a14808.js
2418 ms
grid_7-e4d3d15307.js
789 ms
css
180 ms
webfont.js
135 ms
css
35 ms
K88pR3goAWT7BTt32Z01m6CWcynf_cDxXwCLxiixG1c.ttf
206 ms
DXI1ORHCpsQm3Vp6mXoaTWeP1y_Bkidl4ESyB_O2G_c.ttf
320 ms
MTP_ySUJH_bn48VBG8sNSmeP1y_Bkidl4ESyB_O2G_c.ttf
447 ms
analytics.js
278 ms
1147410cfa90ac804b73ef89d73ae3cc5f488346.jpg
648 ms
0.jpg
677 ms
49357241.iocbvx8c9n.W665.jpg
1407 ms
2_0_FFFFFFFF_FFF5EEFF_0_pageviews
444 ms
15423273.4tzfhymje3.jpg
4801 ms
grid-7-light-sprite-5735912453.png
273 ms
8922055.cbi0opuh9n.W215.png
276 ms
play2.png
530 ms
16623513.m5jtzzrv9l.156x120.png
645 ms
0.jpg
897 ms
0.jpg
767 ms
0.jpg
844 ms
0.jpg
924 ms
0.jpg
885 ms
0.jpg
832 ms
0.jpg
871 ms
49346089.pzt9440gab.W665.png
5073 ms
e41f7d8674091102103dc87589019fd1c7910a7f.jpg
1868 ms
111bdeebe1e68004fd774ff4c7a8ad862dfdfc4d.jpg
1902 ms
abb7ffe9577939904a70b3ae1bf08990c6ab0723.png
2011 ms
b67c4c170abf7d5210902ad7f4cd09c4017d44a6.jpg
467 ms
74ed9f99b75a61b53bfe37d5370f6f017833c81a.jpg
1652 ms
55cb872d31cefe0015bf890eec76f89063a96836.jpg
1091 ms
bfc74355bd80d2c24e4da464fcc36692ad7c1610.jpg
1075 ms
723d7453a7f2852d29cce55e9731e143f728cbcf.jpg
3144 ms
d77d3a16161c054af56375ec2392edc448d52970.jpg
1467 ms
82f5a4707b8c1ed4807f6f7c97ec20568d8638f3.jpg
1875 ms
a5192779c516d213a44eac1570385be11fdb3f8a.jpg
2834 ms
ae044295e003b8ad39b19d1ef891c21807dde0bb.jpg
3719 ms
40fd9695965d6226b50b1743e2bacd3fb60cdc51.jpg
4596 ms
da57067d6e8edf1a8749baba4d4b4ffb52a879ea.jpg
3561 ms
e8445521fdb070bb22ac07c38b6f432ba87f7c6b.jpg
3213 ms
f065391d80a9ca5ac0a3b04a3060c8c7a4c077f3.png
4599 ms
f271607cd2ef932169f63acabea45263baeda7f5.jpg
3932 ms
56dd5809b80b15bc2fecfff31aed4b9c1a6aaf9f.jpg
4140 ms
447e1f39945469f051d2f0b945454bc350da0c5c.jpg
4786 ms
4e5e860de5b53f4969ce00d7cecd76f85a1a87a8.jpg
4817 ms
9f3f03b6cc8e1ae2a023bb75267a7e0726fe7844.jpg
4761 ms
45557e35a9e3f0b99f08f5f31cea62df69caa701.jpg
4759 ms
b1c9b8a00b7570cbab91b7d565cfaa2ed39adac8.jpg
6786 ms
32300a4b7f0a410a93d73458d5a7bd93a4666de6.jpg
5567 ms
07267d0e3a7007b1ec7506acc8d82080df8e3c1e.jpg
6589 ms
706ac59210dd96c2197571fa4ec2d2219e451562.jpg
5366 ms
icons.woff
341 ms
grid-7-widget-contacts-ccd6ee3c3e.png
348 ms
payment-icons-bec23d56ad.png
831 ms
watch.js
4 ms
ZeBlJHbwHO
1177 ms
http:/
40 ms
da46125ad4a4e329ceeb7ac6e0531dd5a73a5cf3.jpg
10591 ms
9bd4163c9d7d858c2b4e0ec191a0e7264f69a438.jpg
8471 ms
100a5b0f489834d0e07d7248b5081754be6f7ce0.jpg
13582 ms
c31fd4554503d1590f7cfc6435944077c1d72f2b.jpg
7713 ms
64eb0a0abe9a073fa36f22fa8f6594bcfcb297f6.jpg
9576 ms
51d85a51cc4e7adb54e74bca5b5cdbd0a111ac43.jpg
19732 ms
921ddeba22effc2eae68095a49d78f27dab841d2.jpg
9356 ms
3c16fe28a6e089c728b62513164e9ff47c9fa0f6.jpg
11927 ms
collect
130 ms
collect
272 ms
rating_4_0.jpg
540 ms
widget_ru_RU.js
1391 ms
eholot.su 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
Buttons do not have an accessible name
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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.
eholot.su 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
Missing source maps for large first-party JavaScript
eholot.su SEO score
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 Eholot.su 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 Eholot.su 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.
eholot.su
Open Graph description is not detected on the main page of EHOLOT. 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: