4.8 sec in total
431 ms
3.9 sec
475 ms
Welcome to pushkin.hh.ru homepage info - get ready to check Pushkin Hh best content for Russia right away, or after learning these important things about pushkin.hh.ru
pushkin.hh.ru — сервис, который помогает найти работу и подобрать персонал в Пушкине более 20 лет! Создавайте резюме и откликайтесь на вакансии. Набирайте сотрудников и публикуйте вакансии.
Visit pushkin.hh.ruWe analyzed Pushkin.hh.ru page load time and found that the first response time was 431 ms and then it took 4.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
pushkin.hh.ru performance score
name
value
score
weighting
Value4.1 s
22/100
10%
Value5.8 s
15/100
25%
Value19.2 s
0/100
10%
Value11,120 ms
0/100
30%
Value0.409
24/100
15%
Value29.0 s
0/100
10%
431 ms
1402 ms
787 ms
658 ms
766 ms
Our browser made a total of 57 requests to load all elements on the main page. We found that 4% of them (2 requests) were addressed to the original Pushkin.hh.ru, 54% (31 requests) were made to I.hh.ru and 19% (11 requests) were made to Spb.hh.ru. The less responsive or slowest element that took the longest time to load (1.5 sec) relates to the external source Spb.hh.ru.
Page size can be reduced by 509.3 kB (53%)
965.2 kB
455.9 kB
In fact, the total size of Pushkin.hh.ru main page is 965.2 kB. 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 583.7 kB which makes up the majority of the site volume.
Potential reduce by 478.5 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 478.5 kB or 82% of the original size.
Potential reduce by 30.8 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. Pushkin Hh images are well optimized though.
Potential reduce by 1 B
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. This website has mostly compressed JavaScripts.
Number of requests can be reduced by 27 (49%)
55
28
The browser has sent 55 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pushkin 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 13 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
pushkin.hh.ru
431 ms
pushkin.hh.ru
1402 ms
magritte.08898d2e43f7848c2e82.css
787 ms
__bloko-imports_cf9c71eda381fb160e3608e7983a095c.css
658 ms
__globals_b9117df2a07deddea3f5613b335e82ea.css
766 ms
vendors.a65c87fe0063355e4057.css
454 ms
App.84cbd85c871c4e3a0a3c.css
618 ms
IndexPage.10c903d1fbd61bd48d7d.css
621 ms
vendors.84891e38a33e3fb54ca0.js
1305 ms
bloko.a2e61d3bf61390987ba7.js
1102 ms
magritte.768e54b92e9601abafef.js
1194 ms
1574.3770a8105b7d37bcde28.js
869 ms
2702.eecd68f91b72127878f1.js
935 ms
3068.0fb58eade7f4f038b7be.js
963 ms
3986.619847c6c141283a9979.js
1025 ms
IndexPage.bdc59d31f444a0c2eddd.js
1173 ms
6925.48fa317f36386fb1a708.js
1132 ms
runtime.9a9ae4981b5cf569559e.js
1204 ms
appEntryPoint.7a4c34a004ac978a66f9.js
1300 ms
6096529.jpeg
1166 ms
10322780.jpg
472 ms
hh.ru.svg
487 ms
qr-telegram-anonymous-hhru.png
526 ms
10322644.jpg
416 ms
10322324.jpg
417 ms
10322315.jpg
420 ms
10322878.jpg
419 ms
10322162.jpg
421 ms
17960480.jpg
531 ms
17960481.png
468 ms
7033482.png
1174 ms
3609163.jpeg
1180 ms
4048399.png
1185 ms
6662054.jpeg
1182 ms
5704032.png
1197 ms
2440973.png
1329 ms
1521274.jpeg
1339 ms
645671.jpeg
1512 ms
871802.jpeg
1347 ms
333545.png
1349 ms
menu3x3__min_.svg
514 ms
hh.ru__min_.svg
524 ms
big-promo-4233-L__min_.jpg
759 ms
big-promo-4233-logo__min_.svg
618 ms
6e8ab99b8908d5d2b666.svg
624 ms
messengers-hand__min_.svg
658 ms
vk__min_.svg
680 ms
telegram__min_.svg
690 ms
viber__min_.svg
782 ms
bd36beda10a092dd913d.svg
768 ms
5d17e0a82dc1e383ed58.svg
809 ms
fab2946c969a09b1aebf.svg
824 ms
hit;HeadHunter
681 ms
sdk.js
1180 ms
openapi.c340c125c61ec5745ebb2a98626e46ab.js
207 ms
rtrg
115 ms
rtrg
239 ms
pushkin.hh.ru accessibility score
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
[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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
Heading elements are not in a sequentially-descending order
Some elements have a [tabindex] value greater than 0
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
pushkin.hh.ru best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
pushkin.hh.ru SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
![]()
EN
![]()
RU
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pushkin.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 Pushkin.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.
pushkin.hh.ru
Open Graph data is detected on the main page of Pushkin Hh. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: