Tools & Wizards About Us
wch.net screenshot

Report Summary

  • 26

    Performance

    Renders faster than
    47% of other websites

  • 50

    Accessibility

    Visual factors better than
    that of 20% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 81

    SEO

    Google-friendlier than
    43% of websites

wch.net

Bowling Green Hospital | Wood County Hospital - Wood County Hospital

Page Load Speed

1.7 sec in total

First Response

39 ms

Resources Loaded

1 sec

Page Rendered

686 ms

wch.net screenshot

About Website

Visit wch.net now to see the best up-to-date Wch content and also check out these interesting facts you probably never knew about wch.net

Community hospital serving Wood County and surrounding area with advanced technology and specialists in Cancer, Orthopedics, Weight Loss Surgery, Women’s Health and more.

Visit wch.net

Key Findings

We analyzed Wch.net page load time and found that the first response time was 39 ms and then it took 1.7 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

wch.net performance score

26

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

47/100

10%

LCP (Largest Contentful Paint)

Value7.9 s

3/100

25%

SI (Speed Index)

Value5.0 s

63/100

10%

TBT (Total Blocking Time)

Value10,500 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.084

93/100

15%

TTI (Time to Interactive)

Value18.7 s

3/100

10%

Network Requests Diagram

wch.net

39 ms

www.woodcountyhospital.org

68 ms

www.woodcountyhospital.org

161 ms

font-awesome.css

45 ms

css2

48 ms

Our browser made a total of 62 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Wch.net, 37% (23 requests) were made to Tag.simpli.fi and 15% (9 requests) were made to Woodcountyhospital.org. The less responsive or slowest element that took the longest time to load (666 ms) relates to the external source Woodcountyhospital.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 157.4 kB (7%)

Content Size

2.2 MB

After Optimization

2.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-86%

Potential reduce by 42.7 kB

  • Original 49.8 kB
  • After minification 35.0 kB
  • After compression 7.1 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 14.8 kB, which is 30% 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 42.7 kB or 86% of the original size.

Image Optimization

-1%

Potential reduce by 11.9 kB

  • Original 2.0 MB
  • After minification 1.9 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. Wch images are well optimized though.

JavaScript Optimization

-58%

Potential reduce by 102.7 kB

  • Original 175.9 kB
  • After minification 175.9 kB
  • After compression 73.2 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 102.7 kB or 58% of the original size.

CSS Optimization

-1%

Potential reduce by 78 B

  • Original 10.0 kB
  • After minification 10.0 kB
  • After compression 10.0 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. Wch.net has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 43 (83%)

Requests Now

52

After Optimization

9

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

wch.net

wch.net

39 ms

www.woodcountyhospital.org

www.woodcountyhospital.org

68 ms

www.woodcountyhospital.org

www.woodcountyhospital.org

161 ms

font-awesome.css

font-awesome.css

45 ms

css2

css2

48 ms

css2

css2

66 ms

DependencyHandler.axd

DependencyHandler.axd

59 ms

ace4f7e0-a7c5-0135-df7e-06659b33d47c

ace4f7e0-a7c5-0135-df7e-06659b33d47c

35 ms

DependencyHandler.axd

DependencyHandler.axd

57 ms

gtm.js

gtm.js

62 ms

sprite.svg

sprite.svg

35 ms

wood-county-hospital-logo.png

wood-county-hospital-logo.png

45 ms

forbes_best_employers_homepage_banner__1920x670px.jpg

forbes_best_employers_homepage_banner__1920x670px.jpg

412 ms

100_rural_hospitals_homepage_banner__1920x670px_.jpeg

100_rural_hospitals_homepage_banner__1920x670px_.jpeg

335 ms

cwls_part_of_your_life_homepage_banner__1920x670px.jpeg

cwls_part_of_your_life_homepage_banner__1920x670px.jpeg

666 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4kY1M2xYkS.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4kY1M2xYkS.woff

27 ms

analytics.js

analytics.js

255 ms

hotjar-360244.js

hotjar-360244.js

354 ms

loader.js

loader.js

248 ms

dpx.js

dpx.js

320 ms

fbevents.js

fbevents.js

248 ms

22532cb0-6c0c-0136-d2ff-06a9ed4ca31b

22532cb0-6c0c-0136-d2ff-06a9ed4ca31b

94 ms

2ca3d670-6c0c-0136-d2ff-06a9ed4ca31b

2ca3d670-6c0c-0136-d2ff-06a9ed4ca31b

227 ms

9e70daf0-605a-0136-4b3c-067f653fa718

9e70daf0-605a-0136-4b3c-067f653fa718

244 ms

3d1dee60-6c0c-0136-d2ff-06a9ed4ca31b

3d1dee60-6c0c-0136-d2ff-06a9ed4ca31b

301 ms

43160c10-6c0c-0136-d2ff-06a9ed4ca31b

43160c10-6c0c-0136-d2ff-06a9ed4ca31b

229 ms

d8acdaf0-6385-0136-eef6-06659b33d47c

d8acdaf0-6385-0136-eef6-06659b33d47c

242 ms

407fee00-6759-0136-d2a6-06a9ed4ca31b

407fee00-6759-0136-d2a6-06a9ed4ca31b

317 ms

19a7fcc0-2a00-0136-e8e5-06659b33d47c

19a7fcc0-2a00-0136-e8e5-06659b33d47c

316 ms

d452e190-a4c2-0136-d76a-06a9ed4ca31b

d452e190-a4c2-0136-d76a-06a9ed4ca31b

300 ms

Bootstrap.js

Bootstrap.js

319 ms

up_loader.1.1.0.js

up_loader.1.1.0.js

299 ms

978e3be0-685c-0137-e63c-06a9ed4ca31b

978e3be0-685c-0137-e63c-06a9ed4ca31b

314 ms

up.js

up.js

346 ms

37df7dc0-eee7-0138-7edf-06b4c2516bae

37df7dc0-eee7-0138-7edf-06b4c2516bae

314 ms

d26b95f0-9350-013a-c72e-06a60fe5fe77

d26b95f0-9350-013a-c72e-06a60fe5fe77

343 ms

js

js

131 ms

6xK-dSZaM9iE8KbpRA_LJ3z8mH9BOJvgkP8o18K0wx41eD8.woff

6xK-dSZaM9iE8KbpRA_LJ3z8mH9BOJvgkP8o18K0wx41eD8.woff

138 ms

6xK-dSZaM9iE8KbpRA_LJ3z8mH9BOJvgkM0o18K0wx41eD8.woff

6xK-dSZaM9iE8KbpRA_LJ3z8mH9BOJvgkM0o18K0wx41eD8.woff

201 ms

6xK-dSZaM9iE8KbpRA_LJ3z8mH9BOJvgkKEo18K0wx41eD8.woff

6xK-dSZaM9iE8KbpRA_LJ3z8mH9BOJvgkKEo18K0wx41eD8.woff

225 ms

6xK-dSZaM9iE8KbpRA_LJ3z8mH9BOJvgkCEv18K0wx41eD8.woff

6xK-dSZaM9iE8KbpRA_LJ3z8mH9BOJvgkCEv18K0wx41eD8.woff

226 ms

6xK-dSZaM9iE8KbpRA_LJ3z8mH9BOJvgkBgv18K0wx41eD8.woff

6xK-dSZaM9iE8KbpRA_LJ3z8mH9BOJvgkBgv18K0wx41eD8.woff

225 ms

call-tracking_7.js

call-tracking_7.js

100 ms

2032385770106158

2032385770106158

81 ms

collect

collect

59 ms

22532cb0-6c0c-0136-d2ff-06a9ed4ca31b

22532cb0-6c0c-0136-d2ff-06a9ed4ca31b

76 ms

e59156d0-6845-0137-54cb-06659b33d47c

e59156d0-6845-0137-54cb-06659b33d47c

77 ms

serverComponent.php

serverComponent.php

72 ms

368660708302535

368660708302535

26 ms

modules.61e17720cf639c3e96a7.js

modules.61e17720cf639c3e96a7.js

74 ms

f894ed90-ec70-0138-7ec4-06b4c2516bae

f894ed90-ec70-0138-7ec4-06b4c2516bae

36 ms

ea56f93204fe867df462f8935ac9693e.js

ea56f93204fe867df462f8935ac9693e.js

44 ms

0c074068ac691bbb51cd7b48c8ab7490.js

0c074068ac691bbb51cd7b48c8ab7490.js

44 ms

19a7fcc0-2a00-0136-e8e5-06659b33d47c

19a7fcc0-2a00-0136-e8e5-06659b33d47c

36 ms

28dc0cc0-ebe9-0138-7ec0-06b4c2516bae

28dc0cc0-ebe9-0138-7ec0-06b4c2516bae

20 ms

box-69edcc3187336f9b0a3fbb4c73be9fe6.html

box-69edcc3187336f9b0a3fbb4c73be9fe6.html

90 ms

wcm

wcm

105 ms

9e70daf0-605a-0136-4b3c-067f653fa718

9e70daf0-605a-0136-4b3c-067f653fa718

66 ms

b9d54900-4963-0139-3c78-06abc14c0bc6

b9d54900-4963-0139-3c78-06abc14c0bc6

65 ms

3d1dee60-6c0c-0136-d2ff-06a9ed4ca31b

3d1dee60-6c0c-0136-d2ff-06a9ed4ca31b

22 ms

43160c10-6c0c-0136-d2ff-06a9ed4ca31b

43160c10-6c0c-0136-d2ff-06a9ed4ca31b

4 ms

2ca3d670-6c0c-0136-d2ff-06a9ed4ca31b

2ca3d670-6c0c-0136-d2ff-06a9ed4ca31b

11 ms

Accessibility Review

wch.net accessibility score

50

Accessibility Issues

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

wch.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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

wch.net SEO score

81

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Page is blocked from indexing

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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 uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wch.net can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Wch.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

wch.net

Open Graph data is detected on the main page of Wch. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: