Tools & Wizards About Us

Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

elder.org

Live-in Care, Elderly Home Care and Dementia Care | Elder

Page Load Speed

4 sec in total

First Response

429 ms

Resources Loaded

2.4 sec

Page Rendered

1.2 sec

About Website

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.org

Key Findings

We 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.

Performance Metrics

elder.org performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

39/100

10%

LCP (Largest Contentful Paint)

Value5.0 s

27/100

25%

SI (Speed Index)

Value9.6 s

11/100

10%

TBT (Total Blocking Time)

Value14,140 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.379

27/100

15%

TTI (Time to Interactive)

Value40.4 s

0/100

10%

Network Requests Diagram

elder.org

429 ms

www.elder.org

567 ms

uc.js

40 ms

job-listings.css

59 ms

style.min.css

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 Optimization Overview & Recommendations

Page size can be reduced by 294.7 kB (13%)

Content Size

2.3 MB

After Optimization

2.1 MB

  • HTML
  • Images
  • JavaScript

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.

HTML Optimization

-88%

Potential reduce by 206.2 kB

  • Original 234.6 kB
  • After minification 234.6 kB
  • After compression 28.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. 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.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 1.9 MB
  • After minification 1.9 MB

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.

JavaScript Optimization

-36%

Potential reduce by 88.5 kB

  • Original 248.7 kB
  • After minification 248.7 kB
  • After compression 160.2 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.

Requests Breakdown

Number of requests can be reduced by 47 (73%)

Requests Now

64

After Optimization

17

  • Images
  • JavaScript
  • CSS

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.

Network Requests Diagram

Accessibility Review

elder.org accessibility score

88

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

High

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

High

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

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

elder.org best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

elder.org SEO score

86

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    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.

Social Sharing Optimization

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: