Website review, no card needed

nzuniforms.com logo

nzuniforms.com website review

Visit site (opens in a new tab)Reviewed 23 October 202642 issues · 73 checks

This review found 42 issues worth fixing on nzuniforms.com, 14 of them high impact, across 73 checks. The most urgent: page weight: 25.8 MB in 103 requests. 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

Not scored yet: Google's speed test didn't run in this review. Re-run the review to get a score.

Real-visitor load time (LCP)75th percentile, phones
2.6 s1.7 sMay 2Oct 172.3 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20261.8 s
May 9, 20261.8 s
May 16, 20261.8 s
May 23, 20261.8 s
May 30, 20261.9 s
Jun 6, 20261.9 s
Jun 13, 20261.9 s
Jun 20, 20261.9 s
Jun 27, 20261.9 s
Jul 4, 20261.9 s
Jul 11, 20262.0 s
Jul 18, 20261.9 s
Jul 25, 20261.9 s
Aug 1, 20261.9 s
Aug 8, 20261.9 s
Aug 15, 20261.9 s
Aug 22, 20262.0 s
Aug 29, 20262.1 s
Sep 5, 20262.2 s
Sep 12, 20262.3 s
Sep 19, 20262.5 s
Sep 26, 20262.5 s
Oct 3, 20262.5 s
Oct 10, 20262.5 s
Oct 17, 20262.3 s
Real-visitor tap response (INP)75th percentile, phones
155 ms123 msMay 2Oct 17146 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026130 ms
May 9, 2026129 ms
May 16, 2026127 ms
May 23, 2026127 ms
May 30, 2026128 ms
Jun 6, 2026129 ms
Jun 13, 2026134 ms
Jun 20, 2026134 ms
Jun 27, 2026132 ms
Jul 4, 2026133 ms
Jul 11, 2026140 ms
Jul 18, 2026135 ms
Jul 25, 2026134 ms
Aug 1, 2026136 ms
Aug 8, 2026131 ms
Aug 15, 2026138 ms
Aug 22, 2026144 ms
Aug 29, 2026145 ms
Sep 5, 2026147 ms
Sep 12, 2026148 ms
Sep 19, 2026151 ms
Sep 26, 2026150 ms
Oct 3, 2026149 ms
Oct 10, 2026146 ms
Oct 17, 2026146 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

Full-page screenshot of nzuniforms.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. nzuniforms.com at 1.2 s1.2 s
  2. nzuniforms.com at 2.5 s2.5 s
  3. nzuniforms.com at 3.7 s3.7 s
  4. nzuniforms.com at 5.0 s5.0 s
  5. nzuniforms.com at 6.2 s6.2 s
  6. nzuniforms.com at 7.4 s7.4 s
  7. nzuniforms.com at 8.7 s8.7 s
  8. nzuniforms.com at 9.9 s9.9 s

Speed

9 to fix
  • 8 third-party services on the page

    8 third-party services load with your homepage (Google CDN, Google Tag Manager and Facebook and others), adding 1.9 MB and 1.1 s of main-thread time.

  • Font display

    650 ms

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

  • Document request latency

    500 ms · 105 KiB

    The HTML itself could arrive about 500 ms sooner: redirects, a slow server response or missing compression delay everything after it.

  • Reduce initial server response time

    521 ms

    Reduce initial server response time. Google estimates savings of 521 ms on a phone.

  • Google CDN adds 375 ms

    375 ms

    Google CDN costs a phone 375 ms of main-thread work and 734 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.

  • Google Tag Manager adds 343 ms

    343 ms

    Google Tag Manager costs a phone 343 ms of main-thread work and 472 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.

  • Main-thread work: 3.3 s

    A phone's processor spends 3.3 s on main-thread work while loading, 1.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • LiveChat adds 74 ms

    74 ms

    LiveChat costs a phone 74 ms of main-thread work and 366 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.

  • Server response: 621 ms

    621 ms

    Your server takes 621 ms to send the HTML. Google recommends under 600 ms; everything else waits for it.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

Core Web Vitals

6 to fix100
  • 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.

  • First Contentful Paint: 5.9 s

    5.9 s

    The first text or image appears after 5.9 s on a phone. Good is under 1.8 s.

  • Speed Index: 12.0 s

    12.0 s

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

  • Largest content (LCP) got 33% slower for real visitors

    +33%

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

  • Real-user FCP: 2.1 s

    2.1 s

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

  • 32 images without width and height

    32 images have no width and height attributes, so the layout jumps as each one loads.

  • Tap response (INP) got 13% slower for real visitors

    +13%

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

5 checks passed
  • Real-user LCP: 0.3 s

    0.3 s

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

  • Real-user INP: 142 ms

    142 ms

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

  • Real-user CLS: 0.04

    0.04

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

  • Real-user TTFB: 606 ms

    606 ms

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

  • Cumulative Layout Shift: 0.085

    0.085

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

Images and page weight

5 to fix18
  • Page weight: 25.8 MB in 103 requests

    25.8 MB

    Your homepage downloads 25.8 MB in 103 requests on a phone: images 22.7 MB (41), scripts 2.1 MB (35) and fonts 388 KiB (8). Under 2 MB keeps phones on slow connections fast.

  • 11 images over 500 KB

    11 images weigh 16.4 MB together. On a phone connection a single image that size takes seconds.

  • 4 images far larger than shown

    2.1 MB

    4 images are downloaded at several times the size a phone draws them, for example iStock-1047620616.jpg at 5,444 px wide, shown at 359 px. Resized copies would save about 2.1 MB.

  • 19 images in older formats

    19 images (18.2 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.

  • 7 images below the first screen load straight away

    7 images further down the page (3.3 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 7.3 g of CO₂ per visit

    7.32 g

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

Accessibility

9 to fixGoogle 7387
  • 7 buttons without a name

    7 buttons have no accessible name, so screen readers announce just “button”.

  • Hidden but focusable

    36 elements hidden from screen readers can still receive keyboard focus.

  • 8 text elements with low contrast

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

  • 4 tap targets too small

    4 tap targets are too small or too close together to hit reliably with a finger.

  • Elements must only use permitted ARIA attributes (3 elements)

    Elements must only use permitted ARIA attributes: 3 elements on the page fail this check, rated serious by axe-core.

  • 12 images without alt text

    12 images have no alt text, which hurts accessibility and image search.

  • 12 links without text

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

  • 8 form fields without a label

    8 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • Headings should not be empty (2 elements)

    Headings should not be empty: 2 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

    Headings skip levels (h1 → h3, h1 → h3 and h2 → h4), which makes the page harder to scan with a screen reader.

1 checks passed
  • 49 automated accessibility rules passed

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

SEO

6 to fixGoogle 7770
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • Title is short (18 characters)

    Your title is only 18 characters: “Home | NZ Uniforms”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • 20 H1 headlines

    There are 20 <h1> headlines (“Labour Day https://www.nzuniforms.com/Monday 26 October 2026 : All stores w…”, “” and “”). One clear main headline is easier for people and search engines.

  • 24 links with vague text

    24 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 138 internal links, 14 external

    The homepage links to 138 pages on nzuniforms.com and 14 external pages.

3 checks passed
  • Canonical URL set

    The canonical URL is https://www.nzuniforms.com/.

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.nzuniforms.com/sitemap.xml.

AI search readiness

1 to fix88
  • No Organization structured data

    There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

  • No llms.txt

    There is no https://www.nzuniforms.com/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 (1,269 words), so crawlers that don't run JavaScript still read it.

Other pages

100
  • 15 internal pages checked

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

1 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

Best practices

2 to fixGoogle 6991
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

  • 3 distorted images

    3 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Mixed content”).

2 checks passed
  • Tap targets are thumb-sized

    24 of 29 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix67
  • 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.

  • Thin social proof

    Social proof on the homepage: 2 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

  • 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 1,155 words of copy

    The homepage carries about 1,155 words of visible text.

3 checks passed
  • 18 calls to action

    The homepage has 18 calls to action, for example “Contact us”, “Learn more” and “Learn More”.

  • 4 short forms

    4 short forms (4 fields at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Meta Pixel.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Meta Pixel (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

    11

    Opening the homepage sets 11 cookies, 4 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.

  • 18 other companies contacted

    Loading the homepage contacts 18 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 nzuniforms.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
Tailwind CSS
Analytics
Google 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 42 issues on nzuniforms.com, including 15 speed issues, 6 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

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