33 sec in total
3.5 sec
28.3 sec
1.2 sec
Welcome to huzhangao.blog.163.com homepage info - get ready to check Huzhangao Blog 163 best content for China right away, or after learning these important things about huzhangao.blog.163.com
Visit huzhangao.blog.163.comWe analyzed Huzhangao.blog.163.com page load time and found that the first response time was 3.5 sec and then it took 29.4 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 6 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
huzhangao.blog.163.com performance score
name
value
score
weighting
Value4.5 s
15/100
10%
Value10.2 s
0/100
25%
Value28.7 s
0/100
10%
Value2,750 ms
3/100
30%
Value0.751
6/100
15%
Value10.4 s
24/100
10%
3525 ms
22 ms
15 ms
12 ms
22 ms
Our browser made a total of 123 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Huzhangao.blog.163.com, 20% (24 requests) were made to B.bst.126.net and 13% (16 requests) were made to Os.blog.163.com. The less responsive or slowest element that took the longest time to load (20.4 sec) relates to the external source Lofter.com.
Page size can be reduced by 693.5 kB (44%)
1.6 MB
892.8 kB
In fact, the total size of Huzhangao.blog.163.com main page is 1.6 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 688.6 kB which makes up the majority of the site volume.
Potential reduce by 219.8 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 219.8 kB or 82% of the original size.
Potential reduce by 14.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. Huzhangao Blog 163 images are well optimized though.
Potential reduce by 310.5 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 310.5 kB or 69% of the original size.
Potential reduce by 148.7 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. Huzhangao.blog.163.com needs all CSS files to be minified and compressed as it can save up to 148.7 kB or 82% of the original size.
Number of requests can be reduced by 42 (41%)
103
61
The browser has sent 103 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Huzhangao Blog 163. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and as a result speed up the page load time.
huzhangao.blog.163.com
3525 ms
c.css
22 ms
nb.css
15 ms
gp_24.jpg
12 ms
gp_02.jpg
22 ms
gp_07.jpg
13 ms
gp_06.jpg
19 ms
gp_09.jpg
19 ms
gp_11.jpg
19 ms
gp_13.jpg
18 ms
gp_16.jpg
25 ms
gp_19.jpg
19 ms
gp_17.jpg
20 ms
icon.png
21 ms
gp_22.jpg
29 ms
lnkbar.png
28 ms
6630133180817252049.jpg
519 ms
1.0.0.js
116 ms
image.png
24 ms
arrow24.png
23 ms
newtopbaricon8.png
23 ms
xcode.png
19 ms
pc.js
44 ms
ph.js
41 ms
crossdomain.html
846 ms
crossdomain.html
536 ms
request.s
471 ms
analyse.png
19621 ms
empty.png
92 ms
6598071421750816566.jpg
1047 ms
4897946069842590386.jpg
2384 ms
ava.s
750 ms
Photo4BlogBean.getPhotoDailyStatistic.dwr
526 ms
crossdomain.html
580 ms
622904123478566331.jpg
1887 ms
2742973648063234353.jpg
858 ms
4848124998965166123.jpg
19515 ms
analyse.png
20373 ms
analytics.js
93 ms
collect
58 ms
SetupBeanNew.getCustomModulesData.dwr
2473 ms
HomeBeanNew.getAccessStatistics.dwr
1227 ms
HomeBeanNew.getMonthStatistics.dwr
1234 ms
HomeBeanNew.getWeatherCityCode.dwr
1345 ms
UserBeanNew.getVisitor.dwr
2045 ms
MusicBeanNew.setCopyrightMusicSessionToken.dwr
4664 ms
blogPhotoAd
20165 ms
close_01.png
16 ms
top_bg.png
12 ms
bottom_bg.png
36 ms
left_bg.png
10 ms
right_bg.png
21 ms
left_top.png
22 ms
right_top.png
20 ms
left_bottom.png
22 ms
right_bottom.png
21 ms
shadow.png
29 ms
BgsBean.getBgsUserByUserId.dwr
960 ms
.gif
3728 ms
ava.s
381 ms
ava.s
1912 ms
ava.s
739 ms
ava.s
741 ms
ava.s
874 ms
ava.s
929 ms
ava.s
980 ms
ava.s
1065 ms
ava.s
2642 ms
ava.s
1227 ms
ava.s
1376 ms
ava.s
1452 ms
ava.s
1384 ms
ava.s
1622 ms
ava.s
1835 ms
20-colourflow-rss-feeds-icon.jpg
1221 ms
icon_subscribe_zhuaxia_fs.gif
20027 ms
icon_subshot01_xianguo.gif
20029 ms
xuanchuan11.gif
20223 ms
1695323784728475433.jpg
1087 ms
icon_subscribe_pageflakes_fs.gif
20019 ms
icon_subscribe_rojo_fs.gif
20019 ms
icon_subscribe_google_fs.gif
20019 ms
icon_subscribe_bloglines_fs.gif
20019 ms
1697857059518871344.jpg
2655 ms
3112268817489915304.jpg
2693 ms
2302183834516643994.jpg
3322 ms
icon_subshot02_youdao.gif
20019 ms
icon_subshot02_qq.gif
20020 ms
2509912367346995787.png
88 ms
6598217656796715591.jpg
631 ms
10.png
15 ms
2114440025051759143.jpg
1613 ms
3278902003702744808.jpg
517 ms
2574088662020029726.jpg
1034 ms
812055307811987373.jpg
1606 ms
991917817929389246.jpg
988 ms
2437573298315365368.jpg
1539 ms
2426314299246935075.jpg
1444 ms
1667739237012084219.jpg
775 ms
69805794225372777.jpg
913 ms
339458821913404769.jpg
1138 ms
812055307811987362.jpg
1589 ms
2114440025051759135.jpg
1589 ms
2114440025051759147.jpg
1592 ms
2114440025051759138.jpg
1596 ms
112589990686359206.gif
1030 ms
0155.gif
5375 ms
2007021220044436009.gif
15476 ms
3702803318628988464.jpg
2522 ms
2389159602320879890.gif
1370 ms
3867747654981170220.gif
1967 ms
1860831071035997444.jpg
432 ms
965740645095320060.gif
1478 ms
1379790335837496376.jpg
1660 ms
2357071454975702361.jpg
440 ms
204.gif
20230 ms
88.gif
466 ms
39406496740576429.jpg
1833 ms
912541874497172501.jpg
539 ms
339458821913404769.jpg
528 ms
4806748177288779738.jpg
897 ms
1480276902522728705.jpg
582 ms
2827697616036524287.jpg
939 ms
huzhangao.blog.163.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.
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
Form elements do not have associated labels
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.
huzhangao.blog.163.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Browser errors were logged to the console
huzhangao.blog.163.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
robots.txt is not valid
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
ZH
GBK
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Huzhangao.blog.163.com can be misinterpreted by Google and other search engines. Our service has detected that Chinese is used on the page, and it matches the claimed language. Our system also found out that Huzhangao.blog.163.com main page’s claimed encoding is gbk. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
huzhangao.blog.163.com
Open Graph description is not detected on the main page of Huzhangao Blog 163. 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: