Tools & Wizards About Us
thrive.org.nz screenshot

Report Summary

  • 22

    Performance

    Renders faster than
    40% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

thrive.org.nz

Home | Auckland Mātua Taiohi, Hapū Māmā Support | E Tipu E Rea Whānau Services

Page Load Speed

5.8 sec in total

First Response

1.2 sec

Resources Loaded

4.2 sec

Page Rendered

445 ms

thrive.org.nz screenshot

About Website

Visit thrive.org.nz now to see the best up-to-date Thrive content and also check out these interesting facts you probably never knew about thrive.org.nz

E Tipu E Rea Whānau Services offers dedicated tautoko to matua taiohi and their whānau, with a kaupapa Māori framework to empower our rangatahi. We hold a special relationship with Ngāti Pāoa, who als...

Visit thrive.org.nz

Key Findings

We analyzed Thrive.org.nz page load time and found that the first response time was 1.2 sec 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

thrive.org.nz performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

22/100

10%

LCP (Largest Contentful Paint)

Value11.7 s

0/100

25%

SI (Speed Index)

Value7.9 s

22/100

10%

TBT (Total Blocking Time)

Value2,210 ms

6/100

30%

CLS (Cumulative Layout Shift)

Value0.067

97/100

15%

TTI (Time to Interactive)

Value14.7 s

8/100

10%

Network Requests Diagram

etipuereaws.org.nz

1157 ms

2ok0x.css

213 ms

2ok0x.css

421 ms

css2

49 ms

2ok0x.css

853 ms

Our browser made a total of 58 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Thrive.org.nz, 21% (12 requests) were made to Static.xx.fbcdn.net and 3% (2 requests) were made to Connect.facebook.net. The less responsive or slowest element that took the longest time to load (1.5 sec) relates to the external source Etipuereaws.org.nz.

Page Optimization Overview & Recommendations

Page size can be reduced by 59.6 kB (6%)

Content Size

998.8 kB

After Optimization

939.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Thrive.org.nz main page is 998.8 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. 70% of websites need less resources to load. Images take 523.0 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 47.7 kB

  • Original 60.4 kB
  • After minification 58.5 kB
  • After compression 12.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. 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 47.7 kB or 79% of the original size.

Image Optimization

-1%

Potential reduce by 6.4 kB

  • Original 523.0 kB
  • After minification 516.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. Thrive images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 4.4 kB

  • Original 322.3 kB
  • After minification 321.3 kB
  • After compression 317.9 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

-1%

Potential reduce by 1.1 kB

  • Original 93.1 kB
  • After minification 93.1 kB
  • After compression 92.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. Thrive.org.nz has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 31 (60%)

Requests Now

52

After Optimization

21

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

etipuereaws.org.nz

etipuereaws.org.nz

1157 ms

2ok0x.css

2ok0x.css

213 ms

2ok0x.css

2ok0x.css

421 ms

css2

css2

49 ms

2ok0x.css

2ok0x.css

853 ms

2ok0x.js

2ok0x.js

1043 ms

js

js

78 ms

sdk.js

sdk.js

33 ms

hooks.min.js

hooks.min.js

833 ms

i18n.min.js

i18n.min.js

834 ms

index.js

index.js

837 ms

index.js

index.js

841 ms

api.js

api.js

68 ms

wp-polyfill.min.js

wp-polyfill.min.js

1087 ms

index.js

index.js

1086 ms

js_composer_front.min.js

js_composer_front.min.js

1087 ms

functions.js

functions.js

1087 ms

theme.js

theme.js

1087 ms

visual_composer.js

visual_composer.js

1247 ms

touch-menu-display.js

touch-menu-display.js

1249 ms

pikaday.jquery.js

pikaday.jquery.js

1458 ms

sponsor.jpg

sponsor.jpg

211 ms

E-Tipu-E-Rea-Logo.png

E-Tipu-E-Rea-Logo.png

433 ms

footer-logo-1.png

footer-logo-1.png

214 ms

footer-logo-4.png

footer-logo-4.png

403 ms

website-sponsor-tab-300x123.jpg

website-sponsor-tab-300x123.jpg

402 ms

Screenshot_2020-12-18-11-19-14-47-002-300x79.jpg

Screenshot_2020-12-18-11-19-14-47-002-300x79.jpg

433 ms

widgets--e1608246825838.jpg

widgets--e1608246825838.jpg

433 ms

NHC-300x96.png

NHC-300x96.png

659 ms

jr-makenzie-300x89.jpg

jr-makenzie-300x89.jpg

658 ms

Todd-Foundation-web-1-266x300.jpg

Todd-Foundation-web-1-266x300.jpg

660 ms

footer-logo.png

footer-logo.png

660 ms

20210722_101832.jpg

20210722_101832.jpg

1027 ms

VID7738.jpg

VID7738.jpg

822 ms

VID7691.jpg

VID7691.jpg

993 ms

VID7406-2.jpg

VID7406-2.jpg

1200 ms

sdk.js

sdk.js

46 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu170w-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu170w-.ttf

35 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Ew-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Ew-.ttf

40 ms

fa-solid-900.woff

fa-solid-900.woff

951 ms

fa-regular-400.woff

fa-regular-400.woff

756 ms

fa-brands-400.woff

fa-brands-400.woff

1175 ms

recaptcha__en.js

recaptcha__en.js

50 ms

page.php

page.php

135 ms

zop2ih_Wxrs.css

zop2ih_Wxrs.css

18 ms

7TXvrmQm8c5.js

7TXvrmQm8c5.js

25 ms

Vvet8_5H-wT.js

Vvet8_5H-wT.js

47 ms

zYyn94Uppv5.js

zYyn94Uppv5.js

50 ms

tC2E_WEPqHv.js

tC2E_WEPqHv.js

49 ms

c64elx0V1Fa.js

c64elx0V1Fa.js

48 ms

p55HfXW__mM.js

p55HfXW__mM.js

48 ms

KroQaZupEyF.js

KroQaZupEyF.js

48 ms

OVpmQGrCmX0.js

OVpmQGrCmX0.js

48 ms

417755386_774441494720571_786627380590916843_n.jpg

417755386_774441494720571_786627380590916843_n.jpg

100 ms

326799726_706949004176261_3357058445473334393_n.jpg

326799726_706949004176261_3357058445473334393_n.jpg

95 ms

wjv1Jo1HAky.js

wjv1Jo1HAky.js

9 ms

sHvFXXh-54U.js

sHvFXXh-54U.js

8 ms

UXtr_j2Fwe-.png

UXtr_j2Fwe-.png

7 ms

Accessibility Review

thrive.org.nz accessibility score

89

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.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

thrive.org.nz best practices score

75

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

High

Browser errors were logged to the console

SEO Factors

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Thrive.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 Thrive.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

thrive.org.nz

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