Tools & Wizards About Us
nizhnekamsk.hh.ru screenshot

Report Summary

  • 3

    Performance

    Renders faster than
    20% of other websites

  • 60

    Accessibility

    Visual factors better than
    that of 26% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

nizhnekamsk.hh.ru

Работа в Нижнекамске, поиск персонала и публикация вакансий - nizhnekamsk.hh.ru

Page Load Speed

6.9 sec in total

First Response

1.2 sec

Resources Loaded

5.2 sec

Page Rendered

471 ms

nizhnekamsk.hh.ru screenshot

About Website

Click here to check amazing Nizhnekamsk Hh content for Russia. Otherwise, check out these important facts you probably never knew about nizhnekamsk.hh.ru

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

Visit nizhnekamsk.hh.ru

Key Findings

We analyzed Nizhnekamsk.hh.ru page load time and found that the first response time was 1.2 sec and then it took 5.7 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

nizhnekamsk.hh.ru performance score

3

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.3 s

7/100

10%

LCP (Largest Contentful Paint)

Value25.5 s

0/100

25%

SI (Speed Index)

Value20.6 s

0/100

10%

TBT (Total Blocking Time)

Value11,930 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.559

12/100

15%

TTI (Time to Interactive)

Value30.2 s

0/100

10%

Network Requests Diagram

nizhnekamsk.hh.ru

1222 ms

nizhnekamsk.hh.ru

1375 ms

__bloko-imports_cf9c71eda381fb160e3608e7983a095c.css

429 ms

__globals_949338dca39ac980fd0a61ac280c0328.css

692 ms

84614.c7ba677fe4b9b8464bdb.css

568 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 Nizhnekamsk.hh.ru, 70% (53 requests) were made to I.hh.ru and 9% (7 requests) were made to Kazan.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 868.7 kB (38%)

Content Size

2.3 MB

After Optimization

1.4 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Nizhnekamsk.hh.ru main page is 2.3 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. Images take 1.5 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 648.0 kB

  • Original 765.6 kB
  • After minification 764.0 kB
  • After compression 117.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 648.0 kB or 85% of the original size.

Image Optimization

-15%

Potential reduce by 217.8 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, Nizhnekamsk Hh needs image optimization as it can save up to 217.8 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 46 (63%)

Requests Now

73

After Optimization

27

  • Images
  • JavaScript
  • CSS

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

nizhnekamsk.hh.ru

nizhnekamsk.hh.ru

1222 ms

nizhnekamsk.hh.ru

nizhnekamsk.hh.ru

1375 ms

__bloko-imports_cf9c71eda381fb160e3608e7983a095c.css

__bloko-imports_cf9c71eda381fb160e3608e7983a095c.css

429 ms

__globals_949338dca39ac980fd0a61ac280c0328.css

__globals_949338dca39ac980fd0a61ac280c0328.css

692 ms

84614.c7ba677fe4b9b8464bdb.css

84614.c7ba677fe4b9b8464bdb.css

568 ms

App.a6cd27d6fa5d4a836f19.css

App.a6cd27d6fa5d4a836f19.css

561 ms

7483.d0d1f4671237305f7079.css

7483.d0d1f4671237305f7079.css

450 ms

16127.26939db15825d9649a31.css

16127.26939db15825d9649a31.css

444 ms

30635.bf5f35133f40b10e42a5.css

30635.bf5f35133f40b10e42a5.css

619 ms

33132.afabb19b0ae31ff5b6f4.css

33132.afabb19b0ae31ff5b6f4.css

759 ms

51867.c2efcd75db4520017735.css

51867.c2efcd75db4520017735.css

1181 ms

74438.51266dd1bfd3f00b840e.css

74438.51266dd1bfd3f00b840e.css

746 ms

98277.7f3d891f73bbe60fd23d.css

98277.7f3d891f73bbe60fd23d.css

876 ms

AdvancedVacancySearch.711a9bed007c210e4444.css

AdvancedVacancySearch.711a9bed007c210e4444.css

784 ms

ApplicantNegotiations.b1608faa1f0243ee5d7e.css

ApplicantNegotiations.b1608faa1f0243ee5d7e.css

859 ms

ApplicantResumes.b22af4a9a712d9ea569d.css

ApplicantResumes.b22af4a9a712d9ea569d.css

929 ms

EmployersCompany.4cad24dbf6ab770eff71.css

EmployersCompany.4cad24dbf6ab770eff71.css

925 ms

EmployersList.e7e76eaaef960f46f576.css

EmployersList.e7e76eaaef960f46f576.css

950 ms

IndexPage.345a90f78f8fc8185bce.css

IndexPage.345a90f78f8fc8185bce.css

1040 ms

VacancySavedSearch.5c89d2be147808bcb6ec.css

VacancySavedSearch.5c89d2be147808bcb6ec.css

1048 ms

magritte.892340f3ef6fa774787a.js

magritte.892340f3ef6fa774787a.js

1257 ms

bloko.dd2cb2997dccb6ccc4d2.js

bloko.dd2cb2997dccb6ccc4d2.js

1278 ms

vendors.0a544bfacd81a54bba45.js

vendors.0a544bfacd81a54bba45.js

1425 ms

30635.bf5f35133f40b10e42a5.js

30635.bf5f35133f40b10e42a5.js

1239 ms

33132.afabb19b0ae31ff5b6f4.js

33132.afabb19b0ae31ff5b6f4.js

1361 ms

74438.51266dd1bfd3f00b840e.js

74438.51266dd1bfd3f00b840e.js

1491 ms

80871.10eec4f676f4186af71c.js

80871.10eec4f676f4186af71c.js

1413 ms

99586.ead7abafb749e8646881.js

99586.ead7abafb749e8646881.js

1431 ms

39440.8ff130c4e29e5e5ee5f5.js

39440.8ff130c4e29e5e5ee5f5.js

1447 ms

AdvancedVacancySearch.711a9bed007c210e4444.js

AdvancedVacancySearch.711a9bed007c210e4444.js

1671 ms

ApplicantNegotiations.b1608faa1f0243ee5d7e.js

ApplicantNegotiations.b1608faa1f0243ee5d7e.js

1588 ms

ApplicantResumes.b22af4a9a712d9ea569d.js

ApplicantResumes.b22af4a9a712d9ea569d.js

1593 ms

ApplicantSuitableVacancies.50696b360d8688077c9f.js

ApplicantSuitableVacancies.50696b360d8688077c9f.js

1590 ms

EmployersCompany.4cad24dbf6ab770eff71.js

EmployersCompany.4cad24dbf6ab770eff71.js

1614 ms

EmployersList.e7e76eaaef960f46f576.js

EmployersList.e7e76eaaef960f46f576.js

1662 ms

IndexPage.345a90f78f8fc8185bce.js

IndexPage.345a90f78f8fc8185bce.js

1787 ms

VacancyFavorite.e234bf3db3ea705c3399.js

VacancyFavorite.e234bf3db3ea705c3399.js

1757 ms

VacancySavedSearch.5c89d2be147808bcb6ec.js

VacancySavedSearch.5c89d2be147808bcb6ec.js

1760 ms

context.js

context.js

1036 ms

runtime.f6e448bf335f776449bd.js

runtime.f6e448bf335f776449bd.js

1347 ms

appEntryPoint.251a67fa0a380e41b9c9.js

appEntryPoint.251a67fa0a380e41b9c9.js

1396 ms

6865266.jpeg

6865266.jpeg

1552 ms

10316531.jpg

10316531.jpg

122 ms

hh.ru.svg

hh.ru.svg

650 ms

qr-telegram-anonymous-hhru.png

qr-telegram-anonymous-hhru.png

737 ms

10316285.jpg

10316285.jpg

138 ms

10315879.jpg

10315879.jpg

142 ms

10315084.png

10315084.png

140 ms

10316715.jpg

10316715.jpg

142 ms

17865697.png

17865697.png

340 ms

17858707.jpg

17858707.jpg

192 ms

6632221.png

6632221.png

1562 ms

884177.png

884177.png

1562 ms

6851778.png

6851778.png

1573 ms

1967894.png

1967894.png

1571 ms

6877066.png

6877066.png

1564 ms

1761214.png

1761214.png

1723 ms

menu3x3__min_.svg

menu3x3__min_.svg

711 ms

hh.ru__min_.svg

hh.ru__min_.svg

736 ms

bg-applicant-supernova-4__min_.jpg

bg-applicant-supernova-4__min_.jpg

781 ms

app-store-buttons__min_.svg

app-store-buttons__min_.svg

792 ms

6e8ab99b8908d5d2b666.svg

6e8ab99b8908d5d2b666.svg

790 ms

messengers-hand__min_.svg

messengers-hand__min_.svg

877 ms

vk__min_.svg

vk__min_.svg

876 ms

telegram__min_.svg

telegram__min_.svg

901 ms

viber__min_.svg

viber__min_.svg

946 ms

bd36beda10a092dd913d.svg

bd36beda10a092dd913d.svg

938 ms

5d17e0a82dc1e383ed58.svg

5d17e0a82dc1e383ed58.svg

1083 ms

fab2946c969a09b1aebf.svg

fab2946c969a09b1aebf.svg

1023 ms

1154ab4b63b3f68e576c.svg

1154ab4b63b3f68e576c.svg

1026 ms

hit;HeadHunter

hit;HeadHunter

542 ms

sdk.js

sdk.js

1312 ms

openapi.c340c125c61ec5745ebb2a98626e46ab.js

openapi.c340c125c61ec5745ebb2a98626e46ab.js

242 ms

hit;HeadHunter

hit;HeadHunter

135 ms

rtrg

rtrg

135 ms

rtrg

rtrg

269 ms

Accessibility Review

nizhnekamsk.hh.ru accessibility score

60

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

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

nizhnekamsk.hh.ru SEO score

91

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

nizhnekamsk.hh.ru

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