5.3 sec in total
519 ms
4.5 sec
343 ms
Welcome to 220pro.ru homepage info - get ready to check 220 PRO best content for Russia right away, or after learning these important things about 220pro.ru
Интернет-магазин 220.PRO собрал в одном on-line каталоге все, что может понадобиться специалистам для монтажа и обслуживания электрических систем жилых, общественных и промышленных зданий. Мы не прост...
Visit 220pro.ruWe analyzed 220pro.ru page load time and found that the first response time was 519 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.
220pro.ru performance score
name
value
score
weighting
Value4.1 s
22/100
10%
Value13.7 s
0/100
25%
Value8.0 s
22/100
10%
Value670 ms
44/100
30%
Value0.086
93/100
15%
Value12.7 s
13/100
10%
519 ms
744 ms
265 ms
398 ms
530 ms
Our browser made a total of 77 requests to load all elements on the main page. We found that 86% of them (66 requests) were addressed to the original 220pro.ru, 3% (2 requests) were made to Google-analytics.com and 3% (2 requests) were made to Counter.yadro.ru. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain 220pro.ru.
Page size can be reduced by 540.5 kB (19%)
2.8 MB
2.2 MB
In fact, the total size of 220pro.ru main page is 2.8 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. 50% of websites need less resources to load. Images take 2.5 MB which makes up the majority of the site volume.
Potential reduce by 100.0 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 57.4 kB, which is 51% 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 100.0 kB or 89% of the original size.
Potential reduce by 370.0 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, 220 PRO needs image optimization as it can save up to 370.0 kB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 250 B
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. This website has mostly compressed JavaScripts.
Potential reduce by 70.3 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. 220pro.ru needs all CSS files to be minified and compressed as it can save up to 70.3 kB or 83% of the original size.
Number of requests can be reduced by 30 (41%)
73
43
The browser has sent 73 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 220 PRO. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
220pro.ru
519 ms
220pro.ru
744 ms
all.css
265 ms
default.css
398 ms
jquery.ui.theme.css
530 ms
jquery.ui.slider.css
397 ms
jquery.js
663 ms
jquery.fancybox-1.3.4.pack.js
531 ms
jquery.fancybox-1.3.4.css
398 ms
ctrlnavigate.js
531 ms
Autolinker.js
661 ms
jquery-ui.min.js
531 ms
ajax_cart.js
659 ms
baloon.js
661 ms
baloon.css
660 ms
project.js
682 ms
jquery.autocomplete-min.js
791 ms
jquery.storage.js
792 ms
callme.js
793 ms
jquery.ui.core.js
794 ms
jquery.ui.widget.js
795 ms
jquery.ui.mouse.js
796 ms
jquery.ui.slider.js
1055 ms
jquery.easing.1.3.js
921 ms
slides.min.jquery.js
922 ms
jquery.corner.js
923 ms
functions.js
973 ms
jquery.maskedinput.js
921 ms
backcall.css
1062 ms
backcall.js
1062 ms
api.js
534 ms
logo.png
149 ms
%D0%A02-1.jpg
278 ms
%D0%B0%D0%B2%D1%82%D0%BE%D0%BC%D0%B0%D1%82%D0%B8%D0%BA%D0%B01.png
724 ms
%D0%BA%D1%80%D0%B5%D0%BF%D0%B5%D0%B61.jpg
278 ms
%D0%B2%D0%B5%D0%BD%D1%82%D0%B8%D0%BB%D1%8F%D1%86%D0%B8%D1%8F1.jpg
398 ms
%D0%BA%D0%B0%D0%B1%D0%B5%D0%BB%D1%8C1.png
588 ms
BLNRA001114.185x185.jpeg
276 ms
723df6347245df347f736a8ae0362480.185x185.jpg
400 ms
774351.185x185.jpg
400 ms
ds201_2.185x185.jpg
399 ms
672222.185x185.jpg
589 ms
401071dd1f431ac461bf5296a422c429.185x185.jpg
540 ms
BLNRA001114.141x165.jpeg
587 ms
723df6347245df347f736a8ae0362480.141x165.jpg
586 ms
774351.141x165.jpg
668 ms
ds201_2.141x165.jpg
720 ms
672222.141x165.jpg
721 ms
401071dd1f431ac461bf5296a422c429.141x165.jpg
719 ms
%D0%A1%D0%BB%D0%B0%D0%B9%D0%B43.jpeg
722 ms
%D0%A1%D0%BB%D0%B0%D0%B9%D0%B41.jpeg
1066 ms
%D0%A1%D0%BB%D0%B0%D0%B9%D0%B42.jpeg
992 ms
%D0%A1%D0%BB%D0%B0%D0%B9%D0%B45.jpeg
986 ms
%D0%A1%D0%BB%D0%B0%D0%B9%D0%B44.jpeg
859 ms
%D0%BA%D0%B0%D0%B1%D0%B5%D0%BB%D1%8C.png
983 ms
%D0%B0%D0%B2%D1%82%D0%BE%D0%BC%D0%B0%D1%82%D0%B8%D0%BA%D0%B0.png
860 ms
%D0%BE%D1%81%D0%B2%D0%B5%D1%89%D0%B5%D0%BD%D0%B8%D0%B5.png
1390 ms
%D1%80%D0%BE%D0%B7%D0%B5%D1%82%D0%BA%D0%B8.png
996 ms
analytics.js
141 ms
mobile_ico.png
1173 ms
message.png
1173 ms
cart.png
1173 ms
hit
682 ms
220-search.svg
1118 ms
line_hr_bg.png
1149 ms
DINPro-Medium.otf
1191 ms
tag.js
980 ms
%D0%A02-1.jpg
1240 ms
loading.gif
1124 ms
caret.png
1125 ms
collect
13 ms
js
75 ms
559294b16c7d3d34dc6c01ce
645 ms
hit
134 ms
559294b16c7d3d34dc6c01ce
157 ms
advert.gif
811 ms
sync_cookie_image_decide
136 ms
220pro.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.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Form elements do not have associated labels
Links do not have a discernible name
220pro.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
220pro.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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 220pro.ru can be misinterpreted by Google and other search engines. Our service has detected that Russian is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that 220pro.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.
220pro.ru
Open Graph description is not detected on the main page of 220 PRO. 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: