Website review, no card needed

johnbull.co.nz logo

johnbull.co.nz website review

Visit site (opens in a new tab)Reviewed 6 November 202631 issues · 82 checks

This review found 31 issues worth fixing on johnbull.co.nz, 7 of them high impact, across 82 checks. The most urgent: page weight: 4.2 MB in 213 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

Real-visitor load time (LCP)75th percentile, phones
2.4 s1.3 sMay 16Oct 311.5 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.7 s
May 23, 20261.5 s
May 30, 20261.5 s
Jun 6, 20261.5 s
Jun 13, 20261.4 s
Jun 20, 20261.5 s
Jun 27, 20261.5 s
Jul 4, 20261.5 s
Jul 11, 20261.8 s
Jul 18, 20261.9 s
Jul 25, 20261.9 s
Aug 1, 20262.3 s
Aug 8, 20262.0 s
Aug 15, 20262.0 s
Aug 22, 20261.9 s
Aug 29, 20261.5 s
Sep 5, 20261.5 s
Sep 12, 20261.6 s
Sep 19, 20261.6 s
Sep 26, 20261.7 s
Oct 3, 20261.7 s
Oct 10, 20261.6 s
Oct 17, 20261.6 s
Oct 24, 20261.5 s
Oct 31, 20261.5 s
Real-visitor tap response (INP)75th percentile, phones
88 ms78 msMay 16Oct 3181 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202682 ms
May 23, 202684 ms
May 30, 202683 ms
Jun 6, 202682 ms
Jun 13, 202684 ms
Jun 20, 202680 ms
Jun 27, 202680 ms
Jul 4, 202683 ms
Jul 11, 202681 ms
Jul 18, 202685 ms
Jul 25, 202687 ms
Aug 1, 202686 ms
Aug 8, 202686 ms
Aug 15, 202687 ms
Aug 22, 202681 ms
Aug 29, 202681 ms
Sep 5, 202680 ms
Sep 12, 202679 ms
Sep 19, 202680 ms
Oct 17, 202685 ms
Oct 24, 202683 ms
Oct 31, 202681 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 johnbull.co.nz (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. johnbull.co.nz at 0.4 s0.4 s
  2. johnbull.co.nz at 0.8 s0.8 s
  3. johnbull.co.nz at 1.1 s1.1 s
  4. johnbull.co.nz at 1.5 s1.5 s
  5. johnbull.co.nz at 1.9 s1.9 s
  6. johnbull.co.nz at 2.3 s2.3 s
  7. johnbull.co.nz at 2.6 s2.6 s
  8. johnbull.co.nz at 3.0 s3.0 s

Speed

7 to fix56
  • Reduce unused JavaScript

    750 ms · 814 KiB

    About 814 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 750 ms faster on a phone.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Hotjar and Vimeo and others), adding 1.5 MB and 917 ms of main-thread time.

  • Mobile performance score: 56

    56/100

    Your mobile performance score is 56. Pages that score under 90 lose visitors before the first paint.

  • Google Tag Manager adds 727 ms

    727 ms

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

  • Render-blocking requests

    450 ms

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

  • Main-thread work: 3.0 s

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

  • Vimeo adds 42 ms

    42 ms

    Vimeo costs a phone 42 ms of main-thread work and 540 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.

  • Improve image delivery

    150 ms · 169 KiB

    5 images could be 169 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

  • 11 long tasks on the main thread

    11 long tasks block the main thread while loading, the longest for 223 ms. During a long task the page ignores taps.

  • Use efficient cache lifetimes

    96 KiB

    10 files are served with short cache lifetimes, so returning visitors download them again (96 KiB).

  • Reduce unused CSS

    22 KiB

    About 22 KiB of CSS is downloaded but never applied on this page.

  • Legacy JavaScript

    12 KiB

    Polyfills for old browsers add 12 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.

  • Duplicated JavaScript

    2 KiB

    2 KiB JavaScript is shipped twice across bundles.

1 checks passed
  • Server response: 20 ms

    20 ms

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

Core Web Vitals

4 to fix100
  • Time to Interactive: 20.9 s

    20.9 s

    The page becomes fully interactive after 20.9 s. Good is under 3.8 s.

  • Largest Contentful Paint: 7.2 s

    7.2 s

    Your largest element takes 7.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • Total Blocking Time: 580 ms

    580 ms

    Scripts block taps and scrolling for 580 ms in total while the page loads. Good is under 200 ms.

  • Speed Index: 5.1 s

    5.1 s

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

  • Tap response (INP) held steady for real visitors

    -1%

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

  • Largest content (LCP) held steady for real visitors

    -5%

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

8 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.4 s

    1.4 s

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

  • Real-user INP: 79 ms

    79 ms

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

  • Real-user CLS: 0.03

    0.03

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

  • Real-user FCP: 0.9 s

    0.9 s

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

  • Real-user TTFB: 498 ms

    498 ms

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

  • Cumulative Layout Shift: 0.08

    0.08

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

  • First Contentful Paint: 1.4 s

    1.4 s

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

Images and page weight

2 to fix60
  • Page weight: 4.2 MB in 213 requests

    4.2 MB

    Your homepage downloads 4.2 MB in 213 requests on a phone: scripts 1.7 MB (48), images 882 KiB (25) and other files 795 KiB (108). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    127 KiB

    1 image is downloaded at several times the size a phone draws it, for example Feature_section_-__Video_Content.png at 2,000 px wide, shown at 390 px. Resized copies would save about 127 KiB.

  • About 1.2 g of CO₂ per visit

    1.19 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.19 g of CO₂e: 142.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 load when needed

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

Accessibility

2 to fixGoogle 9196
  • Invalid ARIA attributes

    12 elements use ARIA attributes their role does not allow, which confuses screen readers.

  • 12 tap targets too small

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 9 images in the HTML carry an alt attribute.

  • 50 automated accessibility rules passed

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

SEO

4 to fixGoogle 10081
  • Title is short (22 characters)

    Your title is only 22 characters: “John Bull - Production”. 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.

  • Meta description is short (33 characters)

    Your meta description is only 33 characters: “Welcome to John Bull - Production”. 70 to 160 characters is enough to sell the click.

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

  • 77 internal links, 6 external

    The homepage links to 77 pages on johnbull.co.nz and 6 external pages.

4 checks passed
  • One H1 headline

    Your main headline reads: “MADE FOR NEW ZEALAND SINCE 1934”.

  • Canonical URL set

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

  • 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.johnbull.co.nz/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.

3 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 (311 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://www.johnbull.co.nz/llms.txt (5 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix93
  • 13 pages share a meta description

    https://www.johnbull.co.nz/collections/all-products, https://www.johnbull.co.nz/collections/all-boots, https://www.johnbull.co.nz/collections/accessories, https://www.johnbull.co.nz/collections/building-and-construction-boots, https://www.johnbull.co.nz/collections/farming-and-agriculture-boots and https://www.johnbull.co.nz/collections/warehouse-and-transport-boots and 7 others use the same meta description. A description written for each page earns more clicks.

  • 12 pages without an H1

    https://www.johnbull.co.nz/collections/all-boots, https://www.johnbull.co.nz/collections/accessories, https://www.johnbull.co.nz/collections/building-and-construction-boots, https://www.johnbull.co.nz/collections/farming-and-agriculture-boots, https://www.johnbull.co.nz/collections/warehouse-and-transport-boots and https://www.johnbull.co.nz/collections/electrical-trades and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

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

  • 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

5 to fixGoogle 5081
  • 4 small tap targets

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

  • 2 third-party cookies

    2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

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

  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

  • Missing source maps

    Large scripts ship without source maps.

  • 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

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

  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

  • About 478 words of copy

    The homepage carries about 478 words of visible text.

4 checks passed
  • 3 calls to action

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

  • 1 short form

    A short form (1 field at most) is right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and The Trade Desk (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.

  • 15 cookies set on arrival

    15

    Opening the homepage sets 15 cookies, 2 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.

  • 26 other companies contacted

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

Apps on your store

No apps were seen in the code your storefront loads.

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

Framework
Tailwind CSS
E-commerce
Shopify
Analytics
Google Tag Manager
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 31 issues on johnbull.co.nz, including 11 speed issues, 4 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