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

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

Page Load Speed

27.8 sec in total

First Response

2.5 sec

Resources Loaded

24.8 sec

Page Rendered

512 ms

ndzkyl.blog.163.com screenshot

About Website

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

Visit ndzkyl.blog.163.com

Key Findings

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

Performance Metrics

ndzkyl.blog.163.com performance score

0

Network Requests Diagram

ndzkyl.blog.163.com

2458 ms

c.css

50 ms

b.css

1817 ms

4848124998881530162.jpg

1113 ms

6630133180817252049.jpg

1668 ms

Our browser made a total of 90 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Ndzkyl.blog.163.com, 26% (23 requests) were made to Os.blog.163.com and 13% (12 requests) were made to B.bst.126.net. The less responsive or slowest element that took the longest time to load (20.2 sec) relates to the external source Api.blog.163.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 636.5 kB (63%)

Content Size

1.0 MB

After Optimization

374.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ndzkyl.blog.163.com main page is 1.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. Javascripts take 535.6 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 105.2 kB

  • Original 129.2 kB
  • After minification 129.2 kB
  • After compression 24.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 105.2 kB or 81% of the original size.

Image Optimization

-8%

Potential reduce by 13.4 kB

  • Original 163.6 kB
  • After minification 150.2 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. Ndzkyl Blog 163 images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 368.4 kB

  • Original 535.6 kB
  • After minification 535.5 kB
  • After compression 167.3 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 368.4 kB or 69% of the original size.

CSS Optimization

-82%

Potential reduce by 149.6 kB

  • Original 182.5 kB
  • After minification 178.6 kB
  • After compression 32.9 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. Ndzkyl.blog.163.com needs all CSS files to be minified and compressed as it can save up to 149.6 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 35 (42%)

Requests Now

84

After Optimization

49

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

ndzkyl.blog.163.com

ndzkyl.blog.163.com

2458 ms

c.css

c.css

50 ms

b.css

b.css

1817 ms

4848124998881530162.jpg

4848124998881530162.jpg

1113 ms

6630133180817252049.jpg

6630133180817252049.jpg

1668 ms

xcode.png

xcode.png

58 ms

1.0.0.js

1.0.0.js

100 ms

pc.js

pc.js

67 ms

ph.js

ph.js

63 ms

5408823152489137635.jpg

5408823152489137635.jpg

3793 ms

4541317274266915365.jpg

4541317274266915365.jpg

2952 ms

5409386102442558191.jpg

5409386102442558191.jpg

4244 ms

5784029297227400892.jpg

5784029297227400892.jpg

5561 ms

5784310771404301721.jpg

5784310771404301721.jpg

1270 ms

icon.png

icon.png

334 ms

1198801925812387419.jpg

1198801925812387419.jpg

5503 ms

1198801925812387464.jpg

1198801925812387464.jpg

1825 ms

1198801925812387523.jpg

1198801925812387523.jpg

2241 ms

1172624752978281188.jpg

1172624752978281188.jpg

2559 ms

rssi.png

rssi.png

288 ms

yodao_logo.gif

yodao_logo.gif

290 ms

blog_rec.png

blog_rec.png

286 ms

lnkbar.png

lnkbar.png

289 ms

image.png

image.png

291 ms

arrow24.png

arrow24.png

292 ms

newtopbaricon8.png

newtopbaricon8.png

292 ms

crossdomain.html

crossdomain.html

765 ms

crossdomain.html

crossdomain.html

946 ms

crossdomain.html

crossdomain.html

808 ms

request.s

request.s

920 ms

analyse.png

analyse.png

949 ms

ava.s

ava.s

387 ms

BlogCircleBean.getUserShowCircles.dwr

BlogCircleBean.getUserShowCircles.dwr

926 ms

ava.s

ava.s

741 ms

loftericon.png

loftericon.png

12472 ms

analyse.png

analyse.png

892 ms

analytics.js

analytics.js

55 ms

collect

collect

42 ms

SetupBeanNew.getCustomModulesData.dwr

SetupBeanNew.getCustomModulesData.dwr

840 ms

HomeBeanNew.getFriends.dwr

HomeBeanNew.getFriends.dwr

1264 ms

HomeBeanNew.getAccessStatistics.dwr

HomeBeanNew.getAccessStatistics.dwr

1241 ms

UserSpaceBean.getUserSpace.dwr

UserSpaceBean.getUserSpace.dwr

5104 ms

NewsBean.getAllOrderedNews.dwr

NewsBean.getAllOrderedNews.dwr

2208 ms

FeelingsBeanNew.getRecentFeelingCards.dwr

FeelingsBeanNew.getRecentFeelingCards.dwr

1244 ms

MusicBeanNew.setCopyrightMusicSessionToken.dwr

MusicBeanNew.setCopyrightMusicSessionToken.dwr

20249 ms

blogPhotoAd

blogPhotoAd

539 ms

close_01.png

close_01.png

103 ms

top_bg.png

top_bg.png

138 ms

bottom_bg.png

bottom_bg.png

138 ms

left_bg.png

left_bg.png

160 ms

right_bg.png

right_bg.png

165 ms

left_top.png

left_top.png

166 ms

right_top.png

right_top.png

213 ms

left_bottom.png

left_bottom.png

216 ms

right_bottom.png

right_bottom.png

236 ms

shadow.png

shadow.png

146 ms

f1ff3f3e89744e55a2cbd5adebed9f36.gif

f1ff3f3e89744e55a2cbd5adebed9f36.gif

19503 ms

r

r

798 ms

BgsBean.getBgsUserByUserId.dwr

BgsBean.getBgsUserByUserId.dwr

2539 ms

ava.s

ava.s

374 ms

ava.s

ava.s

2142 ms

ava.s

ava.s

791 ms

ava.s

ava.s

789 ms

ava.s

ava.s

837 ms

ava.s

ava.s

1074 ms

ava.s

ava.s

3221 ms

ava.s

ava.s

1210 ms

ava.s

ava.s

1293 ms

ava.s

ava.s

3734 ms

ava.s

ava.s

1596 ms

ava.s

ava.s

3603 ms

ava.s

ava.s

1905 ms

ava.s

ava.s

1992 ms

ava.s

ava.s

2343 ms

ava.s

ava.s

2413 ms

ava.s

ava.s

2542 ms

ava.s

ava.s

2762 ms

ava.s

ava.s

2776 ms

ava.s

ava.s

2927 ms

ad

ad

940 ms

close2.png

close2.png

62 ms

jquery-1.4.2.js

jquery-1.4.2.js

109 ms

ad.bid.material_9ba8a084ec524821974fa01ce2124d16

ad.bid.material_9ba8a084ec524821974fa01ce2124d16

3952 ms

AlbumBeanNew.getUserSpace.dwr

AlbumBeanNew.getUserSpace.dwr

887 ms

sniff.png

sniff.png

4176 ms

14293658507231.js

14293658507231.js

2153 ms

-1.gif

-1.gif

55 ms

14293658507230.js

14293658507230.js

1238 ms

empty.png

empty.png

57 ms

4021432992265950114.jpg

4021432992265950114.jpg

1176 ms

SEO Factors

ndzkyl.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 Ndzkyl.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 Ndzkyl.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

ndzkyl.blog.163.com

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