Tools & Wizards About Us
taidi.us screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

taidi.us

泰迪|泰迪熊|泰迪犬|贵宾|贵宾犬|泰迪俱乐部

Page Load Speed

50.7 sec in total

First Response

7.5 sec

Resources Loaded

42.9 sec

Page Rendered

331 ms

taidi.us screenshot

About Website

Click here to check amazing Taidi content. Otherwise, check out these important facts you probably never knew about taidi.us

泰迪俱乐部提供大量泰迪犬交易信息,商家和个人均可自由发布泰迪熊贵宾犬出售和求购广告,同时还有大量泰迪贵宾犬图片,泰迪熊饲养知识,泰迪犬美容技巧等,欢迎广大泰迪狗主人入驻泰迪俱乐部!

Visit taidi.us

Key Findings

We analyzed Taidi.us page load time and found that the first response time was 7.5 sec and then it took 43.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

taidi.us performance score

0

Network Requests Diagram

www.taidi.us

7521 ms

pw_core.css

1756 ms

core.js

1363 ms

pw_ajax.js

870 ms

weibologin.css

1089 ms

Our browser made a total of 121 requests to load all elements on the main page. We found that 30% of them (36 requests) were addressed to the original Taidi.us, 18% (22 requests) were made to Upyun.taidi.us and 17% (21 requests) were made to Pos.baidu.com. The less responsive or slowest element that took the longest time to load (7.5 sec) belongs to the original domain Taidi.us.

Page Optimization Overview & Recommendations

Page size can be reduced by 635.2 kB (34%)

Content Size

1.9 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Taidi.us main page is 1.9 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. 50% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 63.1 kB

  • Original 84.9 kB
  • After minification 84.7 kB
  • After compression 21.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 63.1 kB or 74% of the original size.

Image Optimization

-24%

Potential reduce by 349.8 kB

  • Original 1.4 MB
  • After minification 1.1 MB

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, Taidi needs image optimization as it can save up to 349.8 kB or 24% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-65%

Potential reduce by 199.4 kB

  • Original 309.0 kB
  • After minification 284.4 kB
  • After compression 109.6 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 199.4 kB or 65% of the original size.

CSS Optimization

-72%

Potential reduce by 22.9 kB

  • Original 31.8 kB
  • After minification 29.8 kB
  • After compression 8.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. Taidi.us needs all CSS files to be minified and compressed as it can save up to 22.9 kB or 72% of the original size.

Requests Breakdown

Number of requests can be reduced by 61 (51%)

Requests Now

119

After Optimization

58

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.taidi.us

www.taidi.us

7521 ms

pw_core.css

pw_core.css

1756 ms

core.js

core.js

1363 ms

pw_ajax.js

pw_ajax.js

870 ms

weibologin.css

weibologin.css

1089 ms

ad.js

ad.js

1094 ms

ddsliderplayer.js

ddsliderplayer.js

1093 ms

Deploy.js

Deploy.js

759 ms

picture2_stat.js

picture2_stat.js

1749 ms

stat.php

stat.php

2371 ms

global.js

global.js

3529 ms

adminview.js

adminview.js

1691 ms

app_global.js

app_global.js

1772 ms

zh_cn.js

zh_cn.js

449 ms

qq_n.png

qq_n.png

1341 ms

3_26203_05817e9975f8903.jpg

3_26203_05817e9975f8903.jpg

5951 ms

type-button-3.jpg

type-button-3.jpg

602 ms

bg.jpg

bg.jpg

2786 ms

topbar.png

topbar.png

447 ms

logo.png

logo.png

371 ms

select_arrow.gif

select_arrow.gif

707 ms

button.png

button.png

848 ms

bg_loginways.png

bg_loginways.png

871 ms

cate_fold.gif

cate_fold.gif

933 ms

10.gif

10.gif

1039 ms

8.gif

8.gif

1294 ms

5.gif

5.gif

1308 ms

3.gif

3.gif

2399 ms

6.gif

6.gif

1373 ms

sina_n.png

sina_n.png

1444 ms

3_25730_82e51fed570980c.jpg

3_25730_82e51fed570980c.jpg

6180 ms

3_25634_eed346f320edb03.jpg

3_25634_eed346f320edb03.jpg

6245 ms

3_25633_75763407b06a82f.jpg

3_25633_75763407b06a82f.jpg

6216 ms

3_18032_e9964dff92c8367.jpg

3_18032_e9964dff92c8367.jpg

6205 ms

2.jpg

2.jpg

6273 ms

3.jpg

3.jpg

6287 ms

4.jpg

4.jpg

6427 ms

5.jpg

5.jpg

6597 ms

7.jpg

7.jpg

6568 ms

6.jpg

6.jpg

6624 ms

58.jpg

58.jpg

6626 ms

8.jpg

8.jpg

6609 ms

13.jpg

13.jpg

6771 ms

9.jpg

9.jpg

6932 ms

79.jpg

79.jpg

6876 ms

11.jpg

11.jpg

6623 ms

12.gif

12.gif

6916 ms

78.jpg

78.jpg

6978 ms

23.gif

23.gif

6636 ms

19.gif

19.gif

6648 ms

16.gif

16.gif

6911 ms

navA.png

navA.png

2171 ms

searchA.png

searchA.png

1725 ms

search_input.png

search_input.png

1690 ms

down.png

down.png

2024 ms

search_btn.png

search_btn.png

2158 ms

sygg.html

sygg.html

2561 ms

colon.png

colon.png

2591 ms

hB.png

hB.png

2603 ms

anc.gif

anc.gif

2648 ms

h.png

h.png

2755 ms

h.js

h.js

1751 ms

21.gif

21.gif

736 ms

hm.gif

hm.gif

362 ms

stat2.png

stat2.png

5504 ms

stat.htm

stat.htm

159 ms

core.php

core.php

1754 ms

o.js

o.js

941 ms

ecom

ecom

706 ms

9.gif

9.gif

1662 ms

pic.gif

pic.gif

2374 ms

shell_v2.js

shell_v2.js

300 ms

top.png

top.png

1449 ms

y.php

y.php

570 ms

logger.js

logger.js

303 ms

bds_s_v2.js

bds_s_v2.js

1125 ms

0f000AjMbH3uK8gKoX7D10.jpg

0f000AjMbH3uK8gKoX7D10.jpg

722 ms

ecom

ecom

353 ms

0f00057T9CoQoQ3rKCGPks.png

0f00057T9CoQoQ3rKCGPks.png

693 ms

ecom

ecom

355 ms

0f0007cx4J2IUNDh4pMEqf.png

0f0007cx4J2IUNDh4pMEqf.png

694 ms

ecom

ecom

364 ms

bdsstyle.css

bdsstyle.css

305 ms

getnum

getnum

782 ms

app.gif

app.gif

1469 ms

sc.png

sc.png

302 ms

ecom

ecom

355 ms

0f000Kc1crrzlwj44y5Mzf.jpg

0f000Kc1crrzlwj44y5Mzf.jpg

478 ms

ecom

ecom

352 ms

0f0002sfQkCTJl28z1hzi0.jpg

0f0002sfQkCTJl28z1hzi0.jpg

461 ms

ecom

ecom

357 ms

0f000n0eYuyZCCmywuiZK6.jpg

0f000n0eYuyZCCmywuiZK6.jpg

459 ms

ecom

ecom

357 ms

0f0005w9PrydUO6eEZ5WS6.png

0f0005w9PrydUO6eEZ5WS6.png

738 ms

ecom

ecom

349 ms

0f000Qv8Vtm3xMTWAA37d6.jpg

0f000Qv8Vtm3xMTWAA37d6.jpg

243 ms

ecom

ecom

361 ms

0f000Kc1cFhzekj44y5MSf.png

0f000Kc1cFhzekj44y5MSf.png

705 ms

ecom

ecom

358 ms

0f000QkbRRRHljLNV_Natf.jpg

0f000QkbRRRHljLNV_Natf.jpg

478 ms

ecom

ecom

354 ms

0f000PpQk6Q4JPAt-_kMl6.jpg

0f000PpQk6Q4JPAt-_kMl6.jpg

677 ms

ecom

ecom

358 ms

0f000DTw8Wa_d8sgwQ8Ce0.jpg

0f000DTw8Wa_d8sgwQ8Ce0.jpg

502 ms

ecom

ecom

344 ms

0f0002Wyok98zpE03-PO06.gif

0f0002Wyok98zpE03-PO06.gif

694 ms

ecom

ecom

447 ms

0f000AjMbfmuK8gKoX7DV0.jpg

0f000AjMbfmuK8gKoX7DV0.jpg

714 ms

ecom

ecom

331 ms

0f000QkbRNYHljLNV_Nalf.jpg

0f000QkbRNYHljLNV_Nalf.jpg

487 ms

ecom

ecom

350 ms

ecom

ecom

345 ms

0f0002dkZ5rmSV9FMbXxbs.png

0f0002dkZ5rmSV9FMbXxbs.png

955 ms

ecom

ecom

339 ms

0f0005r4Sr-3ZcRFKpTjzs.jpg

0f0005r4Sr-3ZcRFKpTjzs.jpg

505 ms

ecom

ecom

343 ms

0f000nSU8kug0xle8HC4zf.jpg

0f000nSU8kug0xle8HC4zf.jpg

474 ms

o.htm

o.htm

336 ms

wh.js

wh.js

685 ms

ac.js

ac.js

462 ms

hm.gif

hm.gif

784 ms

SEO Factors

taidi.us SEO score

0

Language and Encoding

  • Language Detected

    ZH

  • Language Claimed

    N/A

  • Encoding

    GBK

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Taidi.us 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 Taidi.us 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

taidi.us

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