6.4 sec in total
887 ms
4.7 sec
864 ms
Visit 220nn.ru now to see the best up-to-date 220 Nn content for Russia and also check out these interesting facts you probably never knew about 220nn.ru
Мы занимаемся продажей, монтажом, обслуживанием, ремонтом кондиционеров и вентиляции в домах, квартирах, офисах, предприятиях Нижнего Новгорода и области.
Visit 220nn.ruWe analyzed 220nn.ru page load time and found that the first response time was 887 ms and then it took 5.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
220nn.ru performance score
name
value
score
weighting
Value6.3 s
3/100
10%
Value10.1 s
0/100
25%
Value10.3 s
8/100
10%
Value1,960 ms
8/100
30%
Value0.154
75/100
15%
Value16.1 s
6/100
10%
887 ms
229 ms
327 ms
34 ms
492 ms
Our browser made a total of 100 requests to load all elements on the main page. We found that 70% of them (70 requests) were addressed to the original 220nn.ru, 17% (17 requests) were made to Fonts.gstatic.com and 3% (3 requests) were made to Counter.megagroup.ru. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain 220nn.ru.
Page size can be reduced by 471.4 kB (23%)
2.1 MB
1.6 MB
In fact, the total size of 220nn.ru main page is 2.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. 70% of websites need less resources to load. Images take 890.1 kB which makes up the majority of the site volume.
Potential reduce by 313.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. This page needs HTML code to be minified as it can gain 150.3 kB, which is 43% 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 313.9 kB or 90% of the original size.
Potential reduce by 8.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. 220 Nn images are well optimized though.
Potential reduce by 82.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 82.6 kB or 14% of the original size.
Potential reduce by 66.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. 220nn.ru needs all CSS files to be minified and compressed as it can save up to 66.4 kB or 31% of the original size.
Number of requests can be reduced by 61 (79%)
77
16
The browser has sent 77 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 220 Nn. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 39 to 1 for JavaScripts and from 17 to 1 for CSS and as a result speed up the page load time.
220nn.ru
887 ms
jquery-ui.css
229 ms
lightgallery.css
327 ms
css
34 ms
jquery.min.js
492 ms
jquery-ui.min.js
328 ms
styles_articles_tpl.css
332 ms
lightgallery.proxy.to.hs.min.css
360 ms
lightgallery.proxy.to.hs.stub.min.js
339 ms
lightgallery.proxy.to.hs.js
435 ms
ru.js
504 ms
common.min.js
441 ms
calendar.css
450 ms
user.css
612 ms
user.green.css
543 ms
user.js
552 ms
theme.less.css
634 ms
printme.js
599 ms
tpl.js
601 ms
baron.min.js
650 ms
shop2.2.js
793 ms
lazyload.min.js
710 ms
jquery.responsivetabs.min.js
715 ms
jquery.matchHeight.min.js
721 ms
jquery.formstyler.min.js
752 ms
jquery.nouislider.all.min.js
769 ms
lightgallery.js
824 ms
jquery.bgdsize.js
823 ms
slick.min.js
861 ms
flexmenu.min.js
862 ms
s3.math.js
877 ms
s3.eventable.js
901 ms
s3.menu.allin.js
935 ms
s3.form.js
936 ms
shop_main.js
998 ms
webflow.js
1001 ms
theme.scss.css
1265 ms
62606bb2b887ee85468b464b.js
592 ms
addon_style.scss.css
908 ms
site_addons.scss.css
843 ms
advantages.scss.css
743 ms
popover_styles.scss.css
795 ms
global_styles.css
790 ms
ors_privacy.scss.css
791 ms
waslidemenu.js
835 ms
menu_side.js
746 ms
advantages.js
791 ms
ors_privacy.js
783 ms
site.min.js
742 ms
defender.min.js
794 ms
css2
18 ms
1telegram.svg
150 ms
logo_150na150.jpg
135 ms
bg.jpg
709 ms
layer_15.png
146 ms
layer_14.png
373 ms
layer_13.png
291 ms
55180243_2.jpg
1318 ms
pic.jpg
520 ms
800_400_white_664f0fd307e04.jpg
335 ms
54893965_3.jpg
945 ms
shape_523.png
479 ms
shape_563.png
483 ms
shape_524.png
629 ms
spacer.gif
593 ms
home1600_28.png
636 ms
home1600_30.png
735 ms
home1600_61.png
745 ms
home1600_63.png
754 ms
roboto_condensed-l.woff
696 ms
ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyWyovBJ731BKfyJ.ttf
122 ms
ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyWAovBJ731BKfyJ.ttf
159 ms
ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyXsovBJ731BKfyJ.ttf
182 ms
ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyUyovBJ731BKfyJ.ttf
203 ms
ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyWyo_BJ731BKfyJ.ttf
202 ms
ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyVspfBJ731BKfyJ.ttf
204 ms
ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyVVpfBJ731BKfyJ.ttf
201 ms
ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyUypfBJ731BKfyJ.ttf
203 ms
ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyUbpfBJ731BKfyJ.ttf
238 ms
roboto_condensed-b.woff
781 ms
va9B4kDNxMZdWfMOD5VnLK3uQR39fFw.ttf
204 ms
TK3_WkUHHAIjg75cFRf3bXL8LICs1y9osUJiYCSUhiCnAw.ttf
239 ms
TK3_WkUHHAIjg75cFRf3bXL8LICs1xZosUJiYCSUhiCnAw.ttf
240 ms
TK3_WkUHHAIjg75cFRf3bXL8LICs18NvsUJiYCSUhiCnAw.ttf
239 ms
TK3_WkUHHAIjg75cFRf3bXL8LICs169vsUJiYCSUhiCnAw.ttf
273 ms
roboto_condensed-r.woff
742 ms
tag.js
963 ms
hit
702 ms
loader.js
690 ms
visitor.js
1213 ms
prosto_one-r.woff
623 ms
KFOlCnqEu92Fr1MmWUlvAx0_IsE.ttf
108 ms
KFOmCnqEu92Fr1Me5WZNCzc.ttf
109 ms
KFOlCnqEu92Fr1MmSU5vAx0_IsE.ttf
110 ms
api.js
109 ms
ba432a50e5b60c8a1b924770eec2bf4b.js
110 ms
advert.gif
754 ms
c42fe10f156b4e23da1e_part.js
116 ms
d8ec5cc990cc096b6b67_part.js
115 ms
sync_cookie_image_decide
159 ms
220nn.ru accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
button, link, and menuitem elements do not have accessible names.
ARIA input fields do not have accessible names
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
Form elements do not have associated labels
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.
220nn.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
220nn.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 220nn.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 220nn.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.
220nn.ru
Open Graph description is not detected on the main page of 220 Nn. 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: