Tools & Wizards About Us
idcbus.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

idcbus.com

服务器租用,服务器托管,主机租用,主机托管,网通服务器租用,100M独享_数据巴士

Page Load Speed

64.5 sec in total

First Response

9.1 sec

Resources Loaded

55.2 sec

Page Rendered

215 ms

idcbus.com screenshot

About Website

Welcome to idcbus.com homepage info - get ready to check Idcbus best content right away, or after learning these important things about idcbus.com

数据巴士是一家专们提供服务器租用,服务器托管,主机租用,主机托管,100M独享,机柜租用等业务,机房主要分布在重庆电信,浙江电信,江苏电信,江西电信,新余电信以及江西网通,双线机房，8年行业经验的老牌IDC

Visit idcbus.com

Key Findings

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

Performance Metrics

idcbus.com performance score

0

Network Requests Diagram

idcbus.com

9055 ms

style.css

5196 ms

flexcrollstyles.css

905 ms

services.css

14726 ms

Server.css

5345 ms

Our browser made a total of 82 requests to load all elements on the main page. We found that 56% of them (46 requests) were addressed to the original Idcbus.com, 12% (10 requests) were made to Pub.idqqimg.com and 6% (5 requests) were made to Bdimg.share.baidu.com. The less responsive or slowest element that took the longest time to load (20.2 sec) belongs to the original domain Idcbus.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 207.1 kB (62%)

Content Size

332.3 kB

After Optimization

125.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Idcbus.com main page is 332.3 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. 25% of websites need less resources to load. Javascripts take 250.3 kB which makes up the majority of the site volume.

HTML Optimization

-69%

Potential reduce by 31.0 kB

  • Original 45.2 kB
  • After minification 43.8 kB
  • After compression 14.2 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 31.0 kB or 69% of the original size.

Image Optimization

-35%

Potential reduce by 3.1 kB

  • Original 9.0 kB
  • After minification 5.9 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. Obviously, Idcbus needs image optimization as it can save up to 3.1 kB or 35% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-61%

Potential reduce by 152.9 kB

  • Original 250.3 kB
  • After minification 173.0 kB
  • After compression 97.4 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 152.9 kB or 61% of the original size.

CSS Optimization

-72%

Potential reduce by 20.0 kB

  • Original 27.8 kB
  • After minification 23.0 kB
  • After compression 7.8 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. Idcbus.com needs all CSS files to be minified and compressed as it can save up to 20.0 kB or 72% of the original size.

Requests Breakdown

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

Requests Now

77

After Optimization

40

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

idcbus.com

idcbus.com

9055 ms

style.css

style.css

5196 ms

flexcrollstyles.css

flexcrollstyles.css

905 ms

services.css

services.css

14726 ms

Server.css

Server.css

5345 ms

Global.css

Global.css

5626 ms

grid.gif

grid.gif

1375 ms

hot.gif

hot.gif

1441 ms

logo.gif

logo.gif

2406 ms

messanger1.gif

messanger1.gif

2887 ms

messangergrid.gif

messangergrid.gif

3367 ms

messanger2.gif

messanger2.gif

3858 ms

messanger3.gif

messanger3.gif

4347 ms

messanger4_footer-92.gif

messanger4_footer-92.gif

4805 ms

hkxiao.gif

hkxiao.gif

4497 ms

ad3.jpg

ad3.jpg

15708 ms

Gongsihuanjing.jpg

Gongsihuanjing.jpg

20242 ms

about_us_logo.jpg

about_us_logo.jpg

9084 ms

service_colotitle1.gif

service_colotitle1.gif

4523 ms

ad3.gif

ad3.gif

4801 ms

service_colotitle2.gif

service_colotitle2.gif

4982 ms

service_colotitle3.gif

service_colotitle3.gif

5275 ms

stat.php

stat.php

1676 ms

fr1.js

fr1.js

1825 ms

frcon.asp

frcon.asp

2123 ms

fr2.js

fr2.js

2277 ms

wpa.js

wpa.js

20185 ms

wpa.php

wpa.php

841 ms

qq_green.js

qq_green.js

2599 ms

kfmenu.css

kfmenu.css

4061 ms

menu.css

menu.css

2370 ms

facebox.css

facebox.css

2845 ms

zx_qq.gif

zx_qq.gif

3704 ms

weixin.jpg

weixin.jpg

11340 ms

logo_denglu.png

logo_denglu.png

901 ms

bg.gif

bg.gif

488 ms

allbtnbg.gif

allbtnbg.gif

468 ms

service_box_top.gif

service_box_top.gif

1828 ms

service_box_bg2.gif

service_box_bg2.gif

918 ms

service_box_bg1.gif

service_box_bg1.gif

2372 ms

colo_arrow.gif

colo_arrow.gif

1332 ms

colocation_secbtm.gif

colocation_secbtm.gif

1381 ms

heng.gif

heng.gif

2240 ms

tab2.jpg

tab2.jpg

3239 ms

tab1.jpg

tab1.jpg

2169 ms

footerbg.gif

footerbg.gif

2316 ms

nm.gif

nm.gif

1246 ms

h.js

h.js

1728 ms

hm.gif

hm.gif

6099 ms

stat.htm

stat.htm

576 ms

core.php

core.php

719 ms

9.gif

9.gif

1152 ms

pic.gif

pic.gif

694 ms

footer_serviceicon.gif

footer_serviceicon.gif

453 ms

app.gif

app.gif

4156 ms

shell_v2.js

shell_v2.js

760 ms

online.css

online.css

1867 ms

jquery-1.js

jquery-1.js

19990 ms

button_old_41.gif

button_old_41.gif

501 ms

Panel.js

Panel.js

673 ms

localStorage.js

localStorage.js

714 ms

contains.js

contains.js

259 ms

bds_s_v2.js

bds_s_v2.js

1102 ms

r.cgi

r.cgi

6380 ms

ta.php

ta.php

558 ms

crmqq.php

crmqq.php

15845 ms

wpa_first_heart_beat.php

wpa_first_heart_beat.php

590 ms

bdsstyle.css

bdsstyle.css

1226 ms

l1.gif

l1.gif

1579 ms

button_old_41.gif

button_old_41.gif

495 ms

button_old_41.gif

button_old_41.gif

451 ms

button_old_41.gif

button_old_41.gif

236 ms

button_11.gif

button_11.gif

226 ms

button_11.gif

button_11.gif

245 ms

button_old_41.gif

button_old_41.gif

237 ms

button_old_41.gif

button_old_41.gif

227 ms

button_old_41.gif

button_old_41.gif

245 ms

button_old_41.gif

button_old_41.gif

219 ms

button_old_41.gif

button_old_41.gif

411 ms

logger.js

logger.js

361 ms

online_bg.png

online_bg.png

5989 ms

hb.crm2.qq.com

hb.crm2.qq.com

596 ms

SEO Factors

idcbus.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 Idcbus.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 Idcbus.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

idcbus.com

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