Tools & Wizards About Us
novouralsk.hh.ru screenshot

Report Summary

  • 6

    Performance

    Renders faster than
    21% of other websites

  • 63

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

novouralsk.hh.ru

Работа в Новоуральске, поиск персонала и публикация вакансий - novouralsk.hh.ru

Page Load Speed

5.5 sec in total

First Response

475 ms

Resources Loaded

4.6 sec

Page Rendered

480 ms

novouralsk.hh.ru screenshot

About Website

Click here to check amazing Novouralsk Hh content for Russia. Otherwise, check out these important facts you probably never knew about novouralsk.hh.ru

novouralsk.hh.ru — сервис, который помогает найти работу и подобрать персонал в Новоуральске более 20 лет! Создавайте резюме и откликайтесь на вакансии. Набирайте сотрудников и публикуйте вакансии.

Visit novouralsk.hh.ru

Key Findings

We analyzed Novouralsk.hh.ru page load time and found that the first response time was 475 ms and then it took 5.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

novouralsk.hh.ru performance score

6

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.9 s

10/100

10%

LCP (Largest Contentful Paint)

Value6.9 s

6/100

25%

SI (Speed Index)

Value19.2 s

0/100

10%

TBT (Total Blocking Time)

Value8,150 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.409

24/100

15%

TTI (Time to Interactive)

Value28.2 s

0/100

10%

Network Requests Diagram

novouralsk.hh.ru

475 ms

novouralsk.hh.ru

1546 ms

__bloko-imports_cf9c71eda381fb160e3608e7983a095c.css

1076 ms

__globals_ea22fa26c45ece5d7af9fea7306f97af.css

1347 ms

75419.6a3672d282c705caadd0.css

1231 ms

Our browser made a total of 77 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Novouralsk.hh.ru, 69% (53 requests) were made to I.hh.ru and 10% (8 requests) were made to Ekaterinburg.hh.ru. The less responsive or slowest element that took the longest time to load (2.3 sec) relates to the external source I.hh.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 638.9 kB (65%)

Content Size

985.6 kB

After Optimization

346.7 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Novouralsk.hh.ru main page is 985.6 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. HTML takes 670.0 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 562.4 kB

  • Original 670.0 kB
  • After minification 668.4 kB
  • After compression 107.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 562.4 kB or 84% of the original size.

Image Optimization

-25%

Potential reduce by 73.7 kB

  • Original 292.9 kB
  • After minification 219.2 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, Novouralsk Hh needs image optimization as it can save up to 73.7 kB or 25% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-13%

Potential reduce by 2.9 kB

  • Original 22.7 kB
  • After minification 22.7 kB
  • After compression 19.8 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.

Requests Breakdown

Number of requests can be reduced by 47 (63%)

Requests Now

75

After Optimization

28

  • Images
  • JavaScript
  • CSS

The browser has sent 75 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Novouralsk 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 23 to 1 for JavaScripts and from 18 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

novouralsk.hh.ru

novouralsk.hh.ru

475 ms

novouralsk.hh.ru

novouralsk.hh.ru

1546 ms

__bloko-imports_cf9c71eda381fb160e3608e7983a095c.css

__bloko-imports_cf9c71eda381fb160e3608e7983a095c.css

1076 ms

__globals_ea22fa26c45ece5d7af9fea7306f97af.css

__globals_ea22fa26c45ece5d7af9fea7306f97af.css

1347 ms

75419.6a3672d282c705caadd0.css

75419.6a3672d282c705caadd0.css

1231 ms

App.2676fcb06818cad254a8.css

App.2676fcb06818cad254a8.css

1220 ms

7483.36f56ba529373ef7b9b4.css

7483.36f56ba529373ef7b9b4.css

1097 ms

16127.26f078c2554d7f8e61eb.css

16127.26f078c2554d7f8e61eb.css

1510 ms

33132.8944b002c5eec0476dcc.css

33132.8944b002c5eec0476dcc.css

1390 ms

51867.a57a88bde4a38432f224.css

51867.a57a88bde4a38432f224.css

1281 ms

55243.95137fb9c597e8082c51.css

55243.95137fb9c597e8082c51.css

1402 ms

85859.f1e81e14196d20493340.css

85859.f1e81e14196d20493340.css

1411 ms

98277.dfb44cfe9dd059cf9605.css

98277.dfb44cfe9dd059cf9605.css

1463 ms

AdvancedVacancySearch.acbf705681b3dff255d7.css

AdvancedVacancySearch.acbf705681b3dff255d7.css

1514 ms

ApplicantNegotiations.89032613a01cc91bbf3e.css

ApplicantNegotiations.89032613a01cc91bbf3e.css

1556 ms

ApplicantResumes.906bbfbc41df45fcd3ef.css

ApplicantResumes.906bbfbc41df45fcd3ef.css

1587 ms

EmployersCompany.d60fadb273891d783a49.css

EmployersCompany.d60fadb273891d783a49.css

1578 ms

EmployersList.73f4bbccd44cfd42f7f9.css

EmployersList.73f4bbccd44cfd42f7f9.css

1629 ms

IndexPage.eb4921ec6b50c5c4262c.css

IndexPage.eb4921ec6b50c5c4262c.css

1696 ms

VacancySavedSearch.c5f63e0b4089fa27da75.css

VacancySavedSearch.c5f63e0b4089fa27da75.css

1677 ms

magritte.9eed4e933e75d2ad1336.js

magritte.9eed4e933e75d2ad1336.js

1996 ms

bloko.797ec3d3be2cbadaaefb.js

bloko.797ec3d3be2cbadaaefb.js

1922 ms

vendors.4ef37ac84d20efc21402.js

vendors.4ef37ac84d20efc21402.js

2053 ms

33132.8944b002c5eec0476dcc.js

33132.8944b002c5eec0476dcc.js

1813 ms

55243.95137fb9c597e8082c51.js

55243.95137fb9c597e8082c51.js

1855 ms

80871.1342534079a84fa8048c.js

80871.1342534079a84fa8048c.js

1870 ms

85859.f1e81e14196d20493340.js

85859.f1e81e14196d20493340.js

1994 ms

99586.3dbfafaebfa020929eb5.js

99586.3dbfafaebfa020929eb5.js

2028 ms

39440.4d62916280b0ccdd7c61.js

39440.4d62916280b0ccdd7c61.js

2051 ms

AdvancedVacancySearch.acbf705681b3dff255d7.js

AdvancedVacancySearch.acbf705681b3dff255d7.js

2090 ms

ApplicantNegotiations.89032613a01cc91bbf3e.js

ApplicantNegotiations.89032613a01cc91bbf3e.js

2166 ms

ApplicantResumes.906bbfbc41df45fcd3ef.js

ApplicantResumes.906bbfbc41df45fcd3ef.js

2170 ms

ApplicantSuitableVacancies.e33830ce509e2ce1adb5.js

ApplicantSuitableVacancies.e33830ce509e2ce1adb5.js

2198 ms

EmployersCompany.d60fadb273891d783a49.js

EmployersCompany.d60fadb273891d783a49.js

2222 ms

EmployersList.73f4bbccd44cfd42f7f9.js

EmployersList.73f4bbccd44cfd42f7f9.js

2219 ms

IndexPage.eb4921ec6b50c5c4262c.js

IndexPage.eb4921ec6b50c5c4262c.js

2272 ms

VacancyFavorite.5a2ff7f74e8f86a1beb1.js

VacancyFavorite.5a2ff7f74e8f86a1beb1.js

2331 ms

VacancySavedSearch.c5f63e0b4089fa27da75.js

VacancySavedSearch.c5f63e0b4089fa27da75.js

2337 ms

context.js

context.js

913 ms

runtime.2b6b7a6c810097b13d1c.js

runtime.2b6b7a6c810097b13d1c.js

1291 ms

appEntryPoint.23ddacf41f904fcf4a83.js

appEntryPoint.23ddacf41f904fcf4a83.js

1298 ms

6865266.jpeg

6865266.jpeg

853 ms

10316316.jpg

10316316.jpg

361 ms

hh.ru.svg

hh.ru.svg

683 ms

qr-telegram-anonymous-hhru.png

qr-telegram-anonymous-hhru.png

725 ms

10316531.jpg

10316531.jpg

364 ms

10316285.jpg

10316285.jpg

359 ms

10315879.jpg

10315879.jpg

363 ms

10317610.jpg

10317610.jpg

362 ms

10316725.jpg

10316725.jpg

361 ms

17872800.png

17872800.png

423 ms

17873048.png

17873048.png

437 ms

3741911.png

3741911.png

849 ms

5813929.jpeg

5813929.jpeg

850 ms

2113350.jpeg

2113350.jpeg

864 ms

6107029.png

6107029.png

870 ms

3006832.jpeg

3006832.jpeg

876 ms

2311016.jpeg

2311016.jpeg

1014 ms

6524753.png

6524753.png

1016 ms

menu3x3__min_.svg

menu3x3__min_.svg

738 ms

hh.ru__min_.svg

hh.ru__min_.svg

745 ms

bg-applicant-supernova-1__min_.jpg

bg-applicant-supernova-1__min_.jpg

838 ms

app-store-buttons__min_.svg

app-store-buttons__min_.svg

802 ms

6e8ab99b8908d5d2b666.svg

6e8ab99b8908d5d2b666.svg

796 ms

messengers-hand__min_.svg

messengers-hand__min_.svg

844 ms

vk__min_.svg

vk__min_.svg

902 ms

telegram__min_.svg

telegram__min_.svg

911 ms

viber__min_.svg

viber__min_.svg

962 ms

bd36beda10a092dd913d.svg

bd36beda10a092dd913d.svg

934 ms

5d17e0a82dc1e383ed58.svg

5d17e0a82dc1e383ed58.svg

971 ms

fab2946c969a09b1aebf.svg

fab2946c969a09b1aebf.svg

976 ms

1154ab4b63b3f68e576c.svg

1154ab4b63b3f68e576c.svg

1033 ms

hit;HeadHunter

hit;HeadHunter

577 ms

sdk.js

sdk.js

1021 ms

openapi.c340c125c61ec5745ebb2a98626e46ab.js

openapi.c340c125c61ec5745ebb2a98626e46ab.js

215 ms

rtrg

rtrg

125 ms

rtrg

rtrg

247 ms

Accessibility Review

novouralsk.hh.ru accessibility score

63

Accessibility Issues

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

High

[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

High

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

High

Some elements have a [tabindex] value greater than 0

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

novouralsk.hh.ru best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

novouralsk.hh.ru SEO score

92

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    RU

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Novouralsk.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 Novouralsk.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.

Social Sharing Optimization

novouralsk.hh.ru

Open Graph data is detected on the main page of Novouralsk Hh. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: