5.6 sec in total
68 ms
4.2 sec
1.3 sec
Welcome to hospicegso.org homepage info - get ready to check Hospice Gso best content right away, or after learning these important things about hospicegso.org
Our patients are always the author of their life story. AuthoraCare Collective helps them author more moments that matter, regardless of their illness or condition.
Visit hospicegso.orgWe analyzed Hospicegso.org page load time and found that the first response time was 68 ms and then it took 5.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
hospicegso.org performance score
name
value
score
weighting
Value8.7 s
0/100
10%
Value28.4 s
0/100
25%
Value22.1 s
0/100
10%
Value2,300 ms
5/100
30%
Value0
100/100
15%
Value28.7 s
0/100
10%
68 ms
194 ms
213 ms
429 ms
131 ms
Our browser made a total of 140 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Hospicegso.org, 79% (111 requests) were made to Authoracare.org and 4% (6 requests) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (1.8 sec) relates to the external source Cdn.callrail.com.
Page size can be reduced by 407.8 kB (8%)
4.9 MB
4.5 MB
In fact, the total size of Hospicegso.org main page is 4.9 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. 85% 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 4.5 MB which makes up the majority of the site volume.
Potential reduce by 57.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 57.1 kB or 78% of the original size.
Potential reduce by 338.3 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. Hospice Gso images are well optimized though.
Potential reduce by 6.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.
Potential reduce by 5.8 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. Hospicegso.org has all CSS files already compressed.
Number of requests can be reduced by 101 (77%)
132
31
The browser has sent 132 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Hospice Gso. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 67 to 1 for JavaScripts and from 36 to 1 for CSS and as a result speed up the page load time.
hospicegso.org
68 ms
www.authoracare.org
194 ms
gtm.js
213 ms
fbevents.js
429 ms
wp-emoji-release.min.js
131 ms
tribe-events-pro-mini-calendar-block.min.css
307 ms
style.min.css
266 ms
style.min.css
329 ms
style.min.css
307 ms
style.min.css
338 ms
style.min.css
344 ms
style.min.css
433 ms
blocks.style.build.css
434 ms
editor.css
463 ms
styles.css
436 ms
normalize.css
435 ms
foundation.min.css
438 ms
style.css
722 ms
MyFontsWebfontsKit.css
689 ms
iej5poy.css
341 ms
lightbox.min.css
688 ms
custom.css
691 ms
um-fonticons-ii.css
687 ms
um-fonticons-fa.css
718 ms
select2.min.css
949 ms
um-crop.css
977 ms
um-modal.css
947 ms
um-styles.css
1135 ms
um-profile.css
943 ms
um-account.css
944 ms
um-misc.css
1565 ms
um-fileupload.css
1012 ms
default.css
1023 ms
default.date.css
1012 ms
default.time.css
1023 ms
um-raty.css
1044 ms
simplebar.css
1058 ms
um-tipsy.css
1174 ms
um-responsive.css
1042 ms
um-old-default.css
1163 ms
api.js
403 ms
conditionizr-4.3.0.min.js
1169 ms
modernizr-2.7.1.min.js
983 ms
analytics.js
654 ms
bat.js
725 ms
conversion_async.js
721 ms
insight.min.js
743 ms
hotjar-3145918.js
738 ms
js
185 ms
jquery.min.js
1352 ms
jquery-migrate.min.js
979 ms
um-gdpr.min.js
969 ms
email-decode.min.js
960 ms
foundation.min.js
1029 ms
app.js
962 ms
p.css
685 ms
1520590348110091
389 ms
lightbox.min.js
883 ms
TweenMax.min.js
871 ms
TimelineMax.min.js
937 ms
EasePack.min.js
928 ms
ScrollMagic.min.js
919 ms
animation.gsap.min.js
719 ms
scripts.js
703 ms
index.js
712 ms
index.js
676 ms
algoliasearch-lite.umd.js
688 ms
instantsearch.production.min.js
684 ms
algolia-search.js
648 ms
collect
117 ms
regenerator-runtime.min.js
451 ms
wp-polyfill.min.js
457 ms
index.js
451 ms
1205 ms
select2.full.min.js
424 ms
underscore-before.js
427 ms
17227400.js
183 ms
modules.61e17720cf639c3e96a7.js
195 ms
underscore.min.js
393 ms
underscore-after.js
394 ms
wp-util.min.js
374 ms
um-crop.min.js
375 ms
um-modal.min.js
362 ms
collect
238 ms
um-jquery-form.min.js
365 ms
um-fileupload.js
359 ms
picker.js
285 ms
17227400
209 ms
picker.date.js
297 ms
picker.time.js
250 ms
hooks.min.js
255 ms
i18n.min.js
292 ms
um-raty.min.js
187 ms
um-tipsy.min.js
185 ms
imagesloaded.min.js
203 ms
masonry.min.js
200 ms
jquery.masonry.min.js
210 ms
simplebar.min.js
192 ms
um-functions.min.js
153 ms
um-responsive.min.js
152 ms
um-conditional.min.js
149 ms
um-scripts.min.js
148 ms
um-profile.min.js
144 ms
um-account.min.js
387 ms
clarity.js
15 ms
chevron-up.png
338 ms
header-heart.png
353 ms
AuthoraCare_Hz_4c_SM.png
351 ms
search.svg
335 ms
tape-right.png
354 ms
Nurse-2-Stock-Photo.jpg
352 ms
GettyImages-936817640.jpg
1492 ms
tape-left.png
354 ms
GettyImages-1171157710.jpg
1491 ms
GettyImages-849182694.jpg
351 ms
chevron.png
353 ms
search-hover.svg
355 ms
gold-text.png
371 ms
Grandfather-and-child.jpg
366 ms
lightgreen-bottom.png
367 ms
postcard.jpg
372 ms
AdobeStock_340523124-scaled.jpg
371 ms
Website-Service-map.png
414 ms
purple-text.png
371 ms
GettyImages-157165185.jpg
374 ms
4.svg
370 ms
badge.svg
375 ms
persona-mobile.jpg
374 ms
footer-heart.png
378 ms
swap.js
1752 ms
d
1056 ms
d
1056 ms
d
1059 ms
3AA80D_0_0.woff
1407 ms
d
1058 ms
d
1062 ms
1039 ms
recaptcha__en.js
1032 ms
personas.jpg
709 ms
697 ms
hospicegso.org 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
[role] values are not valid
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
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
hospicegso.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
hospicegso.org SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
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 Hospicegso.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 Hospicegso.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.
hospicegso.org
Open Graph data is detected on the main page of Hospice Gso. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: