2.3 sec in total
113 ms
1.7 sec
502 ms
Click here to check amazing Future Care content for United States. Otherwise, check out these important facts you probably never knew about futurecare.com
At FutureCare we don't simply provide the best rehabilitation and nursing care – we change lives. We know that your health, or the health of your loved one…
Visit futurecare.comWe analyzed Futurecare.com page load time and found that the first response time was 113 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
futurecare.com performance score
name
value
score
weighting
Value5.7 s
5/100
10%
Value8.7 s
1/100
25%
Value10.6 s
7/100
10%
Value15,430 ms
0/100
30%
Value0.118
85/100
15%
Value28.3 s
0/100
10%
113 ms
718 ms
116 ms
84 ms
87 ms
Our browser made a total of 54 requests to load all elements on the main page. We found that 85% of them (46 requests) were addressed to the original Futurecare.com, 4% (2 requests) were made to Ssl.google-analytics.com and 2% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (718 ms) belongs to the original domain Futurecare.com.
Page size can be reduced by 380.9 kB (23%)
1.7 MB
1.3 MB
In fact, the total size of Futurecare.com main page is 1.7 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. 30% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 18.5 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 3.1 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 18.5 kB or 75% of the original size.
Potential reduce by 120.4 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. Future Care images are well optimized though.
Potential reduce by 69.5 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 69.5 kB or 53% of the original size.
Potential reduce by 172.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. Futurecare.com needs all CSS files to be minified and compressed as it can save up to 172.5 kB or 89% of the original size.
Number of requests can be reduced by 21 (42%)
50
29
The browser has sent 50 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Future Care. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
futurecare.com
113 ms
futurecare.com
718 ms
screen.css
116 ms
under-1024.css
84 ms
under-979.css
87 ms
under-768.css
86 ms
hover.css
169 ms
vital.css
111 ms
owl.carousel.css
149 ms
owl.theme.css
150 ms
jquery.fancybox-buttons.css
150 ms
jquery.fancybox-thumbs.css
180 ms
jquery.fancybox.css
181 ms
jquery.min.js
65 ms
owl.carousel.min.js
261 ms
js
85 ms
equal.height.js
221 ms
jquery.fancybox.js
245 ms
jquery.fancybox-buttons.js
224 ms
jquery.fancybox-thumbs.js
242 ms
jquery.easing-1.3.pack.js
243 ms
jquery.mousewheel-3.0.6.pack.js
307 ms
jquery.jfontsize-1.0.js
301 ms
html-bg.jpg
443 ms
ga.js
141 ms
0.jpg
184 ms
bg_180.png
126 ms
logo_new.png
124 ms
search-button.png
163 ms
navigation-hover.png
162 ms
navigation-seperator.png
161 ms
new_nav_bg.png
225 ms
vital_menu.png
217 ms
pcc-main-banner_003.jpg
350 ms
cardiac-rehab-header.jpg
286 ms
best-nursing-homes-header.jpg
301 ms
vital-strong-header.jpg
362 ms
top-2014.png
327 ms
apply-now.png
352 ms
colleenkennedy-small.jpg
395 ms
map.png
512 ms
facebook.png
402 ms
youtube.png
420 ms
530dee22-e3c1-4e9f-bf62-c31d510d9656.woff
453 ms
bg-button-arrow.png
387 ms
icn-chat.png
428 ms
play-overlay.png
442 ms
leaf.png
453 ms
bg-box-fc.png
458 ms
588c9ba8-1d28-4ad6-bf18-7128152d84c4.woff
464 ms
__utm.gif
33 ms
collect
83 ms
ga-audiences
58 ms
roundtrip.js
32 ms
futurecare.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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
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
futurecare.com 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
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
futurecare.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Futurecare.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Futurecare.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.
futurecare.com
Open Graph description is not detected on the main page of Future Care. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: