Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 63

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

piedmont.org

Piedmont Healthcare | Real Change Lives Here

Page Load Speed

7.4 sec in total

First Response

69 ms

Resources Loaded

5.9 sec

Page Rendered

1.5 sec

piedmont.org screenshot

About Website

Click here to check amazing Piedmont content for United States. Otherwise, check out these important facts you probably never knew about piedmont.org

Piedmont is a not-for-profit, community health system. With 25 hospitals and over 1,755 locations, we are empowering our patients through seamless access to high-quality care.

Visit piedmont.org

Key Findings

We analyzed Piedmont.org page load time and found that the first response time was 69 ms and then it took 7.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

piedmont.org performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.6 s

2/100

10%

LCP (Largest Contentful Paint)

Value49.6 s

0/100

25%

SI (Speed Index)

Value10.5 s

7/100

10%

TBT (Total Blocking Time)

Value8,790 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.014

100/100

15%

TTI (Time to Interactive)

Value25.5 s

0/100

10%

Network Requests Diagram

piedmont.org

69 ms

www.piedmont.org

144 ms

css

85 ms

jquery-3.4.1.min.js

64 ms

jquery-migrate-1.4.1.min.js

99 ms

Our browser made a total of 152 requests to load all elements on the main page. We found that 53% of them (80 requests) were addressed to the original Piedmont.org, 6% (9 requests) were made to Googletagmanager.com and 5% (8 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (4.6 sec) belongs to the original domain Piedmont.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 733.4 kB (6%)

Content Size

12.5 MB

After Optimization

11.8 MB

In fact, the total size of Piedmont.org main page is 12.5 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. Only a small number of websites need less resources to load. Images take 11.3 MB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 158.5 kB

  • Original 210.5 kB
  • After minification 185.7 kB
  • After compression 52.0 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 24.8 kB, which is 12% 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 158.5 kB or 75% of the original size.

Image Optimization

-4%

Potential reduce by 493.5 kB

  • Original 11.3 MB
  • After minification 10.8 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. Piedmont images are well optimized though.

JavaScript Optimization

-7%

Potential reduce by 63.0 kB

  • Original 904.5 kB
  • After minification 904.5 kB
  • After compression 841.6 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. This website has mostly compressed JavaScripts.

CSS Optimization

-19%

Potential reduce by 18.5 kB

  • Original 95.6 kB
  • After minification 95.6 kB
  • After compression 77.1 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. Piedmont.org needs all CSS files to be minified and compressed as it can save up to 18.5 kB or 19% of the original size.

Requests Breakdown

Number of requests can be reduced by 81 (62%)

Requests Now

131

After Optimization

50

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

Accessibility Review

piedmont.org accessibility score

63

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

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

<input type="image"> elements do not have [alt] text

High

Form elements do not have associated labels

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

piedmont.org best practices score

58

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

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

piedmont.org SEO score

85

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Links do not have descriptive text

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

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 Piedmont.org 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 Piedmont.org 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

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