Tools & Wizards About Us
wedoexpress.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

wedoexpress.com

运德国际物流-专业高效的跨境电商物流服务商

Page Load Speed

7.6 sec in total

First Response

240 ms

Resources Loaded

7 sec

Page Rendered

360 ms

wedoexpress.com screenshot

About Website

Welcome to wedoexpress.com homepage info - get ready to check Wedoexpress best content for Mexico right away, or after learning these important things about wedoexpress.com

深圳市前海运德供应链管理有限公司是一家集国际运输、仓储配送、系统软件服务应用的供应链服务商。主营业务美国海运空运,超大件,海外仓,小包快递,FCL整柜,LCL拼柜,纯电电池海运等。依托强大的系统技术集成能力，为广大涉及国际贸易的制造商、贸易商、跨境电商客户提供涵盖信息流、资金流、物流的端到端整体解决方案。

Visit wedoexpress.com

Key Findings

We analyzed Wedoexpress.com page load time and found that the first response time was 240 ms and then it took 7.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

wedoexpress.com performance score

0

Network Requests Diagram

en

240 ms

252 ms

style.css

786 ms

misc.css

1028 ms

jquery-1.10.1.js

1505 ms

Our browser made a total of 85 requests to load all elements on the main page. We found that 87% of them (74 requests) were addressed to the original Wedoexpress.com, 4% (3 requests) were made to S7.addthis.com and 1% (1 request) were made to S22.cnzz.com. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Wedoexpress.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 845.5 kB (56%)

Content Size

1.5 MB

After Optimization

675.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-84%

Potential reduce by 206.5 kB

  • Original 247.1 kB
  • After minification 204.3 kB
  • After compression 40.6 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. This page needs HTML code to be minified as it can gain 42.8 kB, which is 17% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 206.5 kB or 84% of the original size.

Image Optimization

-25%

Potential reduce by 145.3 kB

  • Original 571.5 kB
  • After minification 426.2 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, Wedoexpress needs image optimization as it can save up to 145.3 kB or 25% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-68%

Potential reduce by 414.1 kB

  • Original 606.7 kB
  • After minification 606.7 kB
  • After compression 192.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 414.1 kB or 68% of the original size.

CSS Optimization

-84%

Potential reduce by 79.6 kB

  • Original 95.3 kB
  • After minification 88.1 kB
  • After compression 15.7 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. Wedoexpress.com needs all CSS files to be minified and compressed as it can save up to 79.6 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 12 (14%)

Requests Now

83

After Optimization

71

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

en

en

240 ms

252 ms

style.css

style.css

786 ms

misc.css

misc.css

1028 ms

jquery-1.10.1.js

jquery-1.10.1.js

1505 ms

common.js

common.js

788 ms

base.js

base.js

796 ms

wedoGg.js

wedoGg.js

799 ms

t_ship.js

t_ship.js

1023 ms

highcharts.js

highcharts.js

1526 ms

home.js

home.js

1038 ms

addthis_widget.js

addthis_widget.js

13 ms

max-logo.png

max-logo.png

239 ms

mini-logo.png

mini-logo.png

239 ms

fb.png

fb.png

241 ms

tr.png

tr.png

242 ms

20150703105701_61440.jpg

20150703105701_61440.jpg

530 ms

20150703110604_48989.jpg

20150703110604_48989.jpg

713 ms

track_box.gif

track_box.gif

475 ms

seach_bt.png

seach_bt.png

477 ms

20150505120013_53254.jpg

20150505120013_53254.jpg

477 ms

track-h1.gif

track-h1.gif

478 ms

logo-list1.png

logo-list1.png

1662 ms

track328.gif

track328.gif

716 ms

track329.gif

track329.gif

714 ms

track330.gif

track330.gif

998 ms

track331.gif

track331.gif

768 ms

track332.gif

track332.gif

947 ms

track333.gif

track333.gif

953 ms

track334.gif

track334.gif

953 ms

track335.gif

track335.gif

1248 ms

track336.gif

track336.gif

1184 ms

track337.gif

track337.gif

1192 ms

track338.gif

track338.gif

1192 ms

track339.gif

track339.gif

1235 ms

track340.gif

track340.gif

1421 ms

track341.gif

track341.gif

1428 ms

track342.gif

track342.gif

1428 ms

track343.gif

track343.gif

1710 ms

track344.gif

track344.gif

1487 ms

track345.gif

track345.gif

1657 ms

track346.gif

track346.gif

1665 ms

track347.gif

track347.gif

1665 ms

track348.gif

track348.gif

1727 ms

track349.gif

track349.gif

1953 ms

track350.gif

track350.gif

1952 ms

logo-list2.png

logo-list2.png

2001 ms

z_stat.php

z_stat.php

1785 ms

track351.gif

track351.gif

1974 ms

track352.gif

track352.gif

2010 ms

track353.gif

track353.gif

1824 ms

track354.gif

track354.gif

1958 ms

track355.gif

track355.gif

1958 ms

track356.gif

track356.gif

1774 ms

track357.gif

track357.gif

1772 ms

track358.gif

track358.gif

1827 ms

track359.gif

track359.gif

1956 ms

json.php

json.php

1910 ms

json.php

json.php

1778 ms

track360.gif

track360.gif

1771 ms

track361.gif

track361.gif

1770 ms

track362.gif

track362.gif

1775 ms

track363.gif

track363.gif

1769 ms

track364.gif

track364.gif

1765 ms

track365.gif

track365.gif

1810 ms

track366.gif

track366.gif

1768 ms

track367.gif

track367.gif

1584 ms

stat.htm

stat.htm

167 ms

core.php

core.php

757 ms

dialog-bt.png

dialog-bt.png

296 ms

pop-sel.gif

pop-sel.gif

319 ms

under.png

under.png

326 ms

msgboxicon.png

msgboxicon.png

375 ms

guide-close.png

guide-close.png

375 ms

guide-bg.png

guide-bg.png

1339 ms

json.php

json.php

423 ms

json.php

json.php

495 ms

300lo.json

300lo.json

64 ms

sh.7c7179124ea24ac6ba46caac.html

sh.7c7179124ea24ac6ba46caac.html

44 ms

8 ms

layers.648fb6c882fbeb98be27.js

layers.648fb6c882fbeb98be27.js

35 ms

20150511150332_25071.jpg

20150511150332_25071.jpg

714 ms

fql

fql

58 ms

shares.json

shares.json

56 ms

share

share

110 ms

SEO Factors

wedoexpress.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 Wedoexpress.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 Wedoexpress.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

wedoexpress.com

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