771 ms in total
46 ms
628 ms
97 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 46 ms and then it took 725 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.
gohospice.com performance score
name
value
score
weighting
Value4.0 s
23/100
10%
Value6.3 s
11/100
25%
Value4.5 s
72/100
10%
Value50 ms
100/100
30%
Value0.031
100/100
15%
Value7.5 s
47/100
10%
46 ms
207 ms
103 ms
64 ms
165 ms
Our browser made a total of 68 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Gohospice.com, 74% (50 requests) were made to Lhcgroup.wpenginepowered.com and 6% (4 requests) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (207 ms) relates to the external source Lhcgroup.com.
Page size can be reduced by 61.5 kB (3%)
2.3 MB
2.3 MB
In fact, the total size of Gohospice.com main page is 2.3 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. Images take 2.0 MB which makes up the majority of the site volume.
Potential reduce by 56.4 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 8.5 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 56.4 kB or 78% of the original size.
Potential reduce by 0 B
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 3.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. This website has mostly compressed JavaScripts.
Potential reduce by 1.3 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 has all CSS files already compressed.
Number of requests can be reduced by 35 (61%)
57
22
The browser has sent 57 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 15 to 1 for JavaScripts and from 22 to 1 for CSS and as a result speed up the page load time.
gohospice.com
46 ms
lhcgroup.com
207 ms
jsn7oie.css
103 ms
css
64 ms
pgj3yau.css
165 ms
style.min.css
75 ms
style.min.css
67 ms
style.min.css
69 ms
style.min.css
75 ms
style.min.css
68 ms
style.min.css
68 ms
style.min.css
80 ms
blocks.style.build.css
99 ms
front.min.css
84 ms
jquery.powertip.min.css
83 ms
maps_points.css
89 ms
testimonial-rotator-style.css
87 ms
font-awesome.min.css
62 ms
fontawesome.css
95 ms
galliard.css
108 ms
style.css
118 ms
style_ie.css
101 ms
front.min.js
106 ms
jquery.min.js
111 ms
jquery-migrate.min.js
119 ms
jquery.cycletwo.js
120 ms
jquery.cycletwo.addons.js
121 ms
7b34dbdb8257c275c19f082.js
56 ms
jquery.powertip.min.js
157 ms
maps_points.js
158 ms
underscore.min.js
158 ms
backbone.min.js
159 ms
api-request.min.js
157 ms
wp-api.min.js
158 ms
location-autocomplete.js
159 ms
require.js
160 ms
p.css
23 ms
p.css
2 ms
icon_dropdown.png
38 ms
127 ms
icon_search.png
17 ms
icon_close_primary.png
18 ms
LHC-Group-Tagline-Color-web.png
73 ms
LHC-Group-Identifying-Tag-Color.png
15 ms
mobile-home-bg.png
95 ms
Line_Orange_1.png
16 ms
icon_healthcare-professionals.png
74 ms
icon_individuals-and-families.png
75 ms
icon_hospitals-and-health-systems.png
73 ms
ARC_Logo_Bttn_Vert_RGB.png
73 ms
logo-ahia-horizontal-color.png
76 ms
telemedicine_hero.jpg
76 ms
covid-home-health.jpg
74 ms
covid-individual-1800x2000.jpg
75 ms
LHC-physician2-1800x2429.jpg
77 ms
LHC-career1-1800x2133.jpg
83 ms
Landing-Page-Modern-Healthcare-1800x1544.jpg
78 ms
lhcg_color_logo.jpg
84 ms
medical-director-hero.jpg
82 ms
0QI6MX1D_JOuGQbT0gvTJPa787weuxJBkqg.ttf
18 ms
0QI6MX1D_JOuGQbT0gvTJPa787z5vBJBkqg.ttf
26 ms
app.js
152 ms
d
14 ms
d
15 ms
0QI8MX1D_JOuMw_hLdO6T2wV9KnW-MoFoq92mQ.ttf
7 ms
0QI8MX1D_JOuMw_hLdO6T2wV9KnW-C0Coq92mQ.ttf
15 ms
fontawesome-webfont.woff
34 ms
fontawesome-webfont.woff
33 ms
gohospice.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
Image elements do not have [alt] attributes
Links do not have a discernible name
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
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Document uses legible font sizes
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: