Website review, no card needed

pepperandme.com.au logo

pepperandme.com.au website review

Visit site (opens in a new tab)Reviewed 16 November 202639 issues · 87 checks

This review found 39 issues worth fixing on pepperandme.com.au, 14 of them high impact, across 87 checks. The most urgent: reduce unused JavaScript. 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
1.5 s1.2 sMay 30Nov 141.4 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20261.2 s
Jun 6, 20261.2 s
Jun 13, 20261.2 s
Jun 20, 20261.3 s
Jun 27, 20261.3 s
Jul 4, 20261.3 s
Jul 11, 20261.4 s
Jul 18, 20261.3 s
Jul 25, 20261.3 s
Aug 1, 20261.3 s
Aug 8, 20261.3 s
Aug 15, 20261.3 s
Aug 22, 20261.3 s
Aug 29, 20261.3 s
Sep 5, 20261.4 s
Sep 12, 20261.4 s
Sep 19, 20261.4 s
Sep 26, 20261.5 s
Oct 3, 20261.4 s
Oct 10, 20261.4 s
Oct 17, 20261.4 s
Oct 24, 20261.4 s
Oct 31, 20261.4 s
Nov 7, 20261.5 s
Nov 14, 20261.4 s
Real-visitor tap response (INP)75th percentile, phones
117 ms90 msMay 30Nov 14108 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 202693 ms
Jun 6, 202694 ms
Jun 13, 202694 ms
Jun 20, 202696 ms
Jun 27, 202696 ms
Jul 4, 202698 ms
Jul 11, 202699 ms
Jul 18, 202695 ms
Jul 25, 202695 ms
Aug 1, 202695 ms
Aug 8, 202695 ms
Aug 15, 202696 ms
Aug 22, 202698 ms
Aug 29, 2026100 ms
Sep 5, 202698 ms
Sep 12, 202697 ms
Sep 19, 2026101 ms
Sep 26, 2026104 ms
Oct 3, 2026111 ms
Oct 10, 2026113 ms
Oct 17, 2026113 ms
Oct 24, 2026114 ms
Oct 31, 2026114 ms
Nov 7, 2026112 ms
Nov 14, 2026108 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 pepperandme.com.au (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

8 to fix61
  • Reduce unused JavaScript

    3.1 s · 660 KiB

    About 660 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.1 s faster on a phone.

  • Main-thread work: 4.3 s

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

  • 3,318 HTML elements

    The page has 3,318 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Improve image delivery

    450 ms · 679 KiB

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

  • Mobile performance score: 61

    61/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Shopify, minmaxify.com and Klaviyo and others), adding 1.2 MB and 661 ms of main-thread time.

  • Render-blocking requests

    400 ms

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

  • Shopify adds 207 ms

    207 ms

    Shopify costs a phone 207 ms of main-thread work and 765 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.

  • Use efficient cache lifetimes

    150 ms · 80 KiB

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

  • 7 long tasks on the main thread

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

  • Legacy JavaScript

    33 KiB

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

  • Duplicated JavaScript

    4 KiB

    4 KiB JavaScript is shipped twice across bundles.

1 checks passed
  • Server response: 10 ms

    10 ms

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

Core Web Vitals

5 to fix100
  • Largest Contentful Paint: 16.2 s

    16.2 s

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

  • Time to Interactive: 16.4 s

    16.4 s

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

  • First Contentful Paint: 3.7 s

    3.7 s

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

  • Speed Index: 5.9 s

    5.9 s

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

  • 1 image without width and height

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

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

    +18%

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

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

    +16%

    Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 1.2 s to 1.4 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.9 s

    1.9 s

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

  • Real-user INP: 120 ms

    120 ms

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

  • Real-user CLS: 0.01

    0.01

    For real visitors the layout shifts by 0.01 (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: 389 ms

    389 ms

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

  • Total Blocking Time: 141 ms

    141 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

2 to fix81
  • Page weight: 3.5 MB in 221 requests

    3.5 MB

    Your homepage downloads 3.5 MB in 221 requests on a phone: scripts 1.3 MB (80), images 1.0 MB (39) and other files 910 KiB (71). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    Summer-Range-26_Mobile.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).

  • About 1.0 g of CO₂ per visit

    0.98 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.98 g of CO₂e: 117.6 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

10 to fixGoogle 7887
  • Images must have alternative text (1 element)

    Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.

  • 10 text elements with low contrast

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

  • 9 tap targets too small

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

  • Hidden but focusable

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

  • All page content should be contained by landmarks (15 elements)

    All page content should be contained by landmarks: 15 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.

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • 13 links without text

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

  • Headings skip levels

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

1 checks passed
  • 43 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 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

4 to fixGoogle 8576
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is short (11 characters)

    Your title is only 11 characters: “Pepper & Me”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Meta description is long (297 characters)

    Your meta description is 297 characters; Google truncates after about 160, so the end of your pitch is cut.

  • 9 links crawlers can't follow

    9 links have no real href, so search engines can't follow them.

  • 245 internal links, 12 external

    The homepage links to 245 pages on pepperandme.com.au and 12 external pages.

5 checks passed
  • Canonical URL set

    The canonical URL is https://pepperandme.co.nz/.

  • Structured data in place

    Structured data found: BreadcrumbList, Organization and WebSite.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • 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://pepperandme.co.nz/sitemap.xml.

AI search readiness

1 to fix88
  • 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.

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

  • llms.txt published

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

Other pages

4 to fix68
  • 1 page without a title

    https://pepperandme.co.nz/customer_authentication/redirect has no <title>, so Google invents the link text in results.

  • 1 linked page hidden from search

    https://pepperandme.co.nz/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 15 pages without a meta description

    https://pepperandme.co.nz/collections/black-friday-2026, https://pepperandme.co.nz/collections/summer-range-2026, https://pepperandme.co.nz/customer_authentication/redirect, https://pepperandme.co.nz/collections/shop-all, https://pepperandme.co.nz/collections/salts-and-grinds and https://pepperandme.co.nz/collections/salts-1 and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://pepperandme.co.nz/customer_authentication/redirect has 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 112 found) and read each the way a search engine does.

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

  • Titles are unique

    Every page we checked has its own title.

Best practices

1 to fixGoogle 9693
  • 28 small tap targets

    28 of 121 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.

Content and conversion

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

  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • Thin social proof

    Social proof on the homepage: a star rating. Pairing it with named testimonials or customer logos makes it far more convincing.

  • 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 930 words of copy

    The homepage carries about 930 words of visible text.

6 checks passed
  • 46 calls to action

    The homepage has 46 calls to action, for example “Shop All”, “Shop all friends” and “Buy now”.

  • 30 short forms

    30 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: LinkedIn Insight.

  • Direct contact links

    Visitors can reach you directly: 2 phone links and 2 email links.

  • Opening hours shown

    Your opening hours are on the homepage.

  • Phone number on the homepage

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

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo 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.

  • 20 cookies set on arrival

    20

    Opening the homepage sets 20 cookies, 3 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.

  • 37 other companies contacted

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

Apps on your store

Your storefront loads 11 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Judge Me Reviews · Gsc Countdown Timer · Klaviyo Email Marketing Sms · Minmaxify Order Limits · Monster Cart Upsell Free Gifts · Monster Upsells · Forms · Easify Box Builder · gorgias.chat · rechargecdn.com · 9gtb.com

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

E-commerce
Shopify
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 39 issues on pepperandme.com.au, including 13 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