13.6 sec in total
1.1 sec
11.1 sec
1.4 sec
Click here to check amazing N Tower content for Russia. Otherwise, check out these important facts you probably never knew about n-tower.ru
Аренда престижного офиса класса А в деловом центре Москвы. Аренда лучшего офиса от собственника. Аренда офисов и помещений с отделкой в БЦ Северная Башня, ММДЦ Москва-Сити
Visit n-tower.ruWe analyzed N-tower.ru page load time and found that the first response time was 1.1 sec and then it took 12.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
n-tower.ru performance score
name
value
score
weighting
Value6.7 s
2/100
10%
Value9.1 s
1/100
25%
Value16.9 s
0/100
10%
Value300 ms
78/100
30%
Value0.044
99/100
15%
Value22.7 s
1/100
10%
1079 ms
1242 ms
279 ms
2069 ms
1106 ms
Our browser made a total of 134 requests to load all elements on the main page. We found that 94% of them (126 requests) were addressed to the original N-tower.ru, 1% (2 requests) were made to Google-analytics.com and 1% (1 request) were made to Mc.yandex.ru. The less responsive or slowest element that took the longest time to load (7.9 sec) relates to the external source Mod.calltouch.ru.
Page size can be reduced by 586.6 kB (7%)
8.8 MB
8.2 MB
In fact, the total size of N-tower.ru main page is 8.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. 70% of websites need less resources to load. Images take 8.4 MB which makes up the majority of the site volume.
Potential reduce by 41.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 10.3 kB, which is 20% 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 41.9 kB or 80% of the original size.
Potential reduce by 276.7 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. N Tower images are well optimized though.
Potential reduce by 36.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 36.6 kB or 45% of the original size.
Potential reduce by 231.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. N-tower.ru needs all CSS files to be minified and compressed as it can save up to 231.3 kB or 87% of the original size.
Number of requests can be reduced by 17 (13%)
132
115
The browser has sent 132 CSS, Javascripts, AJAX and image requests in order to completely render the main page of N Tower. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
n-tower.ru
1079 ms
kernel.css
1242 ms
template_dd52bace84111eb447470452088932ff_48716ba921f86f907bc9b86e773ae9f8.css
279 ms
kernel.js
2069 ms
jquery-1.9.1.js
1106 ms
jquery.colorbox-min.js
415 ms
tower.js
548 ms
jquery.scrollTo.2.12.min.js
415 ms
jquery.mCustomScrollbar.min.js
829 ms
js.js
690 ms
normalize.css
686 ms
fonts.css
824 ms
jquery.mCustomScrollbar.css
829 ms
styles.css
1378 ms
font-awesome.min.css
1105 ms
watch.js
1 ms
conversion.js
75 ms
layer-sect01-03-4.png
1007 ms
sect03-gr-bw.jpg
415 ms
sect03-gr-col.jpg
554 ms
sect03-ukr-bw.jpg
276 ms
sect03-ukr-col.jpg
139 ms
sect03-slv-bw.jpg
554 ms
sect03-slv-col.jpg
277 ms
sect03-prv-bw.jpg
551 ms
sect03-prv-col.jpg
415 ms
sect05-rf.png
553 ms
logo.png
554 ms
0c44e962255e9fa9cbe263c78a943a9b.png
690 ms
Biokad.png
830 ms
Untitled-1.png
691 ms
aresbank_-_log.png
691 ms
%D0%A1%D1%82%D1%80%D0%BE%D0%B9%D1%82%D1%80%D0%B0%D0%BD%D1%81%D0%B3%D0%B0%D0%B7.png
692 ms
LOGO%20COLOR%20RUS.png
827 ms
CMED_logo_BW.png
829 ms
KTO%20logo.png
830 ms
ntower01.jpg
1936 ms
3.jpg
1930 ms
2.jpg
2489 ms
4.jpg
1934 ms
8.jpg
1105 ms
7.jpg
1418 ms
9.jpg
1383 ms
1.jpg
1659 ms
5.jpg
1833 ms
6.jpg
1800 ms
DSC_6568.jpg
1939 ms
DSC_6573.jpg
2108 ms
2.jpg
2204 ms
DSC_6454.jpg
2210 ms
sect08-logo1.png
2072 ms
sect08-logo2.png
2076 ms
analytics.js
120 ms
146 ms
sect09-tp1.png
2097 ms
collect
12 ms
d_client.js
7910 ms
regular.woff
2079 ms
js
58 ms
29 ms
italic.woff
1974 ms
medital.woff
2068 ms
medium.woff
1942 ms
bold.woff
1941 ms
light.woff
1808 ms
fontawesome-webfont.woff
1991 ms
sect09-tp1-act.png
1931 ms
sect09-tp2.png
1937 ms
sect09-tp2-act.png
1937 ms
sect09-tp3.png
1805 ms
sect09-tp3-act.png
1931 ms
sect09-tp4.png
1936 ms
sect09-tp4-act.png
1937 ms
sect11-map2.png
2079 ms
logo.png
1804 ms
menu-bg.png
1851 ms
menu-bg-feedback.png
1929 ms
menu-bg-about.png
1761 ms
menu-active-left.png
1661 ms
menu-active-right.png
1387 ms
menu-bg-feedback-left.png
1399 ms
lang.png
1238 ms
layer-sect01-04.jpg
1244 ms
layer-sect01-03-3.jpg
1212 ms
layer-sect01-03-2.jpg
981 ms
layer-sect01-03-1.jpg
1163 ms
layer-sect01-01.png
1102 ms
layer-sect01-02.png
1386 ms
scroll-next-white.png
974 ms
scroll-next-gold.png
1097 ms
layer-sect02-01.png
1073 ms
layer-sect02-03.png
2095 ms
layer-sect02-02.png
1396 ms
layer-sect02-02-1.jpg
1579 ms
layer-sect03-03.png
1093 ms
layer-sect03-02.jpg
1348 ms
layer-sect03-01.jpg
1663 ms
sect03-bubble.png
1113 ms
plus.png
1249 ms
sect03-arr.png
1369 ms
layer-sect04-02.png
1263 ms
layer-sect04-01.png
1398 ms
layer-sect04-01-1.jpg
1574 ms
layer-sect05-01.png
1396 ms
layer-sect06-01.png
1435 ms
layer-sect05-02.png
1480 ms
sect05-tower.png
1546 ms
layer-sect06-02.png
1442 ms
layer-sect07-01.gif
1524 ms
layer-sect08-01.png
1535 ms
question.png
1523 ms
sect07-grad.jpg
1448 ms
layer-sect08-img.jpg
1806 ms
sect08-submenu.png
1539 ms
layer-sect09-02-1.png
1536 ms
layer-sect09-02.jpg
1661 ms
sect09-menu-act.png
1449 ms
layer-sect09-01.png
1533 ms
layer-sect10-01.png
1537 ms
layer-sect10-02.png
1411 ms
layer-sect10-02-1.jpg
1441 ms
sect10-arr-t.png
1533 ms
sect10-dots.png
1538 ms
sect10-arr-l.png
1490 ms
sect10-arr-r.png
1442 ms
sect10-park.png
1440 ms
layer-sect11-02.png
1396 ms
layer-sect11-01.png
1390 ms
sect11-map-bg0.png
1256 ms
sect11-bg-title.png
1124 ms
sect11-bg-send.png
1150 ms
ajax-loader-white.png
1153 ms
scroll-prev-white.png
1109 ms
scroll-prev-gold.png
1108 ms
n-tower.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
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
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.
n-tower.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
n-tower.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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise N-tower.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 N-tower.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.
n-tower.ru
Open Graph description is not detected on the main page of N Tower. 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: