Tools & Wizards About Us
ekaterinburg.hh.ru screenshot

Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 58

    Accessibility

    Visual factors better than
    that of 25% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

ekaterinburg.hh.ru

Работа в Екатеринбурге, поиск персонала и публикация вакансий - ekaterinburg.hh.ru

Page Load Speed

10.5 sec in total

First Response

1.1 sec

Resources Loaded

9 sec

Page Rendered

427 ms

ekaterinburg.hh.ru screenshot

About Website

Visit ekaterinburg.hh.ru now to see the best up-to-date Ekaterinburg Hh content for Russia and also check out these interesting facts you probably never knew about ekaterinburg.hh.ru

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

Visit ekaterinburg.hh.ru

Key Findings

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

Performance Metrics

ekaterinburg.hh.ru performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

14/100

10%

LCP (Largest Contentful Paint)

Value6.6 s

8/100

25%

SI (Speed Index)

Value15.0 s

1/100

10%

TBT (Total Blocking Time)

Value5,430 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.134

80/100

15%

TTI (Time to Interactive)

Value25.7 s

0/100

10%

Network Requests Diagram

ekaterinburg.hh.ru

1083 ms

ekaterinburg.hh.ru

2095 ms

__bloko-imports_6557fec3b728d67ceeb1bccbcc0e4e3d.css

438 ms

__globals_bb8419f853945c9bf737bac33b3aec63.css

697 ms

34830.1b9ccd758d9f1f74214c.css

583 ms

Our browser made a total of 78 requests to load all elements on the main page. We found that 14% of them (11 requests) were addressed to the original Ekaterinburg.hh.ru, 68% (53 requests) were made to I.hh.ru and 10% (8 requests) were made to Hhcdn.ru. The less responsive or slowest element that took the longest time to load (5.1 sec) relates to the external source Counter.yadro.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 750.6 kB (53%)

Content Size

1.4 MB

After Optimization

672.4 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Ekaterinburg.hh.ru main page is 1.4 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. 55% of websites need less resources to load. HTML takes 835.6 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 707.5 kB

  • Original 835.6 kB
  • After minification 834.0 kB
  • After compression 128.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 707.5 kB or 85% of the original size.

Image Optimization

-7%

Potential reduce by 40.3 kB

  • Original 564.7 kB
  • After minification 524.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. Ekaterinburg Hh images are well optimized though.

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 (62%)

Requests Now

76

After Optimization

29

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

ekaterinburg.hh.ru

ekaterinburg.hh.ru

1083 ms

ekaterinburg.hh.ru

ekaterinburg.hh.ru

2095 ms

__bloko-imports_6557fec3b728d67ceeb1bccbcc0e4e3d.css

__bloko-imports_6557fec3b728d67ceeb1bccbcc0e4e3d.css

438 ms

__globals_bb8419f853945c9bf737bac33b3aec63.css

__globals_bb8419f853945c9bf737bac33b3aec63.css

697 ms

34830.1b9ccd758d9f1f74214c.css

34830.1b9ccd758d9f1f74214c.css

583 ms

App.9f31a959686784326a16.css

App.9f31a959686784326a16.css

571 ms

20950.8e48afa89a24c8a90c8e.css

20950.8e48afa89a24c8a90c8e.css

578 ms

45842.206d33f1906497f4295b.css

45842.206d33f1906497f4295b.css

456 ms

54077.634f47adfc1ebc91b44b.css

54077.634f47adfc1ebc91b44b.css

619 ms

69950.44eb5ec435ab67261800.css

69950.44eb5ec435ab67261800.css

635 ms

77549.46bfe1c5d743b74bd4f5.css

77549.46bfe1c5d743b74bd4f5.css

742 ms

85902.811607c89bbf1e4c89ad.css

85902.811607c89bbf1e4c89ad.css

753 ms

AdvancedVacancySearch.e11f399324cb562c8a29.css

AdvancedVacancySearch.e11f399324cb562c8a29.css

737 ms

ApplicantNegotiations.a87d3dd2496454eaab59.css

ApplicantNegotiations.a87d3dd2496454eaab59.css

786 ms

ApplicantResumes.cd37c4f0dac02e83bc3b.css

ApplicantResumes.cd37c4f0dac02e83bc3b.css

804 ms

ApplicantSuitableVacancies.b0eb8116181d5752809e.css

ApplicantSuitableVacancies.b0eb8116181d5752809e.css

862 ms

EmployersCompany.b0978a96c2bdb070b773.css

EmployersCompany.b0978a96c2bdb070b773.css

902 ms

EmployersList.f675f26e3e1a6ab486f4.css

EmployersList.f675f26e3e1a6ab486f4.css

907 ms

IndexPage.283e4de07f21d8b3d54d.css

IndexPage.283e4de07f21d8b3d54d.css

938 ms

VacancyFavorite.d3526fe8c98fac87f23a.css

VacancyFavorite.d3526fe8c98fac87f23a.css

954 ms

VacancySavedSearch.72438ac2bcc3a074ed03.css

VacancySavedSearch.72438ac2bcc3a074ed03.css

970 ms

magritte.a138c5e2de1094b24517.js

magritte.a138c5e2de1094b24517.js

1474 ms

bloko.ab66f89ae34cd6708743.js

bloko.ab66f89ae34cd6708743.js

1376 ms

vendors.0b655a2b06c36ab998e1.js

vendors.0b655a2b06c36ab998e1.js

1395 ms

14825.3f58b621653375d2501f.js

14825.3f58b621653375d2501f.js

1111 ms

20950.8e48afa89a24c8a90c8e.js

20950.8e48afa89a24c8a90c8e.js

1129 ms

40604.b39be904d24b1cbf146f.js

40604.b39be904d24b1cbf146f.js

1141 ms

54077.634f47adfc1ebc91b44b.js

54077.634f47adfc1ebc91b44b.js

1289 ms

57738.d4e41b6a924f249bd05f.js

57738.d4e41b6a924f249bd05f.js

1306 ms

AdvancedVacancySearch.e11f399324cb562c8a29.js

AdvancedVacancySearch.e11f399324cb562c8a29.js

1313 ms

ApplicantNegotiations.a87d3dd2496454eaab59.js

ApplicantNegotiations.a87d3dd2496454eaab59.js

1461 ms

ApplicantResumes.cd37c4f0dac02e83bc3b.js

ApplicantResumes.cd37c4f0dac02e83bc3b.js

1492 ms

ApplicantSuitableVacancies.b0eb8116181d5752809e.js

ApplicantSuitableVacancies.b0eb8116181d5752809e.js

1489 ms

EmployersCompany.b0978a96c2bdb070b773.js

EmployersCompany.b0978a96c2bdb070b773.js

1540 ms

EmployersList.f675f26e3e1a6ab486f4.js

EmployersList.f675f26e3e1a6ab486f4.js

1561 ms

IndexPage.283e4de07f21d8b3d54d.js

IndexPage.283e4de07f21d8b3d54d.js

1766 ms

VacancyFavorite.d3526fe8c98fac87f23a.js

VacancyFavorite.d3526fe8c98fac87f23a.js

1636 ms

VacancySavedSearch.72438ac2bcc3a074ed03.js

VacancySavedSearch.72438ac2bcc3a074ed03.js

1649 ms

context.js

context.js

974 ms

runtime.c40f65ca0bfed883ce37.js

runtime.c40f65ca0bfed883ce37.js

1232 ms

appEntryPoint.59940ecb20cb072a54fa.js

appEntryPoint.59940ecb20cb072a54fa.js

1256 ms

3741911.png

3741911.png

167 ms

10314004.jpg

10314004.jpg

143 ms

hh.ru.svg

hh.ru.svg

748 ms

qr-telegram-anonymous-hhru.png

qr-telegram-anonymous-hhru.png

824 ms

10305135.jpg

10305135.jpg

165 ms

10311723.jpg

10311723.jpg

164 ms

10311707.jpg

10311707.jpg

170 ms

10313729.jpg

10313729.jpg

171 ms

10313747.jpg

10313747.jpg

172 ms

17821658.png

17821658.png

372 ms

10313738.jpg

10313738.jpg

196 ms

5756156.png

5756156.png

666 ms

6591185.jpeg

6591185.jpeg

675 ms

3914451.png

3914451.png

681 ms

6169713.png

6169713.png

684 ms

359951.png

359951.png

289 ms

5900589.png

5900589.png

328 ms

2183263.jpeg

2183263.jpeg

454 ms

3688403.png

3688403.png

509 ms

menu3x3__min_.svg

menu3x3__min_.svg

809 ms

hh.ru__min_.svg

hh.ru__min_.svg

831 ms

big-promo-1455-L__min_.jpg

big-promo-1455-L__min_.jpg

871 ms

big-promo-1455-logo__min_.svg

big-promo-1455-logo__min_.svg

887 ms

6e8ab99b8908d5d2b666.svg

6e8ab99b8908d5d2b666.svg

933 ms

messengers-hand__min_.svg

messengers-hand__min_.svg

958 ms

vk__min_.svg

vk__min_.svg

973 ms

telegram__min_.svg

telegram__min_.svg

994 ms

viber__min_.svg

viber__min_.svg

1043 ms

bd36beda10a092dd913d.svg

bd36beda10a092dd913d.svg

1034 ms

5d17e0a82dc1e383ed58.svg

5d17e0a82dc1e383ed58.svg

1161 ms

fab2946c969a09b1aebf.svg

fab2946c969a09b1aebf.svg

1107 ms

1154ab4b63b3f68e576c.svg

1154ab4b63b3f68e576c.svg

1120 ms

hit;HeadHunter

hit;HeadHunter

5064 ms

sdk.js

sdk.js

312 ms

openapi.318ba3d5a50b8d6990cb0284cb0e0963.js

openapi.318ba3d5a50b8d6990cb0284cb0e0963.js

230 ms

rtrg

rtrg

128 ms

rtrg

rtrg

252 ms

Accessibility Review

ekaterinburg.hh.ru accessibility score

58

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

<frame> or <iframe> elements do not have a title

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

ekaterinburg.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

ekaterinburg.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

    RU

  • Language Claimed

    RU

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ekaterinburg.hh.ru can be misinterpreted by Google and other search engines. Our service has detected that Russian is used on the page, and it matches the claimed language. Our system also found out that Ekaterinburg.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

ekaterinburg.hh.ru

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