4.5 sec in total
95 ms
3.7 sec
718 ms
Visit gohospice.com now to see the best up-to-date Go Hospice content and also check out these interesting facts you probably never knew about gohospice.com
Transitions are challenging, especially when they involve your health or the health of someone you care for. LHC Group is here to help.
Visit gohospice.comWe analyzed Gohospice.com page load time and found that the first response time was 95 ms and then it took 4.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
gohospice.com performance score
name
value
score
weighting
Value5.4 s
7/100
10%
Value8.0 s
3/100
25%
Value17.9 s
0/100
10%
Value22,250 ms
0/100
30%
Value0.022
100/100
15%
Value32.1 s
0/100
10%
95 ms
1981 ms
104 ms
198 ms
88 ms
Our browser made a total of 80 requests to load all elements on the main page. We found that 75% of them (60 requests) were addressed to the original Gohospice.com, 4% (3 requests) were made to Connect.facebook.net and 4% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Gohospice.com.
Page size can be reduced by 514.2 kB (51%)
1.0 MB
503.1 kB
In fact, the total size of Gohospice.com main page is 1.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. 75% 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. HTML takes 361.5 kB which makes up the majority of the site volume.
Potential reduce by 306.9 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 306.9 kB or 85% of the original size.
Potential reduce by 1.8 kB
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. Go Hospice images are well optimized though.
Potential reduce by 10.1 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.
Potential reduce by 195.4 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. Gohospice.com needs all CSS files to be minified and compressed as it can save up to 195.4 kB or 57% of the original size.
Number of requests can be reduced by 55 (79%)
70
15
The browser has sent 70 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Go Hospice. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and from 23 to 1 for CSS and as a result speed up the page load time.
gohospice.com
95 ms
www.gohospice.com
1981 ms
fbevents.js
104 ms
js
198 ms
wp-emoji-release.min.js
88 ms
mediaelementplayer-legacy.min.css
112 ms
wp-mediaelement.min.css
113 ms
style.min.css
115 ms
style.min.css
93 ms
style.min.css
93 ms
style.min.css
114 ms
style.min.css
126 ms
job-listings.css
127 ms
frontend.css
128 ms
css
229 ms
pum-site-styles.css
135 ms
www.gohospice.com.css
157 ms
style.css
205 ms
Defaults.css
137 ms
style.min.css
139 ms
slick.min.css
140 ms
icons.css
202 ms
animate.min.css
199 ms
jetpack.css
203 ms
jquery.min.js
224 ms
frontend-gtag.min.js
228 ms
wpgmza_data.js
287 ms
ultimate-params.min.js
230 ms
slick.min.js
326 ms
jquery-appear.min.js
230 ms
slick-custom.min.js
229 ms
social-proof.v2.js
322 ms
vidcons.css
266 ms
background-style.min.css
265 ms
www.gohospice.com.js
266 ms
core.min.js
259 ms
pum-site-scripts.js
297 ms
pixel-cat.min.js
302 ms
video.compiled.js
301 ms
ultimate_bg.min.js
300 ms
e-202240.js
204 ms
custom.min.js
299 ms
1961921807454796
148 ms
css
155 ms
analytics.js
168 ms
Logo-2019.png
23 ms
Untitled-1-9-1024x384.png
24 ms
News-and-Events_shutterstock_459036295-1024x482-1-1-1024x482.jpg
29 ms
OreIda-Map-for-Web-v3-1024x559.png
24 ms
pexels-marcus-aurelius-6787770-scaled-e1620856340982-1024x576.jpg
33 ms
pexels-david-disponett-2161643-scaled-e1624460464600-1024x576.jpg
30 ms
emailLogo.png
26 ms
FBLogoBLK.png
24 ms
TWLogoBLK.png
26 ms
LILogoBLK.png
30 ms
YTLogoBLK.png
26 ms
Instagram-icon_small.png
28 ms
1071540799589095
86 ms
line-header.png
68 ms
KFOmCnqEu92Fr1Mu4mxM.woff
410 ms
KFOlCnqEu92Fr1MmSU5fBBc-.woff
588 ms
KFOlCnqEu92Fr1MmWUlfBBc-.woff
590 ms
fa-solid-900.woff
187 ms
fa-regular-400.woff
83 ms
material-icons.woff
84 ms
collect
343 ms
fa-brands-400.woff
302 ms
collect
496 ms
embed
489 ms
ajax-loader.gif
168 ms
isotope.js
39 ms
icon-family-active.png
205 ms
icon-heart.png
204 ms
icon-tree.png
205 ms
ult-silk.woff
183 ms
4aafeccc37442ba4b467a8ccda1baf32embedcompiled_fastui.css
46 ms
m=embed
58 ms
client.js
96 ms
ga-audiences
86 ms
cb=gapi.loaded_0
52 ms
gohospice.com accessibility score
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
ARIA input fields do not have accessible names
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
gohospice.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
gohospice.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Gohospice.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 Gohospice.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.
gohospice.com
Open Graph data is detected on the main page of Go Hospice. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: