3.8 sec in total
790 ms
2.7 sec
321 ms
Visit habex.ru now to see the best up-to-date Habex content for Russia and also check out these interesting facts you probably never knew about habex.ru
Газета «Хабаровский Экспресс». Электронный архив печатной версии еженедельной газеты «Хабаровский Экспресс». Флагман издательского холдинга "Гранд Экспресс". Известный общественно-политический городск...
Visit habex.ruWe analyzed Habex.ru page load time and found that the first response time was 790 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
habex.ru performance score
name
value
score
weighting
Value4.5 s
15/100
10%
Value5.8 s
15/100
25%
Value10.6 s
7/100
10%
Value3,630 ms
1/100
30%
Value0.382
27/100
15%
Value18.0 s
3/100
10%
790 ms
111 ms
217 ms
543 ms
226 ms
Our browser made a total of 55 requests to load all elements on the main page. We found that 89% of them (49 requests) were addressed to the original Habex.ru, 4% (2 requests) were made to Bitrix.info and 4% (2 requests) were made to Counter.yadro.ru. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Habex.ru.
Page size can be reduced by 395.8 kB (35%)
1.1 MB
735.7 kB
In fact, the total size of Habex.ru main page is 1.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. 25% of websites need less resources to load. Images take 616.2 kB which makes up the majority of the site volume.
Potential reduce by 23.3 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 23.3 kB or 74% of the original size.
Potential reduce by 22.9 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. Habex images are well optimized though.
Potential reduce by 292.3 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 292.3 kB or 70% of the original size.
Potential reduce by 57.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. Habex.ru needs all CSS files to be minified and compressed as it can save up to 57.2 kB or 86% of the original size.
Number of requests can be reduced by 26 (49%)
53
27
The browser has sent 53 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Habex. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and as a result speed up the page load time.
habex.ru
790 ms
kernel_main.css
111 ms
template_9f9b89212224e8484bc90b08f9aa88ab.css
217 ms
kernel_main.js
543 ms
scripts.js
226 ms
swfobject.js
225 ms
swfaddress.js
227 ms
jquery-1.4.2.min.js
356 ms
jquery.jcarousel.min.js
325 ms
bg2.jpg
118 ms
ba.js
166 ms
%D0%B4%D0%BE%D0%BC%D0%BE%D0%B2%D0%BE%D0%B9.gif
539 ms
header.gif
110 ms
logo_habex3.png
223 ms
icon1.gif
116 ms
icon2.gif
119 ms
icon3.gif
115 ms
login-hidden.png
216 ms
krestik.gif
228 ms
navibar.gif
226 ms
menu.gif
236 ms
%D0%B0%D1%8D%D1%80%D0%BE%D1%84%D0%BB%D0%BE%D1%82.gif
325 ms
%D0%BE%D0%BA%D0%B5%D0%B0%D0%BD.gif
337 ms
%D1%81%D1%83%D0%B1%D0%B1%D0%BE%D1%82%D0%BD%D0%B8%D0%BA.gif
450 ms
lekifotolia600.gif
451 ms
IMG_0785-1.gif
468 ms
%D1%85%D0%BE%D0%BA%D0%BA%D0%B5%D0%B8%D1%81%D1%82%D1%8B.gif
437 ms
01ex12---%D0%BE%D0%B1%D0%BB%D0%BE%D0%B6%D0%BA%D0%B0.png
675 ms
icon4.gif
544 ms
icon5.gif
562 ms
icon6.gif
564 ms
%D0%A1%D0%BE%D1%81%D0%BD%D0%BE%D0%B2%D1%81%D0%BA%D0%B0%D1%8F-%D0%BB%D0%B8%D0%BD%D0%B8%D1%8F-%D0%B1%D0%B0%D0%BD%D0%BD%D0%B5%D1%802.gif
704 ms
zzgstkwrem-nvot.jpg
640 ms
%D0%A1%D0%BD%D0%B5%D0%B3%D0%BE%D0%B2%D0%B8%D0%BA-%D1%84%D0%BE%D1%82%D0%BE-%D0%9C.gif
758 ms
icon7.gif
672 ms
436594.png
1245 ms
%D0%A3%D0%A4%D0%A1%D0%98%D0%9D-%D0%BB%D0%B8%D1%81%D1%82%D0%BE%D0%B2%D0%BA%D0%B0.png
749 ms
DSC00204.png
902 ms
%D0%B2%D0%B5%D1%81%D0%B5%D0%BB%D0%B0%D1%8F-%D0%BC%D0%B0%D1%81%D0%BB%D0%B5%D0%BD%D0%B8%D1%86%D0%B0.png
1020 ms
6.gif
820 ms
2.png
857 ms
6.gif
865 ms
0.png
936 ms
4.gif
963 ms
down.gif
971 ms
up.gif
1017 ms
hit
256 ms
%D0%92%D0%94%D0%92---%D0%BF%D1%80%D0%B8%D0%B5%D0%BC-%D0%BE%D0%B1%D1%8A%D1%8F%D0%B2%D0%BB%D0%B5%D0%BD%D0%B8%D0%B9-%D1%81%D0%B0%D0%B9%D1%82.png
1144 ms
ga.js
6 ms
__utm.gif
13 ms
pic13_1.jpg
973 ms
%D0%9C%D0%BE%D0%B1%D0%B8%D0%BB%D1%8C%D0%BD%D1%8B%D0%B9-%D0%A5%D0%B0%D0%B1%D0%AD%D0%BA%D1%81-%D0%B2%D0%B5%D1%80%D1%82.png
1080 ms
bg-header.gif
1021 ms
bx_stat
208 ms
hit
131 ms
habex.ru accessibility score
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
Links do not have a discernible name
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
habex.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
habex.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
Tap targets are not sized appropriately
RU
N/A
WINDOWS-1251
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Habex.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 Habex.ru main page’s claimed encoding is windows-1251. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
habex.ru
Open Graph description is not detected on the main page of Habex. 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: