7 sec in total
386 ms
6.3 sec
361 ms
Click here to check amazing Tatarstan Hh content for Russia. Otherwise, check out these important facts you probably never knew about tatarstan.hh.ru
kazan.hh.ru — сервис, который помогает найти работу и подобрать персонал в Казани более 20 лет! Создавайте резюме и откликайтесь на вакансии. Набирайте сотрудников и публикуйте вакансии.
Visit tatarstan.hh.ruWe analyzed Tatarstan.hh.ru page load time and found that the first response time was 386 ms and then it took 6.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
tatarstan.hh.ru performance score
name
value
score
weighting
Value5.2 s
9/100
10%
Value17.7 s
0/100
25%
Value14.4 s
1/100
10%
Value4,990 ms
1/100
30%
Value0.3
40/100
15%
Value23.7 s
1/100
10%
386 ms
567 ms
621 ms
169 ms
141 ms
Our browser made a total of 85 requests to load all elements on the main page. We found that 6% of them (5 requests) were addressed to the original Tatarstan.hh.ru, 28% (24 requests) were made to Hhcdn.ru and 19% (16 requests) were made to I.hh.ru. The less responsive or slowest element that took the longest time to load (1.5 sec) relates to the external source I.hh.ru.
Page size can be reduced by 161.0 kB (23%)
709.0 kB
548.0 kB
In fact, the total size of Tatarstan.hh.ru main page is 709.0 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. 50% of websites need less resources to load. HTML takes 301.6 kB which makes up the majority of the site volume.
Potential reduce by 132.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 132.6 kB or 44% of the original size.
Potential reduce by 25.4 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, Tatarstan Hh needs image optimization as it can save up to 25.4 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 3.0 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. This website has mostly compressed JavaScripts.
Number of requests can be reduced by 40 (56%)
71
31
The browser has sent 71 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Tatarstan 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 24 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
tatarstan.hh.ru
386 ms
tatarstan.hh.ru
567 ms
621 ms
revalidate
169 ms
bind
141 ms
verify
140 ms
tatarstan.hh.ru
539 ms
__bloko-imports_75af00bfff0fb372bc6148ef48062bf8.css
729 ms
__globals-other_2feeb4ba52a679ca810e920654e07e9b.css
765 ms
__globals_fce0f8d8c6a50ea651fa3e276a272142.css
946 ms
__dbdf5a6e65f5134238e36190992a8953.js
1504 ms
pv
654 ms
pv
659 ms
pv
636 ms
pv
622 ms
pv
642 ms
151184.png
339 ms
hh.ru-small.svg
146 ms
16383190.png
142 ms
16382233.png
142 ms
16382235.png
140 ms
16381062.png
141 ms
16383186.png
336 ms
16383180.png
334 ms
16383050.png
337 ms
16383493.jpg
336 ms
__fonts_daae654200c3b06443b7fc9c8b905d38.css
905 ms
hh.ru.svg
139 ms
select.svg
210 ms
search.svg
295 ms
navi-sprite.png
300 ms
anonymous-background-man.jpg
921 ms
social-icons.svg
435 ms
16382501.jpg
422 ms
16380467.jpg
557 ms
57702.html
395 ms
154718.jpg
677 ms
online.png
383 ms
store.svg
527 ms
73857.html
782 ms
footer-social.svg
495 ms
hit;HeadHunter
641 ms
dc.js
199 ms
pack.min.js
626 ms
beacon.js
184 ms
fbevents.js
368 ms
watch.js
1 ms
rtrg
621 ms
code.js
806 ms
pv
327 ms
pv
330 ms
inpage_linkid.js
44 ms
__utm.gif
18 ms
__utm.gif
30 ms
sjs.php
503 ms
149 ms
253 ms
runtime.js
58 ms
16349185.jpg
151 ms
16289153.jpg
143 ms
top100.scn
692 ms
IB47O6kwxfq15Ok7HjzGeN+VHrRA1enWH+sjPzE81WL0BTrnBII=
13 ms
1r3UrPcLMlYEJQ==
10 ms
counter
159 ms
ajs.php
95 ms
ajs.php
212 ms
ajs.php
341 ms
show_ads.js
62 ms
lg.php
266 ms
zrt_lookup.html
170 ms
show_ads_impl.js
84 ms
lg.php
148 ms
ads
218 ms
ads
275 ms
osd.js
29 ms
ads
216 ms
lg.php
116 ms
ac.php
379 ms
ac.php
368 ms
ac.php
364 ms
BannerHandler.js
139 ms
lg.php
93 ms
lg.php
94 ms
lg.php
92 ms
pv
134 ms
tatarstan.hh.ru accessibility score
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
<frame> or <iframe> elements do not have a title
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
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.
tatarstan.hh.ru best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Registers an unload listener
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
Issues were logged in the Issues panel in Chrome Devtools
tatarstan.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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tatarstan.hh.ru can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Tatarstan.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.
tatarstan.hh.ru
Open Graph description is not detected on the main page of Tatarstan Hh. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: