4 sec in total
429 ms
2.4 sec
1.2 sec
Welcome to elder.org homepage info - get ready to check Elder best content for United Kingdom right away, or after learning these important things about elder.org
Live-in care & dementia care in the comfort of your home. Get a carer in as little as 24 hours. No unexpected costs and pay nothing upfront.
Visit elder.orgWe analyzed Elder.org page load time and found that the first response time was 429 ms and then it took 3.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
elder.org performance score
name
value
score
weighting
Value3.3 s
39/100
10%
Value5.0 s
27/100
25%
Value9.6 s
11/100
10%
Value14,140 ms
0/100
30%
Value0.379
27/100
15%
Value40.4 s
0/100
10%
429 ms
567 ms
40 ms
59 ms
58 ms
Our browser made a total of 102 requests to load all elements on the main page. We found that 43% of them (44 requests) were addressed to the original Elder.org, 25% (25 requests) were made to Assets.elder.org and 25% (25 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Elder.org.
Page size can be reduced by 294.7 kB (13%)
2.3 MB
2.1 MB
In fact, the total size of Elder.org 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 1.9 MB which makes up the majority of the site volume.
Potential reduce by 206.2 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 206.2 kB or 88% 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. Elder images are well optimized though.
Potential reduce by 88.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 88.5 kB or 36% of the original size.
Number of requests can be reduced by 47 (73%)
64
17
The browser has sent 64 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Elder. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 30 to 1 for JavaScripts and from 19 to 1 for CSS and as a result speed up the page load time.
elder.org
429 ms
www.elder.org
567 ms
uc.js
40 ms
job-listings.css
59 ms
style.min.css
58 ms
theme.min.css
96 ms
header-footer.min.css
63 ms
elementor-icons.min.css
59 ms
frontend.min.css
51 ms
swiper.min.css
95 ms
post-5.css
380 ms
frontend.min.css
84 ms
global.css
374 ms
post-178.css
474 ms
post-110890.css
383 ms
post-44.css
402 ms
post-62107.css
389 ms
public.css
415 ms
css
45 ms
jquery.min.js
739 ms
jquery-migrate.min.js
676 ms
analytics-talk-content-tracking.js
436 ms
getaddress-autocomplete-1.3.0.min.js
58 ms
tp.widget.bootstrap.min.js
28 ms
owl.carousel.min.css
434 ms
animate.min.css
439 ms
custom.css
442 ms
email-decode.min.js
434 ms
ajax.js
464 ms
public.js
464 ms
public.js
481 ms
imagesloaded.min.js
781 ms
owl.carousel.min.js
495 ms
custom.js
500 ms
webpack-pro.runtime.min.js
505 ms
webpack.runtime.min.js
527 ms
frontend-modules.min.js
528 ms
wp-polyfill-inert.min.js
980 ms
regenerator-runtime.min.js
980 ms
wp-polyfill.min.js
980 ms
hooks.min.js
979 ms
db6bd2b553.js
63 ms
4599.js
87 ms
i18n.min.js
1048 ms
frontend.min.js
752 ms
waypoints.min.js
927 ms
core.min.js
1291 ms
frontend.min.js
997 ms
elements-handlers.min.js
952 ms
infinitytrack.js
261 ms
gtm.js
238 ms
Elder-New-Logo.svg
257 ms
logo_white-1.svg
300 ms
Families.png
254 ms
049-Elder-slideshow.jpg
255 ms
083-Elder-5-2022-LOW-RES-2-1-768x701.png
449 ms
Visiting-Care-683x1024.png
337 ms
046-Elder-slideshow-1.jpg
478 ms
039-Elder-slideshow-1-522x450.jpg
464 ms
002-Elder-slideshow.jpg
619 ms
053-Elder-slideshow.jpg
343 ms
054-Elder-slideshow-1.jpg
570 ms
elder-caregiver-tips-1024x621.jpg
346 ms
RS13005-1024x681.jpg
403 ms
148-Elder-5-2022-LOW-RES-2-1024x682.jpg
406 ms
Copy-of-113-Elder-5-2022-LOW-RES-1024x682.jpg
447 ms
UK-Map-887x1024.png
459 ms
HCA_win_22-1-1.png
631 ms
HealthInvestor-Awards-2023-Winner-Domiciliary-care-Small-300x196.png
471 ms
HealthInvestor-Awards-2022-Winner-Domiciliary-care-Small-1-1.png
663 ms
elder-the-times-1.png
670 ms
elder-financial-times-1-1.png
699 ms
elderhq-awards-apr-2022-300x224-1.png
621 ms
1Ptyg83HX_SGhgqO0yLcmjzUAuWexXRW8aevHg.ttf
225 ms
1Ptyg83HX_SGhgqO0yLcmjzUAuWexRNW8aevHg.ttf
269 ms
1Ptyg83HX_SGhgqO0yLcmjzUAuWexTpW8aevHg.ttf
307 ms
1Ptyg83HX_SGhgqO0yLcmjzUAuWexU1W8aevHg.ttf
308 ms
1Ptyg83HX_SGhgqO0yLcmjzUAuWexaFR8aevHg.ttf
308 ms
1Ptyg83HX_SGhgqO0yLcmjzUAuWexZNR8aevHg.ttf
309 ms
1Ptyg83HX_SGhgqO0yLcmjzUAuWexc1R8aevHg.ttf
308 ms
1Ptyg83HX_SGhgqO0yLcmjzUAuWexRNR8aevHg.ttf
307 ms
UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuOKfAZ9hjQ.ttf
290 ms
UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuDyfAZ9hjQ.ttf
290 ms
UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuLyeAZ9hjQ.ttf
288 ms
UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuLyfAZ9hjQ.ttf
290 ms
UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuI6fAZ9hjQ.ttf
290 ms
UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuGKYAZ9hjQ.ttf
291 ms
UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuFuYAZ9hjQ.ttf
293 ms
UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuDyYAZ9hjQ.ttf
293 ms
UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuBWYAZ9hjQ.ttf
293 ms
1Ptwg83HX_SGhgqk2hAjQlW_mEuZ0FsSKeOfGZQ_.ttf
245 ms
1Ptwg83HX_SGhgqk2hAjQlW_mEuZ0FsSG-OfGZQ_.ttf
245 ms
1Ptwg83HX_SGhgqk2hAjQlW_mEuZ0FsSd-OfGZQ_.ttf
245 ms
1Ptwg83HX_SGhgqk2hAjQlW_mEuZ0FsSqeOfGZQ_.ttf
245 ms
1Ptwg83HX_SGhgqk2hAjQlW_mEuZ0FsS9-SfGZQ_.ttf
305 ms
1Ptwg83HX_SGhgqk2hAjQlW_mEuZ0FsSzuSfGZQ_.ttf
304 ms
1Ptwg83HX_SGhgqk2hAjQlW_mEuZ0FsSqeSfGZQ_.ttf
246 ms
1Ptwg83HX_SGhgqk2hAjQlW_mEuZ0FsSgOSfGZQ_.ttf
305 ms
040-Elder-slideshow.jpg
537 ms
Peggy-copy.png
424 ms
Patricia.png
432 ms
Jean-and-Fred.jpg
437 ms
elder.org 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
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
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
elder.org 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
Missing source maps for large first-party JavaScript
elder.org 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
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Elder.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 Elder.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.
elder.org
Open Graph data is detected on the main page of Elder. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: