Website review, no card needed
circa.com.au website review
Visit site (opens in a new tab)Reviewed 5 November 202638 issues · 86 checks
This review found 38 issues worth fixing on circa.com.au, 13 of them high impact, across 86 checks. The most urgent: main-thread work: 9.1 s. 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
84B- #21,224 of 117,726 reviewed websitesbeats 77%
- #13,816 of 66,937 online storesbeats 73%
- #13,414 of 61,033 Shopify storesbeats 72%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.8 s |
| May 23, 2026 | 1.7 s |
| May 30, 2026 | 1.7 s |
| Jun 6, 2026 | 1.6 s |
| Jun 13, 2026 | 1.7 s |
| Jun 20, 2026 | 1.7 s |
| Jun 27, 2026 | 1.7 s |
| Jul 4, 2026 | 1.7 s |
| Jul 11, 2026 | 1.7 s |
| Jul 18, 2026 | 1.6 s |
| Jul 25, 2026 | 1.6 s |
| Aug 1, 2026 | 1.6 s |
| Aug 8, 2026 | 1.6 s |
| Aug 15, 2026 | 1.7 s |
| Aug 22, 2026 | 1.7 s |
| Aug 29, 2026 | 1.7 s |
| Sep 5, 2026 | 1.7 s |
| Sep 12, 2026 | 1.7 s |
| Sep 19, 2026 | 1.7 s |
| Sep 26, 2026 | 1.7 s |
| Oct 3, 2026 | 1.8 s |
| Oct 10, 2026 | 1.7 s |
| Oct 17, 2026 | 1.7 s |
| Oct 24, 2026 | 1.7 s |
| Oct 31, 2026 | 1.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 145 ms |
| May 23, 2026 | 153 ms |
| May 30, 2026 | 149 ms |
| Jun 6, 2026 | 146 ms |
| Jun 13, 2026 | 147 ms |
| Jun 20, 2026 | 145 ms |
| Jun 27, 2026 | 147 ms |
| Jul 4, 2026 | 154 ms |
| Jul 11, 2026 | 159 ms |
| Jul 18, 2026 | 161 ms |
| Jul 25, 2026 | 163 ms |
| Aug 1, 2026 | 163 ms |
| Aug 8, 2026 | 163 ms |
| Aug 15, 2026 | 168 ms |
| Aug 22, 2026 | 164 ms |
| Aug 29, 2026 | 163 ms |
| Sep 5, 2026 | 163 ms |
| Sep 12, 2026 | 155 ms |
| Sep 19, 2026 | 152 ms |
| Sep 26, 2026 | 160 ms |
| Oct 3, 2026 | 160 ms |
| Oct 10, 2026 | 160 ms |
| Oct 17, 2026 | 162 ms |
| Oct 24, 2026 | 153 ms |
| Oct 31, 2026 | 151 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
Main-thread work: 9.1 s
A phone's processor spends 9.1 s on main-thread work while loading, 4.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
5,225 HTML elements
The page has 5,225 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Yotpo and Facebook and others), adding 1.8 MB and 1.7 s of main-thread time.
Reduce unused JavaScript
150 ms · 979 KiBAbout 979 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.
Mobile performance score: 59
59/100Your mobile performance score is 59. Pages that score under 90 lose visitors before the first paint.
Use efficient cache lifetimes
599 KiB26 files are served with short cache lifetimes, so returning visitors download them again (599 KiB).
Google Tag Manager adds 491 ms
491 msGoogle Tag Manager costs a phone 491 ms of main-thread work and 521 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 ms3 files block the first paint until they finish downloading. Deferring or inlining them could save about 450 ms.
Yotpo adds 320 ms
320 msYotpo costs a phone 320 ms of main-thread work and 357 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.
Klaviyo adds 201 ms
201 msKlaviyo costs a phone 201 ms of main-thread work and 322 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 208 ms. During a long task the page ignores taps.
Reduce unused CSS
150 ms · 48 KiBAbout 48 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.
Improve image delivery
82 KiB10 images could be 82 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Legacy JavaScript
53 KiBPolyfills for old browsers add 53 KiB JavaScript that modern phones do not need.
Minify JavaScript
10 KiB10 KiB could be saved by minifying JavaScript.
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.
1 checks passed
Server response: 8 ms
8 msYour server sent the HTML in 8 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Speed Index: 14.8 s
14.8 sVisually, the page fills in at 14.8 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 24.0 s
24.0 sThe page becomes fully interactive after 24.0 s. Good is under 3.8 s.
Total Blocking Time: 1.0 s
1.0 sScripts block taps and scrolling for 1.0 s in total while the page loads. Good is under 200 ms.
40 images without width and height
40 images have no width and height attributes, so the layout jumps as each one loads.
Largest Contentful Paint: 3.5 s
3.5 sYour largest element takes 3.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “hero image”.
Tap response (INP) held steady for real visitors
+2%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 145 ms to 151 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-7%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.8 s to 1.6 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.6 s
1.6 sReal visitors wait 1.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 140 ms
140 msReal visitors wait 140 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.09
0.09For real visitors the layout shifts by 0.09 (75th percentile). Good is under 0.1.
Real-user FCP: 1.1 s
1.1 sReal visitors see the first content after 1.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 626 ms
626 msReal visitors wait 626 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 1.2 s
1.2 sThe first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 6.9 MB in 341 requests
6.9 MBYour homepage downloads 6.9 MB in 341 requests on a phone: scripts 2.5 MB (114), media 1.9 MB (1) and images 1.4 MB (64). Under 2 MB keeps phones on slow connections fast.
5 images far larger than shown
596 KiB5 images are downloaded at several times the size a phone draws them, for example CIRCA_eCOMM_XMAS26_KitchenCareTrioGiftSet_WhiteTea_WildMint_ at 1,800 px wide, shown at 109 px. Resized copies would save about 596 KiB.
An image on the first screen is lazy-loaded
Secondary_Banner_Best_Sellers.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 2.0 g of CO₂ per visit
1.96 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.96 g of CO₂e: 234.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
ARIA attributes must conform to valid values (6 elements)
ARIA attributes must conform to valid values: 6 elements on the page fail this check, rated critical by axe-core.
Certain ARIA roles must be contained by particular parents (2 elements)
Certain ARIA roles must be contained by particular parents: 2 elements on the page fail this check, rated critical by axe-core.
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.
ARIA dialog and alertdialog nodes should have an accessible name (1 element)
ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.
All page content should be contained by landmarks (38 elements)
All page content should be contained by landmarks: 38 elements on the page fail this check, rated moderate by axe-core.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (7 elements).
2 checks passed
Every image has alt text
All 42 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. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Structured data has 2 problems
Structured data found (Corporation) but with 2 problems, for example “Corporation: logo is not an absolute URL ("https:files/1200x628px-sharing-image.jpg")”.
4 links with vague text
4 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
One H1 headline
Your <h1> is empty.
88 internal links, 4 external
The homepage links to 88 pages on circa.com.au and 4 external pages.
6 checks passed
Meta description: 105 characters
Your meta description is 105 characters: “Handmade Scented Soy Candles, Fragrance Diffusers, Hand Washes & Gift Sets proudly made in Australia.”.
Title: 63 characters
Your title is a healthy 63 characters: “Soy Wax Candles, Fragrance Diffusers & Gifts - CIRCA – CIRCA AU”.
Canonical URL set
The canonical URL is https://circa.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://circa.com.au/sitemap.xml.
AI search readiness
Most text only appears after JavaScript runs
29%A phone browser shows 1,291 words, but the HTML your server sends has only 373. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.
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.
Organization data: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and description; sameAs (social profiles) and contact details would complete it.
llms.txt published
The site publishes https://circa.com.au/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a title
https://circa.com.au/customer_authentication/redirect has no <title>, so Google invents the link text in results.
1 linked page hidden from search
https://circa.com.au/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
1 page without a meta description
https://circa.com.au/customer_authentication/redirect has no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://circa.com.au/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 33 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
121 small tap targets
121 of 209 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
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.”).
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 1 testimonial or review block. 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,291 words of copy
The homepage carries about 1,291 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP NOW” and “SHOP BY CATEGORY”.
16 calls to action
The homepage has 16 calls to action, for example “Shop By”, “SHOP NOW” and “SHOP CHRISTMAS COLLECTION”.
1 short form
A short form (1 field at most) is right on the homepage, asking for an email.
Analytics in place
Analytics detected: Microsoft Clarity.
Privacy and tracking
8 trackers load before any consent
8Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Klaviyo and 3 mores (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.
25 cookies set on arrival
25Opening the homepage sets 25 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.
50 other companies contacted
Loading the homepage contacts 50 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 circa.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 12 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Elevar Conversion Tracking · Yotpo Loyalty Rewards · Microsoft Clarity · Eg Auto Add To Cart · Yotpo Product Reviews · Klaviyo Email Marketing Sms · cfjump.com · gorgias.chat · rechargecdn.com · thewishlist.io · 9gtb.com · useamp.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
- Framework
- Tailwind CSS
- E-commerce
- Shopify
- Analytics
- Microsoft Clarity
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 38 issues on circa.com.au, including 15 speed issues, 3 SEO issues 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.