9 sec in total
231 ms
7.6 sec
1.1 sec
Click here to check amazing Habr A content for Israel. Otherwise, check out these important facts you probably never knew about habrahabr.ru
Visit habrahabr.ruWe analyzed Habrahabr.ru page load time and found that the first response time was 231 ms and then it took 8.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
habrahabr.ru performance score
name
value
score
weighting
Value3.7 s
30/100
10%
Value3.7 s
59/100
25%
Value10.6 s
7/100
10%
Value6,170 ms
0/100
30%
Value0.002
100/100
15%
Value20.3 s
2/100
10%
231 ms
1553 ms
66 ms
85 ms
88 ms
Our browser made a total of 116 requests to load all elements on the main page. We found that 3% of them (3 requests) were addressed to the original Habrahabr.ru, 20% (23 requests) were made to Habracdn.net and 19% (22 requests) were made to Hsto.org. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Habrahabr.ru.
Page size can be reduced by 865.6 kB (23%)
3.7 MB
2.9 MB
In fact, the total size of Habrahabr.ru main page is 3.7 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. 35% of websites need less resources to load. Images take 2.9 MB which makes up the majority of the site volume.
Potential reduce by 177.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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 177.9 kB or 85% of the original size.
Potential reduce by 239.8 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. Habr A images are well optimized though.
Potential reduce by 30.7 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 30.7 kB or 23% of the original size.
Potential reduce by 417.2 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. Habrahabr.ru needs all CSS files to be minified and compressed as it can save up to 417.2 kB or 83% of the original size.
Number of requests can be reduced by 49 (60%)
81
32
The browser has sent 81 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Habr A. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 33 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
habrahabr.ru
231 ms
habrahabr.ru
1553 ms
posts.css
66 ms
forms.css
85 ms
all.css
88 ms
global_main.css
111 ms
global_main.js
75 ms
posts.js
96 ms
jquery.form.js
108 ms
highlight.pack.js
106 ms
all.js
93 ms
all.js
97 ms
adriver.js
207 ms
advertising.js
101 ms
adcm.js
891 ms
jquery.cookie.js
98 ms
shortcuts.js
103 ms
global_footer_main.js
201 ms
autoUpdate.adriver.js
661 ms
analytics.js
117 ms
acca820d52e744c29ae3e0800ed84057.png
800 ms
logo.svg
78 ms
flags.png
309 ms
880d18b97de463569c10242636a0d0c7.jpg
769 ms
877493d580304894f45ddf1a4844de04.jpg
776 ms
8ecae129238e41248992fbc16a01e2c5.jpg
787 ms
68bee69e6c988a0b1b7fe9cf49abb6a2.png
796 ms
b632f828476b46b185d208277467bbb0.png
800 ms
046cda7c89b6fb6154d418fd5cd01a87.png
901 ms
0a697a07c50e4d148a18381356b7cc47.png
905 ms
39cb8bc649be4d13658b1c0bc2ad0339.jpg
909 ms
64f4704cb438418da4d959221a9a92f4.png
920 ms
2f69b4fd373b5fa96e986d2f254b0a7a.jpg
929 ms
7c65ea7ac975494fbf5472eb33eb33ad.jpg
974 ms
09d149d5cda89ff19b28feb8734680f1.jpg
1031 ms
d10206da2c134d759caa3642e3f20c3e.jpg
1041 ms
fd5400bd3449f01be31ca77f431c50cc.jpg
1046 ms
7226d46e03f54e2990d2b24c61d9411f.png
1064 ms
f98bda98a0d34df0c3a1b75b96aece81.jpg
1104 ms
8431628dc43a41f6b5e159f11a5534af.jpg
1152 ms
38c7abfc01699d1b676b877463efa2a6.jpg
1181 ms
2f512e40c2662b5d68cc59bcfe891f70_small.jpg
1189 ms
a5c47fcc979718f4eacdefde15ee8acf_small.png
1191 ms
e928af2fb2f01d6da7c1b450f319306f_small.png
1235 ms
hgm_icons.ttf
19 ms
gt-icons.woff
82 ms
context.js
529 ms
collect
115 ms
collect
174 ms
footer.share.png
113 ms
collect
112 ms
watch.js
105 ms
294 ms
432 ms
gt_logo.svg
73 ms
mm_logo.svg
62 ms
hh_logo.svg
58 ms
collect
75 ms
old.adriver.js
438 ms
processor.js
153 ms
context_static_r1082.js
360 ms
acca820d52e744c29ae3e0800ed84057.png
75 ms
880d18b97de463569c10242636a0d0c7.jpg
113 ms
877493d580304894f45ddf1a4844de04.jpg
95 ms
8ecae129238e41248992fbc16a01e2c5.jpg
118 ms
68bee69e6c988a0b1b7fe9cf49abb6a2.png
100 ms
b632f828476b46b185d208277467bbb0.png
102 ms
046cda7c89b6fb6154d418fd5cd01a87.png
11 ms
0a697a07c50e4d148a18381356b7cc47.png
92 ms
39cb8bc649be4d13658b1c0bc2ad0339.jpg
8 ms
64f4704cb438418da4d959221a9a92f4.png
20 ms
2f69b4fd373b5fa96e986d2f254b0a7a.jpg
14 ms
7c65ea7ac975494fbf5472eb33eb33ad.jpg
56 ms
149298
179 ms
watch.js
2 ms
09d149d5cda89ff19b28feb8734680f1.jpg
12 ms
d10206da2c134d759caa3642e3f20c3e.jpg
241 ms
fd5400bd3449f01be31ca77f431c50cc.jpg
19 ms
checkFlash.adriver.js
464 ms
functions.adriver.js
464 ms
7226d46e03f54e2990d2b24c61d9411f.png
96 ms
f98bda98a0d34df0c3a1b75b96aece81.jpg
45 ms
8431628dc43a41f6b5e159f11a5534af.jpg
131 ms
38c7abfc01699d1b676b877463efa2a6.jpg
55 ms
2f512e40c2662b5d68cc59bcfe891f70_small.jpg
47 ms
a5c47fcc979718f4eacdefde15ee8acf_small.png
46 ms
cloud4y.ru
594 ms
srs.myrusakov.ru
738 ms
e928af2fb2f01d6da7c1b450f319306f_small.png
43 ms
pixel
90 ms
pixel
22 ms
merle.cgi
360 ms
merle.cgi
386 ms
script.js
660 ms
1.html
517 ms
script.js
690 ms
1.html
527 ms
1.js
492 ms
html.adriver.js
530 ms
pixel
62 ms
Ao_6ZLGHBJQwSGPVgiQ33Fg
470 ms
adriver-sync
766 ms
Ao_6ZLGHBJQwSGPVgiQ33Fg
724 ms
pixel.adriver.js
519 ms
sync.cgi
1092 ms
sync.cgi
707 ms
index.html
484 ms
sync.cgi
867 ms
sync.cgi
328 ms
sync.cgi
763 ms
adsbygoogle.js
273 ms
ca-pub-4098002249090227.js
17 ms
zrt_lookup.html
45 ms
show_ads_impl.js
47 ms
ads
220 ms
osd.js
4 ms
habrahabr.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.
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
habrahabr.ru best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
habrahabr.ru SEO score
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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Habrahabr.ru can be misinterpreted by Google and other search engines. Our service has detected that English 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 Habrahabr.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.
habrahabr.ru
Open Graph description is not detected on the main page of Habr A. 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: