Tools & Wizards About Us
amedisys.com screenshot

Report Summary

  • 9

    Performance

    Renders faster than
    23% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 66% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

amedisys.com

Home Health Care, Hospice, Palliative Care | Amedisys

Page Load Speed

3 sec in total

First Response

306 ms

Resources Loaded

2.2 sec

Page Rendered

534 ms

amedisys.com screenshot

About Website

Visit amedisys.com now to see the best up-to-date Amedisys content for United States and also check out these interesting facts you probably never knew about amedisys.com

Amedisys is a leading provider of health care in the home, offering high-quality home health, hospice, palliative care and high-acuity care in 38 states.

Visit amedisys.com

Key Findings

We analyzed Amedisys.com page load time and found that the first response time was 306 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

amedisys.com performance score

9

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

14/100

10%

LCP (Largest Contentful Paint)

Value11.4 s

0/100

25%

SI (Speed Index)

Value10.5 s

7/100

10%

TBT (Total Blocking Time)

Value3,320 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.295

40/100

15%

TTI (Time to Interactive)

Value22.9 s

1/100

10%

Network Requests Diagram

www.amedisys.com

306 ms

b9df37c70e.js

80 ms

app.css

55 ms

slick.css

59 ms

slick-theme.css

60 ms

Our browser made a total of 113 requests to load all elements on the main page. We found that 7% of them (8 requests) were addressed to the original Amedisys.com, 35% (39 requests) were made to Cdn.amedisys.com and 13% (15 requests) were made to D.adroll.com. The less responsive or slowest element that took the longest time to load (746 ms) belongs to the original domain Amedisys.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 162.8 kB (8%)

Content Size

2.0 MB

After Optimization

1.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Amedisys.com main page is 2.0 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 66.7 kB

  • Original 83.0 kB
  • After minification 77.5 kB
  • After compression 16.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 66.7 kB or 80% of the original size.

Image Optimization

-4%

Potential reduce by 46.9 kB

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

JavaScript Optimization

-7%

Potential reduce by 40.5 kB

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

CSS Optimization

-16%

Potential reduce by 8.7 kB

  • Original 53.2 kB
  • After minification 53.2 kB
  • After compression 44.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. Amedisys.com needs all CSS files to be minified and compressed as it can save up to 8.7 kB or 16% of the original size.

Requests Breakdown

Number of requests can be reduced by 51 (60%)

Requests Now

85

After Optimization

34

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.amedisys.com

www.amedisys.com

306 ms

b9df37c70e.js

b9df37c70e.js

80 ms

app.css

app.css

55 ms

slick.css

slick.css

59 ms

slick-theme.css

slick-theme.css

60 ms

css2

css2

60 ms

jquery.js

jquery.js

63 ms

formAbandonment.js

formAbandonment.js

60 ms

outbound.js

outbound.js

64 ms

js

js

111 ms

answers.css

answers.css

56 ms

typed.js@2.0.11

typed.js@2.0.11

56 ms

axios.min.js

axios.min.js

68 ms

answerstemplates.compiled.min.js

answerstemplates.compiled.min.js

66 ms

answers.min.js

answers.min.js

109 ms

what-input.js

what-input.js

62 ms

foundation.js

foundation.js

62 ms

slick.min.js

slick.min.js

62 ms

app.js

app.js

62 ms

addthis_widget.js

addthis_widget.js

359 ms

conversion.js

conversion.js

278 ms

gtm.js

gtm.js

254 ms

analytics.js

analytics.js

181 ms

smallOval.svg

smallOval.svg

156 ms

Home-Health-Service-Card.png

Home-Health-Service-Card.png

403 ms

Hospice-Service-Card.png

Hospice-Service-Card.png

541 ms

Palliative-Care-Service-Card.png

Palliative-Care-Service-Card.png

541 ms

Contessa-Card.png

Contessa-Card.png

658 ms

Benefits-HH.png

Benefits-HH.png

745 ms

What-is-Hospice-Care.png

What-is-Hospice-Care.png

746 ms

Palliative-Care-vs-Hospice.jpg

Palliative-Care-vs-Hospice.jpg

657 ms

horizLogo.svg

horizLogo.svg

36 ms

1000

1000

54 ms

personalizedCare-hover.svg

personalizedCare-hover.svg

336 ms

stars-hover.svg

stars-hover.svg

344 ms

nationalAverage-hover.svg

nationalAverage-hover.svg

292 ms

chosenBy-hover.svg

chosenBy-hover.svg

298 ms

caredFor-hover.svg

caredFor-hover.svg

291 ms

personalizedCare.svg

personalizedCare.svg

54 ms

stars.svg

stars.svg

60 ms

nationalAverage.svg

nationalAverage.svg

61 ms

chosenBy.svg

chosenBy.svg

71 ms

caredFor.svg

caredFor.svg

73 ms

Amedisys_day1009.jpg

Amedisys_day1009.jpg

73 ms

2022-shpbest-hhcahps-premier-performer-badge-sm.png

2022-shpbest-hhcahps-premier-performer-badge-sm.png

77 ms

2022-shpbest-cahps-hospice-premier-performer-badge-sm.png

2022-shpbest-cahps-hospice-premier-performer-badge-sm.png

98 ms

CMS-Star-Rating-5.png

CMS-Star-Rating-5.png

98 ms

questions-footer-bg.jpg

questions-footer-bg.jpg

112 ms

amedisys.svg

amedisys.svg

113 ms

linkedin.png

linkedin.png

218 ms

youtube.png

youtube.png

287 ms

twitter.png

twitter.png

296 ms

facebook.png

facebook.png

296 ms

playPlus.svg

playPlus.svg

295 ms

BackTriangle.svg

BackTriangle.svg

325 ms

0QI6MX1D_JOuGQbT0gvTJPa787weuyJG.ttf

0QI6MX1D_JOuGQbT0gvTJPa787weuyJG.ttf

51 ms

0QI6MX1D_JOuGQbT0gvTJPa787z5vCJG.ttf

0QI6MX1D_JOuGQbT0gvTJPa787z5vCJG.ttf

76 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaooCP.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaooCP.ttf

194 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEooCP.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEooCP.ttf

193 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pYCP.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pYCP.ttf

193 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtapYCP.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtapYCP.ttf

193 ms

collect

collect

26 ms

collect

collect

242 ms

379 ms

app.css

app.css

112 ms

slick.css

slick.css

109 ms

slick-theme.css

slick-theme.css

108 ms

css2

css2

109 ms

answers.css

answers.css

321 ms

ajax-loader.gif

ajax-loader.gif

120 ms

js

js

90 ms

destination

destination

349 ms

149603.js

149603.js

283 ms

fbevents.js

fbevents.js

226 ms

app.js

app.js

345 ms

w.js

w.js

224 ms

roundtrip.js

roundtrip.js

217 ms

ga-audiences

ga-audiences

335 ms

C6A3B3XGMJBUDA3AGGYIVH

C6A3B3XGMJBUDA3AGGYIVH

84 ms

149603.js

149603.js

191 ms

web-interactives-embed.js

web-interactives-embed.js

187 ms

leadflows.js

leadflows.js

76 ms

149603.js

149603.js

103 ms

conversations-embed.js

conversations-embed.js

186 ms

71 ms

out

out

35 ms

DSKQ7HX4BBETPBICAVDD6I

DSKQ7HX4BBETPBICAVDD6I

33 ms

out

out

38 ms

out

out

42 ms

out

out

37 ms

out

out

40 ms

out

out

40 ms

out

out

41 ms

out

out

42 ms

out

out

43 ms

out

out

45 ms

out

out

44 ms

out

out

45 ms

settings.luckyorange.net

settings.luckyorange.net

31 ms

trigger

trigger

107 ms

clickstream.legacy.js

clickstream.legacy.js

17 ms

pixel

pixel

128 ms

tap.php

tap.php

119 ms

Pug

Pug

121 ms

xuid

xuid

6 ms

sync

sync

17 ms

bounce

bounce

24 ms

sd

sd

28 ms

in

in

3 ms

rum

rum

22 ms

blink_green.png

blink_green.png

20 ms

logo-light.png

logo-light.png

6 ms

sound-on-white.png

sound-on-white.png

5 ms

Accessibility Review

amedisys.com accessibility score

87

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

High

[aria-hidden="true"] elements contain focusable descendents

High

ARIA input fields do not have accessible names

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

amedisys.com 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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

amedisys.com SEO score

86

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 Amedisys.com 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 Amedisys.com 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

amedisys.com

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