Website review, no card needed
powerfarming.co.nz website review
Visit site (opens in a new tab)Reviewed 3 November 202625 issues · 57 checks
This review found 25 issues worth fixing on powerfarming.co.nz, 5 of them high impact, across 57 checks. The most urgent: fails Core Web Vitals for real visitors. Google's speed test didn't respond, so speed is not measured here; your full playbook measures it. 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
Not scored yet: Google's speed test didn't run in this review. Re-run the review to get a score.
Show as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 3.1 s |
| May 23, 2026 | 3.0 s |
| May 30, 2026 | 2.8 s |
| Jun 6, 2026 | 2.6 s |
| Jun 13, 2026 | 2.6 s |
| Jun 20, 2026 | 2.5 s |
| Jun 27, 2026 | 2.4 s |
| Jul 4, 2026 | 2.4 s |
| Jul 11, 2026 | 2.4 s |
| Jul 18, 2026 | 2.5 s |
| Jul 25, 2026 | 2.5 s |
| Aug 1, 2026 | 2.6 s |
| Aug 8, 2026 | 2.5 s |
| Aug 15, 2026 | 2.5 s |
| Aug 22, 2026 | 2.4 s |
| Aug 29, 2026 | 2.4 s |
| Sep 5, 2026 | 2.4 s |
| Sep 12, 2026 | 2.3 s |
| Sep 19, 2026 | 2.3 s |
| Sep 26, 2026 | 2.3 s |
| Oct 3, 2026 | 2.3 s |
| Oct 10, 2026 | 2.3 s |
| Oct 17, 2026 | 2.4 s |
| Oct 24, 2026 | 2.4 s |
| Oct 31, 2026 | 2.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 112 ms |
| May 23, 2026 | 120 ms |
| May 30, 2026 | 120 ms |
| Jun 6, 2026 | 128 ms |
| Jun 13, 2026 | 139 ms |
| Jun 20, 2026 | 137 ms |
| Jun 27, 2026 | 145 ms |
| Jul 4, 2026 | 142 ms |
| Jul 11, 2026 | 138 ms |
| Jul 18, 2026 | 151 ms |
| Jul 25, 2026 | 153 ms |
| Aug 1, 2026 | 163 ms |
| Aug 8, 2026 | 182 ms |
| Aug 15, 2026 | 196 ms |
| Aug 22, 2026 | 217 ms |
| Aug 29, 2026 | 228 ms |
| Sep 5, 2026 | 222 ms |
| Sep 12, 2026 | 222 ms |
| Sep 19, 2026 | 221 ms |
| Sep 26, 2026 | 222 ms |
| Oct 3, 2026 | 226 ms |
| Oct 10, 2026 | 229 ms |
| Oct 17, 2026 | 253 ms |
| Oct 24, 2026 | 263 ms |
| Oct 31, 2026 | 262 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
Speed
Not measured in this review.
Core Web Vitals
Fails Core Web Vitals for real visitors
Real Chrome users on phones do not pass Google's Core Web Vitals on your site (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.
Real-user INP: 268 ms
268 msReal visitors wait 268 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.25
0.25For real visitors the layout shifts by 0.25 (75th percentile). Good is under 0.1.
Tap response (INP) got 126% slower for real visitors
+126%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 112 ms to 262 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 1.9 s
1.9 sReal visitors see the first content after 1.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.5 s
1.5 sReal visitors wait 1.5 s for your server to start answering (75th percentile). Good is under 800 ms.
2 checks passed
Real-user LCP: 2.3 s
2.3 sReal visitors wait 2.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Largest content (LCP) got 24% faster for real visitors
-24%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 3.1 s to 2.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
Page weight: 4.7 MB
4.7 MBYour homepage downloads 4.7 MB on a phone, 2.2 MB of it images (47%). Under 2 MB keeps phones on slow connections fast.
12 images in older formats
12 images (1.7 MB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.
An image on the first screen is lazy-loaded
Hero-slider_Video-Fallback_FEB26_1920-x-800.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
2 images far larger than shown
376 KiB2 images are downloaded at several times the size a phone draws them, for example Hero-slider_Video-Fallback_FEB26_1920-x-800.jpg at 1,920 px wide, shown at 390 px. Resized copies would save about 376 KiB.
About 1.3 g of CO₂ per visit
1.32 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.32 g of CO₂e: 158.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
2 images without alt text
2 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (10 elements)
All page content should be contained by landmarks: 10 elements on the page fail this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
20 links without text
20 visible links have no text or label, so screen readers cannot say where they go.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
1 checks passed
50 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 5 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
Title is short (20 characters)
Your title is only 20 characters: “Home - Power Farming”. Between 30 and 65 characters leaves room to say what you do and for whom.
Open Graph partly set
Open Graph is missing og:description, so shared links fall back to guesses.
233 internal links, 17 external
The homepage links to 233 pages on powerfarming.co.nz and 17 external pages.
5 checks passed
One H1 headline
Your main headline reads: “Power Farming supplying agricultural tractor, machinery, parts, and service”.
Canonical URL set
The canonical URL is https://www.powerfarming.co.nz/.
Structured data in place
Structured data found: Article, ImageObject, Organization, Person and WebPage.
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://www.powerfarming.co.nz/sitemap_index.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing 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://www.powerfarming.co.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 (854 words), so crawlers that don't run JavaScript still read it.
Other pages
1 linked page hidden from search
https://www.powerfarming.co.nz/product-category/construction is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
2 pages share a title
https://www.powerfarming.co.nz/product-category/construction and https://www.powerfarming.co.nz/industry/construction all use the title “Construction - Power Farming”. Search engines can't tell which page to show for a search, so each competes with the others.
11 pages without a meta description
https://www.powerfarming.co.nz/our-brands, https://www.powerfarming.co.nz/used-gear, https://www.powerfarming.co.nz/hire-direct, https://www.powerfarming.co.nz/industries, https://www.powerfarming.co.nz/industry/dairy and https://www.powerfarming.co.nz/industry/sheep-beef and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.
8 pages slow to respond
https://www.powerfarming.co.nz/product-category/construction, https://www.powerfarming.co.nz/product-category/machinery, https://www.powerfarming.co.nz/our-brands, https://www.powerfarming.co.nz/used-gear, https://www.powerfarming.co.nz/industries and https://www.powerfarming.co.nz/industry/dairy and 2 others took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 145 found) and read each the way a search engine does.
4 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has an H1
Each page we checked has a main headline.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
24 small tap targets
24 of 75 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_CONNECTION_RESET”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 551 words of copy
The homepage carries about 551 words of visible text.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Talk to the experts” and “Contact Us”.
12 calls to action
The homepage has 12 calls to action, for example “Talk to the experts”, “Contact” and “Book a Service”.
2 short forms
2 short forms (3 fields at most) are right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 12 customer or partner logos and 2 trust badges.
Analytics in place
Analytics detected: Google Tag Manager and HubSpot.
Privacy and tracking
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and Meta Pixel and 2 mores (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.
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).
44 other companies contacted
Loading the homepage contacts 44 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: HubSpot cookie banner
A consent management tool (HubSpot cookie banner) loads with the page.
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 powerfarming.co.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
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 25 issues on powerfarming.co.nz, including 6 speed issues, 2 SEO issues and 1 conversion gap. 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.