Website review, no card needed
visionwest.org.nz website review
Visit site (opens in a new tab)Reviewed 2 November 202646 issues · 92 checks
This review found 46 issues worth fixing on visionwest.org.nz, 19 of them high impact, across 92 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
58FClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 3.9 s |
| May 23, 2026 | 4.0 s |
| May 30, 2026 | 4.0 s |
| Jun 6, 2026 | 4.1 s |
| Jun 13, 2026 | 4.2 s |
| Jun 20, 2026 | 4.2 s |
| Jun 27, 2026 | 4.3 s |
| Jul 4, 2026 | 4.5 s |
| Jul 11, 2026 | 4.2 s |
| Jul 18, 2026 | 4.0 s |
| Jul 25, 2026 | 3.9 s |
| Aug 1, 2026 | 3.7 s |
| Aug 8, 2026 | 3.6 s |
| Aug 15, 2026 | 3.6 s |
| Aug 22, 2026 | 3.6 s |
| Aug 29, 2026 | 3.6 s |
| Sep 5, 2026 | 3.6 s |
| Sep 12, 2026 | 3.7 s |
| Sep 19, 2026 | 3.7 s |
| Sep 26, 2026 | 3.8 s |
| Oct 3, 2026 | 3.9 s |
| Oct 10, 2026 | 4.1 s |
| Oct 17, 2026 | 4.0 s |
| Oct 24, 2026 | 3.8 s |
| Oct 31, 2026 | 3.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 225 ms |
| May 23, 2026 | 237 ms |
| May 30, 2026 | 242 ms |
| Jun 6, 2026 | 248 ms |
| Jun 13, 2026 | 252 ms |
| Jun 20, 2026 | 244 ms |
| Jun 27, 2026 | 254 ms |
| Jul 4, 2026 | 261 ms |
| Jul 11, 2026 | 251 ms |
| Jul 18, 2026 | 240 ms |
| Jul 25, 2026 | 232 ms |
| Aug 1, 2026 | 220 ms |
| Aug 8, 2026 | 219 ms |
| Aug 15, 2026 | 219 ms |
| Aug 22, 2026 | 223 ms |
| Aug 29, 2026 | 227 ms |
| Sep 5, 2026 | 227 ms |
| Sep 12, 2026 | 221 ms |
| Sep 19, 2026 | 223 ms |
| Sep 26, 2026 | 228 ms |
| Oct 3, 2026 | 233 ms |
| Oct 10, 2026 | 265 ms |
| Oct 17, 2026 | 251 ms |
| Oct 24, 2026 | 256 ms |
| Oct 31, 2026 | 249 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
How it loaded on a phone
0.8 s
1.6 s
2.4 s
3.2 s
4.0 s
4.8 s
5.6 s
6.4 s
Speed
Reduce unused JavaScript
6.3 s · 1.6 MBAbout 1.6 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 6.3 s faster on a phone.
Render-blocking requests
1.9 s24 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.9 s.
Improve image delivery
1.3 s · 362 KiB5 images could be 362 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.3 s faster on a phone.
Mobile performance score: 22
22/100Your mobile performance score is 22. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 4.0 s
A phone's processor spends 4.0 s on main-thread work while loading, 2.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (YouTube, Hotjar and Google Tag Manager and others), adding 4.0 MB and 1.3 s of main-thread time.
YouTube adds 635 ms
635 msYouTube costs a phone 635 ms of main-thread work and 2.0 MB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Use efficient cache lifetimes
440 KiB16 files are served with short cache lifetimes, so returning visitors download them again (440 KiB).
Hotjar adds 271 ms
271 msHotjar costs a phone 271 ms of main-thread work and 272 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Facebook adds 172 ms
172 msFacebook costs a phone 172 ms of main-thread work and 1.2 MB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Google Tag Manager adds 239 ms
239 msGoogle Tag Manager costs a phone 239 ms of main-thread work and 445 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Reduce unused CSS
150 ms · 126 KiBAbout 126 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
13 long tasks on the main thread
13 long tasks block the main thread while loading, the longest for 192 ms. During a long task the page ignores taps.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Legacy JavaScript
36 KiBPolyfills for old browsers add 36 KiB JavaScript that modern phones do not need.
Chained critical requests
Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
Minify JavaScript
2 KiB2 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 21 ms
21 msYour server sent the HTML in 21 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.
Real-user CLS: 1.09
1.09For real visitors the layout shifts by 1.09 (75th percentile). Good is under 0.1.
Largest Contentful Paint: 22.0 s
22.0 sYour largest element takes 22.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Official Opening of 24 units in our Village of Hope READ MO…”.
Time to Interactive: 32.7 s
32.7 sThe page becomes fully interactive after 32.7 s. Good is under 3.8 s.
Cumulative Layout Shift: 0.977
0.977The layout shifts by 0.977 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Speed Index: 12.8 s
12.8 sVisually, the page fills in at 12.8 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 618 ms
618 msScripts block taps and scrolling for 618 ms in total while the page loads. Good is under 200 ms.
Real-user LCP: 3.0 s
3.0 sReal visitors wait 3.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 227 ms
227 msReal visitors wait 227 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
First Contentful Paint: 2.6 s
2.6 sThe first text or image appears after 2.6 s on a phone. Good is under 1.8 s.
18 images without width and height
18 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+9%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 225 ms to 249 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-6%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 3.9 s to 3.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
Real-user FCP: 1.6 s
1.6 sReal visitors see the first content after 1.6 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 702 ms
702 msReal visitors wait 702 ms for your server to start answering (75th percentile). Good is under 800 ms.
Images and page weight
Page weight: 7.6 MB in 156 requests
7.6 MBYour homepage downloads 7.6 MB in 156 requests on a phone: images 3.6 MB (41), scripts 3.2 MB (55) and fonts 350 KiB (8). Under 2 MB keeps phones on slow connections fast.
1 image below the first screen load straight away
1 image further down the page (26 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 2.2 g of CO₂ per visit
2.16 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.16 g of CO₂e: 258.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
16 tap targets too small
16 tap targets are too small or too close together to hit reliably with a finger.
9 text elements with low contrast
9 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Links look like plain text
1 link inside paragraphs relies on colour alone to stand out.
All page content should be contained by landmarks (9 elements)
All page content should be contained by landmarks: 9 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
3 links without text
3 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h2 → h4, h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 26 images in the HTML carry an alt attribute.
38 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 47 WCAG 2.2 A/AA and best-practice rules on the phone render: 38 passed and 9 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
3 H1 headlines
There are 3 <h1> headlines (“Help struggling families create homes”, “We all go through times when we need the support …” and “Latest News”). One clear main headline is easier for people and search engines.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
151 internal links, 57 external
The homepage links to 151 pages on visionwest.org.nz and 57 external pages.
6 checks passed
Meta description: 135 characters
Your meta description is 135 characters: “Visionwest journey with young people, families, whānau with disabilities and the elderly with an unwavering hope for a …”.
Title: 53 characters
Your title is a healthy 53 characters: “Visionwest Waka Whakakitenga | Building Hope Together”.
Canonical URL set
The canonical URL is https://visionwest.org.nz/.
Structured data in place
Structured data found: Article, Organization, Person, WebPage and WebSite.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://visionwest.org.nz/sitemap_index.xml.
AI search readiness
Organization data is thin (2 of 6 facts)
Your Organization JSON-LD is missing logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
No llms.txt
There is no https://visionwest.org.nz/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.
2 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Text is in the HTML
Your server sends the page's text in the HTML (2,034 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages share a title
https://visionwest.org.nz/housing/our-people and https://visionwest.org.nz/housing/regions all use the title “Visionwest Community Housing | Transitional & Long-Term Social Housin…”. Search engines can't tell which page to show for a search, so each competes with the others.
2 pages share a meta description
https://visionwest.org.nz/housing/our-people and https://visionwest.org.nz/housing/regions use the same meta description. A description written for each page earns more clicks.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://visionwest.org.nz/ohinga-tu/youth-housing, whose canonical is https://visionwest.org.nz/housing/youth-housing. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
6 pages slow to respond
https://visionwest.org.nz/housing/housing-services/transitional, https://visionwest.org.nz/housing/housing-services/long-term, https://visionwest.org.nz/housing/housing-services/sustaining-tenancies, https://visionwest.org.nz/housing/landlords, https://visionwest.org.nz/housing/work-with-us and https://visionwest.org.nz/housing/about-us/auckland took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 85 found) and read each the way a search engine does.
5 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Every page has a meta description
All 15 pages that loaded have a meta description.
Every page has an H1
Each page we checked has a main headline.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
3 broken images
3 images failed to load on a phone, for example https://scontent-syd2-1.xx.fbcdn.net/v/t15.5256-10/871763378_1163235616649645_7174718696436438161_n.jpg?_nc_cat=107&ccb=1-7&_nc_sid=d2b52d&_nc_ohc=JNS22Corke8Q7kNvwEfKg5Q&_nc_oc=AdpQVVo6V9QkmHx2wE2vpL.
5 third-party cookies
5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
4 small tap targets
4 of 11 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_TUNNEL_CONNECTION_FAILED”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.
A 8-field form
Your longest form asks for 8 fields (5 required). Every extra field lowers completion.
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
No risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
About 581 words of copy
The homepage carries about 581 words of visible text.
3 checks passed
6 calls to action
The homepage has 6 calls to action, for example “Contact Us”, “Subscribe” and “Get in Touch”.
Social proof on the page
Social proof on the homepage: 1 testimonial or review block and 1 trust badge.
Analytics in place
Analytics detected: Google Tag Manager, Meta Pixel and Hotjar.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and LinkedIn Insight and 1 more (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.
11 cookies set on arrival
11Opening the homepage sets 11 cookies, 1 of them by other companies (measured from a US location before any click).
No consent tool detected
No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.
22 other companies contacted
Loading the homepage contacts 22 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at visionwest.org.nz, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- WordPress
- Framework
- jQuery
- Analytics
- Google Tag Manager | Hotjar
- Hosting
- Cloudflare
Company
- Employees
- 1,694
- Headquarters
- Auckland
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 46 issues on visionwest.org.nz, including 22 speed issues, 3 SEO issues and 3 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.