Tools & Wizards About Us
whsyy.net screenshot

Report Summary

  • 43

    Performance

    Renders faster than
    62% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 68

    SEO

    Google-friendlier than
    28% of websites

whsyy.net

武汉市第三医院

Page Load Speed

48.2 sec in total

First Response

2.3 sec

Resources Loaded

45.5 sec

Page Rendered

388 ms

whsyy.net screenshot

About Website

Click here to check amazing Whsyy content. Otherwise, check out these important facts you probably never knew about whsyy.net

武汉市第三医院

Visit whsyy.net

Key Findings

We analyzed Whsyy.net page load time and found that the first response time was 2.3 sec and then it took 45.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there were 36 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

whsyy.net performance score

43

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

31/100

10%

LCP (Largest Contentful Paint)

Value5.0 s

27/100

25%

SI (Speed Index)

Value12.4 s

3/100

10%

TBT (Total Blocking Time)

Value280 ms

81/100

30%

CLS (Cumulative Layout Shift)

Value0.882

3/100

15%

TTI (Time to Interactive)

Value4.8 s

79/100

10%

Network Requests Diagram

whsyy.net

2259 ms

css.css

1221 ms

jquery.js

4338 ms

MSClass.js

2679 ms

dropdown.js

880 ms

Our browser made a total of 93 requests to load all elements on the main page. We found that 99% of them (92 requests) were addressed to the original Whsyy.net, 1% (1 request) were made to S13.cnzz.com. The less responsive or slowest element that took the longest time to load (20.3 sec) belongs to the original domain Whsyy.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 155.1 kB (11%)

Content Size

1.4 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-79%

Potential reduce by 34.3 kB

  • Original 43.5 kB
  • After minification 43.2 kB
  • After compression 9.2 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 34.3 kB or 79% of the original size.

Image Optimization

-5%

Potential reduce by 70.8 kB

  • Original 1.3 MB
  • After minification 1.2 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. Whsyy images are well optimized though.

JavaScript Optimization

-60%

Potential reduce by 29.0 kB

  • Original 48.7 kB
  • After minification 47.7 kB
  • After compression 19.7 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 29.0 kB or 60% of the original size.

CSS Optimization

-80%

Potential reduce by 21.0 kB

  • Original 26.3 kB
  • After minification 23.8 kB
  • After compression 5.3 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. Whsyy.net needs all CSS files to be minified and compressed as it can save up to 21.0 kB or 80% of the original size.

Requests Breakdown

Number of requests can be reduced by 7 (13%)

Requests Now

54

After Optimization

47

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

whsyy.net

whsyy.net

2259 ms

css.css

css.css

1221 ms

jquery.js

jquery.js

4338 ms

MSClass.js

MSClass.js

2679 ms

dropdown.js

dropdown.js

880 ms

cn.index.js

cn.index.js

833 ms

cn.global.js

cn.global.js

1253 ms

picshow.js

picshow.js

876 ms

jquery-1.8.3.min.js

jquery-1.8.3.min.js

1614 ms

myjs.js

myjs.js

843 ms

logo.gif

logo.gif

744 ms

i1.gif

i1.gif

386 ms

i2.gif

i2.gif

417 ms

i3.gif

i3.gif

352 ms

1384150225.jpg

1384150225.jpg

19680 ms

1383527091.jpg

1383527091.jpg

19680 ms

1386820462.jpg

1386820462.jpg

19681 ms

1459472237.png

1459472237.png

19681 ms

1458181942.png

1458181942.png

19682 ms

1457053074.jpg

1457053074.jpg

4127 ms

1457052463.png

1457052463.png

15761 ms

1456541468.png

1456541468.png

19682 ms

ryjclc.gif

ryjclc.gif

19683 ms

bmzs.gif

bmzs.gif

19684 ms

hmhd.gif

hmhd.gif

19684 ms

ksfb.gif

ksfb.gif

19687 ms

jkjz.gif

jkjz.gif

19687 ms

yydz.gif

yydz.gif

19688 ms

img1.gif

img1.gif

19688 ms

jiantou_left.jpg

jiantou_left.jpg

19689 ms

1453346794.jpg

1453346794.jpg

19689 ms

1453363726.jpg

1453363726.jpg

19691 ms

1453366009.png

1453366009.png

19691 ms

1453357678.jpg

1453357678.jpg

19691 ms

1453346494.png

1453346494.png

19692 ms

1453358419.jpg

1453358419.jpg

19692 ms

1453356179.jpg

1453356179.jpg

19693 ms

1453513004.png

1453513004.png

19692 ms

1453336281.png

1453336281.png

19692 ms

1453432562.jpg

1453432562.jpg

19693 ms

1453360359.jpg

1453360359.jpg

19694 ms

1453515129.png

1453515129.png

19693 ms

jiantou_right.jpg

jiantou_right.jpg

19694 ms

ksdh.gif

ksdh.gif

19695 ms

x_b.gif

x_b.gif

19696 ms

hltd_0820.JPG

hltd_0820.JPG

19688 ms

djxf.jpg

djxf.jpg

20325 ms

yk_0820.jpg

yk_0820.jpg

20291 ms

x11.gif

x11.gif

20262 ms

x2.gif

x2.gif

19936 ms

z_stat.php

z_stat.php

2074 ms

1426233013.jpg

1426233013.jpg

19546 ms

1426232889.jpg

1426232889.jpg

10291 ms

1426232334.jpg

1426232334.jpg

9356 ms

1426232911.jpg

1426232911.jpg

5354 ms

1426232949.jpg

1426232949.jpg

6228 ms

1426232992.png

1426232992.png

20000 ms

xl.gif

xl.gif

5341 ms

wx.gif

wx.gif

5755 ms

ewm.gif

ewm.gif

5745 ms

top_bg.gif

top_bg.gif

6587 ms

t_l_bg.png

t_l_bg.png

6863 ms

ss_bg.gif

ss_bg.gif

8333 ms

btn_bg.gif

btn_bg.gif

6696 ms

bg.gif

bg.gif

6979 ms

bo_bg.png

bo_bg.png

7057 ms

hw_000505.gif

hw_000505.gif

7302 ms

a.gif

a.gif

7383 ms

h.gif

h.gif

7400 ms

qh_bg.gif

qh_bg.gif

9004 ms

bt_bg.png

bt_bg.png

7790 ms

i_h.png

i_h.png

7762 ms

i_a.png

i_a.png

8148 ms

ico_li.gif

ico_li.gif

8226 ms

yjj.png

yjj.png

8835 ms

yygk_h2.gif

yygk_h2.gif

8638 ms

yy_bg.gif

yy_bg.gif

10092 ms

yygh_h2.gif

yygh_h2.gif

9098 ms

zjfc_h2_bg.gif

zjfc_h2_bg.gif

9176 ms

zjfh_h2.gif

zjfh_h2.gif

9436 ms

a_k.gif

a_k.gif

9511 ms

h2_bg1.gif

h2_bg1.gif

9529 ms

62.gif

62.gif

9735 ms

62a.gif

62a.gif

10234 ms

71.png

71.png

9650 ms

ys.gif

ys.gif

9653 ms

yy_k.gif

yy_k.gif

9193 ms

hltd_d.gif

hltd_d.gif

7708 ms

li_i1.gif

li_i1.gif

6383 ms

ss_dib.gif

ss_dib.gif

6906 ms

tss_bg.gif

tss_bg.gif

5329 ms

foot_bg.gif

foot_bg.gif

5725 ms

hw_000506.gif

hw_000506.gif

5441 ms

Accessibility Review

whsyy.net accessibility score

75

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.

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

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

whsyy.net best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

whsyy.net SEO score

68

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

High

robots.txt is not valid

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document doesn't use legible font sizes

High

Tap targets are not sized appropriately

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 Whsyy.net 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 Whsyy.net 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

whsyy.net

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