Report Summary

  • 60

    Performance

    Renders faster than
    75% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 89

    SEO

    Google-friendlier than
    66% of websites

wecan.org.au

WeCan Cancer Supportive Care: for people affected by cancer

Page Load Speed

1.4 sec in total

First Response

682 ms

Resources Loaded

683 ms

Page Rendered

0 ms

wecan.org.au screenshot

About Website

Welcome to wecan.org.au homepage info - get ready to check We Can best content right away, or after learning these important things about wecan.org.au

WeCan is an Australian supportive care site providing people affected by cancer with information, resources and services after a diagnosis.

Visit wecan.org.au

Key Findings

We analyzed Wecan.org.au page load time and found that the first response time was 682 ms and then it took 683 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

wecan.org.au performance score

60

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.8 s

11/100

10%

LCP (Largest Contentful Paint)

Value6.7 s

8/100

25%

SI (Speed Index)

Value6.5 s

39/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.035

100/100

15%

TTI (Time to Interactive)

Value4.8 s

78/100

10%

Network Requests Diagram

wecan.org.au

682 ms

Our browser made a total of 1 request to load all elements on the main page. We found that all of those requests were addressed to Wecan.org.au and no external sources were called. The less responsive or slowest element that took the longest time to load (682 ms) belongs to the original domain Wecan.org.au.

Page Optimization Overview & Recommendations

Page size can be reduced by 387.9 kB (53%)

Content Size

726.2 kB

After Optimization

338.3 kB

In fact, the total size of Wecan.org.au main page is 726.2 kB. This result falls within the top 5000 of lightweight and thus fast loading web pages. Only a small number of websites need less resources to load. CSS take 508.3 kB which makes up the majority of the site volume.

HTML Optimization

-55%

Potential reduce by 798 B

  • Original 1.4 kB
  • After minification 1.4 kB
  • After compression 651 B

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 798 B or 55% of the original size.

Image Optimization

-4%

Potential reduce by 2.8 kB

  • Original 75.4 kB
  • After minification 72.6 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. We Can images are well optimized though.

JavaScript Optimization

-37%

Potential reduce by 51.9 kB

  • Original 141.1 kB
  • After minification 139.4 kB
  • After compression 89.1 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 51.9 kB or 37% of the original size.

CSS Optimization

-65%

Potential reduce by 332.4 kB

  • Original 508.3 kB
  • After minification 508.2 kB
  • After compression 175.9 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. Wecan.org.au needs all CSS files to be minified and compressed as it can save up to 332.4 kB or 65% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

0

After Optimization

0

Besides the initial HTML request, no CSS, Javascripts, AJAX or image files were requested in the course of web page rendering.

Accessibility Review

wecan.org.au accessibility score

98

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.

Best Practices

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

wecan.org.au SEO score

89

Search Engine Optimization Advices

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wecan.org.au 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 Wecan.org.au 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 description is not detected on the main page of We Can. 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: