Tools & Wizards About Us
lifewise.org.nz screenshot

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

  • 90

    SEO

    Google-friendlier than
    68% of websites

lifewise.org.nz

Lifewise NZ - Improve Freedom, Choice, & Equity in Aotearoa | Lifewise

Page Load Speed

7.6 sec in total

First Response

1.1 sec

Resources Loaded

6.3 sec

Page Rendered

229 ms

lifewise.org.nz screenshot

About Website

Click here to check amazing Lifewise content for New Zealand. Otherwise, check out these important facts you probably never knew about lifewise.org.nz

Lifewise is an Auckland-based community social development organisation. We help people living in hardship have better opportunities & futures

Visit lifewise.org.nz

Key Findings

We analyzed Lifewise.org.nz page load time and found that the first response time was 1.1 sec and then it took 6.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

lifewise.org.nz performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value12.8 s

0/100

10%

LCP (Largest Contentful Paint)

Value12.8 s

0/100

25%

SI (Speed Index)

Value19.9 s

0/100

10%

TBT (Total Blocking Time)

Value680 ms

44/100

30%

CLS (Cumulative Layout Shift)

Value0.507

16/100

15%

TTI (Time to Interactive)

Value21.7 s

1/100

10%

Network Requests Diagram

lifewise.org.nz

1135 ms

Page1dee73f766bb4fbc937e4703e9a61e36

492 ms

main.css

673 ms

Page1dee73f766bb4fbc937e4703e9a61e36

1696 ms

Lifewise.js

659 ms

Our browser made a total of 42 requests to load all elements on the main page. We found that 83% of them (35 requests) were addressed to the original Lifewise.org.nz, 10% (4 requests) were made to Fast.fonts.com and 5% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (3.1 sec) belongs to the original domain Lifewise.org.nz.

Page Optimization Overview & Recommendations

Page size can be reduced by 114.6 kB (37%)

Content Size

312.0 kB

After Optimization

197.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Lifewise.org.nz main page is 312.0 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 25% of websites need less resources to load. Images take 201.7 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 13.4 kB

  • Original 18.1 kB
  • After minification 14.0 kB
  • After compression 4.7 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 4.1 kB, which is 22% 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 13.4 kB or 74% of the original size.

Image Optimization

-21%

Potential reduce by 43.2 kB

  • Original 201.7 kB
  • After minification 158.5 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. Obviously, Lifewise needs image optimization as it can save up to 43.2 kB or 21% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-54%

Potential reduce by 33.6 kB

  • Original 62.7 kB
  • After minification 54.7 kB
  • After compression 29.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 33.6 kB or 54% of the original size.

CSS Optimization

-83%

Potential reduce by 24.5 kB

  • Original 29.5 kB
  • After minification 23.1 kB
  • After compression 5.0 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. Lifewise.org.nz needs all CSS files to be minified and compressed as it can save up to 24.5 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 16 (43%)

Requests Now

37

After Optimization

21

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

lifewise.org.nz

lifewise.org.nz

1135 ms

Page1dee73f766bb4fbc937e4703e9a61e36

Page1dee73f766bb4fbc937e4703e9a61e36

492 ms

main.css

main.css

673 ms

Page1dee73f766bb4fbc937e4703e9a61e36

Page1dee73f766bb4fbc937e4703e9a61e36

1696 ms

Lifewise.js

Lifewise.js

659 ms

f8886953-23da-4f5d-bfa6-e568e07d8a5e.js

f8886953-23da-4f5d-bfa6-e568e07d8a5e.js

59 ms

ga.js

ga.js

49 ms

canvas.jpg

canvas.jpg

591 ms

header.png

header.png

209 ms

logo-background.png

logo-background.png

423 ms

logo.jpg

logo.jpg

221 ms

tagline.png

tagline.png

222 ms

light-overlay.png

light-overlay.png

206 ms

navigation-current-background.png

navigation-current-background.png

407 ms

navigation-link-background.png

navigation-link-background.png

403 ms

header-shadow.png

header-shadow.png

413 ms

people-on-beach-266-False-default.jpg

people-on-beach-266-False-default.jpg

605 ms

HotButton2ee3f4559c734dc1b799994cb209473d

HotButton2ee3f4559c734dc1b799994cb209473d

706 ms

HotButton7da2902d9e9445a08a2c65cdb516ece3

HotButton7da2902d9e9445a08a2c65cdb516ece3

2592 ms

HotButton34e8e6ca24214dd388866e0cfccf482f

HotButton34e8e6ca24214dd388866e0cfccf482f

1214 ms

HotButton06fb9f11e2b94e77a24aee06c2d71357

HotButton06fb9f11e2b94e77a24aee06c2d71357

1963 ms

background.png

background.png

734 ms

page-shadow.png

page-shadow.png

807 ms

page-shadow-middle.png

page-shadow-middle.png

897 ms

footer-sitemap-background.png

footer-sitemap-background.png

928 ms

more-bullet.png

more-bullet.png

1014 ms

constrained-shadow-left.png

constrained-shadow-left.png

1091 ms

constrained-shadow-right.png

constrained-shadow-right.png

1122 ms

HotButton2ee3f4559c734dc1b799994cb209473d

HotButton2ee3f4559c734dc1b799994cb209473d

3130 ms

HotButton7da2902d9e9445a08a2c65cdb516ece3

HotButton7da2902d9e9445a08a2c65cdb516ece3

1333 ms

HotButton34e8e6ca24214dd388866e0cfccf482f

HotButton34e8e6ca24214dd388866e0cfccf482f

1860 ms

HotButton06fb9f11e2b94e77a24aee06c2d71357

HotButton06fb9f11e2b94e77a24aee06c2d71357

1536 ms

__utm.gif

__utm.gif

14 ms

collect

collect

75 ms

2cac77ec-9bc0-4ee7-87e4-27650190744f.woff

2cac77ec-9bc0-4ee7-87e4-27650190744f.woff

77 ms

7147ec3a-8ff8-4ec9-8c5c-bd1571dc6ae6.woff

7147ec3a-8ff8-4ec9-8c5c-bd1571dc6ae6.woff

54 ms

5a05cf7f-f332-456f-ae67-d8c26e0d35b3.woff

5a05cf7f-f332-456f-ae67-d8c26e0d35b3.woff

86 ms

Overlay

Overlay

200 ms

Loading

Loading

207 ms

Close

Close

212 ms

Loading

Loading

200 ms

Close

Close

201 ms

Accessibility Review

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

Heading elements are not in a sequentially-descending order

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

lifewise.org.nz best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

lifewise.org.nz SEO score

90

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

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

lifewise.org.nz

Open Graph description is not detected on the main page of Lifewise. 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: