Tools & Wizards About Us
pindao.blogbus.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

pindao.blogbus.com

网站被关闭提示

Page Load Speed

35.7 sec in total

First Response

6 sec

Resources Loaded

28.5 sec

Page Rendered

1.2 sec

pindao.blogbus.com screenshot

About Website

Click here to check amazing Pindao Blogbus content for United States. Otherwise, check out these important facts you probably never knew about pindao.blogbus.com

博客大巴是国内第一家博客托管服务商，也是首家商业运作、提供收费服务的中文博客网站，在中文博客业内享有盛誉

Visit pindao.blogbus.com

Key Findings

We analyzed Pindao.blogbus.com page load time and found that the first response time was 6 sec and then it took 29.7 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.

Performance Metrics

pindao.blogbus.com performance score

0

Network Requests Diagram

pindao.blogbus.com

6028 ms

www.blogbus.com

4511 ms

boilerplate.css

1400 ms

base.css

1410 ms

jquery.js

1413 ms

Our browser made a total of 58 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Pindao.blogbus.com, 33% (19 requests) were made to Public2.blogbus.com and 26% (15 requests) were made to Img2.blogbuscdn.com. The less responsive or slowest element that took the longest time to load (15.3 sec) relates to the external source Ad.thinkmedia.cn.

Page Optimization Overview & Recommendations

Page size can be reduced by 227.1 kB (48%)

Content Size

477.4 kB

After Optimization

250.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Pindao.blogbus.com main page is 477.4 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 290.2 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 22.2 kB

  • Original 28.5 kB
  • After minification 27.5 kB
  • After compression 6.3 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 22.2 kB or 78% of the original size.

Image Optimization

-5%

Potential reduce by 6.8 kB

  • Original 144.6 kB
  • After minification 137.7 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. Pindao Blogbus images are well optimized though.

JavaScript Optimization

-65%

Potential reduce by 187.9 kB

  • Original 290.2 kB
  • After minification 268.1 kB
  • After compression 102.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 187.9 kB or 65% of the original size.

CSS Optimization

-72%

Potential reduce by 10.2 kB

  • Original 14.2 kB
  • After minification 13.3 kB
  • After compression 4.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. Pindao.blogbus.com needs all CSS files to be minified and compressed as it can save up to 10.2 kB or 72% of the original size.

Requests Breakdown

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

Requests Now

54

After Optimization

35

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

pindao.blogbus.com

pindao.blogbus.com

6028 ms

www.blogbus.com

www.blogbus.com

4511 ms

boilerplate.css

boilerplate.css

1400 ms

base.css

base.css

1410 ms

jquery.js

jquery.js

1413 ms

m.js

m.js

793 ms

respond.css

respond.css

1397 ms

infinitescroll.css

infinitescroll.css

1410 ms

respond.min.js

respond.min.js

1406 ms

jquery.masonry.js

jquery.masonry.js

1500 ms

jquery.infinitescroll.js

jquery.infinitescroll.js

1496 ms

blogbus_logo.png

blogbus_logo.png

43 ms

ico_ios.png

ico_ios.png

249 ms

ico_android.png

ico_android.png

45 ms

ico_explore.png

ico_explore.png

46 ms

ico_post.png

ico_post.png

302 ms

ico_settings.png

ico_settings.png

46 ms

pindao_search_button.jpg

pindao_search_button.jpg

48 ms

tcum

tcum

756 ms

ico_bullet.png

ico_bullet.png

45 ms

189ff624094a1ff2aeb2b2dd2dbe32e6.jpg!200

189ff624094a1ff2aeb2b2dd2dbe32e6.jpg!200

527 ms

avatar_6035697_48.jpg

avatar_6035697_48.jpg

765 ms

page2.png

page2.png

242 ms

size=80x600

size=80x600

15347 ms

default_domain

default_domain

778 ms

k.js

k.js

751 ms

avatar_12127258_48.jpg

avatar_12127258_48.jpg

769 ms

avatar_4265738_48.jpg

avatar_4265738_48.jpg

777 ms

avatar_4620966_48.jpg

avatar_4620966_48.jpg

776 ms

9f7d465490f099d623fcd8a54cd974d3.jpg!200

9f7d465490f099d623fcd8a54cd974d3.jpg!200

443 ms

d73d424361484f54d3f1794d82af13c9.jpg!200

d73d424361484f54d3f1794d82af13c9.jpg!200

416 ms

93379ac3de810b2de67bc340896985e7.jpg!200

93379ac3de810b2de67bc340896985e7.jpg!200

419 ms

fcde8224bf83c29e0643cde036f1a94b.jpg!200

fcde8224bf83c29e0643cde036f1a94b.jpg!200

432 ms

d31272956818ce19c2f1e7dcd3cbada6.jpg!200

d31272956818ce19c2f1e7dcd3cbada6.jpg!200

440 ms

540fef32baa3713711354a2feddf4b26.jpg!200

540fef32baa3713711354a2feddf4b26.jpg!200

429 ms

fde4a6c4309e194c45071b2dd4a5b970.jpg!200

fde4a6c4309e194c45071b2dd4a5b970.jpg!200

432 ms

0a7e534a8fc67add54a57c1d00d4c61d.png!200

0a7e534a8fc67add54a57c1d00d4c61d.png!200

461 ms

70c0795418e1920c0994602299be3bf2.jpg!200

70c0795418e1920c0994602299be3bf2.jpg!200

440 ms

6272675d888d3eeb4770dbb763dcac7b.jpg!200

6272675d888d3eeb4770dbb763dcac7b.jpg!200

454 ms

23.jpg!200

23.jpg!200

456 ms

967d6872e94665137c0ee9e75a0f903e.png!200

967d6872e94665137c0ee9e75a0f903e.png!200

465 ms

64f4df57a1d3ddb0103d831ff3fc0199.jpg!200

64f4df57a1d3ddb0103d831ff3fc0199.jpg!200

464 ms

d77bcd3ff854a3e5e833f9d1d51615ec.jpg!200

d77bcd3ff854a3e5e833f9d1d51615ec.jpg!200

458 ms

arrow.png

arrow.png

23 ms

head.gif

head.gif

389 ms

a.htm

a.htm

3877 ms

cmp.htm

cmp.htm

863 ms

h.js

h.js

1611 ms

h.js

h.js

1622 ms

hm.gif

hm.gif

542 ms

21.gif

21.gif

713 ms

masonry_loading_1.gif

masonry_loading_1.gif

36 ms

hm.gif

hm.gif

1412 ms

o.htm

o.htm

1931 ms

hm.gif

hm.gif

541 ms

hm.gif

hm.gif

540 ms

wh.js

wh.js

756 ms

ac.js

ac.js

520 ms

SEO Factors

pindao.blogbus.com SEO score

0

Language and Encoding

  • Language Detected

    ZH

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pindao.blogbus.com can be misinterpreted by Google and other search engines. Our service has detected that Chinese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Pindao.blogbus.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

pindao.blogbus.com

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