Tools & Wizards About Us
yuzhno-sakhalinsk.hh.ru screenshot

Report Summary

  • 11

    Performance

    Renders faster than
    24% of other websites

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

yuzhno-sakhalinsk.hh.ru

Работа в Южно-Сахалинске, поиск персонала и публикация вакансий - yuzhno-sakhalinsk.hh.ru

Page Load Speed

5.2 sec in total

First Response

494 ms

Resources Loaded

4.1 sec

Page Rendered

561 ms

yuzhno-sakhalinsk.hh.ru screenshot

About Website

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

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

Visit yuzhno-sakhalinsk.hh.ru

Key Findings

We analyzed Yuzhno-sakhalinsk.hh.ru page load time and found that the first response time was 494 ms and then it took 4.7 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

yuzhno-sakhalinsk.hh.ru performance score

11

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.1 s

9/100

10%

LCP (Largest Contentful Paint)

Value5.1 s

25/100

25%

SI (Speed Index)

Value18.0 s

0/100

10%

TBT (Total Blocking Time)

Value8,530 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.385

27/100

15%

TTI (Time to Interactive)

Value28.3 s

0/100

10%

Network Requests Diagram

yuzhno-sakhalinsk.hh.ru

494 ms

yuzhno-sakhalinsk.hh.ru

1349 ms

__bloko-imports_cf9c71eda381fb160e3608e7983a095c.css

531 ms

__globals_0de5e3574f4f51d5caf6109f4d152686.css

787 ms

75419.6a3672d282c705caadd0.css

661 ms

Our browser made a total of 76 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Yuzhno-sakhalinsk.hh.ru, 68% (52 requests) were made to I.hh.ru and 11% (8 requests) were made to Vladivostok.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 761.3 kB (70%)

Content Size

1.1 MB

After Optimization

328.1 kB

  • HTML
  • Images
  • JavaScript

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

HTML Optimization

-85%

Potential reduce by 685.3 kB

  • Original 807.9 kB
  • After minification 806.3 kB
  • After compression 122.6 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 685.3 kB or 85% of the original size.

Image Optimization

-28%

Potential reduce by 73.1 kB

  • Original 258.8 kB
  • After minification 185.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. Obviously, Yuzhno Sakhalinsk Hh needs image optimization as it can save up to 73.1 kB or 28% 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 (61%)

Requests Now

74

After Optimization

29

  • Images
  • JavaScript
  • CSS

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

yuzhno-sakhalinsk.hh.ru

yuzhno-sakhalinsk.hh.ru

494 ms

yuzhno-sakhalinsk.hh.ru

yuzhno-sakhalinsk.hh.ru

1349 ms

__bloko-imports_cf9c71eda381fb160e3608e7983a095c.css

__bloko-imports_cf9c71eda381fb160e3608e7983a095c.css

531 ms

__globals_0de5e3574f4f51d5caf6109f4d152686.css

__globals_0de5e3574f4f51d5caf6109f4d152686.css

787 ms

75419.6a3672d282c705caadd0.css

75419.6a3672d282c705caadd0.css

661 ms

App.eab763412a55de44c7b8.css

App.eab763412a55de44c7b8.css

687 ms

7483.36f56ba529373ef7b9b4.css

7483.36f56ba529373ef7b9b4.css

544 ms

16127.26f078c2554d7f8e61eb.css

16127.26f078c2554d7f8e61eb.css

546 ms

33132.8944b002c5eec0476dcc.css

33132.8944b002c5eec0476dcc.css

842 ms

51867.a57a88bde4a38432f224.css

51867.a57a88bde4a38432f224.css

731 ms

55243.95137fb9c597e8082c51.css

55243.95137fb9c597e8082c51.css

726 ms

85859.b05d338727458757af47.css

85859.b05d338727458757af47.css

837 ms

98277.dfb44cfe9dd059cf9605.css

98277.dfb44cfe9dd059cf9605.css

849 ms

AdvancedVacancySearch.acbf705681b3dff255d7.css

AdvancedVacancySearch.acbf705681b3dff255d7.css

892 ms

ApplicantNegotiations.89032613a01cc91bbf3e.css

ApplicantNegotiations.89032613a01cc91bbf3e.css

893 ms

ApplicantResumes.334a37ac958dbfe4723a.css

ApplicantResumes.334a37ac958dbfe4723a.css

1098 ms

EmployersCompany.d60fadb273891d783a49.css

EmployersCompany.d60fadb273891d783a49.css

1001 ms

EmployersList.73f4bbccd44cfd42f7f9.css

EmployersList.73f4bbccd44cfd42f7f9.css

1006 ms

IndexPage.eb4921ec6b50c5c4262c.css

IndexPage.eb4921ec6b50c5c4262c.css

1040 ms

VacancySavedSearch.c5f63e0b4089fa27da75.css

VacancySavedSearch.c5f63e0b4089fa27da75.css

1060 ms

magritte.bd9c776145b0f80269ae.js

magritte.bd9c776145b0f80269ae.js

1335 ms

bloko.034cdce56f8c0a4f3f27.js

bloko.034cdce56f8c0a4f3f27.js

1346 ms

vendors.0285f94bb83b0ef321cf.js

vendors.0285f94bb83b0ef321cf.js

1466 ms

33132.8944b002c5eec0476dcc.js

33132.8944b002c5eec0476dcc.js

1224 ms

55243.95137fb9c597e8082c51.js

55243.95137fb9c597e8082c51.js

1242 ms

80871.1342534079a84fa8048c.js

80871.1342534079a84fa8048c.js

1422 ms

85859.b05d338727458757af47.js

85859.b05d338727458757af47.js

1411 ms

99586.3dbfafaebfa020929eb5.js

99586.3dbfafaebfa020929eb5.js

1415 ms

39440.4d62916280b0ccdd7c61.js

39440.4d62916280b0ccdd7c61.js

1505 ms

AdvancedVacancySearch.acbf705681b3dff255d7.js

AdvancedVacancySearch.acbf705681b3dff255d7.js

1517 ms

ApplicantNegotiations.89032613a01cc91bbf3e.js

ApplicantNegotiations.89032613a01cc91bbf3e.js

1582 ms

ApplicantResumes.334a37ac958dbfe4723a.js

ApplicantResumes.334a37ac958dbfe4723a.js

1600 ms

ApplicantSuitableVacancies.a352f5f8a3c5397c453d.js

ApplicantSuitableVacancies.a352f5f8a3c5397c453d.js

1591 ms

EmployersCompany.d60fadb273891d783a49.js

EmployersCompany.d60fadb273891d783a49.js

1631 ms

EmployersList.73f4bbccd44cfd42f7f9.js

EmployersList.73f4bbccd44cfd42f7f9.js

1674 ms

IndexPage.eb4921ec6b50c5c4262c.js

IndexPage.eb4921ec6b50c5c4262c.js

1693 ms

VacancyFavorite.5a2ff7f74e8f86a1beb1.js

VacancyFavorite.5a2ff7f74e8f86a1beb1.js

1748 ms

VacancySavedSearch.c5f63e0b4089fa27da75.js

VacancySavedSearch.c5f63e0b4089fa27da75.js

1761 ms

context.js

context.js

945 ms

runtime.e503eb0175553ae252aa.js

runtime.e503eb0175553ae252aa.js

1241 ms

appEntryPoint.6a41ccf1d5c4c8930580.js

appEntryPoint.6a41ccf1d5c4c8930580.js

1258 ms

6865266.jpeg

6865266.jpeg

816 ms

10316316.jpg

10316316.jpg

366 ms

10316531.jpg

10316531.jpg

391 ms

10316285.jpg

10316285.jpg

390 ms

10315879.jpg

10315879.jpg

391 ms

10317610.jpg

10317610.jpg

388 ms

10316725.jpg

10316725.jpg

388 ms

17872800.png

17872800.png

427 ms

17873048.png

17873048.png

464 ms

hh.ru.svg

hh.ru.svg

740 ms

qr-telegram-anonymous-hhru.png

qr-telegram-anonymous-hhru.png

751 ms

5793553.jpeg

5793553.jpeg

820 ms

5529160.jpeg

5529160.jpeg

818 ms

6896162.png

6896162.png

819 ms

4199168.jpeg

4199168.jpeg

828 ms

3848403.jpeg

3848403.jpeg

822 ms

5867493.png

5867493.png

978 ms

6735474.jpeg

6735474.jpeg

983 ms

hh.ru__min_.svg

hh.ru__min_.svg

780 ms

bg-applicant-supernova-3__min_.jpg

bg-applicant-supernova-3__min_.jpg

1099 ms

app-store-buttons__min_.svg

app-store-buttons__min_.svg

811 ms

6e8ab99b8908d5d2b666.svg

6e8ab99b8908d5d2b666.svg

830 ms

messengers-hand__min_.svg

messengers-hand__min_.svg

874 ms

vk__min_.svg

vk__min_.svg

887 ms

telegram__min_.svg

telegram__min_.svg

944 ms

viber__min_.svg

viber__min_.svg

975 ms

bd36beda10a092dd913d.svg

bd36beda10a092dd913d.svg

980 ms

5d17e0a82dc1e383ed58.svg

5d17e0a82dc1e383ed58.svg

1024 ms

fab2946c969a09b1aebf.svg

fab2946c969a09b1aebf.svg

1034 ms

1154ab4b63b3f68e576c.svg

1154ab4b63b3f68e576c.svg

1094 ms

hit;HeadHunter

hit;HeadHunter

650 ms

sdk.js

sdk.js

1395 ms

openapi.c340c125c61ec5745ebb2a98626e46ab.js

openapi.c340c125c61ec5745ebb2a98626e46ab.js

208 ms

rtrg

rtrg

119 ms

rtrg

rtrg

241 ms

Accessibility Review

yuzhno-sakhalinsk.hh.ru accessibility score

68

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

<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

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

yuzhno-sakhalinsk.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

yuzhno-sakhalinsk.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 Yuzhno-sakhalinsk.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 Yuzhno-sakhalinsk.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

yuzhno-sakhalinsk.hh.ru

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