40.3 sec in total
2.5 sec
37.6 sec
249 ms
Click here to check amazing Timehr content. Otherwise, check out these important facts you probably never knew about timehr.com
2003年初创立至今,持续为千万级年薪老总职业导航,为成长型企业及超大型企业谋猎CEO、COO、CHO 、CFO、CIO、CMO、CTO等高端职位!猎头公司排名遥遥领先,于2014年荣膺中国猎头协会秘书长单位。
Visit timehr.comWe analyzed Timehr.com page load time and found that the first response time was 2.5 sec and then it took 37.9 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there were 4 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
timehr.com performance score
name
value
score
weighting
Value2.5 s
69/100
10%
Value14.8 s
0/100
25%
Value12.6 s
3/100
10%
Value660 ms
45/100
30%
Value0.73
6/100
15%
Value10.9 s
21/100
10%
2460 ms
3810 ms
8995 ms
4520 ms
2107 ms
Our browser made a total of 63 requests to load all elements on the main page. We found that 79% of them (50 requests) were addressed to the original Timehr.com, 11% (7 requests) were made to Myshifen.baidu.com and 5% (3 requests) were made to Hm.baidu.com. The less responsive or slowest element that took the longest time to load (20.5 sec) belongs to the original domain Timehr.com.
Page size can be reduced by 490.7 kB (67%)
728.4 kB
237.7 kB
In fact, the total size of Timehr.com main page is 728.4 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. 20% of websites need less resources to load. Javascripts take 380.7 kB which makes up the majority of the site volume.
Potential reduce by 41.4 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. This page needs HTML code to be minified as it can gain 5.6 kB, which is 11% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 41.4 kB or 80% of the original size.
Potential reduce by 166.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, Timehr needs image optimization as it can save up to 166.3 kB or 57% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 281.4 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 281.4 kB or 74% of the original size.
Potential reduce by 1.5 kB
CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Timehr.com needs all CSS files to be minified and compressed as it can save up to 1.5 kB or 70% of the original size.
Number of requests can be reduced by 20 (36%)
56
36
The browser has sent 56 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Timehr. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and as a result speed up the page load time.
timehr.com
2460 ms
www.timehr.com
3810 ms
yui-base.js
8995 ms
tbra.js
4520 ms
ads.js
2107 ms
css.css
4823 ms
mootools-1.2.3-core-yc.js
2611 ms
humanmessage.js
2429 ms
tbra04.js
4341 ms
1920824.js
5450 ms
_tt.gif
923 ms
bg.jpg
364 ms
topbg.jpg
325 ms
logo.jpg
991 ms
logo_right_bg.jpg
1440 ms
nav_01.gif
990 ms
nav_02.gif
1123 ms
nav_03.gif
734 ms
nav_04.gif
2749 ms
nav_05.gif
1114 ms
nav_06.gif
1304 ms
nav_bg.gif
2237 ms
mainnav_01.gif
1491 ms
hoticon.gif
1481 ms
menu_down_bg.jpg
1659 ms
www.timehr_slide.jpg
4868 ms
%E9%98%B3%E5%85%89%E5%8A%A1%E5%AE%9E%E5%8D%8F%E5%90%8C%E9%AB%98%E6%95%88(1).png
12393 ms
%E7%A7%98%E4%B9%A6%E9%95%BF.png
17356 ms
%E5%B9%B3%E5%92%8C%E6%89%A7%E7%9D%80%E6%BF%80%E6%83%85%E8%B6%85%E8%B6%8A.png
14448 ms
%E4%BA%BA%E4%BA%8B%E7%9B%B8%E5%AE%9C%E6%B6%A6%E9%80%9A%E7%A4%BE%E4%BC%9A(1).png
12737 ms
left_bg_top.jpg
20473 ms
more.jpg
5236 ms
left_bg_down.jpg
5602 ms
search.jpg
5947 ms
%E8%85%BE%E9%A9%B9%E8%BE%BE%E5%AE%98%E7%BD%91%E9%93%BE%E6%8E%A5(4).png
20473 ms
%E7%8C%8E%E5%A4%B4%E4%BC%9A%E6%A0%87.png
19120 ms
line01.jpg
13049 ms
more01.jpg
13360 ms
20150131083626824.jpg
15951 ms
blog.jpg
15345 ms
%E9%A6%96%E9%A1%B5%E6%99%AF%E7%B4%A0%E5%A5%87%E5%8D%9A%E5%AE%A2%E4%B8%8B%E6%96%B9%E5%9B%BE%E7%89%87.png
20471 ms
7183014A08B8260AF6340FC3DD986C01.jpg
20472 ms
tbra.css
17726 ms
left_bg_mid.jpg
389 ms
icon1.jpg
736 ms
tit_bg.jpg
1098 ms
tit_01.jpg
2487 ms
icon2.jpg
1704 ms
searchinput.jpg
1976 ms
seach_bg.gif
2239 ms
title_point01.gif
2531 ms
menubg01.jpg
2743 ms
ga.js
9 ms
__utm.gif
13 ms
h.js
728 ms
hm.gif
363 ms
entry.js
4420 ms
style.css
462 ms
buildnormal.js
805 ms
bg.gif
540 ms
send.gif
579 ms
message.gif
622 ms
input.gif
623 ms
timehr.com accessibility score
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
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Image elements do not have [alt] attributes
Links do not have a discernible name
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.
timehr.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
timehr.com 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
ZH
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Timehr.com can be misinterpreted by Google and other search engines. Our service has detected that Chinese 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 Timehr.com 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.
timehr.com
Open Graph description is not detected on the main page of Timehr. 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: