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

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

Page Load Speed

36.8 sec in total

First Response

2.2 sec

Resources Loaded

28.1 sec

Page Rendered

6.4 sec

fei263.blog.163.com screenshot

About Website

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

Visit fei263.blog.163.com

Key Findings

We analyzed Fei263.blog.163.com page load time and found that the first response time was 2.2 sec and then it took 34.5 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

fei263.blog.163.com performance score

0

Network Requests Diagram

fei263.blog.163.com

2234 ms

c.css

269 ms

b.css

4886 ms

6630133180817252049.jpg

19896 ms

xcode.png

183 ms

Our browser made a total of 64 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Fei263.blog.163.com, 28% (18 requests) were made to Os.blog.163.com and 16% (10 requests) were made to B.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 565.9 kB (52%)

Content Size

1.1 MB

After Optimization

515.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fei263.blog.163.com main page is 1.1 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. 25% 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.8 kB

  • Original 120.6 kB
  • After minification 120.5 kB
  • After compression 23.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 96.8 kB or 80% of the original size.

Image Optimization

-3%

Potential reduce by 9.2 kB

  • Original 328.8 kB
  • After minification 319.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. Fei 263 Blog 163 images are well optimized though.

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.4 kB

  • Original 182.4 kB
  • After minification 178.5 kB
  • After compression 33.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. Fei263.blog.163.com needs all CSS files to be minified and compressed as it can save up to 149.4 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 23 (40%)

Requests Now

57

After Optimization

34

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 57 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fei 263 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.

Network Requests Diagram

fei263.blog.163.com

fei263.blog.163.com

2234 ms

c.css

c.css

269 ms

b.css

b.css

4886 ms

6630133180817252049.jpg

6630133180817252049.jpg

19896 ms

xcode.png

xcode.png

183 ms

1.0.0.js

1.0.0.js

338 ms

pc.js

pc.js

195 ms

ph.js

ph.js

188 ms

5365476006059702679.jpg

5365476006059702679.jpg

9596 ms

icon.png

icon.png

201 ms

4816036851519825893.jpg

4816036851519825893.jpg

7670 ms

5365757481036413323.jpg

5365757481036413323.jpg

5588 ms

4816036851519825932.jpg

4816036851519825932.jpg

1865 ms

5365757481036413322.jpg

5365757481036413322.jpg

2681 ms

4816036851519825934.jpg

4816036851519825934.jpg

20160 ms

lnkbar.png

lnkbar.png

179 ms

image.png

image.png

182 ms

arrow24.png

arrow24.png

180 ms

newtopbaricon8.png

newtopbaricon8.png

180 ms

crossdomain.html

crossdomain.html

985 ms

crossdomain.html

crossdomain.html

1217 ms

crossdomain.html

crossdomain.html

762 ms

request.s

request.s

731 ms

analyse.png

analyse.png

19884 ms

ava.s

ava.s

1791 ms

loftericon.png

loftericon.png

857 ms

Photo4BlogBean.getPhotoDailyStatistic.dwr

Photo4BlogBean.getPhotoDailyStatistic.dwr

1549 ms

ava.s

ava.s

1015 ms

analyse.png

analyse.png

19573 ms

analytics.js

analytics.js

147 ms

collect

collect

56 ms

HomeBeanNew.getAccessStatistics.dwr

HomeBeanNew.getAccessStatistics.dwr

1038 ms

HomeBeanNew.getMonthStatistics.dwr

HomeBeanNew.getMonthStatistics.dwr

1059 ms

UserBeanNew.getVisitor.dwr

UserBeanNew.getVisitor.dwr

1097 ms

FeelingsBeanNew.getRecentFeelingCards.dwr

FeelingsBeanNew.getRecentFeelingCards.dwr

1503 ms

BlogBeanNew.getBlogClasses.dwr

BlogBeanNew.getBlogClasses.dwr

1525 ms

MusicBeanNew.setCopyrightMusicSessionToken.dwr

MusicBeanNew.setCopyrightMusicSessionToken.dwr

2347 ms

blogPhotoAd

blogPhotoAd

20416 ms

close_01.png

close_01.png

29 ms

top_bg.png

top_bg.png

71 ms

bottom_bg.png

bottom_bg.png

70 ms

left_bg.png

left_bg.png

69 ms

right_bg.png

right_bg.png

74 ms

left_top.png

left_top.png

72 ms

right_top.png

right_top.png

81 ms

left_bottom.png

left_bottom.png

120 ms

right_bottom.png

right_bottom.png

129 ms

shadow.png

shadow.png

37 ms

BgsBean.getBgsUserByUserId.dwr

BgsBean.getBgsUserByUserId.dwr

1026 ms

ava.s

ava.s

1711 ms

ava.s

ava.s

502 ms

ava.s

ava.s

2614 ms

ava.s

ava.s

2217 ms

ava.s

ava.s

922 ms

ava.s

ava.s

1006 ms

ava.s

ava.s

3167 ms

ava.s

ava.s

1515 ms

ava.s

ava.s

1927 ms

ava.s

ava.s

2085 ms

ava.s

ava.s

2588 ms

ava.s

ava.s

2805 ms

ava.s

ava.s

4070 ms

ava.s

ava.s

3124 ms

ava.s

ava.s

3517 ms

SEO Factors

fei263.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 Fei263.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 Fei263.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

fei263.blog.163.com

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