Tools & Wizards About Us
blogbus.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

blogbus.com

Welcome to tengine!

Page Load Speed

26.5 sec in total

First Response

1.3 sec

Resources Loaded

25 sec

Page Rendered

200 ms

blogbus.com screenshot

About Website

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

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

Visit blogbus.com

Key Findings

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

blogbus.com performance score

0

Network Requests Diagram

blogbus.com

1270 ms

www.blogbus.com

2950 ms

boilerplate.css

5543 ms

base.css

5552 ms

jquery.js

5566 ms

Our browser made a total of 58 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original 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 435.3 kB (35%)

Content Size

1.3 MB

After Optimization

818.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Blogbus.com main page is 1.3 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. 30% of websites need less resources to load. Images take 682.8 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 22.5 kB

  • Original 28.8 kB
  • After minification 27.8 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.5 kB or 78% of the original size.

Image Optimization

-5%

Potential reduce by 34.6 kB

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

JavaScript Optimization

-65%

Potential reduce by 258.7 kB

  • Original 395.4 kB
  • After minification 371.3 kB
  • After compression 136.7 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 258.7 kB or 65% of the original size.

CSS Optimization

-81%

Potential reduce by 119.5 kB

  • Original 146.6 kB
  • After minification 140.7 kB
  • After compression 27.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. Blogbus.com needs all CSS files to be minified and compressed as it can save up to 119.5 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 18 (33%)

Requests Now

54

After Optimization

36

  • AJAX
  • Images
  • JavaScript
  • CSS

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

blogbus.com

blogbus.com

1270 ms

www.blogbus.com

www.blogbus.com

2950 ms

boilerplate.css

boilerplate.css

5543 ms

base.css

base.css

5552 ms

jquery.js

jquery.js

5566 ms

m.js

m.js

3377 ms

respond.css

respond.css

5540 ms

infinitescroll.css

infinitescroll.css

5541 ms

respond.min.js

respond.min.js

5540 ms

jquery.masonry.js

jquery.masonry.js

5562 ms

jquery.infinitescroll.js

jquery.infinitescroll.js

5630 ms

default_domain

default_domain

2170 ms

k.js

k.js

2266 ms

189ff624094a1ff2aeb2b2dd2dbe32e6.jpg!200

189ff624094a1ff2aeb2b2dd2dbe32e6.jpg!200

5508 ms

avatar_6035697_48.jpg

avatar_6035697_48.jpg

1969 ms

size=80x600

size=80x600

15302 ms

avatar_12127258_48.jpg

avatar_12127258_48.jpg

1999 ms

avatar_4265738_48.jpg

avatar_4265738_48.jpg

2017 ms

avatar_4620966_48.jpg

avatar_4620966_48.jpg

2312 ms

9f7d465490f099d623fcd8a54cd974d3.jpg!200

9f7d465490f099d623fcd8a54cd974d3.jpg!200

5500 ms

d73d424361484f54d3f1794d82af13c9.jpg!200

d73d424361484f54d3f1794d82af13c9.jpg!200

5487 ms

93379ac3de810b2de67bc340896985e7.jpg!200

93379ac3de810b2de67bc340896985e7.jpg!200

5502 ms

fcde8224bf83c29e0643cde036f1a94b.jpg!200

fcde8224bf83c29e0643cde036f1a94b.jpg!200

5501 ms

d31272956818ce19c2f1e7dcd3cbada6.jpg!200

d31272956818ce19c2f1e7dcd3cbada6.jpg!200

5502 ms

540fef32baa3713711354a2feddf4b26.jpg!200

540fef32baa3713711354a2feddf4b26.jpg!200

5502 ms

fde4a6c4309e194c45071b2dd4a5b970.jpg!200

fde4a6c4309e194c45071b2dd4a5b970.jpg!200

5504 ms

0a7e534a8fc67add54a57c1d00d4c61d.png!200

0a7e534a8fc67add54a57c1d00d4c61d.png!200

5521 ms

70c0795418e1920c0994602299be3bf2.jpg!200

70c0795418e1920c0994602299be3bf2.jpg!200

5512 ms

6272675d888d3eeb4770dbb763dcac7b.jpg!200

6272675d888d3eeb4770dbb763dcac7b.jpg!200

5518 ms

23.jpg!200

23.jpg!200

5516 ms

967d6872e94665137c0ee9e75a0f903e.png!200

967d6872e94665137c0ee9e75a0f903e.png!200

5520 ms

64f4df57a1d3ddb0103d831ff3fc0199.jpg!200

64f4df57a1d3ddb0103d831ff3fc0199.jpg!200

5519 ms

d77bcd3ff854a3e5e833f9d1d51615ec.jpg!200

d77bcd3ff854a3e5e833f9d1d51615ec.jpg!200

5523 ms

blogbus_logo.png

blogbus_logo.png

54 ms

ico_ios.png

ico_ios.png

57 ms

ico_android.png

ico_android.png

56 ms

ico_explore.png

ico_explore.png

58 ms

ico_post.png

ico_post.png

300 ms

ico_settings.png

ico_settings.png

57 ms

pindao_search_button.jpg

pindao_search_button.jpg

99 ms

arrow.png

arrow.png

313 ms

acwm

acwm

1856 ms

ico_bullet.png

ico_bullet.png

25 ms

page2.png

page2.png

294 ms

a.htm

a.htm

836 ms

head.gif

head.gif

382 ms

cmp.htm

cmp.htm

1060 ms

h.js

h.js

954 ms

h.js

h.js

3201 ms

hm.gif

hm.gif

1461 ms

21.gif

21.gif

1285 ms

masonry_loading_1.gif

masonry_loading_1.gif

17 ms

hm.gif

hm.gif

465 ms

o.htm

o.htm

883 ms

hm.gif

hm.gif

435 ms

hm.gif

hm.gif

862 ms

wh.js

wh.js

744 ms

ac.js

ac.js

503 ms

SEO Factors

blogbus.com SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Blogbus.com can be misinterpreted by Google and other search engines. Our service has detected that English 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 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

blogbus.com

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