Tools & Wizards About Us
inlife.org.au screenshot

Report Summary

  • 30

    Performance

    Renders faster than
    50% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

inlife.org.au

Home | Inlife

Page Load Speed

4.7 sec in total

First Response

110 ms

Resources Loaded

3.9 sec

Page Rendered

735 ms

inlife.org.au screenshot

About Website

Click here to check amazing Inlife content. Otherwise, check out these important facts you probably never knew about inlife.org.au

A team specifically built for you. It's just one of the ways we're transforming the experience of disability support. Why choose InLife?

Visit inlife.org.au

Key Findings

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

Performance Metrics

inlife.org.au performance score

30

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

16/100

10%

LCP (Largest Contentful Paint)

Value8.7 s

1/100

25%

SI (Speed Index)

Value11.8 s

4/100

10%

TBT (Total Blocking Time)

Value720 ms

41/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value23.0 s

1/100

10%

Network Requests Diagram

inlife.org.au

110 ms

inlife.org.au

691 ms

www.inlife.org.au

1028 ms

ukv4bsl.css

115 ms

glide.min.css

27 ms

Our browser made a total of 55 requests to load all elements on the main page. We found that 69% of them (38 requests) were addressed to the original Inlife.org.au, 11% (6 requests) were made to Use.typekit.net and 7% (4 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 Inlife.org.au.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.6 MB (36%)

Content Size

4.4 MB

After Optimization

2.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Inlife.org.au main page is 4.4 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. 80% 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 4.3 MB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 69.3 kB

  • Original 97.4 kB
  • After minification 97.0 kB
  • After compression 28.0 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 69.3 kB or 71% of the original size.

Image Optimization

-36%

Potential reduce by 1.5 MB

  • Original 4.3 MB
  • After minification 2.8 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. Obviously, Inlife needs image optimization as it can save up to 1.5 MB or 36% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-8%

Potential reduce by 470 B

  • Original 6.1 kB
  • After minification 6.1 kB
  • After compression 5.6 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. This website has mostly compressed JavaScripts.

CSS Optimization

-0%

Potential reduce by 0 B

  • Original 5 B

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.

Requests Breakdown

Number of requests can be reduced by 14 (33%)

Requests Now

42

After Optimization

28

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

inlife.org.au

inlife.org.au

110 ms

inlife.org.au

inlife.org.au

691 ms

www.inlife.org.au

www.inlife.org.au

1028 ms

ukv4bsl.css

ukv4bsl.css

115 ms

glide.min.css

glide.min.css

27 ms

glightbox.min.css

glightbox.min.css

698 ms

styles.css

styles.css

60 ms

sharethis.js

sharethis.js

33 ms

js

js

125 ms

email-decode.min.js

email-decode.min.js

25 ms

webfont.js

webfont.js

30 ms

glide.min.js

glide.min.js

46 ms

glightbox.min.js

glightbox.min.js

45 ms

main.js

main.js

92 ms

sidebarv2.js

sidebarv2.js

44 ms

visor.js

visor.js

71 ms

plugin.js

plugin.js

83 ms

embed.js

embed.js

85 ms

p.css

p.css

20 ms

home-icon.svg

home-icon.svg

56 ms

career-icon.svg

career-icon.svg

53 ms

play-button.svg

play-button.svg

50 ms

neil-circle.png

neil-circle.png

55 ms

nyaksi-circle.png

nyaksi-circle.png

644 ms

anj-circle.png

anj-circle.png

854 ms

20240917_115712_5f1db9c060f17d749cd29d80f7c74393.jpg

20240917_115712_5f1db9c060f17d749cd29d80f7c74393.jpg

58 ms

image000000-2_c47fd67b7b116a5cc979fdbd771647bd.JPEG

image000000-2_c47fd67b7b116a5cc979fdbd771647bd.JPEG

57 ms

IMG_0142_fffc2537181ffe4bc754b2ba7af34066.jpeg

IMG_0142_fffc2537181ffe4bc754b2ba7af34066.jpeg

60 ms

cloud-icon.svg

cloud-icon.svg

58 ms

signup-icon.svg

signup-icon.svg

60 ms

ic-Call-us.svg

ic-Call-us.svg

97 ms

ic-Email-us.svg

ic-Email-us.svg

98 ms

aboriginal.svg

aboriginal.svg

95 ms

torres.svg

torres.svg

99 ms

commu-1.svg

commu-1.svg

298 ms

commu-2.svg

commu-2.svg

100 ms

image-89.png

image-89.png

99 ms

ndis-logo.png

ndis-logo.png

99 ms

rounded-bg-yellow.svg

rounded-bg-yellow.svg

264 ms

MADDEY-NIXY_22nd-June-22_0720-1_72e6678dc4da11dd1d67b9a8f70e5e7a.jpg

MADDEY-NIXY_22nd-June-22_0720-1_72e6678dc4da11dd1d67b9a8f70e5e7a.jpg

1306 ms

swirl-mobile-bwbg.svg

swirl-mobile-bwbg.svg

65 ms

green-bg.svg

green-bg.svg

74 ms

InLife-client-Anj-Barker-working-out-at-the-gym_4315beef5e81eadb33286a860912c7bd.png

InLife-client-Anj-Barker-working-out-at-the-gym_4315beef5e81eadb33286a860912c7bd.png

132 ms

NEIL-McKENZIE00546_353fe568217a4ecd8f2727f818d6534e.jpg

NEIL-McKENZIE00546_353fe568217a4ecd8f2727f818d6534e.jpg

194 ms

ELIZAASH_00256_37f9af6940d4a6fc7627ec24c4a0fcd3.jpg

ELIZAASH_00256_37f9af6940d4a6fc7627ec24c4a0fcd3.jpg

194 ms

d

d

22 ms

d

d

59 ms

d

d

58 ms

d

d

58 ms

d

d

58 ms

css

css

66 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

27 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

34 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWVAexQ.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWVAexQ.ttf

45 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkxhjWVAexQ.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkxhjWVAexQ.ttf

44 ms

Accessibility Review

inlife.org.au accessibility score

98

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

Links do not have a discernible name

Best Practices

inlife.org.au best practices score

92

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

Page has valid source maps

SEO Factors

inlife.org.au SEO score

100

Search Engine Optimization Advices

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

inlife.org.au

Open Graph data is detected on the main page of Inlife. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: