4.7 sec in total
325 ms
4 sec
431 ms
Click here to check amazing Norilsk Hh content for Russia. Otherwise, check out these important facts you probably never knew about norilsk.hh.ru
norilsk.hh.ru — сервис, который помогает найти работу и подобрать персонал в Норильске более 20 лет! Создавайте резюме и откликайтесь на вакансии. Набирайте сотрудников и публикуйте вакансии.
Visit norilsk.hh.ruWe analyzed Norilsk.hh.ru page load time and found that the first response time was 325 ms and then it took 4.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
norilsk.hh.ru performance score
name
value
score
weighting
Value3.9 s
25/100
10%
Value5.5 s
19/100
25%
Value15.4 s
1/100
10%
Value7,240 ms
0/100
30%
Value0.134
80/100
15%
Value25.9 s
0/100
10%
325 ms
1450 ms
571 ms
700 ms
416 ms
Our browser made a total of 87 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Norilsk.hh.ru, 71% (62 requests) were made to I.hh.ru and 10% (9 requests) were made to Krasnoyarsk.hh.ru. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source I.hh.ru.
Page size can be reduced by 760.2 kB (69%)
1.1 MB
339.7 kB
In fact, the total size of Norilsk.hh.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. 50% of websites need less resources to load. HTML takes 866.5 kB which makes up the majority of the site volume.
Potential reduce by 747.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. 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 747.0 kB or 86% of the original size.
Potential reduce by 10.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. Norilsk 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 50 (59%)
85
35
The browser has sent 85 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Norilsk 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 19 to 1 for JavaScripts and from 21 to 1 for CSS and as a result speed up the page load time.
norilsk.hh.ru
325 ms
norilsk.hh.ru
1450 ms
__bloko-imports_5375cd9ccdaf8989a07f2dba89cbc003.css
571 ms
__globals_48eff91b74a6937e339449cca21864d4.css
700 ms
12410.9348814f2a7db63a69d4.css
416 ms
15750.de8d397a302c3530e119.css
416 ms
39018.4017d2a4daced1edf34c.css
417 ms
42159.2611b6feba1999e5e3bc.css
420 ms
45054.6db59c8b3c20343b6754.css
582 ms
51843.c96b7664df4cafdc9601.css
586 ms
80812.acbf1788ee892cd64cb1.css
591 ms
2401.5d2add566842ce4b39f6.css
590 ms
9885.4bb37b36c9da9293a9e9.css
733 ms
15543.90717bb9c68f1fd836e6.css
746 ms
18812.63450bdab5ded5b8e159.css
752 ms
20927.28e6d21a0dc15f2fc358.css
750 ms
45842.93af0f29ea9d08cde981.css
753 ms
49662.af53aa1fef60289f774c.css
861 ms
50821.442aa147c02943cf2508.css
898 ms
66176.8b6deac9bf62fc42e70a.css
909 ms
70734.83c9029dc626841532c4.css
914 ms
75195.ffae9f761b8fa83054a4.css
915 ms
76680.30c54e5437ed4a07616c.css
919 ms
magritte.53e6b9c0b2f448ca32c3.js
1165 ms
bloko.7fcc9a57bab03e5b2332.js
1480 ms
vendors.7aa73b4653c157c8396b.js
1664 ms
vendors.lux.e723a8868452694b416b.js
1495 ms
anonymousUser.46af98f2b03452743cf1.js
1247 ms
9364.cab5fd51834850cbed5c.js
1099 ms
30667.72399673ff99c9667c0b.js
1273 ms
51396.275d1c110b8e64fe8ea5.js
1337 ms
70031.8721864da19354500ec2.js
1420 ms
72811.04b373706c401b3e6485.js
1456 ms
73765.6d303e99b1f13220eda2.js
1518 ms
IndexPage.c6a8fa85f2a384545af8.js
1725 ms
VacancyResponsesAutoInvite.7e0b100e34d86cdcc47e.js
1624 ms
49808.f8271d60085c0a10ac0a.js
1646 ms
runtime.66c1547bc9a82211f184.js
1678 ms
context.js
1084 ms
appEntryPoint.d7186b6199f917cd8972.js
1280 ms
5756156.png
386 ms
10300273.jpg
387 ms
hh.ru.svg
865 ms
qr-telegram-anonymous-hhru.png
886 ms
10300029.jpg
410 ms
10299779.jpg
404 ms
10300044.png
439 ms
10300246.jpg
409 ms
10300042.jpg
410 ms
10300309.jpg
414 ms
10300126.jpg
436 ms
5856901.png
810 ms
2912804.jpeg
807 ms
2999092.jpeg
806 ms
2708417.jpeg
810 ms
2307900.jpeg
808 ms
3097020.png
551 ms
5899117.png
718 ms
6172737.jpeg
882 ms
menu3x3__min_.svg
880 ms
hh.ru__min_.svg
894 ms
bg-applicant-supernova-6__min_.jpg
922 ms
app-store-buttons__min_.svg
942 ms
6e8ab99b8908d5d2b666.svg
1004 ms
messengers-hand__min_.svg
1029 ms
vk__min_.svg
1045 ms
telegram__min_.svg
1063 ms
viber__min_.svg
1086 ms
bd36beda10a092dd913d.svg
1088 ms
5d17e0a82dc1e383ed58.svg
1164 ms
fab2946c969a09b1aebf.svg
1177 ms
5b5c8ba9ed6440da3a18.svg
1199 ms
7344ac7a1cf5cb7e360e.svg
1209 ms
2f4f55ec27a7c096cb90.svg
1234 ms
1e0cc58033e2210b2b19.svg
1254 ms
1154ab4b63b3f68e576c.svg
1335 ms
fa0e65e20dd6d5369362.svg
1341 ms
hit;HeadHunter
511 ms
sdk.js
1420 ms
vk-socialicon__min_.svg
1235 ms
ok-socialicon__min_.svg
1177 ms
dzen-socialicon__min_.svg
1124 ms
telegram-socialicon__min_.svg
1116 ms
6d11a64942b4026d05fb.svg
1140 ms
openapi.917ca96d9331f956d945e39706791fde.js
244 ms
rtrg
137 ms
rtrg
266 ms
norilsk.hh.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
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.
norilsk.hh.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
norilsk.hh.ru 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 Norilsk.hh.ru 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 Norilsk.hh.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.
norilsk.hh.ru
Open Graph data is detected on the main page of Norilsk Hh. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: