9.5 sec in total
1 sec
7.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 sec and then it took 8.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
n-tower.ru performance score
name
value
score
weighting
Value6.6 s
2/100
10%
Value9.7 s
0/100
25%
Value15.0 s
1/100
10%
Value160 ms
93/100
30%
Value0.055
98/100
15%
Value21.5 s
1/100
10%
1045 ms
1045 ms
246 ms
1676 ms
844 ms
Our browser made a total of 133 requests to load all elements on the main page. We found that 95% of them (126 requests) were addressed to the original N-tower.ru, 2% (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 (2.4 sec) belongs to the original domain N-tower.ru.
Page size can be reduced by 550.8 kB (6%)
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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 8.4 MB which makes up the majority of the site volume.
Potential reduce by 42.6 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 19% 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 42.6 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 140 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 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 16 (12%)
131
115
The browser has sent 131 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 11 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
n-tower.ru
1045 ms
kernel.css
1045 ms
template_dd52bace84111eb447470452088932ff_48716ba921f86f907bc9b86e773ae9f8.css
246 ms
kernel.js
1676 ms
jquery-1.9.1.js
844 ms
jquery.colorbox-min.js
367 ms
tower.js
583 ms
jquery.scrollTo.2.12.min.js
367 ms
jquery.mCustomScrollbar.min.js
611 ms
js.js
615 ms
normalize.css
703 ms
fonts.css
730 ms
jquery.mCustomScrollbar.css
739 ms
styles.css
1157 ms
font-awesome.min.css
968 ms
watch.js
6 ms
conversion.js
26 ms
layer-sect01-03-4.png
1034 ms
sect03-gr-bw.jpg
671 ms
sect03-gr-col.jpg
672 ms
sect03-ukr-bw.jpg
671 ms
sect03-ukr-col.jpg
671 ms
sect03-slv-bw.jpg
672 ms
sect03-slv-col.jpg
781 ms
sect03-prv-bw.jpg
897 ms
sect03-prv-col.jpg
1024 ms
sect05-rf.png
776 ms
logo.png
881 ms
0c44e962255e9fa9cbe263c78a943a9b.png
883 ms
Biokad.png
896 ms
Untitled-1.png
996 ms
aresbank_-_log.png
997 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
1022 ms
LOGO%20COLOR%20RUS.png
1022 ms
CMED_logo_BW.png
1110 ms
KTO%20logo.png
1112 ms
ntower01.jpg
1492 ms
3.jpg
1720 ms
2.jpg
2420 ms
4.jpg
1499 ms
8.jpg
1781 ms
7.jpg
1780 ms
9.jpg
1708 ms
1.jpg
1741 ms
5.jpg
1945 ms
6.jpg
1828 ms
DSC_6568.jpg
1861 ms
DSC_6573.jpg
1990 ms
2.jpg
1981 ms
DSC_6454.jpg
1932 ms
sect08-logo1.png
1971 ms
sect08-logo2.png
2189 ms
analytics.js
610 ms
646 ms
sect09-tp1.png
1582 ms
regular.woff
1578 ms
italic.woff
1577 ms
medital.woff
1577 ms
medium.woff
1577 ms
bold.woff
1576 ms
collect
37 ms
d_client.js
1326 ms
light.woff
1492 ms
70 ms
fontawesome-webfont.woff
1645 ms
sect09-tp1-act.png
1399 ms
sect09-tp2.png
1460 ms
sect09-tp2-act.png
1455 ms
sect09-tp3.png
1487 ms
sect09-tp3-act.png
1408 ms
sect09-tp4.png
1465 ms
sect09-tp4-act.png
1450 ms
sect11-map2.png
1705 ms
logo.png
1505 ms
menu-bg.png
1512 ms
menu-bg-feedback.png
1452 ms
menu-bg-about.png
1468 ms
menu-active-left.png
1098 ms
menu-active-right.png
1129 ms
menu-bg-feedback-left.png
916 ms
lang.png
939 ms
layer-sect01-04.jpg
1044 ms
layer-sect01-03-3.jpg
908 ms
layer-sect01-03-2.jpg
971 ms
layer-sect01-03-1.jpg
1024 ms
layer-sect01-01.png
901 ms
layer-sect01-02.png
971 ms
scroll-next-white.png
855 ms
scroll-next-gold.png
878 ms
layer-sect02-01.png
886 ms
layer-sect02-03.png
1272 ms
layer-sect02-02.png
1979 ms
layer-sect02-02-1.jpg
1217 ms
layer-sect03-03.png
781 ms
layer-sect03-02.jpg
1147 ms
layer-sect03-01.jpg
1067 ms
sect03-bubble.png
904 ms
plus.png
1012 ms
sect03-arr.png
1128 ms
layer-sect04-02.png
1147 ms
layer-sect04-01.png
1091 ms
layer-sect04-01-1.jpg
1280 ms
layer-sect05-01.png
1142 ms
layer-sect06-01.png
1142 ms
layer-sect05-02.png
1123 ms
sect05-tower.png
1135 ms
layer-sect06-02.png
1188 ms
layer-sect07-01.gif
1193 ms
layer-sect08-01.png
1147 ms
question.png
1151 ms
sect07-grad.jpg
1189 ms
layer-sect08-img.jpg
1484 ms
sect08-submenu.png
1192 ms
layer-sect09-02-1.png
1144 ms
layer-sect09-02.jpg
1265 ms
sect09-menu-act.png
1189 ms
layer-sect09-01.png
1191 ms
layer-sect10-01.png
1190 ms
layer-sect10-02.png
1212 ms
layer-sect10-02-1.jpg
1220 ms
sect10-arr-t.png
1219 ms
sect10-dots.png
1195 ms
sect10-arr-l.png
1221 ms
sect10-arr-r.png
1238 ms
sect10-park.png
1238 ms
layer-sect11-02.png
1201 ms
layer-sect11-01.png
1163 ms
sect11-map-bg0.png
1077 ms
sect11-bg-title.png
983 ms
sect11-bg-send.png
962 ms
ajax-loader-white.png
964 ms
scroll-prev-white.png
923 ms
scroll-prev-gold.png
938 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
Browser errors were logged to the console
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: