Website review, no card needed
beginningboutique.com.au website review
Visit site (opens in a new tab)Reviewed 20 October 202646 issues · 99 checks
This review found 46 issues worth fixing on beginningboutique.com.au, 15 of them high impact, across 99 checks. The most urgent: improve image delivery. 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
76C- #75,445 of 124,378 reviewed websitesbeats 35%
- #48,296 of 69,874 online storesbeats 26%
- #45,740 of 63,538 Shopify storesbeats 23%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 2.2 s |
| May 16, 2026 | 2.2 s |
| May 23, 2026 | 2.1 s |
| May 30, 2026 | 1.9 s |
| Jun 6, 2026 | 1.9 s |
| Jun 13, 2026 | 1.9 s |
| Jun 20, 2026 | 1.8 s |
| Jun 27, 2026 | 1.8 s |
| Jul 4, 2026 | 1.8 s |
| Jul 11, 2026 | 1.8 s |
| Jul 18, 2026 | 1.9 s |
| Jul 25, 2026 | 1.9 s |
| Aug 1, 2026 | 1.9 s |
| Aug 8, 2026 | 1.8 s |
| Aug 15, 2026 | 1.8 s |
| Aug 22, 2026 | 2.1 s |
| Aug 29, 2026 | 2.2 s |
| Sep 5, 2026 | 2.5 s |
| Sep 12, 2026 | 2.6 s |
| Sep 19, 2026 | 2.5 s |
| Sep 26, 2026 | 2.5 s |
| Oct 3, 2026 | 2.2 s |
| Oct 10, 2026 | 2.1 s |
| Oct 17, 2026 | 2.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 269 ms |
| May 16, 2026 | 252 ms |
| May 23, 2026 | 246 ms |
| May 30, 2026 | 238 ms |
| Jun 6, 2026 | 241 ms |
| Jun 13, 2026 | 238 ms |
| Jun 20, 2026 | 237 ms |
| Jun 27, 2026 | 240 ms |
| Jul 4, 2026 | 241 ms |
| Jul 11, 2026 | 240 ms |
| Jul 18, 2026 | 245 ms |
| Jul 25, 2026 | 246 ms |
| Aug 1, 2026 | 263 ms |
| Aug 8, 2026 | 279 ms |
| Aug 15, 2026 | 304 ms |
| Aug 22, 2026 | 335 ms |
| Aug 29, 2026 | 337 ms |
| Sep 5, 2026 | 369 ms |
| Sep 12, 2026 | 385 ms |
| Sep 19, 2026 | 362 ms |
| Sep 26, 2026 | 354 ms |
| Oct 3, 2026 | 335 ms |
| Oct 10, 2026 | 321 ms |
| Oct 17, 2026 | 336 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
1.2 s
2.3 s
3.5 s
4.7 s
5.8 s
7.0 s
8.2 s
9.3 s
Speed
Improve image delivery
3.9 s · 1.3 MB18 images could be 1.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.9 s faster on a phone.
Main-thread work: 11.0 s
A phone's processor spends 11.0 s on main-thread work while loading, 7.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 38
38/100Your mobile performance score is 38 (desktop: 57). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Yotpo and Klaviyo and others), adding 3.2 MB and 2.6 s of main-thread time.
Use efficient cache lifetimes
400 ms · 1.4 MB54 files are served with short cache lifetimes, so returning visitors download them again (1.4 MB).
Reduce unused JavaScript
150 ms · 1.3 MBAbout 1.3 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.
Render-blocking requests
850 ms8 files block the first paint until they finish downloading. Deferring or inlining them could save about 850 ms.
Google Tag Manager adds 704 ms
704 msGoogle Tag Manager costs a phone 704 ms of main-thread work and 712 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.
Reduce unused CSS
450 ms · 146 KiBAbout 146 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.
Yotpo adds 467 ms
467 msYotpo costs a phone 467 ms of main-thread work and 767 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 408 ms
408 msKlaviyo costs a phone 408 ms of main-thread work and 452 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.
gotolstoy.com adds 336 ms
336 msgotolstoy.com costs a phone 336 ms of main-thread work and 836 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 335 ms. During a long task the page ignores taps.
Facebook adds 291 ms
291 msFacebook costs a phone 291 ms of main-thread work and 280 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.
2,421 HTML elements
The page has 2,421 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Minify JavaScript
150 ms · 60 KiB60 KiB could be saved by minifying JavaScript.
Font display
100 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).
Legacy JavaScript
72 KiBPolyfills for old browsers add 72 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.
1 checks passed
Server response: 20 ms
20 msYour server sent the HTML in 20 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.
Largest Contentful Paint: 14.0 s
14.0 sYour largest element takes 14.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “AU New 19/10”.
Time to Interactive: 43.5 s
43.5 sThe page becomes fully interactive after 43.5 s. Good is under 3.8 s.
Speed Index: 14.1 s
14.1 sVisually, the page fills in at 14.1 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.5 s
3.5 sThe first text or image appears after 3.5 s on a phone. Good is under 1.8 s.
Total Blocking Time: 853 ms
853 msScripts block taps and scrolling for 853 ms in total while the page loads. Good is under 200 ms.
Real-user INP: 207 ms
207 msReal visitors wait 207 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 26% slower for real visitors
+26%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 269 ms to 336 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 2.0 s
2.0 sReal visitors see the first content after 2.0 s (75th percentile). Good is under 1.8 s.
5 images without width and height
5 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
-4%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.2 s to 2.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user LCP: 2.3 s
2.3 sReal visitors wait 2.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.02
0.02For real visitors the layout shifts by 0.02 (75th percentile). Good is under 0.1.
Real-user TTFB: 660 ms
660 msReal visitors wait 660 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.053
0.053The layout barely moves while loading (CLS 0.053, good is under 0.1).
Images and page weight
Page weight: 8.1 MB in 395 requests
8.1 MBYour homepage downloads 8.1 MB in 395 requests on a phone: scripts 3.4 MB (170), images 2.9 MB (46) and other files 957 KiB (131). Under 2 MB keeps phones on slow connections fast.
7 images far larger than shown
572 KiB7 images are downloaded at several times the size a phone draws them, for example Maiah-Yellow-Bloom-Maxi-Dress-1.jpg at 750 px wide, shown at 100 px. Resized copies would save about 572 KiB.
2 images in older formats
2 images (431 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 2.3 g of CO₂ per visit
2.28 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.28 g of CO₂e: 274.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
5 tap targets too small
5 tap targets are too small or too close together to hit reliably with a finger.
Elements must only use permitted ARIA attributes (1 element)
Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.
All page content should be contained by landmarks (5 elements)
All page content should be contained by landmarks: 5 elements on the page fail this check, rated moderate by axe-core.
Heading levels should only increase by one (1 element)
Heading levels should only increase by one: 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.
Hidden but focusable
25 elements hidden from screen readers can still receive keyboard focus.
3 text elements with low contrast
3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
ARIA role should be appropriate for the element (2 elements)
ARIA role should be appropriate for the element: 2 elements on the page fail this check, rated minor by axe-core.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (2 elements).
2 checks passed
Every image has alt text
All 47 images in the HTML carry an alt attribute.
45 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: 45 passed and 8 failed. 5 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 (306 characters)
Your meta description is 306 characters; Google truncates after about 160, so the end of your pitch is cut.
343 internal links, 19 external
The homepage links to 343 pages on beginningboutique.com.au and 19 external pages.
7 checks passed
One H1 headline
Your main headline reads: “Beginning Boutique | Australia's Best Dresses, Tops & Bottoms.”.
Title: 65 characters
Your title is a healthy 65 characters: “Beginning Boutique | Australia's Best Dresses, Tops & Bottoms. AU”.
Canonical URL set
The canonical URL is https://www.beginningboutique.com.au/.
Structured data in place
Structured data found: Organization, WebPage 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.beginningboutique.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: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (1,086 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.beginningboutique.com.au/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a meta description
https://www.beginningboutique.com.au/collections/beginning-boutique-x-mia-oglesby has no meta description, so Google writes the search snippet from whatever text it finds.
15 pages without an H1
https://www.beginningboutique.com.au/collections/best-sellers, https://www.beginningboutique.com.au/collections/sale, https://www.beginningboutique.com.au/products/cherry-pink-keyring, https://www.beginningboutique.com.au/products/teddy-bear-tumbler-cup, https://www.beginningboutique.com.au/pages/afterpay and https://www.beginningboutique.com.au/pages/shipping-information and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.
9 pages with very little text
https://www.beginningboutique.com.au/collections/best-sellers, https://www.beginningboutique.com.au/collections/sale, https://www.beginningboutique.com.au/collections/back-in-stock-styles, https://www.beginningboutique.com.au/collections/best-sellers-new-colours, https://www.beginningboutique.com.au/collections/formal-dresses and https://www.beginningboutique.com.au/collections/pink-formal-dresses and 3 others have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
3 pages slow to respond
https://www.beginningboutique.com.au/collections/pink-formal-dresses, https://www.beginningboutique.com.au/collections/yellow-formal-dresses and https://www.beginningboutique.com.au/collections/red-formal-dresses took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 135 found) and read each the way a search engine does.
5 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.
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
1 broken image
1 image failed to load on a phone, for example https://www.beginningboutique.com.au/.
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.”).
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_CONNECTION_RESET”.
2 checks passed
Tap targets are thumb-sized
50 of 59 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.
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.
About 669 words of copy
The homepage carries about 669 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
7 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SPRING SHOP”.
32 calls to action
The homepage has 32 calls to action, for example “Shop All New”, “Pre Order Styles” and “Shop All Formal Dresses”.
3 short forms
3 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Microsoft Clarity.
Direct contact links
Visitors can reach you directly: 1 phone link and 0 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
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
9 trackers load before any consent
9Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 4 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.
34 cookies set on arrival
34Opening the homepage sets 34 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.
63 other companies contacted
Loading the homepage contacts 63 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 beginningboutique.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
- E-commerce
- Shopify
- Analytics
- Microsoft Clarity
Company
- Founded
- 2008
- Headquarters
- Brisbane
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 46 issues on beginningboutique.com.au, including 25 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.