Website review, no card needed
zepto.com.au website review
Visit site (opens in a new tab)Reviewed 3 November 202626 issues · 63 checks
This review found 26 issues worth fixing on zepto.com.au, 9 of them high impact, across 63 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 | 4.4 s |
| May 23, 2026 | 4.4 s |
| May 30, 2026 | 4.4 s |
| Jun 6, 2026 | 4.4 s |
| Jun 13, 2026 | 4.4 s |
| Jun 20, 2026 | 4.4 s |
| Jun 27, 2026 | 4.4 s |
| Jul 4, 2026 | 4.3 s |
| Jul 11, 2026 | 4.4 s |
| Jul 18, 2026 | 4.6 s |
| Jul 25, 2026 | 4.6 s |
| Aug 1, 2026 | 4.7 s |
| Aug 8, 2026 | 4.7 s |
| Aug 15, 2026 | 4.7 s |
| Aug 22, 2026 | 4.9 s |
| Aug 29, 2026 | 4.9 s |
| Sep 5, 2026 | 5.1 s |
| Sep 12, 2026 | 5.3 s |
| Sep 19, 2026 | 5.3 s |
| Sep 26, 2026 | 5.3 s |
| Oct 3, 2026 | 5.2 s |
| Oct 10, 2026 | 5.0 s |
| Oct 17, 2026 | 5.0 s |
| Oct 24, 2026 | 4.9 s |
| Oct 31, 2026 | 5.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 250 ms |
| May 23, 2026 | 256 ms |
| May 30, 2026 | 257 ms |
| Jun 6, 2026 | 260 ms |
| Jun 13, 2026 | 284 ms |
| Jun 20, 2026 | 275 ms |
| Jun 27, 2026 | 283 ms |
| Jul 4, 2026 | 293 ms |
| Jul 11, 2026 | 282 ms |
| Jul 18, 2026 | 273 ms |
| Jul 25, 2026 | 262 ms |
| Aug 1, 2026 | 220 ms |
| Aug 8, 2026 | 228 ms |
| Aug 15, 2026 | 231 ms |
| Aug 22, 2026 | 238 ms |
| Aug 29, 2026 | 259 ms |
| Sep 5, 2026 | 245 ms |
| Sep 12, 2026 | 249 ms |
| Sep 19, 2026 | 247 ms |
| Sep 26, 2026 | 253 ms |
| Oct 3, 2026 | 258 ms |
| Oct 10, 2026 | 218 ms |
| Oct 17, 2026 | 224 ms |
| Oct 24, 2026 | 186 ms |
| Oct 31, 2026 | 179 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 LCP: 4.9 s
4.9 sReal visitors wait 4.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 3.6 s
3.6 sReal visitors see the first content after 3.6 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 2.1 s
2.1 sReal visitors wait 2.1 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 13% slower for real visitors
+13%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 4.4 s to 5.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user INP: 181 ms
181 msReal visitors wait 181 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Tap response (INP) got 28% faster for real visitors
-28%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 250 ms to 179 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
Page weight: 6.6 MB
6.6 MBYour homepage downloads 6.6 MB on a phone, 4.8 MB of it images (73%). Under 2 MB keeps phones on slow connections fast.
17 images below the first screen load straight away
17 images further down the page (1,002 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
12 images in older formats
12 images (887 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.
4 images far larger than shown
31 KiB4 images are downloaded at several times the size a phone draws them, for example Suzie-Blog-tile_11cbda6f49c579a7577b126c1f824ca1.png at 390 px wide, shown at 120 px. Resized copies would save about 31 KiB.
About 1.9 g of CO₂ per visit
1.86 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.86 g of CO₂e: 223.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
3 tap targets too small
3 tap targets are too small or too close together to hit reliably with a finger.
ARIA input fields must have an accessible name (1 element)
ARIA input fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.
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.
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.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
62 links without text
62 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.
2 checks passed
Every image has alt text
All 62 images in the HTML carry an alt attribute.
49 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: 49 passed and 6 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Structured data has 1 problem
Structured data found (BreadcrumbList, LocalBusiness, Organization and WebPage) but with 1 problem, for example “Organization: missing name”.
121 internal links, 9 external
The homepage links to 121 pages on zepto.com.au and 9 external pages.
7 checks passed
Meta description: 138 characters
Your meta description is 138 characters: “Zepto is unlocking the future of transactions with the next generation of real-time account-to-account and Direct Debit…”.
One H1 headline
Your main headline reads: “Pioneering the payments future”.
Title: 59 characters
Your title is a healthy 59 characters: “Zepto | The Leaders in Account-to-Account Payment Solutions”.
Canonical URL set
The canonical URL is https://zepto.com.au/.
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://zepto.com.au/sitemaps-1-sitemap.xml.
AI search readiness
robots.txt blocks 1 AI answer engine crawler
1 of 6Your robots.txt shuts out Perplexity (PerplexityBot). These fetch pages to answer people's questions and cite the source, so your site can't be quoted or linked in those answers.
Organization data is thin (1 of 6 facts)
Your Organization JSON-LD is missing url, 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.
No llms.txt
There is no https://zepto.com.au/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.
Opted out of AI training for 2 crawlers
robots.txt blocks GPTBot and Google-Extended, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers.
1 checks passed
Text is in the HTML
Your server sends the page's text in the HTML (1,388 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages share a title
https://zepto.com.au/a-better-way-to-pay and https://zepto.com.au/a-better-way-to-pay/account-to-account-payments all use the title “Zepto | Account-To-Account Payments”. Search engines can't tell which page to show for a search, so each competes with the others.
2 pages without a meta description
https://zepto.com.au/insights/payday-super-starts-july-1-the-real-challenge-isnt-just-compliance-its-infrastructure and https://zepto.com.au/insights/everyone-talks-about-partnership-heres-what-it-actually-looks-like have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages share a meta description
https://zepto.com.au/a-better-way-to-pay and https://zepto.com.au/a-better-way-to-pay/account-to-account-payments use the same meta description. A description written for each page earns more clicks.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://zepto.com.au/a-better-way-to-pay, whose canonical is https://zepto.com.au/a-better-way-to-pay/account-to-account-payments. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 68 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.
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
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://embed.typeform.com/next/css/widget.css' from origin 'https://zepto.com.au' has bee…”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
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 opening hours
The homepage shows no opening hours. If customers visit or call, show when.
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.
About 528 words of copy
The homepage carries about 528 words of visible text.
6 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Enquire Now”.
4 calls to action
The homepage has 4 calls to action, for example “Enquire Now”, “Sign Up” and “Request a demo”.
1 short form
A short form (4 fields at most) is right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 41 customer or partner logos and 3 trust badges.
Analytics in place
Analytics detected: Google Tag Manager, Microsoft Clarity and Cloudflare Web Analytics.
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.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Clarity 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.
14 cookies set on arrival
14Opening the homepage sets 14 cookies (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.
29 other companies contacted
Loading the homepage contacts 29 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 zepto.com.au, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- SEOmatic
- Framework
- jQuery
- Analytics
- Google Tag Manager | Microsoft Clarity
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 26 issues on zepto.com.au, including 4 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.