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

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

Page Load Speed

26.7 sec in total

First Response

2 sec

Resources Loaded

23.7 sec

Page Rendered

1.1 sec

wlt436.blog.163.com screenshot

About Website

Click here to check amazing Wlt 436 Blog 163 content for China. Otherwise, check out these important facts you probably never knew about wlt436.blog.163.com

Visit wlt436.blog.163.com

Key Findings

We analyzed Wlt436.blog.163.com page load time and found that the first response time was 2 sec and then it took 24.8 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 was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

wlt436.blog.163.com performance score

0

Network Requests Diagram

wlt436.blog.163.com

1964 ms

c.css

25 ms

b.css

846 ms

6630133180817252049.jpg

7131 ms

xcode.png

206 ms

Our browser made a total of 52 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Wlt436.blog.163.com, 23% (12 requests) were made to Img.bimg.126.net and 21% (11 requests) were made to B.bst.126.net. The less responsive or slowest element that took the longest time to load (19.6 sec) relates to the external source Imglf2.nosdn.127.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 566.3 kB (68%)

Content Size

837.1 kB

After Optimization

270.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Wlt436.blog.163.com main page is 837.1 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. 30% of websites need less resources to load. Javascripts take 449.0 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 96.7 kB

  • Original 121.6 kB
  • After minification 121.6 kB
  • After compression 24.9 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 96.7 kB or 80% of the original size.

Image Optimization

-11%

Potential reduce by 9.2 kB

  • Original 83.4 kB
  • After minification 74.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, Wlt 436 Blog 163 needs image optimization as it can save up to 9.2 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-69%

Potential reduce by 310.5 kB

  • Original 449.0 kB
  • After minification 449.0 kB
  • After compression 138.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 310.5 kB or 69% of the original size.

CSS Optimization

-82%

Potential reduce by 149.9 kB

  • Original 183.1 kB
  • After minification 179.1 kB
  • After compression 33.1 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. Wlt436.blog.163.com needs all CSS files to be minified and compressed as it can save up to 149.9 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 30 (60%)

Requests Now

50

After Optimization

20

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 50 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Wlt 436 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 as a result speed up the page load time.

Network Requests Diagram

wlt436.blog.163.com

wlt436.blog.163.com

1964 ms

c.css

c.css

25 ms

b.css

b.css

846 ms

6630133180817252049.jpg

6630133180817252049.jpg

7131 ms

xcode.png

xcode.png

206 ms

1.0.0.js

1.0.0.js

208 ms

pc.js

pc.js

238 ms

ph.js

ph.js

289 ms

588845651279433262.jpg

588845651279433262.jpg

1010 ms

icon.png

icon.png

155 ms

1175158027768671087.jpg

1175158027768671087.jpg

2151 ms

5637943783515005557.jpg

5637943783515005557.jpg

781 ms

638948197133914861.jpg

638948197133914861.jpg

784 ms

1175158027768671084.jpg

1175158027768671084.jpg

783 ms

1175158027768671083.jpg

1175158027768671083.jpg

9151 ms

1175158027768671090.jpg

1175158027768671090.jpg

2001 ms

1175158027768671089.jpg

1175158027768671089.jpg

1147 ms

1175158027768671153.jpg

1175158027768671153.jpg

1148 ms

5383208929591883518.jpg

5383208929591883518.jpg

1271 ms

5383208929591883517.jpg

5383208929591883517.jpg

1535 ms

1175158027768671085.jpg

1175158027768671085.jpg

1535 ms

lnkbar.png

lnkbar.png

166 ms

image.png

image.png

186 ms

arrow24.png

arrow24.png

242 ms

newtopbaricon8.png

newtopbaricon8.png

243 ms

crossdomain.html

crossdomain.html

1037 ms

crossdomain.html

crossdomain.html

803 ms

request.s

request.s

946 ms

analyse.png

analyse.png

10548 ms

empty.png

empty.png

43 ms

ava.s

ava.s

436 ms

crossdomain.html

crossdomain.html

728 ms

ava.s

ava.s

795 ms

analyse.png

analyse.png

798 ms

analytics.js

analytics.js

151 ms

collect

collect

57 ms

MusicBeanNew.setCopyrightMusicSessionToken.dwr

MusicBeanNew.setCopyrightMusicSessionToken.dwr

1114 ms

blogPhotoAd

blogPhotoAd

376 ms

close_01.png

close_01.png

91 ms

top_bg.png

top_bg.png

165 ms

bottom_bg.png

bottom_bg.png

167 ms

left_bg.png

left_bg.png

229 ms

right_bg.png

right_bg.png

241 ms

left_top.png

left_top.png

257 ms

right_top.png

right_top.png

256 ms

left_bottom.png

left_bottom.png

261 ms

right_bottom.png

right_bottom.png

257 ms

shadow.png

shadow.png

195 ms

HomeBeanNew.getAccessStatistics.dwr

HomeBeanNew.getAccessStatistics.dwr

1194 ms

FeelingsBeanNew.getRecentFeelingCards.dwr

FeelingsBeanNew.getRecentFeelingCards.dwr

1531 ms

WEJTRnhkaWZlcXFZRmYra1AzTnhyQnBYUlNQTVg0blpqanJTQVdRZnYzazNqaVFpL1Y5aitRPT0.jpg

WEJTRnhkaWZlcXFZRmYra1AzTnhyQnBYUlNQTVg0blpqanJTQVdRZnYzazNqaVFpL1Y5aitRPT0.jpg

19559 ms

BgsBean.getBgsUserByUserId.dwr

BgsBean.getBgsUserByUserId.dwr

1130 ms

SEO Factors

wlt436.blog.163.com SEO score

0

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 Wlt436.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 Wlt436.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

wlt436.blog.163.com

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