Tools & Wizards About Us
zheleznogorsk-kursk.hh.ru screenshot

Report Summary

  • 11

    Performance

    Renders faster than
    24% of other websites

  • 59

    Accessibility

    Visual factors better than
    that of 26% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

zheleznogorsk-kursk.hh.ru

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

Page Load Speed

4.9 sec in total

First Response

333 ms

Resources Loaded

4 sec

Page Rendered

504 ms

zheleznogorsk-kursk.hh.ru screenshot

About Website

Click here to check amazing Zheleznogorsk Kursk Hh content for Russia. Otherwise, check out these important facts you probably never knew about zheleznogorsk-kursk.hh.ru

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

Visit zheleznogorsk-kursk.hh.ru

Key Findings

We analyzed Zheleznogorsk-kursk.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

zheleznogorsk-kursk.hh.ru performance score

11

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.0 s

9/100

10%

LCP (Largest Contentful Paint)

Value5.0 s

26/100

25%

SI (Speed Index)

Value20.8 s

0/100

10%

TBT (Total Blocking Time)

Value5,150 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.409

24/100

15%

TTI (Time to Interactive)

Value30.0 s

0/100

10%

Network Requests Diagram

zheleznogorsk-kursk.hh.ru

333 ms

zheleznogorsk-kursk.hh.ru

1319 ms

__bloko-imports_cf9c71eda381fb160e3608e7983a095c.css

566 ms

__globals_c83885c429e61d7ee450afa3b1dcde53.css

814 ms

84614.c7ba677fe4b9b8464bdb.css

685 ms

Our browser made a total of 78 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Zheleznogorsk-kursk.hh.ru, 67% (52 requests) were made to I.hh.ru and 14% (11 requests) were made to Voronezh.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 794.7 kB (36%)

Content Size

2.2 MB

After Optimization

1.4 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Zheleznogorsk-kursk.hh.ru main page is 2.2 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. 65% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 574.7 kB

  • Original 683.5 kB
  • After minification 681.9 kB
  • After compression 108.8 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 574.7 kB or 84% of the original size.

Image Optimization

-15%

Potential reduce by 217.1 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, Zheleznogorsk Kursk Hh needs image optimization as it can save up to 217.1 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 45 (59%)

Requests Now

76

After Optimization

31

  • Images
  • JavaScript
  • CSS

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

zheleznogorsk-kursk.hh.ru

zheleznogorsk-kursk.hh.ru

333 ms

zheleznogorsk-kursk.hh.ru

zheleznogorsk-kursk.hh.ru

1319 ms

__bloko-imports_cf9c71eda381fb160e3608e7983a095c.css

__bloko-imports_cf9c71eda381fb160e3608e7983a095c.css

566 ms

__globals_c83885c429e61d7ee450afa3b1dcde53.css

__globals_c83885c429e61d7ee450afa3b1dcde53.css

814 ms

84614.c7ba677fe4b9b8464bdb.css

84614.c7ba677fe4b9b8464bdb.css

685 ms

App.d2ff9960eac4c5df33b9.css

App.d2ff9960eac4c5df33b9.css

698 ms

7483.d0d1f4671237305f7079.css

7483.d0d1f4671237305f7079.css

578 ms

16127.26939db15825d9649a31.css

16127.26939db15825d9649a31.css

988 ms

30635.09ffcdca39c9834d9189.css

30635.09ffcdca39c9834d9189.css

749 ms

33132.16ad1519cafffe99cc15.css

33132.16ad1519cafffe99cc15.css

890 ms

51867.c2efcd75db4520017735.css

51867.c2efcd75db4520017735.css

862 ms

74438.71b77d8d056400104ca4.css

74438.71b77d8d056400104ca4.css

870 ms

98277.7f3d891f73bbe60fd23d.css

98277.7f3d891f73bbe60fd23d.css

926 ms

AdvancedVacancySearch.d5820931a7fbe5dff7af.css

AdvancedVacancySearch.d5820931a7fbe5dff7af.css

975 ms

ApplicantNegotiations.db8f1a0323b2f436ec3f.css

ApplicantNegotiations.db8f1a0323b2f436ec3f.css

1026 ms

ApplicantResumes.f964cc7e695b80c4f4d6.css

ApplicantResumes.f964cc7e695b80c4f4d6.css

1049 ms

EmployersCompany.c8512b398f9538426971.css

EmployersCompany.c8512b398f9538426971.css

1072 ms

EmployersList.823ff4a15a8caadb322e.css

EmployersList.823ff4a15a8caadb322e.css

1088 ms

IndexPage.bdf0f034ab15db89605b.css

IndexPage.bdf0f034ab15db89605b.css

1155 ms

VacancySavedSearch.4fe46989c660cbff42db.css

VacancySavedSearch.4fe46989c660cbff42db.css

1150 ms

magritte.7e689ffa8e037ece6a48.js

magritte.7e689ffa8e037ece6a48.js

1361 ms

bloko.7f921a4a5aaf41f1cafd.js

bloko.7f921a4a5aaf41f1cafd.js

1386 ms

vendors.ca387f7928d7c87c225b.js

vendors.ca387f7928d7c87c225b.js

1538 ms

30635.09ffcdca39c9834d9189.js

30635.09ffcdca39c9834d9189.js

1266 ms

33132.16ad1519cafffe99cc15.js

33132.16ad1519cafffe99cc15.js

1351 ms

74438.71b77d8d056400104ca4.js

74438.71b77d8d056400104ca4.js

1364 ms

80871.2f2ce2513ecf4f782e20.js

80871.2f2ce2513ecf4f782e20.js

1435 ms

99586.51c0563465ce4b2aac07.js

99586.51c0563465ce4b2aac07.js

1533 ms

39440.a31c1c463fb15b517bb3.js

39440.a31c1c463fb15b517bb3.js

1532 ms

AdvancedVacancySearch.d5820931a7fbe5dff7af.js

AdvancedVacancySearch.d5820931a7fbe5dff7af.js

1535 ms

ApplicantNegotiations.db8f1a0323b2f436ec3f.js

ApplicantNegotiations.db8f1a0323b2f436ec3f.js

1550 ms

ApplicantResumes.f964cc7e695b80c4f4d6.js

ApplicantResumes.f964cc7e695b80c4f4d6.js

1616 ms

ApplicantSuitableVacancies.4531eaf82bedc4637003.js

ApplicantSuitableVacancies.4531eaf82bedc4637003.js

1695 ms

EmployersCompany.c8512b398f9538426971.js

EmployersCompany.c8512b398f9538426971.js

1703 ms

EmployersList.823ff4a15a8caadb322e.js

EmployersList.823ff4a15a8caadb322e.js

1702 ms

IndexPage.bdf0f034ab15db89605b.js

IndexPage.bdf0f034ab15db89605b.js

1708 ms

VacancyFavorite.d9598f29cec8cf314f19.js

VacancyFavorite.d9598f29cec8cf314f19.js

1712 ms

VacancySavedSearch.4fe46989c660cbff42db.js

VacancySavedSearch.4fe46989c660cbff42db.js

1781 ms

context.js

context.js

1020 ms

runtime.43eafdaa7032cd9c93d0.js

runtime.43eafdaa7032cd9c93d0.js

1294 ms

appEntryPoint.3125278be43e2f11bc3b.js

appEntryPoint.3125278be43e2f11bc3b.js

1303 ms

6865266.jpeg

6865266.jpeg

810 ms

10316531.jpg

10316531.jpg

394 ms

2593525.png

2593525.png

420 ms

6558217.jpeg

6558217.jpeg

421 ms

6456865.jpeg

6456865.jpeg

835 ms

1888930.png

1888930.png

830 ms

3862731.jpeg

3862731.jpeg

423 ms

4235372.jpeg

4235372.jpeg

586 ms

3981091.png

3981091.png

586 ms

6130301.jpeg

6130301.jpeg

600 ms

3800659.jpeg

3800659.jpeg

760 ms

2415805.jpeg

2415805.jpeg

753 ms

hh.ru.svg

hh.ru.svg

705 ms

qr-telegram-anonymous-hhru.png

qr-telegram-anonymous-hhru.png

710 ms

10316285.jpg

10316285.jpg

412 ms

10315879.jpg

10315879.jpg

416 ms

10315084.png

10315084.png

416 ms

10316715.jpg

10316715.jpg

415 ms

17865697.png

17865697.png

617 ms

17858707.jpg

17858707.jpg

464 ms

hh.ru__min_.svg

hh.ru__min_.svg

683 ms

bg-applicant-supernova-4__min_.jpg

bg-applicant-supernova-4__min_.jpg

891 ms

app-store-buttons__min_.svg

app-store-buttons__min_.svg

831 ms

6e8ab99b8908d5d2b666.svg

6e8ab99b8908d5d2b666.svg

839 ms

messengers-hand__min_.svg

messengers-hand__min_.svg

851 ms

vk__min_.svg

vk__min_.svg

848 ms

telegram__min_.svg

telegram__min_.svg

846 ms

viber__min_.svg

viber__min_.svg

996 ms

bd36beda10a092dd913d.svg

bd36beda10a092dd913d.svg

989 ms

5d17e0a82dc1e383ed58.svg

5d17e0a82dc1e383ed58.svg

999 ms

fab2946c969a09b1aebf.svg

fab2946c969a09b1aebf.svg

1005 ms

1154ab4b63b3f68e576c.svg

1154ab4b63b3f68e576c.svg

997 ms

hit;HeadHunter

hit;HeadHunter

546 ms

sdk.js

sdk.js

1423 ms

openapi.c340c125c61ec5745ebb2a98626e46ab.js

openapi.c340c125c61ec5745ebb2a98626e46ab.js

215 ms

rtrg

rtrg

121 ms

rtrg

rtrg

241 ms

Accessibility Review

zheleznogorsk-kursk.hh.ru accessibility score

59

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

zheleznogorsk-kursk.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

zheleznogorsk-kursk.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 Zheleznogorsk-kursk.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 Zheleznogorsk-kursk.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

zheleznogorsk-kursk.hh.ru

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