22.1 sec in total
497 ms
21.1 sec
519 ms
Visit head-liner.ru now to see the best up-to-date Headliner content for Russia and also check out these interesting facts you probably never knew about head-liner.ru
Продажа квартир в многофункциональном жилом комплексе «Headliner» в деловом центре Москвы от застройщика ГК «Кортрос». Купить квартиру ЖК «Хедлайнер» недалеко от Москва-Сити.
Visit head-liner.ruWe analyzed Head-liner.ru page load time and found that the first response time was 497 ms and then it took 21.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
head-liner.ru performance score
name
value
score
weighting
Value2.1 s
82/100
10%
Value38.6 s
0/100
25%
Value30.3 s
0/100
10%
Value3,370 ms
2/100
30%
Value0.025
100/100
15%
Value38.8 s
0/100
10%
497 ms
732 ms
20012 ms
1317 ms
81 ms
Our browser made a total of 80 requests to load all elements on the main page. We found that 61% of them (49 requests) were addressed to the original Head-liner.ru, 8% (6 requests) were made to Youtube.com and 4% (3 requests) were made to App.comagic.ru. The less responsive or slowest element that took the longest time to load (20 sec) relates to the external source Smartcallback.ru.
Page size can be reduced by 115.7 kB (2%)
5.3 MB
5.1 MB
In fact, the total size of Head-liner.ru main page is 5.3 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 4.5 MB which makes up the majority of the site volume.
Potential reduce by 87.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 13.3 kB, which is 12% 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 87.0 kB or 80% of the original size.
Potential reduce by 9.2 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. Headliner images are well optimized though.
Potential reduce by 9.1 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. This website has mostly compressed JavaScripts.
Potential reduce by 10.5 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. Head-liner.ru has all CSS files already compressed.
Number of requests can be reduced by 30 (45%)
66
36
The browser has sent 66 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Headliner. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
head-liner.ru
497 ms
head-liner.ru
732 ms
SmartCallBack.js
20012 ms
cs.min.js
1317 ms
gtm.js
81 ms
winner.png
710 ms
f605a3d70bbee56eaa33406845f9bec9.jpeg
1354 ms
3df62b610488185f503bda47edac0071.jpg
1449 ms
22dfbc4103910061b4a029e4590b97ea.jpg
1575 ms
main-advantage-1.png
724 ms
main-advantage-2.png
723 ms
main-advantage-3.png
730 ms
main-advantage-4.png
830 ms
stage-1.jpg
1685 ms
infrastructure-1.png
858 ms
infrastructure-2.png
961 ms
infrastructure-3.png
987 ms
infrastructure-4.png
1093 ms
3d4705153b07525d0ea6fae2ba2dc70b.JPG
1240 ms
ec4ec79150939cd771e7bd3347340f3c.JPG
1764 ms
3d0b001ca39b587c4fddc69a11c25ab3.JPG
1370 ms
f0f4a00bd9093c439e0377b32bd34d4d.JPG
1374 ms
0c98a155defeda153bbc8b8792eaede2.JPG
1470 ms
04c95fcd446c59b62ac1e2258e79ab34.JPG
1499 ms
_5r8xZA3EHY
71 ms
kernel_main.css
1495 ms
page_6be609f27559f60827048fbb93978e51.css
1587 ms
template_5ee7603eb24394f9b6f56053477be87b.css
1602 ms
kernel_main.js
1677 ms
js
36 ms
js
60 ms
ie-11-support.js
1280 ms
init.js
1046 ms
1066 ms
template_c1c58abfec5f2b02a5aaa4a341201e33.js
1680 ms
loader.js
1071 ms
SaleImage.png
1882 ms
www-player.css
31 ms
www-embed-player.js
13 ms
base.js
93 ms
ad_status.js
269 ms
hkwQPN6l4_SNpHVtjw8vAhWItmV3wkCVMuKaKCsfQ0c.js
178 ms
embed.js
78 ms
KFOmCnqEu92Fr1Mu4mxM.woff
67 ms
KFOlCnqEu92Fr1MmEU9fBBc-.woff
75 ms
Create
124 ms
id
102 ms
GenerateIT
15 ms
124 ms
comagic.widgets.min.js
243 ms
647 ms
logo_kortros_vertical.svg
193 ms
logo_main.svg
197 ms
btn_close_black.svg
195 ms
award-2021.png
198 ms
triangle_small_red.svg
252 ms
arrow_next.svg
326 ms
checkbox_unchecked.svg
327 ms
bg.jpg
328 ms
play-icon.svg
329 ms
video-btn.svg
366 ms
vk.svg
369 ms
telegram.svg
384 ms
cg-logo-2019.svg
386 ms
logo_voskhod.svg
395 ms
ProximaNova-Semibold.woff
470 ms
RobotoSlab-Regular.woff
477 ms
Robotoslabregular.woff
499 ms
RobotoSlab-Medium.woff
478 ms
RobotoSlab-Thin.woff
478 ms
Robotoslabbold.woff
535 ms
code.js
841 ms
DSPCounter.js
971 ms
widget.js
830 ms
Robotoslabregular.ttf
173 ms
Robotoslabbold.ttf
171 ms
openapi.c340c125c61ec5745ebb2a98626e46ab.js
221 ms
rtrg
124 ms
log_event
15 ms
122 ms
head-liner.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
[aria-*] attributes do not match their roles
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
Buttons do not have an accessible name
<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
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
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
head-liner.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
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
head-liner.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
RU
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Head-liner.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 Head-liner.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.
head-liner.ru
Open Graph description is not detected on the main page of Headliner. 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: