Tools & Wizards About Us
wdsz.net screenshot

Report Summary

  • 69

    Performance

    Renders faster than
    81% of other websites

  • 70

    Accessibility

    Visual factors better than
    that of 36% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

wdsz.net

Page Load Speed

11.8 sec in total

First Response

725 ms

Resources Loaded

10.7 sec

Page Rendered

424 ms

wdsz.net screenshot

About Website

Welcome to wdsz.net homepage info - get ready to check Wdsz best content for China right away, or after learning these important things about wdsz.net

武当休闲山庄 一个集原创摄影,街拍,贴图,图文,影视,在线视频,汽车交流,中国功夫,求助解答,生活旅游资讯与一体的中文综合论坛社区

Visit wdsz.net

Key Findings

We analyzed Wdsz.net page load time and found that the first response time was 725 ms and then it took 11.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

wdsz.net performance score

69

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

19/100

10%

LCP (Largest Contentful Paint)

Value5.0 s

28/100

25%

SI (Speed Index)

Value5.0 s

63/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value4.2 s

85/100

10%

Network Requests Diagram

wdsz.net

725 ms

www.wdsz.net

720 ms

pw_core.css

265 ms

core.js

268 ms

pw_ajax.js

267 ms

Our browser made a total of 34 requests to load all elements on the main page. We found that 76% of them (26 requests) were addressed to the original Wdsz.net, 6% (2 requests) were made to Hm.baidu.com and 3% (1 request) were made to Pic.wdsz.net. The less responsive or slowest element that took the longest time to load (5.7 sec) relates to the external source App.open.phpwind.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 211.1 kB (74%)

Content Size

284.2 kB

After Optimization

73.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-79%

Potential reduce by 94.8 kB

  • Original 120.7 kB
  • After minification 118.5 kB
  • After compression 25.9 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 94.8 kB or 79% of the original size.

Image Optimization

-3%

Potential reduce by 211 B

  • Original 7.9 kB
  • After minification 7.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. Wdsz images are well optimized though.

JavaScript Optimization

-74%

Potential reduce by 93.2 kB

  • Original 126.1 kB
  • After minification 100.5 kB
  • After compression 32.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 93.2 kB or 74% of the original size.

CSS Optimization

-78%

Potential reduce by 22.9 kB

  • Original 29.5 kB
  • After minification 27.1 kB
  • After compression 6.6 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. Wdsz.net needs all CSS files to be minified and compressed as it can save up to 22.9 kB or 78% of the original size.

Requests Breakdown

Number of requests can be reduced by 21 (66%)

Requests Now

32

After Optimization

11

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

wdsz.net

wdsz.net

725 ms

www.wdsz.net

www.wdsz.net

720 ms

pw_core.css

pw_core.css

265 ms

core.js

core.js

268 ms

pw_ajax.js

pw_ajax.js

267 ms

Deploy.js

Deploy.js

142 ms

global.js

global.js

272 ms

adminview.js

adminview.js

271 ms

app_global.js

app_global.js

272 ms

zh_cn.js

zh_cn.js

136 ms

l2.gif

l2.gif

847 ms

top.jpg

top.jpg

142 ms

topbar.png

topbar.png

136 ms

logo.gif

logo.gif

142 ms

select_arrow.gif

select_arrow.gif

134 ms

button.png

button.png

142 ms

cate_fold.gif

cate_fold.gif

140 ms

navA.png

navA.png

261 ms

searchA.png

searchA.png

261 ms

down.png

down.png

251 ms

search_btn.png

search_btn.png

251 ms

anc.gif

anc.gif

250 ms

h.png

h.png

199 ms

old.gif

old.gif

326 ms

new.gif

new.gif

332 ms

lock.gif

lock.gif

334 ms

stat.php

stat.php

1360 ms

stat.htm

stat.htm

166 ms

core.php

core.php

1756 ms

pic1.gif

pic1.gif

745 ms

hm.js

hm.js

964 ms

app.open.phpwind.com

app.open.phpwind.com

5723 ms

top.png

top.png

142 ms

hm.gif

hm.gif

325 ms

Accessibility Review

wdsz.net accessibility score

70

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Form elements do not have associated labels

High

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

wdsz.net best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

High

Browser errors were logged to the console

SEO Factors

wdsz.net SEO score

69

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    GBK

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wdsz.net can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Wdsz.net 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

wdsz.net

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