Website review, no card needed

beginningboutique.co.uk logo

beginningboutique.co.uk website review

Visit site (opens in a new tab)Reviewed 9 November 202645 issues · 97 checks

This review found 45 issues worth fixing on beginningboutique.co.uk, 14 of them high impact, across 97 checks. The most urgent: improve image delivery. 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
2.9 s1.9 sAug 22Nov 72.8 s
Show as table
DateReal-visitor load time (LCP)
Aug 22, 20262.3 s
Aug 29, 20262.3 s
Sep 5, 20262.3 s
Sep 12, 20262.3 s
Sep 19, 20262.3 s
Sep 26, 20262.2 s
Oct 3, 20262.1 s
Oct 10, 20262.0 s
Oct 17, 20262.2 s
Oct 24, 20262.4 s
Oct 31, 20262.7 s
Nov 7, 20262.8 s
Real-visitor tap response (INP)75th percentile, phones
679 ms376 msAug 22Nov 7411 ms
Show as table
DateReal-visitor tap response (INP)
Aug 22, 2026475 ms
Aug 29, 2026567 ms
Sep 5, 2026628 ms
Sep 12, 2026644 ms
Sep 19, 2026630 ms
Sep 26, 2026581 ms
Oct 3, 2026495 ms
Oct 10, 2026448 ms
Oct 17, 2026437 ms
Oct 24, 2026416 ms
Oct 31, 2026419 ms
Nov 7, 2026411 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 beginningboutique.co.uk (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. beginningboutique.co.uk at 1.1 s1.1 s
  2. beginningboutique.co.uk at 2.3 s2.3 s
  3. beginningboutique.co.uk at 3.4 s3.4 s
  4. beginningboutique.co.uk at 4.5 s4.5 s
  5. beginningboutique.co.uk at 5.7 s5.7 s
  6. beginningboutique.co.uk at 6.8 s6.8 s
  7. beginningboutique.co.uk at 7.9 s7.9 s
  8. beginningboutique.co.uk at 9.1 s9.1 s

Speed

14 to fix46
  • Improve image delivery

    3.1 s · 1.3 MB

    17 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.1 s faster on a phone.

  • Mobile performance score: 46

    46/100

    Your mobile performance score is 46. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Main-thread work: 6.7 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Yotpo and Facebook and others), adding 3.1 MB and 1.8 s of main-thread time.

  • Use efficient cache lifetimes

    500 ms · 1.2 MB

    50 files are served with short cache lifetimes, so returning visitors download them again (1.2 MB).

  • Reduce unused JavaScript

    460 ms · 1.1 MB

    About 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 460 ms faster on a phone.

  • Google Tag Manager adds 645 ms

    645 ms

    Google Tag Manager costs a phone 645 ms of main-thread work and 906 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

    430 ms · 146 KiB

    About 146 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 430 ms faster on a phone.

  • Render-blocking requests

    550 ms

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

  • Yotpo adds 292 ms

    292 ms

    Yotpo costs a phone 292 ms of main-thread work and 558 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.

  • 18 long tasks on the main thread

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

  • 2,413 HTML elements

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

  • Klaviyo adds 188 ms

    188 ms

    Klaviyo costs a phone 188 ms of main-thread work and 446 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 152 ms

    152 ms

    gotolstoy.com costs a phone 152 ms of main-thread work and 778 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.

  • Font display

    100 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).

  • Minify JavaScript

    60 KiB

    60 KiB could be saved by minifying JavaScript.

  • Legacy JavaScript

    57 KiB

    Polyfills for old browsers add 57 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 ms

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

Core Web Vitals

11 to fix33
  • 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: 16.7 s

    16.7 s

    Your largest element takes 16.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “UK Winter 9/11”.

  • Time to Interactive: 40.0 s

    40.0 s

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

  • Speed Index: 13.7 s

    13.7 s

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

  • Total Blocking Time: 681 ms

    681 ms

    Scripts block taps and scrolling for 681 ms in total while the page loads. Good is under 200 ms.

  • Real-user LCP: 2.8 s

    2.8 s

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

  • Real-user INP: 260 ms

    260 ms

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

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

    +21%

    Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 2.3 s to 2.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Real-user FCP: 2.5 s

    2.5 s

    Real visitors see the first content after 2.5 s (75th percentile). Good is under 1.8 s.

  • First Contentful Paint: 2.2 s

    2.2 s

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

  • 7 images without width and height

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

4 checks passed
  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Real-user TTFB: 431 ms

    431 ms

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

  • Tap response (INP) got 20% faster for real visitors

    -20%

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

2 to fix50
  • Page weight: 7.9 MB in 424 requests

    7.9 MB

    Your homepage downloads 7.9 MB in 424 requests on a phone: scripts 3.2 MB (157), images 2.8 MB (46) and other files 1.1 MB (173). Under 2 MB keeps phones on slow connections fast.

  • 8 images far larger than shown

    589 KiB

    8 images are downloaded at several times the size a phone draws them, for example Emiko-Silver-Sequin-Mini-Skirt-3_866af063-0f93-4b92-ad9a-46b at 750 px wide, shown at 100 px. Resized copies would save about 589 KiB.

  • 1 image in older formats

    1 image (167 KiB) is 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.2 g of CO₂ per visit

    2.24 g

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

9 to fixGoogle 8589
  • 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.

  • 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. (1 element).

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

2 to fixGoogle 10091
  • Meta description is long (298 characters)

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

  • Structured data has 1 problem

    Structured data found (Organization, WebPage and WebSite) but with 1 problem, for example “Organization: url points at a different host (https://www.beginningboutique.com.au)”.

  • 353 internal links, 20 external

    The homepage links to 353 pages on beginningboutique.co.uk and 20 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “Beginning Boutique | Australia's Best Dresses, Tops & Bottoms.”.

  • Title: 63 characters

    Your title is a healthy 63 characters: “Beginning Boutique | The Best Dresses, Tops & Bottoms Online AU”.

  • Canonical URL set

    The canonical URL is https://www.beginningboutique.co.uk/.

  • 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.co.uk/sitemap.xml.

AI search readiness

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

  • llms.txt published

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

Other pages

1 to fix95
  • 15 pages without an H1

    https://www.beginningboutique.co.uk/collections/best-sellers, https://www.beginningboutique.co.uk/collections/sale, https://www.beginningboutique.co.uk/products/beginning-hibiscus-bow-air-freshener, https://www.beginningboutique.co.uk/products/coconut-and-pineapple-body-cream, https://www.beginningboutique.co.uk/pages/afterpay and https://www.beginningboutique.co.uk/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.co.uk/collections/best-sellers, https://www.beginningboutique.co.uk/collections/sale, https://www.beginningboutique.co.uk/collections/back-in-stock-styles, https://www.beginningboutique.co.uk/collections/best-sellers-new-colours, https://www.beginningboutique.co.uk/collections/prom-dresses and https://www.beginningboutique.co.uk/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.

  • 1 page slow to respond

    https://www.beginningboutique.co.uk/collections/blue-formal-dresses took over 3 s to send its HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 140 found) and read each the way a search engine does.

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

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • 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

3 to fixGoogle 7776
  • 1 broken image

    1 image failed to load on a phone, for example https://www.beginningboutique.co.uk/.

  • 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 “missing ) after argument list”.

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

2 to fix89
  • 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 687 words of copy

    The homepage carries about 687 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”.

  • 31 calls to action

    The homepage has 31 calls to action, for example “Shop All New”, “Pre Order Styles” and “Shop All Prom Dresses”.

  • 3 short forms

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

  • Analytics in place

    Analytics detected: Google Analytics and 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

1 to fix
  • 9 trackers load before any consent

    9

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

  • 38 cookies set on arrival

    38

    Opening the homepage sets 38 cookies, 2 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.

  • 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.co.uk, 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

Triplewhale · Gorgias Live Chat Helpdesk · Yotpo Loyalty Rewards · Elevar Conversion Tracking · Klaviyo Email Marketing Sms · Tolstoy · Yotpo Product Reviews · Tapcart Mobile App · Geoip Country Redirect · Loop Returns · googleapis.com · auspost-collect-app.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
Analytics
Google 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 45 issues on beginningboutique.co.uk, including 25 speed issues, 2 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

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