9.2 sec in total
555 ms
7 sec
1.7 sec
Visit eco50.ru now to see the best up-to-date ECO50 content for Russia and also check out these interesting facts you probably never knew about eco50.ru
Солнечные батареи, ветрогенераторы, контроллеры, инверторы, аккумуляторы, светодиодные светильники, светодиодные прожекторы, LED освещение, солнечные водонагреватели, генераторы, солнечные электростан...
Visit eco50.ruWe analyzed Eco50.ru page load time and found that the first response time was 555 ms and then it took 8.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
eco50.ru performance score
name
value
score
weighting
Value2.9 s
54/100
10%
Value5.5 s
19/100
25%
Value20.9 s
0/100
10%
Value25,740 ms
0/100
30%
Value0.001
100/100
15%
Value36.7 s
0/100
10%
555 ms
1385 ms
236 ms
353 ms
380 ms
Our browser made a total of 75 requests to load all elements on the main page. We found that 89% of them (67 requests) were addressed to the original Eco50.ru, 3% (2 requests) were made to Ssl.google-analytics.com and 3% (2 requests) were made to Cdn-ru.bitrix24.ru. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Eco50.ru.
Page size can be reduced by 537.9 kB (46%)
1.2 MB
636.7 kB
In fact, the total size of Eco50.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. 60% of websites need less resources to load. HTML takes 514.5 kB which makes up the majority of the site volume.
Potential reduce by 429.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. 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 429.1 kB or 83% of the original size.
Potential reduce by 49.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, ECO50 needs image optimization as it can save up to 49.3 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 35.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 35.3 kB or 32% of the original size.
Potential reduce by 24.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. Eco50.ru needs all CSS files to be minified and compressed as it can save up to 24.2 kB or 19% of the original size.
Number of requests can be reduced by 41 (65%)
63
22
The browser has sent 63 CSS, Javascripts, AJAX and image requests in order to completely render the main page of ECO50. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and from 17 to 1 for CSS and as a result speed up the page load time.
eco50.ru
555 ms
eco50.ru
1385 ms
jquery.min.js
236 ms
frontend.min.js
353 ms
jquery.fancybox.pack.js
380 ms
flexdiscountFrontend.min.js
384 ms
jquery.countdownTimer.min.js
395 ms
frontend.min.js
399 ms
jquery.cookie.js
398 ms
frontend.bundle.js
583 ms
buy1click.js
495 ms
frontend_features.js
495 ms
frontend.min.css
513 ms
jquery.fancybox.css
519 ms
frontend.min.css
523 ms
frontend.bundle.css
615 ms
buy1click.css
617 ms
style_eco50.ru__.css
632 ms
grouped_brands.css
640 ms
frontend_features.css
646 ms
mastershop.shop.min.css
816 ms
user.css
724 ms
main.js
728 ms
main.css
751 ms
itemsetsFrontend.css
768 ms
itemsetsFrontend.js
769 ms
itemsetsFrontendLocaleOriginal.js
908 ms
ct_phone.min.js
523 ms
window.css
942 ms
window.js
945 ms
1043 ms
pay.js
763 ms
957 ms
955 ms
vendor.min.js
1034 ms
mastershop.min.js
1033 ms
mastershop.shop.min.js
950 ms
mastershop.custom.css
1034 ms
mastershop.custom.js
1032 ms
ga.js
149 ms
watch.js
59 ms
logo.png
204 ms
lazy-image.png
218 ms
188.1420x0.png
816 ms
lazy-image.png
289 ms
%D0%91%D0%B5%D0%B7%20%D0%B8%D0%BC%D0%B5%D0%BD%D0%B8-1.png
300 ms
icon_%D0%A1%D0%AD%D0%A1.jpg
306 ms
icon_%D0%BF%D0%B0%D0%BD%D0%B5%D0%BB%D0%B8.jpg
307 ms
icon_%D0%B0%D0%BA%D0%B1.jpg
333 ms
icon_%D0%B8%D0%B1%D0%BF.jpg
404 ms
icon_%D0%B8%D0%B1%D0%BF.jpg
419 ms
icon_%D0%BA%D0%BE%D0%BD%D1%82%D1%80%D0%BE%D0%BB%D0%BB%D0%B5%D1%80%D1%8B.jpg
427 ms
icon_%D0%B0%D0%BA%D0%B1%20%D0%B8%D0%B1%D0%BF.jpg
430 ms
icon_%D0%92%D0%B5%D1%82%D1%80%D0%BE%D0%B3%D0%B5%D0%BD%D0%B5%D1%80%D0%B0%D1%82%D0%BE%D1%80.jpg
446 ms
icon_%D1%81%D1%82%D0%B0%D0%B1%D0%BB.jpg
522 ms
icon_%D0%B7%D0%B0%D1%80%D1%8F%D0%B4.jpg
538 ms
icon_%D0%BE%D1%81%D0%B2%D0%B5%D1%89%D0%B5%D0%BD%D0%B8%D0%B5.jpg
548 ms
icon_%D0%BA%D0%BE%D0%BD%D0%B2%D0%B5%D1%80%D1%82%D0%B5%D1%80.jpg
553 ms
icon_%D1%84%D0%BE%D1%82%D0%BE%D0%BB%D0%BE%D0%B2%D1%83%D1%88%D0%BA%D0%B8.jpg
560 ms
montserrat-v15-latin-ext_latin_cyrillic-ext_cyrillic-regular.woff
760 ms
montserrat-v15-latin-ext_latin_cyrillic-ext_cyrillic-500.woff
760 ms
montserrat-v15-latin-ext_latin_cyrillic-ext_cyrillic-600.woff
921 ms
montserrat-v15-latin-ext_latin_cyrillic-ext_cyrillic-700.woff
782 ms
frontend.field.js
575 ms
frontend.fonts.css
705 ms
frontend.field.css
734 ms
field.css
760 ms
__utm.gif
16 ms
collect
65 ms
loader_1_a6izfj.js
725 ms
fa-solid-900.woff
484 ms
fa-regular-400.woff
1256 ms
fa-light-300.woff
1256 ms
fa-brands-400.woff
347 ms
call.tracker.js
684 ms
eco50.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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
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.
eco50.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
Browser errors were logged to the console
Page has valid source maps
eco50.ru SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
robots.txt is not valid
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 Eco50.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 Eco50.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.
eco50.ru
Open Graph data is detected on the main page of ECO50. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: