Tools & Wizards About Us
nanerbang.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

nanerbang.com

男儿邦，关注大脑、心理和人工智能的个人科技网站

Page Load Speed

57.8 sec in total

First Response

2.3 sec

Resources Loaded

54.1 sec

Page Rendered

1.3 sec

nanerbang.com screenshot

About Website

Click here to check amazing Nanerbang content for China. Otherwise, check out these important facts you probably never knew about nanerbang.com

男儿邦，是一个以大脑、心理和人工智能为主要内容的专业个人科技网站，但不局限于这些领域。男儿邦的站长是一个兴趣广泛的人，他追求理性，热爱人类大脑创造的一切文明。

Visit nanerbang.com

Key Findings

We analyzed Nanerbang.com page load time and found that the first response time was 2.3 sec and then it took 55.5 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

nanerbang.com performance score

0

Network Requests Diagram

nanerbang.com

2278 ms

www.nanerbang.com

18419 ms

5f5173e08c60.css

15296 ms

ds.js

2041 ms

97fdd4540b68.js

11462 ms

Our browser made a total of 94 requests to load all elements on the main page. We found that 22% of them (21 requests) were addressed to the original Nanerbang.com, 13% (12 requests) were made to Asearch.alicdn.com and 10% (9 requests) were made to Bdimg.share.baidu.com. The less responsive or slowest element that took the longest time to load (19.6 sec) relates to the external source Rcm-cn.amazon-adsystem.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 554.5 kB (44%)

Content Size

1.2 MB

After Optimization

693.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Nanerbang.com main page is 1.2 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 444.2 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 67.1 kB

  • Original 90.9 kB
  • After minification 90.0 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 67.1 kB or 74% of the original size.

Image Optimization

-1%

Potential reduce by 5.6 kB

  • Original 444.2 kB
  • After minification 438.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. Nanerbang images are well optimized though.

JavaScript Optimization

-57%

Potential reduce by 230.5 kB

  • Original 405.6 kB
  • After minification 405.6 kB
  • After compression 175.2 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 230.5 kB or 57% of the original size.

CSS Optimization

-82%

Potential reduce by 251.3 kB

  • Original 307.4 kB
  • After minification 300.5 kB
  • After compression 56.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. Nanerbang.com needs all CSS files to be minified and compressed as it can save up to 251.3 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 37 (43%)

Requests Now

86

After Optimization

49

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 86 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Nanerbang. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

nanerbang.com

nanerbang.com

2278 ms

www.nanerbang.com

www.nanerbang.com

18419 ms

5f5173e08c60.css

5f5173e08c60.css

15296 ms

ds.js

ds.js

2041 ms

97fdd4540b68.js

97fdd4540b68.js

11462 ms

lishirenwen.gif

lishirenwen.gif

4700 ms

dianshiju_1.gif

dianshiju_1.gif

3417 ms

rengongzhineng.gif

rengongzhineng.gif

1162 ms

yingping.png

yingping.png

2266 ms

hongloumeng.png

hongloumeng.png

6034 ms

django_2.gif

django_2.gif

2632 ms

xinliyudanao.gif

xinliyudanao.gif

2996 ms

diannaojiqiao.gif

diannaojiqiao.gif

3375 ms

bianchengjiyi.gif

bianchengjiyi.gif

4897 ms

html5.gif

html5.gif

6071 ms

pinzhishenghuo.png

pinzhishenghuo.png

4349 ms

apache_1.gif

apache_1.gif

5856 ms

cunzaigan_4.gif

cunzaigan_4.gif

4998 ms

yishi.gif

yishi.gif

5898 ms

yuzhouguan.png

yuzhouguan.png

14475 ms

webqianduan.gif

webqianduan.gif

7409 ms

python.png

python.png

9063 ms

ocdm

ocdm

928 ms

c.js

c.js

733 ms

ask

ask

2321 ms

ct

ct

3521 ms

lm.jpg

lm.jpg

717 ms

ocdm

ocdm

836 ms

ask

ask

897 ms

ct

ct

4261 ms

lm.jpg

lm.jpg

332 ms

ocdm

ocdm

2851 ms

qi

qi

900 ms

t.gif

t.gif

773 ms

t.gif

t.gif

1496 ms

sogou_icon_wz_1.png

sogou_icon_wz_1.png

921 ms

fc.js

fc.js

256 ms

pixel

pixel

451 ms

cm

cm

19587 ms

ocdm

ocdm

468 ms

pixel

pixel

485 ms

qqcm

qqcm

1886 ms

ex

ex

1751 ms

embed.compat.js

embed.compat.js

1571 ms

prebat.php

prebat.php

2198 ms

tanxssp.js

tanxssp.js

1100 ms

share.js

share.js

2633 ms

hm.js

hm.js

16706 ms

counts.json

counts.json

1156 ms

ex

ex

4043 ms

embed.default.css

embed.default.css

146 ms

share_api.js

share_api.js

400 ms

share_view.js

share_view.js

836 ms

tangram.js

tangram.js

3963 ms

api_base.js

api_base.js

811 ms

view_base.js

view_base.js

1479 ms

acbeacon2.html

acbeacon2.html

366 ms

spf

spf

658 ms

TB1DmcoJXXXXXavXpXXXXXXXXXX-26-26.png

TB1DmcoJXXXXXavXpXXXXXXXXXX-26-26.png

223 ms

creation-164857uaSd33GHMrk-437386.html

creation-164857uaSd33GHMrk-437386.html

369 ms

TB1Lt7aJXXXXXcjXVXXXXXXXXXX-117-26.png

TB1Lt7aJXXXXXcjXVXXXXXXXXXX-117-26.png

220 ms

TB1rRQpJXXXXXcvXXXXXXXXXXXX-40-26.png

TB1rRQpJXXXXXcvXXXXXXXXXXXX-40-26.png

387 ms

TB1upAiJXXXXXa5aXXXXXXXXXXX-116-30.png

TB1upAiJXXXXXa5aXXXXXXXXXXX-116-30.png

390 ms

t.gif

t.gif

830 ms

tanxclick.js

tanxclick.js

62 ms

tns.simba.taobao.com

tns.simba.taobao.com

8405 ms

logger.js

logger.js

396 ms

app.gif

app.gif

1075 ms

um.js

um.js

497 ms

img

img

1202 ms

partners.js

partners.js

406 ms

share_style0_32.css

share_style0_32.css

424 ms

um.json

um.json

1599 ms

getDeviceInfo

getDeviceInfo

998 ms

getDeviceInfo

getDeviceInfo

914 ms

TB2jznDhXXXXXbsXXXXXXXXXXXX_!!33283107-0-saturn_solar.jpg_sum.jpg

TB2jznDhXXXXXbsXXXXXXXXXXXX_!!33283107-0-saturn_solar.jpg_sum.jpg

133 ms

feature_v1.htm

feature_v1.htm

993 ms

TB2jznDhXXXXXbsXXXXXXXXXXXX_!!33283107-0-saturn_solar.jpg_250x250.jpg

TB2jznDhXXXXXbsXXXXXXXXXXXX_!!33283107-0-saturn_solar.jpg_250x250.jpg

223 ms

TB2GaV9mXXXXXaOXpXXXXXXXXXX_!!0-saturn_solar.jpg_250x250.jpg

TB2GaV9mXXXXXaOXpXXXXXXXXXX_!!0-saturn_solar.jpg_250x250.jpg

186 ms

TB26_ULcVXXXXavXXXXXXXXXXXX_!!33283107-0-saturn_solar.jpg_250x250.jpg

TB26_ULcVXXXXavXXXXXXXXXXXX_!!33283107-0-saturn_solar.jpg_250x250.jpg

239 ms

TB22LoblFXXXXagXpXXXXXXXXXX_!!0-saturn_solar.jpg_250x250.jpg

TB22LoblFXXXXagXpXXXXXXXXXX_!!0-saturn_solar.jpg_250x250.jpg

237 ms

TB2uC.0fpXXXXaOXXXXXXXXXXXX_!!97605225-0-saturn_solar.jpg_250x250.jpg

TB2uC.0fpXXXXaOXXXXXXXXXXXX_!!97605225-0-saturn_solar.jpg_250x250.jpg

200 ms

TB2EeObmpXXXXbZXXXXXXXXXXXX_!!0-saturn_solar.jpg_250x250.jpg

TB2EeObmpXXXXbZXXXXXXXXXXXX_!!0-saturn_solar.jpg_250x250.jpg

240 ms

TB2NLoFcFXXXXXnXpXXXXXXXXXX_!!96891521-0-saturn_solar.jpg_250x250.jpg

TB2NLoFcFXXXXXnXpXXXXXXXXXX_!!96891521-0-saturn_solar.jpg_250x250.jpg

267 ms

TB2ocpIipXXXXa7XXXXXXXXXXXX_!!40415745-0-saturn_solar.jpg_250x250.jpg

TB2ocpIipXXXXa7XXXXXXXXXXXX_!!40415745-0-saturn_solar.jpg_250x250.jpg

320 ms

TB2fw9KfVXXXXXxXXXXXXXXXXXX_!!45164304-0-saturn_solar.jpg_250x250.jpg

TB2fw9KfVXXXXXxXXXXXXXXXXXX_!!45164304-0-saturn_solar.jpg_250x250.jpg

240 ms

TB2NsxSkVXXXXaGXpXXXXXXXXXX_!!0-saturn_solar.jpg_250x250.jpg

TB2NsxSkVXXXXaGXpXXXXXXXXXX_!!0-saturn_solar.jpg_250x250.jpg

318 ms

TB2Y1.ilFXXXXbAXpXXXXXXXXXX_!!0-saturn_solar.jpg_250x250.jpg

TB2Y1.ilFXXXXbAXpXXXXXXXXXX_!!0-saturn_solar.jpg_250x250.jpg

328 ms

TB11KimHpXXXXXJXXXXQKC3FVXX-27-59.png

TB11KimHpXXXXXJXXXXQKC3FVXX-27-59.png

227 ms

TB1Mng.HpXXXXb4XFXX1qpgFpXX-20-14.gif

TB1Mng.HpXXXXb4XFXX1qpgFpXX-20-14.gif

326 ms

TB1LKo.HpXXXXbiXFXX91dEGXXX-29-16.png

TB1LKo.HpXXXXbiXFXX91dEGXXX-29-16.png

263 ms

hm.gif

hm.gif

335 ms

o.htm

o.htm

663 ms

hm.gif

hm.gif

770 ms

SEO Factors

nanerbang.com SEO score

0

Language and Encoding

  • Language Detected

    ZH

  • Language Claimed

    ZH

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Nanerbang.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 Nanerbang.com main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

nanerbang.com

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