Tools & Wizards About Us
e.58.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

e.58.com

【58同城生活服务推广|如何成为58会员】 -58推广

Page Load Speed

48.7 sec in total

First Response

4.9 sec

Resources Loaded

43.5 sec

Page Rendered

320 ms

e.58.com screenshot

About Website

Click here to check amazing E 58 content for China. Otherwise, check out these important facts you probably never knew about e.58.com

58同城生活服务推广,为您量身订造的网络推广服务,包含招聘、房产、二手、生活服务等多行业推广优化,门槛低,收费低,覆盖面广,效果显著.成为58会员即可享受全方位高效推广.详情咨询58推广咨询热线

Visit e.58.com

Key Findings

We analyzed E.58.com page load time and found that the first response time was 4.9 sec and then it took 43.8 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 was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

e.58.com performance score

0

Network Requests Diagram

e.58.com

4926 ms

base.css

3978 ms

module.css

790 ms

e58.css

3525 ms

createElement-lte-IE8.js

331 ms

Our browser made a total of 59 requests to load all elements on the main page. We found that 63% of them (37 requests) were addressed to the original E.58.com, 8% (5 requests) were made to Img.58cdn.com.cn and 5% (3 requests) were made to Chat16.live800.com. The less responsive or slowest element that took the longest time to load (20.1 sec) belongs to the original domain E.58.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 94.9 kB (15%)

Content Size

622.2 kB

After Optimization

527.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-71%

Potential reduce by 18.5 kB

  • Original 26.0 kB
  • After minification 23.4 kB
  • After compression 7.5 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 18.5 kB or 71% of the original size.

Image Optimization

-6%

Potential reduce by 33.9 kB

  • Original 521.6 kB
  • After minification 487.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. E 58 images are well optimized though.

JavaScript Optimization

-40%

Potential reduce by 15.2 kB

  • Original 38.0 kB
  • After minification 35.3 kB
  • After compression 22.9 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 15.2 kB or 40% of the original size.

CSS Optimization

-75%

Potential reduce by 27.4 kB

  • Original 36.6 kB
  • After minification 32.6 kB
  • After compression 9.2 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. E.58.com needs all CSS files to be minified and compressed as it can save up to 27.4 kB or 75% of the original size.

Requests Breakdown

Number of requests can be reduced by 22 (39%)

Requests Now

56

After Optimization

34

  • Images
  • JavaScript
  • CSS

The browser has sent 56 CSS, Javascripts, AJAX and image requests in order to completely render the main page of E 58. 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 from 6 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

e.58.com

e.58.com

4926 ms

base.css

base.css

3978 ms

module.css

module.css

790 ms

e58.css

e58.css

3525 ms

createElement-lte-IE8.js

createElement-lte-IE8.js

331 ms

jquery-1.8.1.min.js

jquery-1.8.1.min.js

20072 ms

js.js

js.js

682 ms

getCookie_v0.js

getCookie_v0.js

601 ms

sendmsg.js

sendmsg.js

681 ms

tip_v20150714152124.css

tip_v20150714152124.css

69 ms

base_v0.css

base_v0.css

68 ms

friendlinks.css

friendlinks.css

678 ms

ff865aecb6.js

ff865aecb6.js

1731 ms

phone.js

phone.js

420 ms

referrer4.js

referrer4.js

9305 ms

changeCity_v0.js

changeCity_v0.js

277 ms

monitor.js

monitor.js

2387 ms

staticButton.js

staticButton.js

2629 ms

foc_banner01.png

foc_banner01.png

696 ms

foc_banner02.png

foc_banner02.png

723 ms

foc_banner03.png

foc_banner03.png

692 ms

foc_banner04.png

foc_banner04.png

694 ms

logonewbg.png

logonewbg.png

383 ms

logo2.gif

logo2.gif

727 ms

online_consult.png

online_consult.png

377 ms

mini_phone.png

mini_phone.png

1749 ms

mini_online_consult.png

mini_online_consult.png

1936 ms

mini_rocket.png

mini_rocket.png

751 ms

shipin2.jpg

shipin2.jpg

3163 ms

shipin1.jpg

shipin1.jpg

760 ms

shipin3.jpg

shipin3.jpg

7978 ms

shipin4.jpg

shipin4.jpg

2670 ms

shipin5.jpg

shipin5.jpg

1137 ms

anli01.jpg

anli01.jpg

8445 ms

anli01.jpg

anli01.jpg

18718 ms

anli01.jpg

anli01.jpg

7349 ms

anli01.jpg

anli01.jpg

12002 ms

anli01.jpg

anli01.jpg

6676 ms

anli01.jpg

anli01.jpg

18803 ms

blank

blank

17 ms

e58_ico.png

e58_ico.png

586 ms

head.png

head.png

7832 ms

focus-bg01.png

focus-bg01.png

9213 ms

focus-bg02.png

focus-bg02.png

8344 ms

ico-num.png

ico-num.png

8731 ms

ico-13.png

ico-13.png

8828 ms

ico-17.png

ico-17.png

9070 ms

ico-06.png

ico-06.png

10030 ms

ico-14.png

ico-14.png

9430 ms

ico-15.png

ico-15.png

9689 ms

icontactus.png

icontactus.png

9814 ms

empty.js.gif

empty.js.gif

406 ms

hm.js

hm.js

1479 ms

staticButtonStatic.js

staticButtonStatic.js

3795 ms

hm.gif

hm.gif

1145 ms

ga.js

ga.js

138 ms

__utm.gif

__utm.gif

42 ms

1_offline.gif

1_offline.gif

6140 ms

SurferServer

SurferServer

981 ms

SEO Factors

e.58.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 E.58.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 E.58.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

e.58.com

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