Report Summary

  • 13

    Performance

    Renders faster than
    25% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

ellenor.org

ellenor | Providing Hospice Care and Support to Families

Page Load Speed

3.4 sec in total

First Response

256 ms

Resources Loaded

2 sec

Page Rendered

1.1 sec

ellenor.org screenshot

About Website

Welcome to ellenor.org homepage info - get ready to check Ellenor best content right away, or after learning these important things about ellenor.org

We are ellenor - the only charity in the county that provides hospice care for people of all ages. Learn about our care and the ways you can support us.

Visit ellenor.org

Key Findings

We analyzed Ellenor.org page load time and found that the first response time was 256 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

ellenor.org performance score

13

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

31/100

10%

LCP (Largest Contentful Paint)

Value27.4 s

0/100

25%

SI (Speed Index)

Value10.6 s

7/100

10%

TBT (Total Blocking Time)

Value1,540 ms

13/100

30%

CLS (Cumulative Layout Shift)

Value0.345

32/100

15%

TTI (Time to Interactive)

Value21.1 s

1/100

10%

Network Requests Diagram

ellenor.org

256 ms

ellenor.org

428 ms

api.js

75 ms

jquery.min.js

28 ms

eb_widgets.js

62 ms

Our browser made a total of 60 requests to load all elements on the main page. We found that 52% of them (31 requests) were addressed to the original Ellenor.org, 8% (5 requests) were made to Cdn.jsdelivr.net and 7% (4 requests) were made to Connect.facebook.net. The less responsive or slowest element that took the longest time to load (998 ms) belongs to the original domain Ellenor.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.4 MB (11%)

Content Size

21.6 MB

After Optimization

19.3 MB

In fact, the total size of Ellenor.org main page is 21.6 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. 65% of websites need less resources to load. Images take 20.9 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 94.1 kB

  • Original 112.0 kB
  • After minification 75.9 kB
  • After compression 17.9 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 36.1 kB, which is 32% 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 94.1 kB or 84% of the original size.

Image Optimization

-10%

Potential reduce by 2.2 MB

  • Original 20.9 MB
  • After minification 18.7 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. Ellenor images are well optimized though.

JavaScript Optimization

-14%

Potential reduce by 85.2 kB

  • Original 590.9 kB
  • After minification 590.8 kB
  • After compression 505.7 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 85.2 kB or 14% of the original size.

CSS Optimization

-31%

Potential reduce by 13.3 kB

  • Original 43.6 kB
  • After minification 43.6 kB
  • After compression 30.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. Ellenor.org needs all CSS files to be minified and compressed as it can save up to 13.3 kB or 31% of the original size.

Requests Breakdown

Number of requests can be reduced by 26 (46%)

Requests Now

56

After Optimization

30

The browser has sent 56 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ellenor. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

ellenor.org accessibility score

89

Accessibility Issues

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

Buttons do not have an accessible name

High

Links do not have a discernible name

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.

Best Practices

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

Page has valid source maps

SEO Factors

ellenor.org SEO score

83

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

High

Tap targets are not sized appropriately

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 Ellenor.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 Ellenor.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 Ellenor. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: