Tools & Wizards About Us
hospicecares.cc screenshot

Report Summary

  • 30

    Performance

    Renders faster than
    49% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 83% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

hospicecares.cc

Hospice Cleveland County | Hospice and Palliative Care | Shelby, NC

Page Load Speed

7.6 sec in total

First Response

1.6 sec

Resources Loaded

5 sec

Page Rendered

885 ms

hospicecares.cc screenshot

About Website

Click here to check amazing Hospice Care S content. Otherwise, check out these important facts you probably never knew about hospicecares.cc

Hospice Cleveland County exists to provide compassionate care and support for individuals with a life-limiting illness, regardless of their ability to pay.

Visit hospicecares.cc

Key Findings

We analyzed Hospicecares.cc page load time and found that the first response time was 1.6 sec and then it took 5.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

hospicecares.cc performance score

30

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.9 s

0/100

10%

LCP (Largest Contentful Paint)

Value20.8 s

0/100

25%

SI (Speed Index)

Value16.4 s

0/100

10%

TBT (Total Blocking Time)

Value530 ms

56/100

30%

CLS (Cumulative Layout Shift)

Value0.108

87/100

15%

TTI (Time to Interactive)

Value19.9 s

2/100

10%

Network Requests Diagram

www.hospicecares.cc

1649 ms

wp-emoji-release.min.js

14 ms

style.min.css

21 ms

fusion-5.min.css

37 ms

jquery.js

18 ms

Our browser made a total of 132 requests to load all elements on the main page. We found that 91% of them (120 requests) were addressed to the original Hospicecares.cc, 4% (5 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Hospicecares.cc.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.6 MB (32%)

Content Size

5.1 MB

After Optimization

3.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Hospicecares.cc main page is 5.1 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. 55% of websites need less resources to load. Images take 3.3 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 86.3 kB

  • Original 104.4 kB
  • After minification 102.0 kB
  • After compression 18.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. 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 86.3 kB or 83% of the original size.

Image Optimization

-6%

Potential reduce by 201.2 kB

  • Original 3.3 MB
  • After minification 3.1 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. Hospice Care S images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 621.9 kB

  • Original 907.7 kB
  • After minification 907.6 kB
  • After compression 285.8 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 621.9 kB or 69% of the original size.

CSS Optimization

-87%

Potential reduce by 692.8 kB

  • Original 800.9 kB
  • After minification 797.0 kB
  • After compression 108.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. Hospicecares.cc needs all CSS files to be minified and compressed as it can save up to 692.8 kB or 87% of the original size.

Requests Breakdown

Number of requests can be reduced by 102 (82%)

Requests Now

125

After Optimization

23

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.hospicecares.cc

www.hospicecares.cc

1649 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

14 ms

style.min.css

style.min.css

21 ms

fusion-5.min.css

fusion-5.min.css

37 ms

jquery.js

jquery.js

18 ms

jquery-migrate.min.js

jquery-migrate.min.js

18 ms

js

js

105 ms

jquery.fitvids.js

jquery.fitvids.js

16 ms

fusion-video-general.js

fusion-video-general.js

33 ms

jquery.ilightbox.js

jquery.ilightbox.js

88 ms

jquery.mousewheel.js

jquery.mousewheel.js

31 ms

fusion-lightbox.js

fusion-lightbox.js

32 ms

imagesLoaded.js

imagesLoaded.js

87 ms

isotope.js

isotope.js

121 ms

packery.js

packery.js

141 ms

avada-portfolio.js

avada-portfolio.js

102 ms

jquery.infinitescroll.js

jquery.infinitescroll.js

141 ms

avada-faqs.js

avada-faqs.js

101 ms

fusion-equal-heights.js

fusion-equal-heights.js

140 ms

fusion-events.js

fusion-events.js

158 ms

cssua.js

cssua.js

150 ms

jquery.waypoints.js

jquery.waypoints.js

150 ms

modernizr.js

modernizr.js

151 ms

fusion-waypoints.js

fusion-waypoints.js

157 ms

fusion-animations.js

fusion-animations.js

255 ms

jquery.countTo.js

jquery.countTo.js

283 ms

jquery.appear.js

jquery.appear.js

292 ms

fusion-counters-box.js

fusion-counters-box.js

292 ms

jquery.fusion_maps.js

jquery.fusion_maps.js

342 ms

fusion-google-map.js

fusion-google-map.js

317 ms

jquery.fade.js

jquery.fade.js

317 ms

jquery.requestAnimationFrame.js

jquery.requestAnimationFrame.js

316 ms

fusion-parallax.js

fusion-parallax.js

341 ms

fusion-video-bg.js

fusion-video-bg.js

347 ms

fusion-container.js

fusion-container.js

350 ms

fusion-content-boxes.js

fusion-content-boxes.js

352 ms

jquery.event.move.js

jquery.event.move.js

353 ms

fusion-image-before-after.js

fusion-image-before-after.js

348 ms

fusion-gallery.js

fusion-gallery.js

342 ms

bootstrap.transition.js

bootstrap.transition.js

360 ms

bootstrap.tab.js

bootstrap.tab.js

373 ms

fusion-tabs.js

fusion-tabs.js

362 ms

Chart.js

Chart.js

375 ms

fusion-chart.js

fusion-chart.js

357 ms

bootstrap.collapse.js

bootstrap.collapse.js

355 ms

sdk.js

sdk.js

68 ms

fusion-toggles.js

fusion-toggles.js

318 ms

fusion-column-bg-image.js

fusion-column-bg-image.js

358 ms

fusion-column.js

fusion-column.js

351 ms

jquery.easyPieChart.js

jquery.easyPieChart.js

350 ms

fusion-counters-circle.js

fusion-counters-circle.js

342 ms

jquery.cycle.js

jquery.cycle.js

337 ms

js

js

161 ms

analytics.js

analytics.js

181 ms

fusion-testimonials.js

fusion-testimonials.js

318 ms

fusion-progress.js

fusion-progress.js

319 ms

fusion-title.js

fusion-title.js

319 ms

bootstrap.modal.js

bootstrap.modal.js

317 ms

sdk.js

sdk.js

12 ms

fusion-modal.js

fusion-modal.js

311 ms

jquery.countdown.js

jquery.countdown.js

314 ms

fusion-countdown.js

fusion-countdown.js

314 ms

fusion-recent-posts.js

fusion-recent-posts.js

311 ms

fusion-syntax-highlighter.js

fusion-syntax-highlighter.js

217 ms

109 ms

fusion-flip-boxes.js

fusion-flip-boxes.js

188 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

70 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf

86 ms

7Aulp_0qiz-aVz7u3PJLcUMYOFkpl0k30e0.ttf

7Aulp_0qiz-aVz7u3PJLcUMYOFkpl0k30e0.ttf

100 ms

2-cO9IRs1JiJN1FRAMjTN5zd9vgsFF_5asQTb6hZ2JKZRekViesC.ttf

2-cO9IRs1JiJN1FRAMjTN5zd9vgsFF_5asQTb6hZ2JKZRekViesC.ttf

141 ms

2-cO9IRs1JiJN1FRAMjTN5zd9vgsFF_5asQTb6hZ2JKZou4ViesC.ttf

2-cO9IRs1JiJN1FRAMjTN5zd9vgsFF_5asQTb6hZ2JKZou4ViesC.ttf

155 ms

vimeoPlayer.js

vimeoPlayer.js

185 ms

fusion-video.js

fusion-video.js

177 ms

jquery.hoverintent.js

jquery.hoverintent.js

182 ms

avada-vertical-menu-widget.js

avada-vertical-menu-widget.js

160 ms

bootstrap.tooltip.js

bootstrap.tooltip.js

162 ms

bootstrap.popover.js

bootstrap.popover.js

165 ms

collect

collect

36 ms

jquery.carouFredSel.js

jquery.carouFredSel.js

142 ms

jquery.easing.js

jquery.easing.js

138 ms

jquery.flexslider.js

jquery.flexslider.js

139 ms

jquery.hoverflow.js

jquery.hoverflow.js

132 ms

jquery.placeholder.min.js

jquery.placeholder.min.js

136 ms

jquery.touchSwipe.js

jquery.touchSwipe.js

136 ms

fusion-alert.js

fusion-alert.js

139 ms

fusion-carousel.js

fusion-carousel.js

140 ms

fusion-flexslider.js

fusion-flexslider.js

116 ms

fusion-popover.js

fusion-popover.js

112 ms

fusion-tooltip.js

fusion-tooltip.js

113 ms

fusion-sharing-box.js

fusion-sharing-box.js

114 ms

fusion-blog.js

fusion-blog.js

106 ms

fusion-button.js

fusion-button.js

107 ms

fusion-general-global.js

fusion-general-global.js

81 ms

fusion-ie1011.js

fusion-ie1011.js

64 ms

avada-header.js

avada-header.js

68 ms

avada-menu.js

avada-menu.js

68 ms

fusion-scroll-to-anchor.js

fusion-scroll-to-anchor.js

60 ms

fusion-responsive-typography.js

fusion-responsive-typography.js

59 ms

bootstrap.scrollspy.js

bootstrap.scrollspy.js

58 ms

avada-comments.js

avada-comments.js

55 ms

avada-general-footer.js

avada-general-footer.js

57 ms

avada-quantity.js

avada-quantity.js

57 ms

avada-scrollspy.js

avada-scrollspy.js

59 ms

avada-select.js

avada-select.js

59 ms

avada-sidebars.js

avada-sidebars.js

57 ms

jquery.sticky-kit.js

jquery.sticky-kit.js

55 ms

avada-tabs-widget.js

avada-tabs-widget.js

56 ms

jquery.toTop.js

jquery.toTop.js

55 ms

avada-to-top.js

avada-to-top.js

58 ms

avada-drop-down.js

avada-drop-down.js

56 ms

avada-events.js

avada-events.js

53 ms

avada-fusion-slider.js

avada-fusion-slider.js

53 ms

wp-embed.min.js

wp-embed.min.js

51 ms

icomoon.woff

icomoon.woff

123 ms

hospice-logo-notag-80.jpg

hospice-logo-notag-80.jpg

131 ms

premiere-pro-reflections-tutorial.jpg

premiere-pro-reflections-tutorial.jpg

131 ms

memory-bear-pillow.jpg

memory-bear-pillow.jpg

171 ms

2024-CD-Logo.jpg

2024-CD-Logo.jpg

195 ms

Blue-Candles.jpg

Blue-Candles.jpg

131 ms

2024-CD-Logo-700x441.jpg

2024-CD-Logo-700x441.jpg

172 ms

VIA-Holiday-Logo-700x441.jpg

VIA-Holiday-Logo-700x441.jpg

134 ms

recent-news.jpg

recent-news.jpg

182 ms

upcoming-events-pillows.jpg

upcoming-events-pillows.jpg

168 ms

Volunteer-Heading-3-e1559071899320.jpg

Volunteer-Heading-3-e1559071899320.jpg

179 ms

water-drop-bg-2.jpg

water-drop-bg-2.jpg

178 ms

hospice-logo-white-240.png

hospice-logo-white-240.png

177 ms

gold-seal.png

gold-seal.png

180 ms

united-way.jpg

united-way.jpg

185 ms

we-honor-veterans-footer.jpg

we-honor-veterans-footer.jpg

181 ms

nhpco.png

nhpco.png

181 ms

hospice-logo-notag-160.png

hospice-logo-notag-160.png

20 ms

Hospice-Cleveland-County.jpg

Hospice-Cleveland-County.jpg

40 ms

Accessibility Review

hospicecares.cc accessibility score

94

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

hospicecares.cc 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

SEO Factors

hospicecares.cc SEO score

92

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

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 Hospicecares.cc 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 Hospicecares.cc 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

hospicecares.cc

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