Tools & Wizards About Us
pyatigorsk.hh.ru screenshot

Report Summary

  • 2

    Performance

    Renders faster than
    20% 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

  • 91

    SEO

    Google-friendlier than
    70% of websites

pyatigorsk.hh.ru

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

Page Load Speed

6.5 sec in total

First Response

346 ms

Resources Loaded

5.5 sec

Page Rendered

719 ms

pyatigorsk.hh.ru screenshot

About Website

Welcome to pyatigorsk.hh.ru homepage info - get ready to check Pyatigorsk Hh best content for Russia right away, or after learning these important things about pyatigorsk.hh.ru

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

Visit pyatigorsk.hh.ru

Key Findings

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

Performance Metrics

pyatigorsk.hh.ru performance score

2

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.5 s

6/100

10%

LCP (Largest Contentful Paint)

Value22.2 s

0/100

25%

SI (Speed Index)

Value19.1 s

0/100

10%

TBT (Total Blocking Time)

Value6,980 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.559

12/100

15%

TTI (Time to Interactive)

Value26.1 s

0/100

10%

Network Requests Diagram

pyatigorsk.hh.ru

346 ms

pyatigorsk.hh.ru

2055 ms

__bloko-imports_cf9c71eda381fb160e3608e7983a095c.css

428 ms

__globals_347aa21a4aa0081560724f14b0604205.css

696 ms

84614.c7ba677fe4b9b8464bdb.css

566 ms

Our browser made a total of 84 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Pyatigorsk.hh.ru, 65% (55 requests) were made to I.hh.ru and 11% (9 requests) were made to Krasnodar.hh.ru. The less responsive or slowest element that took the longest time to load (2.4 sec) relates to the external source Krasnodar.hh.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.3 MB (47%)

Content Size

2.8 MB

After Optimization

1.5 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Pyatigorsk.hh.ru main page is 2.8 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. Images take 1.5 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 1.1 MB

  • Original 1.3 MB
  • After minification 1.3 MB
  • After compression 180.4 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 1.1 MB or 86% of the original size.

Image Optimization

-15%

Potential reduce by 224.0 kB

  • Original 1.5 MB
  • After minification 1.3 MB

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, Pyatigorsk Hh needs image optimization as it can save up to 224.0 kB or 15% 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 49 (60%)

Requests Now

82

After Optimization

33

  • Images
  • JavaScript
  • CSS

The browser has sent 82 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pyatigorsk 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

pyatigorsk.hh.ru

pyatigorsk.hh.ru

346 ms

pyatigorsk.hh.ru

pyatigorsk.hh.ru

2055 ms

__bloko-imports_cf9c71eda381fb160e3608e7983a095c.css

__bloko-imports_cf9c71eda381fb160e3608e7983a095c.css

428 ms

__globals_347aa21a4aa0081560724f14b0604205.css

__globals_347aa21a4aa0081560724f14b0604205.css

696 ms

84614.c7ba677fe4b9b8464bdb.css

84614.c7ba677fe4b9b8464bdb.css

566 ms

App.7e1deb56edd4d3274be0.css

App.7e1deb56edd4d3274be0.css

582 ms

7483.d0d1f4671237305f7079.css

7483.d0d1f4671237305f7079.css

451 ms

16127.26939db15825d9649a31.css

16127.26939db15825d9649a31.css

442 ms

30635.6d399f47b27eb9f08187.css

30635.6d399f47b27eb9f08187.css

612 ms

33132.2aeb54b5aef96dc00a6b.css

33132.2aeb54b5aef96dc00a6b.css

756 ms

51867.c2efcd75db4520017735.css

51867.c2efcd75db4520017735.css

635 ms

74438.c30bf34195061540f18e.css

74438.c30bf34195061540f18e.css

879 ms

98277.7f3d891f73bbe60fd23d.css

98277.7f3d891f73bbe60fd23d.css

750 ms

AdvancedVacancySearch.dd9d03fba5920f595e35.css

AdvancedVacancySearch.dd9d03fba5920f595e35.css

778 ms

ApplicantNegotiations.32802b6585e4ef6abbf9.css

ApplicantNegotiations.32802b6585e4ef6abbf9.css

801 ms

ApplicantResumes.5617fabdd481fd4d1d03.css

ApplicantResumes.5617fabdd481fd4d1d03.css

874 ms

EmployersCompany.4c5dac66846cfd274223.css

EmployersCompany.4c5dac66846cfd274223.css

916 ms

EmployersList.b47cc74da6028ee2284a.css

EmployersList.b47cc74da6028ee2284a.css

921 ms

IndexPage.d53be0e9626bf2400c4c.css

IndexPage.d53be0e9626bf2400c4c.css

959 ms

VacancySavedSearch.f017f0ef2bc03ebab81c.css

VacancySavedSearch.f017f0ef2bc03ebab81c.css

965 ms

magritte.467fd7607209bb631732.js

magritte.467fd7607209bb631732.js

1224 ms

bloko.0bf57127357fe7b5d30f.js

bloko.0bf57127357fe7b5d30f.js

1585 ms

vendors.055615a77cd1a7656079.js

vendors.055615a77cd1a7656079.js

1389 ms

30635.6d399f47b27eb9f08187.js

30635.6d399f47b27eb9f08187.js

1102 ms

33132.2aeb54b5aef96dc00a6b.js

33132.2aeb54b5aef96dc00a6b.js

1134 ms

74438.c30bf34195061540f18e.js

74438.c30bf34195061540f18e.js

1152 ms

80871.8f61a531071e1810bccf.js

80871.8f61a531071e1810bccf.js

1274 ms

99586.17c4948ddc915e404250.js

99586.17c4948ddc915e404250.js

1307 ms

39440.3220275f7e55efde3d92.js

39440.3220275f7e55efde3d92.js

1329 ms

AdvancedVacancySearch.dd9d03fba5920f595e35.js

AdvancedVacancySearch.dd9d03fba5920f595e35.js

1396 ms

ApplicantNegotiations.32802b6585e4ef6abbf9.js

ApplicantNegotiations.32802b6585e4ef6abbf9.js

1451 ms

ApplicantResumes.5617fabdd481fd4d1d03.js

ApplicantResumes.5617fabdd481fd4d1d03.js

1488 ms

ApplicantSuitableVacancies.f5e655a3c3291d4e64ad.js

ApplicantSuitableVacancies.f5e655a3c3291d4e64ad.js

1496 ms

EmployersCompany.4c5dac66846cfd274223.js

EmployersCompany.4c5dac66846cfd274223.js

1555 ms

EmployersList.b47cc74da6028ee2284a.js

EmployersList.b47cc74da6028ee2284a.js

1562 ms

IndexPage.d53be0e9626bf2400c4c.js

IndexPage.d53be0e9626bf2400c4c.js

1647 ms

VacancyFavorite.3ea971e7f703d6830341.js

VacancyFavorite.3ea971e7f703d6830341.js

1652 ms

VacancySavedSearch.f017f0ef2bc03ebab81c.js

VacancySavedSearch.f017f0ef2bc03ebab81c.js

1664 ms

context.js

context.js

964 ms

runtime.b1610f1dc3df92398aee.js

runtime.b1610f1dc3df92398aee.js

1295 ms

appEntryPoint.9d1bc4b958a93f14e178.js

appEntryPoint.9d1bc4b958a93f14e178.js

1290 ms

5873010.jpeg

5873010.jpeg

263 ms

6865266.jpeg

6865266.jpeg

2331 ms

10316531.jpg

10316531.jpg

327 ms

1695766.png

1695766.png

1923 ms

2982496.png

2982496.png

2335 ms

2800603.png

2800603.png

2336 ms

2782115.png

2782115.png

2333 ms

6802938.jpeg

6802938.jpeg

2339 ms

6407649.jpeg

6407649.jpeg

2085 ms

6241994.jpeg

6241994.jpeg

2249 ms

566825.jpeg

566825.jpeg

2414 ms

hh.ru.svg

hh.ru.svg

774 ms

qr-telegram-anonymous-hhru.png

qr-telegram-anonymous-hhru.png

841 ms

10316285.jpg

10316285.jpg

341 ms

10315879.jpg

10315879.jpg

345 ms

10315084.png

10315084.png

344 ms

10315847.jpg

10315847.jpg

343 ms

10315243.jpg

10315243.jpg

346 ms

17865697.png

17865697.png

549 ms

17858707.jpg

17858707.jpg

415 ms

3635424.jpeg

3635424.jpeg

288 ms

617310.png

617310.png

288 ms

2309545.jpeg

2309545.jpeg

287 ms

menu3x3__min_.svg

menu3x3__min_.svg

799 ms

hh.ru__min_.svg

hh.ru__min_.svg

807 ms

bg-applicant-supernova-4__min_.jpg

bg-applicant-supernova-4__min_.jpg

878 ms

app-store-buttons__min_.svg

app-store-buttons__min_.svg

875 ms

6e8ab99b8908d5d2b666.svg

6e8ab99b8908d5d2b666.svg

891 ms

check__min_.svg

check__min_.svg

956 ms

98b908fec43f97f29f72.svg

98b908fec43f97f29f72.svg

961 ms

messengers-hand__min_.svg

messengers-hand__min_.svg

972 ms

vk__min_.svg

vk__min_.svg

1039 ms

telegram__min_.svg

telegram__min_.svg

1041 ms

viber__min_.svg

viber__min_.svg

1053 ms

bd36beda10a092dd913d.svg

bd36beda10a092dd913d.svg

1085 ms

5d17e0a82dc1e383ed58.svg

5d17e0a82dc1e383ed58.svg

1097 ms

fab2946c969a09b1aebf.svg

fab2946c969a09b1aebf.svg

1103 ms

hit;HeadHunter

hit;HeadHunter

537 ms

sdk.js

sdk.js

279 ms

1154ab4b63b3f68e576c.svg

1154ab4b63b3f68e576c.svg

1136 ms

openapi.c340c125c61ec5745ebb2a98626e46ab.js

openapi.c340c125c61ec5745ebb2a98626e46ab.js

233 ms

rtrg

rtrg

134 ms

rtrg

rtrg

264 ms

Accessibility Review

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

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

pyatigorsk.hh.ru SEO score

91

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

pyatigorsk.hh.ru

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