Programmable

Website review, no card needed

totalaccess.co.nz logo

totalaccess.co.nz website review

Visit site (opens in a new tab)Reviewed 24 October 202617 issues · 87 checks

This review found 17 issues worth fixing on totalaccess.co.nz, 3 of them high impact, across 87 checks. The most urgent: improve image delivery. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Site score

93A

Closest competitors among WooCommerce stores

Compare side by side
Real-visitor load time (LCP)75th percentile, phones
2.3 s514 msMay 2Oct 17794 ms
Show as table
DateReal-visitor load time (LCP)
May 2, 20262.0 s
May 9, 20262.0 s
May 16, 20262.1 s
May 23, 20262.1 s
May 30, 20262.1 s
Jun 6, 20262.1 s
Jun 13, 20262.0 s
Jun 20, 20262.0 s
Jun 27, 20262.0 s
Jul 4, 20262.0 s
Jul 11, 20262.0 s
Jul 18, 20261.8 s
Jul 25, 20261.3 s
Aug 1, 2026920 ms
Aug 8, 2026827 ms
Aug 15, 2026786 ms
Aug 22, 2026808 ms
Aug 29, 2026817 ms
Sep 5, 2026735 ms
Sep 12, 2026724 ms
Sep 19, 2026765 ms
Sep 26, 2026751 ms
Oct 3, 2026789 ms
Oct 10, 2026794 ms
Oct 17, 2026794 ms
Real-visitor tap response (INP)75th percentile, phones
117 ms73 msMay 2Oct 1786 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026104 ms
May 9, 2026104 ms
May 16, 202698 ms
May 23, 2026100 ms
May 30, 2026107 ms
Jun 6, 2026112 ms
Jun 13, 2026104 ms
Jun 20, 202699 ms
Jun 27, 202699 ms
Jul 4, 202697 ms
Jul 11, 2026104 ms
Jul 18, 2026104 ms
Jul 25, 202695 ms
Aug 1, 202686 ms
Aug 8, 202685 ms
Aug 15, 202680 ms
Aug 22, 202686 ms
Aug 29, 202686 ms
Sep 5, 202682 ms
Sep 12, 202678 ms
Sep 19, 202678 ms
Sep 26, 202684 ms
Oct 3, 202678 ms
Oct 10, 202678 ms
Oct 17, 202686 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

www.totalaccess.co.nz (opens in a new tab)
Live view · interaction off

Speed

3 to fix92

  • Improve image delivery

    1.1 s · 487 KiB

    7 images could be 487 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.1 s faster on a phone.

  • Render-blocking requests

    550 ms

    7 files block the first paint until they finish downloading. Deferring or inlining them could save about 550 ms.

  • Font display

    500 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 500 ms).

  • Reduce unused CSS

    150 ms · 12 KiB

    About 12 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.

  • 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.

3 checks passed

  • Mobile performance score: 92

    92/100

    Your mobile performance score is 92 (desktop: 87). That is in Google's “good” band (90 and up).

  • Main-thread work: 0.2 s

    A phone's processor spends 0.2 s on main-thread work while loading, 48 ms of it running JavaScript. That is comfortably low.

  • Server response: 209 ms

    209 ms

    Your server sent the HTML in 209 ms, well inside Google's 600 ms guideline.

Core Web Vitals

2 to fix100

  • Largest Contentful Paint: 2.9 s

    2.9 s

    Your largest element takes 2.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Cherry pickers, scissor lifts, truck and ute mounted booms,…”. Most of its time is element render delay (2.3 s).

  • Speed Index: 4.1 s

    4.1 s

    Visually, the page fills in at 4.1 s (Speed Index). Good is under 3.4 s.

12 checks passed

  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 1.3 s

    1.3 s

    Real visitors wait 1.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 78 ms

    78 ms

    Real visitors wait 78 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.2 s

    1.2 s

    Real visitors see the first content after 1.2 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 752 ms

    752 ms

    Real visitors wait 752 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Tap response (INP) got 21% faster for real visitors

    -21%

    Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 104 ms to 86 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) got 60% faster for real visitors

    -60%

    Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.0 s to 0.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Time to Interactive: 2.9 s

    2.9 s

    The page is fully interactive after 2.9 s.

  • Cumulative Layout Shift: 0.044

    0.044

    The layout barely moves while loading (CLS 0.044, good is under 0.1).

  • First Contentful Paint: 1.1 s

    1.1 s

    The first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.

  • Total Blocking Time: 0 ms

    0 ms

    Scripts block the page for only 0 ms while loading. Good is under 200 ms.

Images and page weight

2 to fix80

  • 5 images in older formats

    5 images (598 KiB) 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.

  • 3 images far larger than shown

    126 KiB

    3 images are downloaded at several times the size a phone draws them, for example truck_mounted_boom.jpg at 1,284 px wide, shown at 342 px. Resized copies would save about 126 KiB.

  • About 0.3 g of CO₂ per visit

    0.30 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.30 g of CO₂e: 36.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

2 checks passed

  • Page weight: 1.1 MB in 26 requests

    1.1 MB

    Your homepage downloads 1.1 MB in 26 requests on a phone: images 813 KiB (9), fonts 206 KiB (6) and HTML 41 KiB (1). That is a lean page.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

4 to fixGoogle 9693

  • 2 text elements with low contrast

    2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Interactive controls must not be nested (1 element)

    Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

  • 52 links without text

    52 visible links have no text or label, so screen readers cannot say where they go.

  • Users should be able to zoom and scale the text up to 500% (1 element)

    Users should be able to zoom and scale the text up to 500%: 1 element on the page fails this check, rated minor by axe-core.

2 checks passed

  • Every image has alt text

    All 28 images in the HTML carry an alt attribute.

  • 41 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 44 WCAG 2.2 A/AA and best-practice rules on the phone render: 41 passed and 3 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

1 to fixGoogle 10097

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 92 internal links, 5 external

    The homepage links to 92 pages on totalaccess.co.nz and 5 external pages.

7 checks passed

  • Meta description: 154 characters

    Your meta description is 154 characters: “Access equipment hire across New Zealand - booms, scissor lifts, telehandlers and lighting towers. Five branches, natio…”.

  • One H1 headline

    Your main headline reads: “Access equipment hire across New Zealand”.

  • Title: 39 characters

    Your title is a healthy 39 characters: “Access Equipment Hire NZ | Total Access”.

  • Canonical URL set

    The canonical URL is https://www.totalaccess.co.nz/.

  • Structured data in place

    Structured data found: Article, LocalBusiness, 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.totalaccess.co.nz/sitemap_index.xml.

AI search readiness

100

  • No llms.txt

    There is no /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.

  • Organization data: 6 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.

Other pages

100

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 32 found) and read each the way a search engine does.

7 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 a meta description

    All 15 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • 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

1 to fixGoogle 10093

  • 10 small tap targets

    10 of 23 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

2 checks passed

  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Security and trust

2 to fix86

  • No HSTS header

    No Strict-Transport-Security header, so browsers may still try plain http first on a return visit.

  • No Content-Security-Policy

    No Content-Security-Policy header, the main browser-side defence against injected scripts.

  • No clickjacking protection

    Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

  • No X-Content-Type-Options

    X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

  • No Referrer-Policy

    No Referrer-Policy header, so full URLs can leak to the sites you link to.

  • No Permissions-Policy

    No Permissions-Policy header to switch off camera, microphone and location for embedded content.

  • No security.txt

    There is no /.well-known/security.txt telling researchers how to report a security problem to you.

5 checks passed

  • Served over HTTPS

    The homepage is served over HTTPS (totalaccess.co.nz).

  • Valid certificate (73 days left)

    The certificate from Let's Encrypt · YR1 verifies for totalaccess.co.nz and is valid for another 73 days.

  • http:// redirects to https

    http://totalaccess.co.nz redirects to the secure version.

  • HTTP/2

    The server speaks HTTP/2, so browsers load many files over one connection.

  • All 37 links work

    All 37 links checked from your homepage (33 internal, 4 external) answered without errors.

Domain and trust

  • No CAA record

    totalaccess.co.nz has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

Content and conversion

2 to fix88

  • Thin social proof

    Social proof on the homepage: “Over 8,000 customers”. Pairing it with named testimonials or customer logos makes it far more convincing.

  • Only about 121 words

    The homepage has only about 121 words of visible text; thin pages give Google and first-time buyers little to go on.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

  • 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.

6 checks passed

  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “ORDER 0” and “CALL 0800 447 3669”.

  • 12 calls to action

    The homepage has 12 calls to action, for example “Your order 0”, “Call 0800 447 3669” and “Order 0”.

  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 17 phone links and 1 email link.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

Email authentication

90

  • Email authentication score: 90/100

    Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

3 checks passed

  • DMARC policy: quarantine

    DMARC tells receivers to quarantine mail that fails authentication, and sends you reports.

  • SPF with a strict ending (-all)

    An SPF record lists your sending servers and tells receivers to reject anything else: “v=spf1 include:spf.protection.outlook.com -all”.

  • DKIM signing found

    A DKIM key is published (selector “selector1” and “k1”), so receivers can verify mail really came from you.

Privacy and tracking

  • 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.

1 checks passed

  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

Upkeep, stack and company

  • 1 plugin is behind its latest release.devvn-image-hotspot 1.2.0 → 1.3.0

Stack

CMS
WordPress 7.1.3
Framework
jQuery
E-commerce
WooCommerce
Analytics
Google Analytics

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 17 issues on totalaccess.co.nz, including 5 speed issues, 1 SEO issue and 2 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25