6.6 sec in total
445 ms
5.6 sec
508 ms
Click here to check amazing Hh content for Ukraine. Otherwise, check out these important facts you probably never knew about hh.ua
hh.ru — сервис, который помогает найти работу и подобрать персонал в Москве более 20 лет! Создавайте резюме и откликайтесь на вакансии. Набирайте сотрудников и публикуйте вакансии.
Visit hh.uaWe analyzed Hh.ua page load time and found that the first response time was 445 ms and then it took 6.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
hh.ua performance score
name
value
score
weighting
Value6.0 s
4/100
10%
Value8.4 s
2/100
25%
Value16.4 s
0/100
10%
Value8,560 ms
0/100
30%
Value0.134
80/100
15%
Value29.0 s
0/100
10%
445 ms
672 ms
1340 ms
584 ms
835 ms
Our browser made a total of 91 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Hh.ua, 70% (64 requests) were made to I.hh.ru and 11% (10 requests) were made to Hh.ru. The less responsive or slowest element that took the longest time to load (2 sec) relates to the external source I.hh.ru.
Page size can be reduced by 754.4 kB (61%)
1.2 MB
485.2 kB
In fact, the total size of Hh.ua main page is 1.2 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. HTML takes 881.6 kB which makes up the majority of the site volume.
Potential reduce by 742.2 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 742.2 kB or 84% of the original size.
Potential reduce by 9.3 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. Hh images are well optimized though.
Potential reduce by 2.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 2.9 kB or 13% of the original size.
Number of requests can be reduced by 59 (68%)
87
28
The browser has sent 87 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 24 to 1 for JavaScripts and from 28 to 1 for CSS and as a result speed up the page load time.
hh.ua
445 ms
hh.ua
672 ms
hh.ru
1340 ms
__bloko-imports_d1d4f104745781e3ef3407ea0ec1340c.css
584 ms
__globals_00f591ecdb80600d3a09a099724c79cc.css
835 ms
69891.7be3e67b4385d70345d2.css
1109 ms
616.7b8cc0f8f2265f97e63e.css
434 ms
9861.8b2aab93fe4d30e77367.css
417 ms
11191.985db97ca7291768e7bb.css
704 ms
11433.965e702944f6ac3da6f2.css
591 ms
12561.401b0ec3d2ab332f923b.css
615 ms
13570.71e317449534ffe69e46.css
748 ms
18812.656894dbda357325d3a6.css
750 ms
20927.8eb816d644a7ba99385b.css
979 ms
40180.50acc8f8f44a25404c30.css
868 ms
45842.910924c1d2f3931c9091.css
1063 ms
49036.c2919a8d5bd92bd83013.css
913 ms
49662.32036b86e63388164a12.css
997 ms
52775.3d793c5b3f23a9924036.css
1046 ms
69950.94df90eebd7ca0f28b11.css
1234 ms
75195.9b56183c3aacf80ebfc4.css
1175 ms
75825.3459e2be7b5a849ff5cd.css
1163 ms
78357.23db1613a5d91c76567c.css
1211 ms
86457.9bb61ed407c70b89a9b7.css
1227 ms
86503.4ac40749ee1320bdd85f.css
1268 ms
87490.61ad647208b8e888b401.css
1336 ms
88634.37f3c60c9632c4f07993.css
1356 ms
92382.5af37aac728f883217de.css
1377 ms
98570.439abfe6a2659aa7aacb.css
1391 ms
98855.635031b8ce150f95ab49.css
1394 ms
99316.165172c739310c2888b2.css
1457 ms
magritte.a006c3878c34e3776a53.js
1590 ms
bloko.4598a77445302e72891e.js
1880 ms
vendors.5024afe2310f6a5d8c89.js
1896 ms
vendors.lux.1480ad09483f5a7b6e25.js
1975 ms
anonymousUser.60839041a7b11a14480f.js
1591 ms
45766.46cf2e1d6aca80901c40.js
1624 ms
48953.0f1c7072420f36dea809.js
1785 ms
70031.9dbb9fecc35d558af2f1.js
1784 ms
context.js
1059 ms
77957.12a63e507fbce6b67531.js
1386 ms
85988.44b22cff2165e485c474.js
1545 ms
80519.dc9076d225a4991bcb56.js
1371 ms
ApplicantNegotiations.b7e5c24897bb99292f8f.js
1379 ms
ApplicantResumes.59d8357d6547aecca4a5.js
1456 ms
ApplicantSuitableVacancies.4fbf40e1479edb88e823.js
1359 ms
EmployersCompany.c7a5ae622b1ade29d3f8.js
1383 ms
EmployersList.d9e13de073e75037fb93.js
1384 ms
IndexPage.515451c28b5bad954a7f.js
1322 ms
VacancyFavorite.83392c4f0c1267f64258.js
1284 ms
VacancySavedSearch.382acb9d7271cf02ecb8.js
1341 ms
runtime.28c2a5fc23e950deb5bb.js
1273 ms
appEntryPoint.8975f24aafd0632a7f44.js
1303 ms
3968175.jpeg
166 ms
10304378.jpg
368 ms
hh.ru.svg
805 ms
qr-telegram-anonymous-hhru.png
824 ms
10310077.jpg
407 ms
10308915.jpg
401 ms
10309272.jpg
400 ms
10310910.jpg
407 ms
10309462.jpg
407 ms
17765404.jpg
478 ms
10310155.jpg
424 ms
6694610.jpeg
243 ms
6178209.png
296 ms
6273034.png
296 ms
6302874.jpeg
295 ms
5922045.jpeg
295 ms
6002761.jpeg
328 ms
2217771.jpeg
413 ms
3212532.png
457 ms
menu3x3__min_.svg
814 ms
hh.ru__min_.svg
900 ms
bg-applicant-supernova-4__min_.jpg
940 ms
app-store-buttons__min_.svg
928 ms
6e8ab99b8908d5d2b666.svg
938 ms
messengers-hand__min_.svg
945 ms
vk__min_.svg
976 ms
telegram__min_.svg
1081 ms
viber__min_.svg
1092 ms
bd36beda10a092dd913d.svg
1068 ms
5d17e0a82dc1e383ed58.svg
1084 ms
fab2946c969a09b1aebf.svg
1081 ms
1154ab4b63b3f68e576c.svg
1110 ms
hit;HeadHunter
521 ms
sdk.js
1904 ms
hit;HeadHunter
125 ms
openapi.a2ed73393cad04481c1dfb3f7794921f.js
278 ms
rtrg
149 ms
rtrg
296 ms
hh.ua 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
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.ua 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
hh.ua 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
EN
RU
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hh.ua can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Russian language. Our system also found out that Hh.ua 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.ua
Open Graph data is detected on the main page of Hh. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: