Website review, no card needed
chocolatefreckles.com.au website review
Visit site (opens in a new tab)Reviewed 21 November 202627 issues · 78 checks
This review found 27 issues worth fixing on chocolatefreckles.com.au, 5 of them high impact, across 78 checks. The most urgent: 12 text elements with low contrast. 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
86B- #12,258 of 125,854 reviewed websitesbeats 87%
- #7,334 of 70,284 online storesbeats 85%
- #7,102 of 63,840 Shopify storesbeats 84%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Jul 11, 2026 | 915 ms |
| Jul 25, 2026 | 916 ms |
| Aug 1, 2026 | 921 ms |
| Aug 8, 2026 | 912 ms |
| Aug 15, 2026 | 991 ms |
| Aug 22, 2026 | 995 ms |
| Aug 29, 2026 | 954 ms |
| Sep 12, 2026 | 862 ms |
| Oct 31, 2026 | 929 ms |
| Nov 7, 2026 | 849 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Jul 11, 2026 | 74 ms |
| Jul 25, 2026 | 75 ms |
| Aug 1, 2026 | 79 ms |
| Aug 8, 2026 | 87 ms |
| Aug 15, 2026 | 91 ms |
| Aug 22, 2026 | 95 ms |
| Aug 29, 2026 | 96 ms |
| Oct 31, 2026 | 95 ms |
| Nov 7, 2026 | 96 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
How it loaded on a phone
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Reduce unused JavaScript
450 ms · 405 KiBAbout 405 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.
Improve image delivery
150 ms · 656 KiB20 images could be 656 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.
Render-blocking requests
500 ms3 files block the first paint until they finish downloading. Deferring or inlining them could save about 500 ms.
Shopify adds 148 ms
148 msShopify costs a phone 148 ms of main-thread work and 568 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.
1,563 HTML elements
The page has 1,563 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 (Shopify, Privy and squarecdn.com and others), adding 972 KiB and 267 ms of main-thread time.
Reduce unused CSS
150 ms · 25 KiBAbout 25 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.
Use efficient cache lifetimes
159 KiB8 files are served with short cache lifetimes, so returning visitors download them again (159 KiB).
1 long task on the main thread
1 long task block the main thread while loading, the longest for 61 ms. During a long task the page ignores taps.
Legacy JavaScript
27 KiBPolyfills for old browsers add 27 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.
Minify JavaScript
5 KiB5 KiB could be saved by minifying JavaScript.
3 checks passed
Mobile performance score: 90
90/100Your mobile performance score is 90. That is in Google's “good” band (90 and up).
Main-thread work: 1.1 s
A phone's processor spends 1.1 s on main-thread work while loading, 502 ms of it running JavaScript. That is comfortably low.
Server response: 7 ms
7 msYour server sent the HTML in 7 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 11.9 s
11.9 sThe page becomes fully interactive after 11.9 s. Good is under 3.8 s.
Tap response (INP) got 28% slower for real visitors
+28%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 74 ms to 96 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
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.
Largest content (LCP) held steady for real visitors
-3%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 0.9 s to 0.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Not enough real-visitor data yet
Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.
4 checks passed
Speed Index: 3.2 s
3.2 sVisually, the page fills in at 3.2 s (Speed Index), inside the 3.4 s “good” threshold.
First Contentful Paint: 1.1 s
1.1 sThe first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.028
0.028The layout barely moves while loading (CLS 0.028, good is under 0.1).
Total Blocking Time: 6 ms
6 msScripts block the page for only 6 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 3.5 MB in 199 requests
3.5 MBYour homepage downloads 3.5 MB in 199 requests on a phone: images 1.5 MB (24), scripts 1,004 KiB (61) and other files 876 KiB (104). Under 2 MB keeps phones on slow connections fast.
4 images in older formats
4 images (144 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.
About 1.0 g of CO₂ per visit
0.99 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.99 g of CO₂e: 118.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 load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
12 text elements with low contrast
12 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
5 tap targets too small
5 tap targets are too small or too close together to hit reliably with a finger.
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 (7 elements)
All page content should be contained by landmarks: 7 elements on the page fail this check, rated moderate by axe-core.
Document should not have more than one banner landmark (1 element)
Document should not have more than one banner landmark: 1 element on the page fails 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.
9 links without text
9 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.
ARIA role should be appropriate for the element (1 element)
ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 43 images in the HTML carry an alt attribute.
46 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 8 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Meta description is long (296 characters)
Your meta description is 296 characters; Google truncates after about 160, so the end of your pitch is cut.
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
One H1 headline
Your <h1> is empty.
248 internal links, 6 external
The homepage links to 248 pages on chocolatefreckles.com.au and 6 external pages.
6 checks passed
Title: 65 characters
Your title is a healthy 65 characters: “Chocolate Freckles | Children and Baby clothing and gift boutique”.
Canonical URL set
The canonical URL is https://www.chocolatefreckles.com.au/.
Structured data in place
Structured data found: 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://www.chocolatefreckles.com.au/sitemap.xml.
AI search readiness
4 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 sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (841 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.chocolatefreckles.com.au/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
8 pages without a meta description
https://www.chocolatefreckles.com.au/collections/acorn, https://www.chocolatefreckles.com.au/collections/alex-and-ant, https://www.chocolatefreckles.com.au/collections/bebe, https://www.chocolatefreckles.com.au/collections/golden-children, https://www.chocolatefreckles.com.au/collections/halcyon-nights and https://www.chocolatefreckles.com.au/collections/jamie-kay and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.
5 pages slow to respond
https://www.chocolatefreckles.com.au/collections/bebe, https://www.chocolatefreckles.com.au/collections/eve-girl, https://www.chocolatefreckles.com.au/collections/golden-children, https://www.chocolatefreckles.com.au/collections/halcyon-nights and https://www.chocolatefreckles.com.au/collections/jamie-kay took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 94 found) and read each the way a search engine does.
6 checks passed
Linked pages load
12 pages of 15 loaded without an error (the rest turned automated requests away).
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.
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 12 pages that loaded have a <title>.
Best practices
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 ()”.
2 checks passed
Tap targets are thumb-sized
29 of 35 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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 349 words of copy
The homepage carries about 349 words of visible text.
3 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP CRYWOLF SUMMER” and “SHOP OUR AWESOME HATS”.
13 calls to action
The homepage has 13 calls to action, for example “Why shop with us?”, “Buy a Gift Card” and “SHOP OUR AWESOME HATS”.
4 short forms
4 short forms (1 field at most) are right on the homepage.
Privacy and tracking
4 trackers load before any consent
4Before 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.
15 cookies set on arrival
15Opening the homepage sets 15 cookies, 1 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 chocolatefreckles.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 6 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Product Labels And Badges · Essential Post Purchase Upsell · privy.com · chimpstatic.com · nfcube.com · Swym Wishlist Plus
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
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 27 issues on chocolatefreckles.com.au, including 8 speed issues, 3 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.