Tools & Wizards About Us
huanfu.blog.163.com screenshot

Report Summary

  • 13

    Performance

    Renders faster than
    25% of other websites

  • 38

    Accessibility

    Visual factors better than
    that of 18% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

Page Load Speed

32.9 sec in total

First Response

3 sec

Resources Loaded

27.4 sec

Page Rendered

2.6 sec

huanfu.blog.163.com screenshot

About Website

Visit huanfu.blog.163.com now to see the best up-to-date Huanfu Blog 163 content for China and also check out these interesting facts you probably never knew about huanfu.blog.163.com

Visit huanfu.blog.163.com

Key Findings

We analyzed Huanfu.blog.163.com page load time and found that the first response time was 3 sec and then it took 29.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there were 5 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

huanfu.blog.163.com performance score

13

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.0 s

9/100

10%

LCP (Largest Contentful Paint)

Value7.2 s

5/100

25%

SI (Speed Index)

Value12.2 s

3/100

10%

TBT (Total Blocking Time)

Value1,380 ms

16/100

30%

CLS (Cumulative Layout Shift)

Value0.749

6/100

15%

TTI (Time to Interactive)

Value7.6 s

46/100

10%

Network Requests Diagram

huanfu.blog.163.com

2964 ms

c.css

162 ms

b.css

3159 ms

r

884 ms

ava.s

4723 ms

Our browser made a total of 75 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Huanfu.blog.163.com, 13% (10 requests) were made to B.bst.126.net and 9% (7 requests) were made to B2.bst.126.net. The less responsive or slowest element that took the longest time to load (20.4 sec) relates to the external source Lofter.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 617.4 kB (21%)

Content Size

3.0 MB

After Optimization

2.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Huanfu.blog.163.com main page is 3.0 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. 35% of websites need less resources to load. Images take 2.1 MB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 74.4 kB

  • Original 97.3 kB
  • After minification 97.1 kB
  • After compression 23.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. 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 74.4 kB or 76% of the original size.

Image Optimization

-1%

Potential reduce by 29.9 kB

  • Original 2.1 MB
  • After minification 2.1 MB

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. Huanfu Blog 163 images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 358.3 kB

  • Original 521.3 kB
  • After minification 521.3 kB
  • After compression 163.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 358.3 kB or 69% of the original size.

CSS Optimization

-82%

Potential reduce by 154.8 kB

  • Original 189.8 kB
  • After minification 184.5 kB
  • After compression 35.0 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. Huanfu.blog.163.com needs all CSS files to be minified and compressed as it can save up to 154.8 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 26 (41%)

Requests Now

64

After Optimization

38

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 64 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Huanfu 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 9 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

huanfu.blog.163.com

huanfu.blog.163.com

2964 ms

c.css

c.css

162 ms

b.css

b.css

3159 ms

r

r

884 ms

ava.s

ava.s

4723 ms

rec.s

rec.s

1001 ms

6630133180817252049.jpg

6630133180817252049.jpg

1935 ms

xcode.png

xcode.png

146 ms

1.0.0.js

1.0.0.js

1451 ms

pc.js

pc.js

224 ms

ph.js

ph.js

195 ms

reset.css

reset.css

964 ms

ad.css

ad.css

964 ms

791a66e3e7f34db1a832227f3b0dac3c.jpg

791a66e3e7f34db1a832227f3b0dac3c.jpg

3002 ms

jquery-1.4.2.js

jquery-1.4.2.js

988 ms

scroll.js

scroll.js

967 ms

b43e69c57df74208b0db31e5410e4cc6.jpg

b43e69c57df74208b0db31e5410e4cc6.jpg

2371 ms

63c8416881bd46b48aac2484c107ea40.jpg

63c8416881bd46b48aac2484c107ea40.jpg

2369 ms

49ae1212f7704131a8348100ac5e50cd.jpg

49ae1212f7704131a8348100ac5e50cd.jpg

2363 ms

0ac6222e1a524c5c847cc29a744c7860.jpg

0ac6222e1a524c5c847cc29a744c7860.jpg

2372 ms

58ac21fd837d4f4eb33e0b842ab19d93.jpg

58ac21fd837d4f4eb33e0b842ab19d93.jpg

2371 ms

3149704989409280442.jpg

3149704989409280442.jpg

899 ms

icon.png

icon.png

143 ms

lnkbar.png

lnkbar.png

146 ms

image.png

image.png

145 ms

arrow24.png

arrow24.png

142 ms

newtopbaricon8.png

newtopbaricon8.png

146 ms

5123689001081131504.jpg

5123689001081131504.jpg

1733 ms

3741928340408500595.jpg

3741928340408500595.jpg

2269 ms

logo-24.png

logo-24.png

77 ms

discount-1.png

discount-1.png

297 ms

crossdomain.html

crossdomain.html

714 ms

crossdomain.html

crossdomain.html

1113 ms

request.s

request.s

1505 ms

analyse.png

analyse.png

19869 ms

crossdomain.html

crossdomain.html

864 ms

163NewsList.do

163NewsList.do

806 ms

mailEntry.do

mailEntry.do

19811 ms

analyse.png

analyse.png

19601 ms

analytics.js

analytics.js

80 ms

collect

collect

34 ms

imgsize.ph.126.net

imgsize.ph.126.net

482 ms

BlogBeanNew.getBlogsNewTheme.dwr

BlogBeanNew.getBlogsNewTheme.dwr

2191 ms

MusicBeanNew.setCopyrightMusicSessionToken.dwr

MusicBeanNew.setCopyrightMusicSessionToken.dwr

1133 ms

blogPhotoAd

blogPhotoAd

20394 ms

close_01.png

close_01.png

32 ms

top_bg.png

top_bg.png

45 ms

bottom_bg.png

bottom_bg.png

44 ms

left_bg.png

left_bg.png

48 ms

right_bg.png

right_bg.png

47 ms

left_top.png

left_top.png

46 ms

right_top.png

right_top.png

46 ms

left_bottom.png

left_bottom.png

75 ms

right_bottom.png

right_bottom.png

75 ms

shadow.png

shadow.png

28 ms

6630437745537827087.jpg

6630437745537827087.jpg

2346 ms

6631284369490649607.jpg

6631284369490649607.jpg

1972 ms

6631285469000834014.jpg

6631285469000834014.jpg

3310 ms

6597853718446607928.jpg

6597853718446607928.jpg

5114 ms

3073706745698128676.jpg

3073706745698128676.jpg

4258 ms

6597201708051518033.jpg

6597201708051518033.jpg

8517 ms

1024568915244441164.jpg

1024568915244441164.jpg

3043 ms

1297318167676989327.jpg

1297318167676989327.jpg

5645 ms

6630877550189632967.jpg

6630877550189632967.jpg

1895 ms

6631311857281347878.jpg

6631311857281347878.jpg

1367 ms

6630322296816909752.jpg

6630322296816909752.jpg

2646 ms

6597192911958317953.jpg

6597192911958317953.jpg

19627 ms

2779846870012446589.jpg

2779846870012446589.jpg

1982 ms

6630782992188356545.jpg

6630782992188356545.jpg

3265 ms

3342233873562393397.jpg

3342233873562393397.jpg

1435 ms

6597161026121616751.jpg

6597161026121616751.jpg

1980 ms

2503156967905431751.jpg

2503156967905431751.jpg

1135 ms

6630913834072070742.jpg

6630913834072070742.jpg

3002 ms

6630876450676631967.jpg

6630876450676631967.jpg

2250 ms

i-htJMM34.jpg

i-htJMM34.jpg

70 ms

Accessibility Review

huanfu.blog.163.com accessibility score

38

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

High

<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

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

huanfu.blog.163.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

High

Browser errors were logged to the console

SEO Factors

huanfu.blog.163.com SEO score

69

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

High

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

High

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    ZH

  • Language Claimed

    ZH

  • Encoding

    GBK

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Huanfu.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 Huanfu.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.

Social Sharing Optimization

huanfu.blog.163.com

Open Graph description is not detected on the main page of Huanfu 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: