Tools & Wizards About Us
zheleznodorozhnyj.hh.ru screenshot

Report Summary

  • 4

    Performance

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

zheleznodorozhnyj.hh.ru

Работа в Железнодорожном (Московская область), поиск персонала и публикация вакансий - zheleznodorozhniy50.hh.ru

Page Load Speed

5.6 sec in total

First Response

459 ms

Resources Loaded

4.7 sec

Page Rendered

454 ms

zheleznodorozhnyj.hh.ru screenshot

About Website

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

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

Visit zheleznodorozhnyj.hh.ru

Key Findings

We analyzed Zheleznodorozhnyj.hh.ru page load time and found that the first response time was 459 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

zheleznodorozhnyj.hh.ru performance score

4

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.3 s

3/100

10%

LCP (Largest Contentful Paint)

Value8.3 s

2/100

25%

SI (Speed Index)

Value20.4 s

0/100

10%

TBT (Total Blocking Time)

Value5,660 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.409

24/100

15%

TTI (Time to Interactive)

Value27.5 s

0/100

10%

Network Requests Diagram

zheleznodorozhnyj.hh.ru

459 ms

zheleznodorozhniy50.hh.ru

1769 ms

__bloko-imports_cf9c71eda381fb160e3608e7983a095c.css

307 ms

__globals_c7ebc29db8cd2578875956095ffcd3f3.css

708 ms

84614.c7ba677fe4b9b8464bdb.css

469 ms

Our browser made a total of 79 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Zheleznodorozhnyj.hh.ru, 67% (53 requests) were made to I.hh.ru and 13% (10 requests) were made to Hh.ru. The less responsive or slowest element that took the longest time to load (1.8 sec) relates to the external source Zheleznodorozhniy50.hh.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 636.1 kB (58%)

Content Size

1.1 MB

After Optimization

469.7 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Zheleznodorozhnyj.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 737.1 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 623.0 kB

  • Original 737.1 kB
  • After minification 735.5 kB
  • After compression 114.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 623.0 kB or 85% of the original size.

Image Optimization

-3%

Potential reduce by 10.2 kB

  • Original 346.0 kB
  • After minification 335.7 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. Zheleznodorozhnyj 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 (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 Zheleznodorozhnyj 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

zheleznodorozhnyj.hh.ru

zheleznodorozhnyj.hh.ru

459 ms

zheleznodorozhniy50.hh.ru

zheleznodorozhniy50.hh.ru

1769 ms

__bloko-imports_cf9c71eda381fb160e3608e7983a095c.css

__bloko-imports_cf9c71eda381fb160e3608e7983a095c.css

307 ms

__globals_c7ebc29db8cd2578875956095ffcd3f3.css

__globals_c7ebc29db8cd2578875956095ffcd3f3.css

708 ms

84614.c7ba677fe4b9b8464bdb.css

84614.c7ba677fe4b9b8464bdb.css

469 ms

App.af6378e9aa44433b97a6.css

App.af6378e9aa44433b97a6.css

350 ms

7483.d0d1f4671237305f7079.css

7483.d0d1f4671237305f7079.css

464 ms

16127.26939db15825d9649a31.css

16127.26939db15825d9649a31.css

460 ms

30640.e7d6330ffef34e10a635.css

30640.e7d6330ffef34e10a635.css

493 ms

33132.23bf4816ff4822b73cee.css

33132.23bf4816ff4822b73cee.css

547 ms

51867.c2efcd75db4520017735.css

51867.c2efcd75db4520017735.css

644 ms

74438.8393047074d1e24ecb9c.css

74438.8393047074d1e24ecb9c.css

650 ms

98277.7f3d891f73bbe60fd23d.css

98277.7f3d891f73bbe60fd23d.css

640 ms

AdvancedVacancySearch.dd9d03fba5920f595e35.css

AdvancedVacancySearch.dd9d03fba5920f595e35.css

657 ms

ApplicantNegotiations.3e111b2c9a3fea1c28fa.css

ApplicantNegotiations.3e111b2c9a3fea1c28fa.css

734 ms

ApplicantResumes.bf814adb53fe8b16ff8a.css

ApplicantResumes.bf814adb53fe8b16ff8a.css

820 ms

EmployersCompany.4c5dac66846cfd274223.css

EmployersCompany.4c5dac66846cfd274223.css

810 ms

EmployersList.b47cc74da6028ee2284a.css

EmployersList.b47cc74da6028ee2284a.css

816 ms

IndexPage.af613fd8a65d57fe4ca8.css

IndexPage.af613fd8a65d57fe4ca8.css

840 ms

VacancySavedSearch.ba5ca9a7dd4a593992fe.css

VacancySavedSearch.ba5ca9a7dd4a593992fe.css

870 ms

magritte.121eb1cd3436bc13b8e5.js

magritte.121eb1cd3436bc13b8e5.js

1026 ms

bloko.d1309d34cd7afeb90a28.js

bloko.d1309d34cd7afeb90a28.js

1258 ms

vendors.413c496af630647c46e3.js

vendors.413c496af630647c46e3.js

1312 ms

30640.e7d6330ffef34e10a635.js

30640.e7d6330ffef34e10a635.js

1004 ms

33132.23bf4816ff4822b73cee.js

33132.23bf4816ff4822b73cee.js

1017 ms

74438.8393047074d1e24ecb9c.js

74438.8393047074d1e24ecb9c.js

1053 ms

80871.2793b505aa74efc759a3.js

80871.2793b505aa74efc759a3.js

1174 ms

99586.eae8aace9a0d032232df.js

99586.eae8aace9a0d032232df.js

1190 ms

39440.929b8e8ec21a4a5b1e84.js

39440.929b8e8ec21a4a5b1e84.js

1196 ms

AdvancedVacancySearch.dd9d03fba5920f595e35.js

AdvancedVacancySearch.dd9d03fba5920f595e35.js

1223 ms

ApplicantNegotiations.3e111b2c9a3fea1c28fa.js

ApplicantNegotiations.3e111b2c9a3fea1c28fa.js

1344 ms

ApplicantResumes.bf814adb53fe8b16ff8a.js

ApplicantResumes.bf814adb53fe8b16ff8a.js

1374 ms

ApplicantSuitableVacancies.1b95ef3bca1c3ba4dbdf.js

ApplicantSuitableVacancies.1b95ef3bca1c3ba4dbdf.js

1364 ms

EmployersCompany.4c5dac66846cfd274223.js

EmployersCompany.4c5dac66846cfd274223.js

1392 ms

EmployersList.b47cc74da6028ee2284a.js

EmployersList.b47cc74da6028ee2284a.js

1425 ms

IndexPage.af613fd8a65d57fe4ca8.js

IndexPage.af613fd8a65d57fe4ca8.js

1486 ms

VacancyFavorite.3ea971e7f703d6830341.js

VacancyFavorite.3ea971e7f703d6830341.js

1509 ms

VacancySavedSearch.ba5ca9a7dd4a593992fe.js

VacancySavedSearch.ba5ca9a7dd4a593992fe.js

1531 ms

context.js

context.js

920 ms

runtime.18d5aac0ad45b494d400.js

runtime.18d5aac0ad45b494d400.js

1234 ms

appEntryPoint.4678aa67ca1892f8f38a.js

appEntryPoint.4678aa67ca1892f8f38a.js

1212 ms

6865266.jpeg

6865266.jpeg

341 ms

10316531.jpg

10316531.jpg

199 ms

hh.ru.svg

hh.ru.svg

715 ms

qr-telegram-anonymous-hhru.png

qr-telegram-anonymous-hhru.png

776 ms

10316285.jpg

10316285.jpg

203 ms

10315879.jpg

10315879.jpg

208 ms

10315084.png

10315084.png

206 ms

10315847.jpg

10315847.jpg

209 ms

10315243.jpg

10315243.jpg

222 ms

17858707.jpg

17858707.jpg

269 ms

17852603.jpg

17852603.jpg

291 ms

4009951.jpeg

4009951.jpeg

365 ms

1111895.png

1111895.png

366 ms

6758874.jpeg

6758874.jpeg

360 ms

6791170.png

6791170.png

362 ms

1090256.png

1090256.png

363 ms

916322.jpeg

916322.jpeg

646 ms

1434293.jpeg

1434293.jpeg

527 ms

461846.png

461846.png

524 ms

3510113.jpeg

3510113.jpeg

527 ms

menu3x3__min_.svg

menu3x3__min_.svg

765 ms

hh.ru__min_.svg

hh.ru__min_.svg

788 ms

bg-applicant-supernova-6__min_.jpg

bg-applicant-supernova-6__min_.jpg

861 ms

app-store-buttons__min_.svg

app-store-buttons__min_.svg

830 ms

6e8ab99b8908d5d2b666.svg

6e8ab99b8908d5d2b666.svg

854 ms

messengers-hand__min_.svg

messengers-hand__min_.svg

910 ms

vk__min_.svg

vk__min_.svg

929 ms

telegram__min_.svg

telegram__min_.svg

950 ms

viber__min_.svg

viber__min_.svg

994 ms

bd36beda10a092dd913d.svg

bd36beda10a092dd913d.svg

996 ms

5d17e0a82dc1e383ed58.svg

5d17e0a82dc1e383ed58.svg

1009 ms

fab2946c969a09b1aebf.svg

fab2946c969a09b1aebf.svg

1052 ms

1154ab4b63b3f68e576c.svg

1154ab4b63b3f68e576c.svg

1071 ms

hit;HeadHunter

hit;HeadHunter

606 ms

sdk.js

sdk.js

785 ms

openapi.c340c125c61ec5745ebb2a98626e46ab.js

openapi.c340c125c61ec5745ebb2a98626e46ab.js

240 ms

rtrg

rtrg

137 ms

rtrg

rtrg

269 ms

Accessibility Review

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

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

zheleznodorozhnyj.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 Zheleznodorozhnyj.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 Zheleznodorozhnyj.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

zheleznodorozhnyj.hh.ru

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