10.5 sec in total
703 ms
9.6 sec
224 ms
Click here to check amazing Hh content for Kazakhstan. Otherwise, check out these important facts you probably never knew about hh.kz
hh.kz — сервис, который помогает найти работу и подобрать персонал в Казахстане! Создавайте резюме и откликайтесь на вакансии. Набирайте сотрудников и публикуйте вакансии.
Visit hh.kzWe analyzed Hh.kz page load time and found that the first response time was 703 ms and then it took 9.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
hh.kz performance score
name
value
score
weighting
Value5.0 s
10/100
10%
Value20.3 s
0/100
25%
Value12.5 s
3/100
10%
Value2,320 ms
5/100
30%
Value0.177
68/100
15%
Value19.9 s
2/100
10%
703 ms
996 ms
604 ms
131 ms
429 ms
Our browser made a total of 82 requests to load all elements on the main page. We found that 6% of them (5 requests) were addressed to the original Hh.kz, 34% (28 requests) were made to Hhcdn.ru and 18% (15 requests) were made to I.hh.kz. The less responsive or slowest element that took the longest time to load (3.6 sec) relates to the external source I.hh.kz.
Page size can be reduced by 189.0 kB (32%)
595.0 kB
406.0 kB
In fact, the total size of Hh.kz main page is 595.0 kB. 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. HTML takes 292.9 kB which makes up the majority of the site volume.
Potential reduce by 124.7 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 124.7 kB or 43% of the original size.
Potential reduce by 17.4 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. Obviously, Hh needs image optimization as it can save up to 17.4 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 46.9 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 46.9 kB or 34% of the original size.
Number of requests can be reduced by 42 (59%)
71
29
The browser has sent 71 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Hh. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 27 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
hh.kz
703 ms
hh.kz
996 ms
604 ms
revalidate
131 ms
bind
429 ms
verify
431 ms
hh.kz
1172 ms
__bloko_ae65c31001da8cbe60d5cb6178cadda8.css
1490 ms
__globals-other_4a87a3d2d7ba0e9f9b69f224eb328bc0.css
1886 ms
__globals_04a50f9e1dc905f70fdaa622450282b6.css
2130 ms
__a00ffdf4880ff702ff2dda800f23d38b.js
3551 ms
pv
555 ms
pv
564 ms
pv
565 ms
pv
568 ms
pv
498 ms
148424.png
134 ms
16380926.jpg
135 ms
16110260.png
135 ms
16335995.png
135 ms
16110262.png
134 ms
16380495.png
288 ms
16335997.png
288 ms
16380496.png
287 ms
16379537.jpg
287 ms
hh.ru-small.svg
237 ms
__fonts_daae654200c3b06443b7fc9c8b905d38.css
1125 ms
hh.kz.svg
211 ms
select.svg
208 ms
search.svg
408 ms
navi-sprite.png
401 ms
anonymous-background-kz.jpg
435 ms
social-icons.svg
565 ms
16289182.jpg
257 ms
16289184.jpg
361 ms
71318.html
353 ms
71257.html
355 ms
online.png
553 ms
store.svg
753 ms
footer-social.svg
559 ms
hit;HeadHunter
579 ms
dc.js
114 ms
pack.min.js
581 ms
beacon.js
76 ms
fbevents.js
72 ms
z.js
1324 ms
watch.js
451 ms
rtrg
575 ms
code.js
666 ms
pv
280 ms
pv
282 ms
118 ms
152 ms
inpage_linkid.js
76 ms
__utm.gif
12 ms
__utm.gif
14 ms
BannerHandler.js
667 ms
16380322.jpg
142 ms
16289185.jpg
139 ms
advert.gif
84 ms
top100.scn
549 ms
1
94 ms
counter
161 ms
pv
137 ms
pv
136 ms
IB47O6kwxfq15Ok7HjzGeN+VHrRA1enWH+sjPzE81WL0BTrnBII=
5 ms
1r3UrPcLMlYEJQ==
3 ms
57758.html
133 ms
51170.html
137 ms
context.js
453 ms
ajs.php
353 ms
ajs.php
104 ms
ajs.php
101 ms
ajs.php
98 ms
z.js
230 ms
lg.php
62 ms
pv
132 ms
lg.php
67 ms
lg.php
68 ms
z.png
238 ms
lg.php
12 ms
pv
134 ms
hh.kz 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
Image elements do not have [alt] attributes
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
[id] attributes on active, focusable elements are not unique
Heading elements are not in a sequentially-descending order
Some elements have a [tabindex] value greater than 0
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.
hh.kz best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
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
Missing source maps for large first-party JavaScript
hh.kz SEO score
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
Tap targets are not sized appropriately
RU
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hh.kz 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 Hh.kz 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.
hh.kz
Open Graph description is not detected on the main page of Hh. 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: