Tools & Wizards About Us
arkhangelsk.hh.ru screenshot

Report Summary

  • 6

    Performance

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

arkhangelsk.hh.ru

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

Page Load Speed

5.4 sec in total

First Response

338 ms

Resources Loaded

4.5 sec

Page Rendered

607 ms

arkhangelsk.hh.ru screenshot

About Website

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

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

Visit arkhangelsk.hh.ru

Key Findings

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

arkhangelsk.hh.ru performance score

6

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.1 s

9/100

10%

LCP (Largest Contentful Paint)

Value6.9 s

6/100

25%

SI (Speed Index)

Value17.3 s

0/100

10%

TBT (Total Blocking Time)

Value5,290 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.409

24/100

15%

TTI (Time to Interactive)

Value26.5 s

0/100

10%

Network Requests Diagram

arkhangelsk.hh.ru

338 ms

arkhangelsk.hh.ru

1435 ms

__bloko-imports_02c6af9fb8291812a3eb386ae95416ff.css

460 ms

__globals_faec70f565dc8957f8344401ad7e9ff4.css

715 ms

80530.2d484ce874853891e745.css

623 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 Arkhangelsk.hh.ru, 65% (51 requests) were made to I.hh.ru and 13% (10 requests) were made to Spb.hh.ru. The less responsive or slowest element that took the longest time to load (1.9 sec) relates to the external source Cpa.hh.ru.

Page Optimization Overview & Recommendations

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

Content Size

1.1 MB

After Optimization

378.3 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Arkhangelsk.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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. HTML takes 759.6 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 642.3 kB

  • Original 759.6 kB
  • After minification 757.9 kB
  • After compression 117.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 642.3 kB or 85% of the original size.

Image Optimization

-11%

Potential reduce by 31.1 kB

  • Original 272.4 kB
  • After minification 241.3 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, Arkhangelsk Hh needs image optimization as it can save up to 31.1 kB or 11% 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 (60%)

Requests Now

75

After Optimization

30

  • Images
  • JavaScript
  • CSS

The browser has sent 75 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Arkhangelsk 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 22 to 1 for JavaScripts and from 17 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

arkhangelsk.hh.ru

arkhangelsk.hh.ru

338 ms

arkhangelsk.hh.ru

arkhangelsk.hh.ru

1435 ms

__bloko-imports_02c6af9fb8291812a3eb386ae95416ff.css

__bloko-imports_02c6af9fb8291812a3eb386ae95416ff.css

460 ms

__globals_faec70f565dc8957f8344401ad7e9ff4.css

__globals_faec70f565dc8957f8344401ad7e9ff4.css

715 ms

80530.2d484ce874853891e745.css

80530.2d484ce874853891e745.css

623 ms

App.92c7bf3d438dfaa24621.css

App.92c7bf3d438dfaa24621.css

607 ms

1690.d87ad13e92e84563e08d.css

1690.d87ad13e92e84563e08d.css

592 ms

45842.c51b66c36c3d74f301b4.css

45842.c51b66c36c3d74f301b4.css

485 ms

49662.5c61b235ee7387b45eea.css

49662.5c61b235ee7387b45eea.css

677 ms

69950.a21e1f7674a10cf79f28.css

69950.a21e1f7674a10cf79f28.css

672 ms

72796.d8ad3264ae6afe039400.css

72796.d8ad3264ae6afe039400.css

795 ms

85902.8a508bbf498ebfcf43ad.css

85902.8a508bbf498ebfcf43ad.css

786 ms

AdvancedVacancySearch.b21eeb30717e1d9173bc.css

AdvancedVacancySearch.b21eeb30717e1d9173bc.css

777 ms

ApplicantNegotiations.1efb337f4f751530ff73.css

ApplicantNegotiations.1efb337f4f751530ff73.css

838 ms

ApplicantResumes.280b39e806c8c48c6205.css

ApplicantResumes.280b39e806c8c48c6205.css

858 ms

EmployersCompany.1636ac131b77e53cdab4.css

EmployersCompany.1636ac131b77e53cdab4.css

881 ms

EmployersList.f4037bb942fba73a6bca.css

EmployersList.f4037bb942fba73a6bca.css

962 ms

IndexPage.5133943f86b2c9b8d5fa.css

IndexPage.5133943f86b2c9b8d5fa.css

977 ms

VacancySavedSearch.780cb07a0f6b85e44978.css

VacancySavedSearch.780cb07a0f6b85e44978.css

964 ms

magritte.770a17138c5d92322cbf.js

magritte.770a17138c5d92322cbf.js

1286 ms

bloko.65b2a4279e4147633ac6.js

bloko.65b2a4279e4147633ac6.js

1304 ms

vendors.6acb434de5ce5119c57a.js

vendors.6acb434de5ce5119c57a.js

1323 ms

1690.d87ad13e92e84563e08d.js

1690.d87ad13e92e84563e08d.js

1144 ms

14825.b8e829350fdaa2f7c878.js

14825.b8e829350fdaa2f7c878.js

1133 ms

40604.7438c840d56c5530633b.js

40604.7438c840d56c5530633b.js

1154 ms

72796.d8ad3264ae6afe039400.js

72796.d8ad3264ae6afe039400.js

1310 ms

3234.7e6b4732c25aa0565953.js

3234.7e6b4732c25aa0565953.js

1340 ms

AdvancedVacancySearch.b21eeb30717e1d9173bc.js

AdvancedVacancySearch.b21eeb30717e1d9173bc.js

1330 ms

ApplicantNegotiations.1efb337f4f751530ff73.js

ApplicantNegotiations.1efb337f4f751530ff73.js

1456 ms

ApplicantResumes.280b39e806c8c48c6205.js

ApplicantResumes.280b39e806c8c48c6205.js

1476 ms

ApplicantSuitableVacancies.f6a7798a0a8eeafc9b83.js

ApplicantSuitableVacancies.f6a7798a0a8eeafc9b83.js

1480 ms

EmployersCompany.1636ac131b77e53cdab4.js

EmployersCompany.1636ac131b77e53cdab4.js

1489 ms

EmployersList.f4037bb942fba73a6bca.js

EmployersList.f4037bb942fba73a6bca.js

1502 ms

IndexPage.5133943f86b2c9b8d5fa.js

IndexPage.5133943f86b2c9b8d5fa.js

1542 ms

VacancyFavorite.aa285ebecb5aa8038a49.js

VacancyFavorite.aa285ebecb5aa8038a49.js

1624 ms

VacancySavedSearch.780cb07a0f6b85e44978.js

VacancySavedSearch.780cb07a0f6b85e44978.js

1647 ms

runtime.98fb3fa198c933f9a86a.js

runtime.98fb3fa198c933f9a86a.js

1655 ms

appEntryPoint.021c9f0914396ec1bd18.js

appEntryPoint.021c9f0914396ec1bd18.js

1659 ms

context.js

context.js

997 ms

6842158.jpeg

6842158.jpeg

1567 ms

10297176.jpg

10297176.jpg

199 ms

hh.ru.svg

hh.ru.svg

683 ms

qr-telegram-anonymous-hhru.png

qr-telegram-anonymous-hhru.png

724 ms

10315084.png

10315084.png

218 ms

10314940.jpg

10314940.jpg

230 ms

10313759.jpg

10313759.jpg

236 ms

10315223.jpg

10315223.jpg

236 ms

10292133.jpg

10292133.jpg

228 ms

17846713.jpg

17846713.jpg

262 ms

17840702.jpg

17840702.jpg

316 ms

6513917.jpeg

6513917.jpeg

1182 ms

6253746.png

6253746.png

1193 ms

6293650.jpeg

6293650.jpeg

1591 ms

5979717.png

5979717.png

1607 ms

3041496.png

3041496.png

1190 ms

4251212.png

4251212.png

1358 ms

3950075.png

3950075.png

1363 ms

4085639.jpeg

4085639.jpeg

1358 ms

3764095.png

3764095.png

1529 ms

menu3x3__min_.svg

menu3x3__min_.svg

762 ms

hh.ru__min_.svg

hh.ru__min_.svg

785 ms

bg-applicant-supernova-2__min_.jpg

bg-applicant-supernova-2__min_.jpg

808 ms

app-store-buttons__min_.svg

app-store-buttons__min_.svg

798 ms

6e8ab99b8908d5d2b666.svg

6e8ab99b8908d5d2b666.svg

814 ms

messengers-hand__min_.svg

messengers-hand__min_.svg

852 ms

vk__min_.svg

vk__min_.svg

927 ms

telegram__min_.svg

telegram__min_.svg

949 ms

viber__min_.svg

viber__min_.svg

963 ms

bd36beda10a092dd913d.svg

bd36beda10a092dd913d.svg

942 ms

5d17e0a82dc1e383ed58.svg

5d17e0a82dc1e383ed58.svg

954 ms

fab2946c969a09b1aebf.svg

fab2946c969a09b1aebf.svg

996 ms

1154ab4b63b3f68e576c.svg

1154ab4b63b3f68e576c.svg

1061 ms

hit;HeadHunter

hit;HeadHunter

580 ms

sdk.js

sdk.js

1907 ms

openapi.c340c125c61ec5745ebb2a98626e46ab.js

openapi.c340c125c61ec5745ebb2a98626e46ab.js

236 ms

hit;HeadHunter

hit;HeadHunter

134 ms

rtrg

rtrg

135 ms

rtrg

rtrg

263 ms

Accessibility Review

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

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

arkhangelsk.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 Arkhangelsk.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 Arkhangelsk.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

arkhangelsk.hh.ru

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