64.7 sec in total
1.6 sec
62.4 sec
688 ms
Visit haotor.com now to see the best up-to-date Haotor content for China and also check out these interesting facts you probably never knew about haotor.com
web-bt电影下载网-14-21年记录-历史百度权重5-外链超多
Visit haotor.comWe analyzed Haotor.com page load time and found that the first response time was 1.6 sec and then it took 63.1 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 16 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
haotor.com performance score
name
value
score
weighting
Value2.7 s
58/100
10%
Value3.1 s
74/100
25%
Value6.4 s
40/100
10%
Value30 ms
100/100
30%
Value0.447
20/100
15%
Value3.0 s
96/100
10%
1595 ms
9715 ms
907 ms
3452 ms
20266 ms
Our browser made a total of 154 requests to load all elements on the main page. We found that 49% of them (75 requests) were addressed to the original Haotor.com, 8% (12 requests) were made to Bdimg.share.baidu.com and 3% (5 requests) were made to Vip4.rwjfs.com. The less responsive or slowest element that took the longest time to load (20.3 sec) belongs to the original domain Haotor.com.
Page size can be reduced by 477.7 kB (34%)
1.4 MB
936.6 kB
In fact, the total size of Haotor.com main page is 1.4 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. 40% of websites need less resources to load. Images take 763.3 kB which makes up the majority of the site volume.
Potential reduce by 100.0 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 14.0 kB, which is 12% 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 100.0 kB or 85% of the original size.
Potential reduce by 51.6 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. Haotor images are well optimized though.
Potential reduce by 296.6 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 296.6 kB or 60% of the original size.
Potential reduce by 29.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. Haotor.com needs all CSS files to be minified and compressed as it can save up to 29.5 kB or 74% of the original size.
Number of requests can be reduced by 61 (46%)
134
73
The browser has sent 134 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Haotor. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 45 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
haotor.com
1595 ms
www.haotor.com
9715 ms
wp-emoji-release.min.js
907 ms
style.css
3452 ms
jquery.min.js
20266 ms
slider.js
5453 ms
jquery.cycle.js
4956 ms
hoverIntent.js
2175 ms
superfish.js
15039 ms
jquery-ui.tabs.min.js
5726 ms
jquery.lazyload.js
4008 ms
DD_belatedPNG_0.0.8a-min.js
6536 ms
IE6Top.js
7202 ms
c.js
887 ms
i2.php
1688 ms
glider.css
2466 ms
ie6.css
2844 ms
ie7.css
2917 ms
cpc2_i.js
1801 ms
cpv_fm_r.js
1205 ms
logo.png
5904 ms
fenxiang.png
2415 ms
timthumb.php
3163 ms
timthumb.php
2705 ms
timthumb.php
3217 ms
timthumb.php
17165 ms
timthumb.php
12770 ms
timthumb.php
17065 ms
timthumb.php
8844 ms
timthumb.php
12286 ms
timthumb.php
8217 ms
timthumb.php
9428 ms
timthumb.php
10489 ms
timthumb.php
17778 ms
timthumb.php
10932 ms
timthumb.php
11375 ms
timthumb.php
12482 ms
timthumb.php
12827 ms
timthumb.php
13839 ms
timthumb.php
15914 ms
timthumb.php
18044 ms
timthumb.php
16262 ms
timthumb.php
17581 ms
timthumb.php
17137 ms
timthumb.php
19975 ms
timthumb.php
19323 ms
timthumb.php
19974 ms
timthumb.php
19975 ms
timthumb.php
19975 ms
timthumb.php
19975 ms
timthumb.php
19976 ms
timthumb.php
19975 ms
timthumb.php
19975 ms
timthumb.php
19976 ms
timthumb.php
19975 ms
timthumb.php
19976 ms
share.js
5131 ms
save_log.php
376 ms
ha0000.php
771 ms
mcqm
954 ms
rich_media_show_bottom_bg.gif
887 ms
logo.png
358 ms
jsc1.ashx
5530 ms
iiadlogodl.png
1586 ms
jsc1.ashx
1696 ms
couplet_close.jpg
2358 ms
z_stat.php
977 ms
mcqm
1052 ms
switch_standard.css
924 ms
stat.htm
180 ms
core.php
1212 ms
adPic.new.20150909.min.js
82 ms
adx.php
1693 ms
switch.js
2957 ms
rBEhWlJYrAEIAAAAAAACetYAYQwAAECuwP__W4AAAKS951.png
113 ms
5707eb01N6d56c747.jpg
163 ms
bot-patch.min.js
65 ms
click.min.js
108 ms
timthumb.php
19041 ms
9.gif
1644 ms
pic.gif
816 ms
ir.ashx
2775 ms
timthumb.php
20277 ms
timthumb.php
19821 ms
timthumb.php
18490 ms
55e40d3fN2a01189f.png
127 ms
app.gif
732 ms
rv1.ashx
1625 ms
tj.yule8.net
893 ms
share_api.js
363 ms
share_view.js
726 ms
timthumb.php
18099 ms
tangram.js
4223 ms
api_base.js
741 ms
z_stat.php
1407 ms
view_base.js
490 ms
close.png
921 ms
v2.ashx
4288 ms
logo.png
4514 ms
stat.htm
224 ms
core.php
276 ms
fx.htm
1673 ms
timthumb.php
15415 ms
logger.js
403 ms
timthumb.php
20138 ms
timthumb.php
13995 ms
Wno.html
18 ms
z_stat.php
781 ms
z_stat.php
1267 ms
partners.js
385 ms
share_style1_32.css
432 ms
data.js
381 ms
stat.htm
195 ms
core.php
284 ms
timthumb.php
14072 ms
9.gif
1127 ms
getnum
7664 ms
icons_1_32.png
4594 ms
sc.png
598 ms
320-1.jpg
9898 ms
stat.htm
165 ms
core.php
276 ms
timthumb.php
13689 ms
index
1938 ms
timthumb.php
14691 ms
app.gif
979 ms
timthumb.php
13996 ms
timthumb.php
13220 ms
b0a79c606049469a8e0160dd038d7e1d.jpg
20212 ms
timthumb.php
12966 ms
g-207450.v-692774
885 ms
timthumb.php
13597 ms
statIwt_www_new-min.js
58 ms
vasd_pv.js
4 ms
javascript
1920 ms
reportVv.js
6 ms
core-min.js
78 ms
irt
1417 ms
3984 ms
timthumb.php
13365 ms
timthumb.php
13911 ms
timthumb.php
13717 ms
timthumb.php
11441 ms
timthumb.php
15944 ms
timthumb.php
16651 ms
timthumb.php
12325 ms
ico-bullet.gif
12595 ms
play
522 ms
blank.gif
19 ms
o.htm
1066 ms
wh.js
768 ms
ac.js
564 ms
fp.htm
1466 ms
fp.htm
474 ms
haotor.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.
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.
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
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.
haotor.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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
haotor.com SEO score
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
EN
ZH
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Haotor.com 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 Chinese language. Our system also found out that Haotor.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.
haotor.com
Open Graph description is not detected on the main page of Haotor. 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: