Tools & Wizards About Us

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

58wall.com

论坛 - Powered by Discuz!

Page Load Speed

29.9 sec in total

First Response

922 ms

Resources Loaded

28.3 sec

Page Rendered

669 ms

About Website

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

论坛

Visit 58wall.com

Key Findings

We analyzed 58wall.com page load time and found that the first response time was 922 ms and then it took 29 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

58wall.com performance score

0

Network Requests Diagram

www.58wall.com

922 ms

style_41_common.css

219 ms

style_41_forum_index.css

143 ms

common.js

182 ms

forum.js

154 ms

Our browser made a total of 173 requests to load all elements on the main page. We found that 26% of them (45 requests) were addressed to the original 58wall.com, 16% (27 requests) were made to Asearch.alicdn.com and 9% (15 requests) were made to Cpro.baidustatic.com. The less responsive or slowest element that took the longest time to load (20.1 sec) relates to the external source I1.piimg.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 533.8 kB (60%)

Content Size

893.5 kB

After Optimization

359.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-80%

Potential reduce by 76.3 kB

  • Original 95.6 kB
  • After minification 95.3 kB
  • After compression 19.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 76.3 kB or 80% of the original size.

Image Optimization

-10%

Potential reduce by 17.3 kB

  • Original 169.3 kB
  • After minification 152.1 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. 58 Wall images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 374.3 kB

  • Original 547.1 kB
  • After minification 540.5 kB
  • After compression 172.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 374.3 kB or 68% of the original size.

CSS Optimization

-81%

Potential reduce by 65.9 kB

  • Original 81.4 kB
  • After minification 72.0 kB
  • After compression 15.5 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. 58wall.com needs all CSS files to be minified and compressed as it can save up to 65.9 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 73 (45%)

Requests Now

162

After Optimization

89

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

SEO Factors

58wall.com 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 58wall.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 58wall.com 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

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