Tools & Wizards About Us
leninsk-kuznetsk.hh.ru screenshot

Report Summary

  • 6

    Performance

    Renders faster than
    21% of other websites

  • 70

    Accessibility

    Visual factors better than
    that of 35% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

leninsk-kuznetsk.hh.ru

Работа в Ленинск-Кузнецком, поиск персонала и публикация вакансий - leninsk-kuznetsk.hh.ru

Page Load Speed

4.9 sec in total

First Response

333 ms

Resources Loaded

4.1 sec

Page Rendered

486 ms

leninsk-kuznetsk.hh.ru screenshot

About Website

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

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

Visit leninsk-kuznetsk.hh.ru

Key Findings

We analyzed Leninsk-kuznetsk.hh.ru page load time and found that the first response time was 333 ms and then it took 4.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

leninsk-kuznetsk.hh.ru performance score

6

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.0 s

10/100

10%

LCP (Largest Contentful Paint)

Value7.7 s

3/100

25%

SI (Speed Index)

Value19.1 s

0/100

10%

TBT (Total Blocking Time)

Value10,130 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.385

27/100

15%

TTI (Time to Interactive)

Value29.0 s

0/100

10%

Network Requests Diagram

leninsk-kuznetsk.hh.ru

333 ms

leninsk-kuznetsk.hh.ru

1388 ms

__bloko-imports_cf9c71eda381fb160e3608e7983a095c.css

570 ms

__globals_0de5e3574f4f51d5caf6109f4d152686.css

835 ms

75419.6a3672d282c705caadd0.css

708 ms

Our browser made a total of 79 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Leninsk-kuznetsk.hh.ru, 66% (52 requests) were made to I.hh.ru and 14% (11 requests) were made to Novosibirsk.hh.ru. The less responsive or slowest element that took the longest time to load (1.8 sec) relates to the external source I.hh.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 669.6 kB (64%)

Content Size

1.1 MB

After Optimization

382.6 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Leninsk-kuznetsk.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. 60% of websites need less resources to load. HTML takes 698.8 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 588.5 kB

  • Original 698.8 kB
  • After minification 697.2 kB
  • After compression 110.3 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 588.5 kB or 84% of the original size.

Image Optimization

-24%

Potential reduce by 78.2 kB

  • Original 330.7 kB
  • After minification 252.5 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, Leninsk Kuznetsk Hh needs image optimization as it can save up to 78.2 kB or 24% 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 (61%)

Requests Now

77

After Optimization

30

  • Images
  • JavaScript
  • CSS

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

leninsk-kuznetsk.hh.ru

leninsk-kuznetsk.hh.ru

333 ms

leninsk-kuznetsk.hh.ru

leninsk-kuznetsk.hh.ru

1388 ms

__bloko-imports_cf9c71eda381fb160e3608e7983a095c.css

__bloko-imports_cf9c71eda381fb160e3608e7983a095c.css

570 ms

__globals_0de5e3574f4f51d5caf6109f4d152686.css

__globals_0de5e3574f4f51d5caf6109f4d152686.css

835 ms

75419.6a3672d282c705caadd0.css

75419.6a3672d282c705caadd0.css

708 ms

App.eab763412a55de44c7b8.css

App.eab763412a55de44c7b8.css

724 ms

7483.36f56ba529373ef7b9b4.css

7483.36f56ba529373ef7b9b4.css

584 ms

16127.26f078c2554d7f8e61eb.css

16127.26f078c2554d7f8e61eb.css

588 ms

33132.8944b002c5eec0476dcc.css

33132.8944b002c5eec0476dcc.css

892 ms

51867.a57a88bde4a38432f224.css

51867.a57a88bde4a38432f224.css

765 ms

55243.95137fb9c597e8082c51.css

55243.95137fb9c597e8082c51.css

774 ms

85859.b05d338727458757af47.css

85859.b05d338727458757af47.css

888 ms

98277.dfb44cfe9dd059cf9605.css

98277.dfb44cfe9dd059cf9605.css

896 ms

AdvancedVacancySearch.acbf705681b3dff255d7.css

AdvancedVacancySearch.acbf705681b3dff255d7.css

928 ms

ApplicantNegotiations.89032613a01cc91bbf3e.css

ApplicantNegotiations.89032613a01cc91bbf3e.css

941 ms

ApplicantResumes.334a37ac958dbfe4723a.css

ApplicantResumes.334a37ac958dbfe4723a.css

1012 ms

EmployersCompany.d60fadb273891d783a49.css

EmployersCompany.d60fadb273891d783a49.css

1052 ms

EmployersList.73f4bbccd44cfd42f7f9.css

EmployersList.73f4bbccd44cfd42f7f9.css

1054 ms

IndexPage.eb4921ec6b50c5c4262c.css

IndexPage.eb4921ec6b50c5c4262c.css

1073 ms

VacancySavedSearch.c5f63e0b4089fa27da75.css

VacancySavedSearch.c5f63e0b4089fa27da75.css

1091 ms

magritte.bd9c776145b0f80269ae.js

magritte.bd9c776145b0f80269ae.js

1295 ms

bloko.034cdce56f8c0a4f3f27.js

bloko.034cdce56f8c0a4f3f27.js

1348 ms

vendors.0285f94bb83b0ef321cf.js

vendors.0285f94bb83b0ef321cf.js

1537 ms

33132.8944b002c5eec0476dcc.js

33132.8944b002c5eec0476dcc.js

1232 ms

55243.95137fb9c597e8082c51.js

55243.95137fb9c597e8082c51.js

1253 ms

80871.1342534079a84fa8048c.js

80871.1342534079a84fa8048c.js

1289 ms

85859.b05d338727458757af47.js

85859.b05d338727458757af47.js

1444 ms

99586.3dbfafaebfa020929eb5.js

99586.3dbfafaebfa020929eb5.js

1444 ms

39440.4d62916280b0ccdd7c61.js

39440.4d62916280b0ccdd7c61.js

1476 ms

AdvancedVacancySearch.acbf705681b3dff255d7.js

AdvancedVacancySearch.acbf705681b3dff255d7.js

1464 ms

ApplicantNegotiations.89032613a01cc91bbf3e.js

ApplicantNegotiations.89032613a01cc91bbf3e.js

1514 ms

ApplicantResumes.334a37ac958dbfe4723a.js

ApplicantResumes.334a37ac958dbfe4723a.js

1636 ms

ApplicantSuitableVacancies.a352f5f8a3c5397c453d.js

ApplicantSuitableVacancies.a352f5f8a3c5397c453d.js

1616 ms

EmployersCompany.d60fadb273891d783a49.js

EmployersCompany.d60fadb273891d783a49.js

1631 ms

EmployersList.73f4bbccd44cfd42f7f9.js

EmployersList.73f4bbccd44cfd42f7f9.js

1648 ms

IndexPage.eb4921ec6b50c5c4262c.js

IndexPage.eb4921ec6b50c5c4262c.js

1688 ms

VacancyFavorite.5a2ff7f74e8f86a1beb1.js

VacancyFavorite.5a2ff7f74e8f86a1beb1.js

1700 ms

VacancySavedSearch.c5f63e0b4089fa27da75.js

VacancySavedSearch.c5f63e0b4089fa27da75.js

1789 ms

context.js

context.js

1063 ms

runtime.e503eb0175553ae252aa.js

runtime.e503eb0175553ae252aa.js

1235 ms

appEntryPoint.6a41ccf1d5c4c8930580.js

appEntryPoint.6a41ccf1d5c4c8930580.js

1232 ms

6865266.jpeg

6865266.jpeg

403 ms

10316316.jpg

10316316.jpg

406 ms

hh.ru.svg

hh.ru.svg

714 ms

qr-telegram-anonymous-hhru.png

qr-telegram-anonymous-hhru.png

752 ms

4236792.jpeg

4236792.jpeg

819 ms

2396109.png

2396109.png

820 ms

2935280.png

2935280.png

833 ms

6327218.png

6327218.png

832 ms

2453737.png

2453737.png

420 ms

5979317.jpeg

5979317.jpeg

569 ms

6441737.jpeg

6441737.jpeg

587 ms

6859534.png

6859534.png

735 ms

6638301.jpeg

6638301.jpeg

757 ms

3618979.png

3618979.png

903 ms

10316531.jpg

10316531.jpg

427 ms

10316285.jpg

10316285.jpg

429 ms

10315879.jpg

10315879.jpg

430 ms

10317610.jpg

10317610.jpg

427 ms

10316725.jpg

10316725.jpg

429 ms

17872800.png

17872800.png

468 ms

17873048.png

17873048.png

508 ms

hh.ru__min_.svg

hh.ru__min_.svg

733 ms

bg-applicant-supernova-4__min_.jpg

bg-applicant-supernova-4__min_.jpg

968 ms

app-store-buttons__min_.svg

app-store-buttons__min_.svg

843 ms

6e8ab99b8908d5d2b666.svg

6e8ab99b8908d5d2b666.svg

846 ms

messengers-hand__min_.svg

messengers-hand__min_.svg

847 ms

vk__min_.svg

vk__min_.svg

883 ms

telegram__min_.svg

telegram__min_.svg

898 ms

viber__min_.svg

viber__min_.svg

1009 ms

bd36beda10a092dd913d.svg

bd36beda10a092dd913d.svg

989 ms

5d17e0a82dc1e383ed58.svg

5d17e0a82dc1e383ed58.svg

998 ms

fab2946c969a09b1aebf.svg

fab2946c969a09b1aebf.svg

1026 ms

1154ab4b63b3f68e576c.svg

1154ab4b63b3f68e576c.svg

1040 ms

hit;HeadHunter

hit;HeadHunter

685 ms

sdk.js

sdk.js

1437 ms

openapi.c340c125c61ec5745ebb2a98626e46ab.js

openapi.c340c125c61ec5745ebb2a98626e46ab.js

226 ms

rtrg

rtrg

128 ms

rtrg

rtrg

258 ms

Accessibility Review

leninsk-kuznetsk.hh.ru accessibility score

70

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

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

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

leninsk-kuznetsk.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

leninsk-kuznetsk.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 Leninsk-kuznetsk.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 Leninsk-kuznetsk.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

leninsk-kuznetsk.hh.ru

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