Website review, no card needed

beulahlondon.com logo

beulahlondon.com website review

Visit site (opens in a new tab)Reviewed 7 November 202646 issues · 93 checks

This review found 46 issues worth fixing on beulahlondon.com, 17 of them high impact, across 93 checks. The most urgent: page weight: 28.2 MB in 389 requests. 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
4.2 s1.6 sMay 16Oct 313.2 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.5 s
May 23, 20262.4 s
May 30, 20262.3 s
Jun 6, 20262.1 s
Jun 13, 20262.0 s
Jun 20, 20262.0 s
Jun 27, 20261.9 s
Jul 4, 20261.9 s
Jul 11, 20262.0 s
Jul 18, 20262.0 s
Jul 25, 20262.1 s
Aug 1, 20262.4 s
Aug 8, 20262.6 s
Aug 15, 20262.8 s
Aug 22, 20262.8 s
Aug 29, 20262.9 s
Sep 5, 20263.3 s
Sep 12, 20263.7 s
Sep 19, 20263.9 s
Sep 26, 20263.8 s
Oct 3, 20263.6 s
Oct 10, 20263.5 s
Oct 17, 20263.4 s
Oct 24, 20263.3 s
Oct 31, 20263.2 s
Real-visitor tap response (INP)75th percentile, phones
172 ms143 msMay 16Oct 31163 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026150 ms
May 23, 2026148 ms
May 30, 2026146 ms
Jun 6, 2026150 ms
Jun 13, 2026151 ms
Jun 20, 2026154 ms
Jun 27, 2026156 ms
Jul 4, 2026158 ms
Jul 11, 2026160 ms
Jul 18, 2026155 ms
Jul 25, 2026154 ms
Aug 1, 2026152 ms
Aug 8, 2026155 ms
Aug 15, 2026155 ms
Aug 22, 2026156 ms
Aug 29, 2026157 ms
Sep 5, 2026155 ms
Sep 12, 2026162 ms
Sep 19, 2026167 ms
Sep 26, 2026166 ms
Oct 3, 2026167 ms
Oct 10, 2026169 ms
Oct 17, 2026163 ms
Oct 24, 2026164 ms
Oct 31, 2026163 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 beulahlondon.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. beulahlondon.com at 0.6 s0.6 s
  2. beulahlondon.com at 1.3 s1.3 s
  3. beulahlondon.com at 1.9 s1.9 s
  4. beulahlondon.com at 2.5 s2.5 s
  5. beulahlondon.com at 3.1 s3.1 s
  6. beulahlondon.com at 3.8 s3.8 s
  7. beulahlondon.com at 4.4 s4.4 s
  8. beulahlondon.com at 5.0 s5.0 s

Speed

11 to fix57
  • Reduce unused JavaScript

    1.1 s · 1.0 MB

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

  • Render-blocking requests

    1.2 s

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

  • 5,244 HTML elements

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

  • Main-thread work: 4.2 s

    A phone's processor spends 4.2 s on main-thread work while loading, 1.7 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 (Shopify, amaicdn.com and Google CDN and others), adding 2.1 MB and 969 ms of main-thread time.

  • Mobile performance score: 57

    57/100

    Your mobile performance score is 57. Pages that score under 90 lose visitors before the first paint.

  • Use efficient cache lifetimes

    408 KiB

    27 files are served with short cache lifetimes, so returning visitors download them again (408 KiB).

  • Improve image delivery

    373 KiB

    14 images could be 373 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Shopify adds 316 ms

    316 ms

    Shopify costs a phone 316 ms of main-thread work and 423 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.

  • amaicdn.com adds 208 ms

    208 ms

    amaicdn.com costs a phone 208 ms of main-thread work and 401 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.

  • Google CDN adds 115 ms

    115 ms

    Google CDN costs a phone 115 ms of main-thread work and 416 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

    200 ms · 71 KiB

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

  • 9 long tasks on the main thread

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

  • Legacy JavaScript

    81 KiB

    Polyfills for old browsers add 81 KiB JavaScript that modern phones do not need.

  • Font display

    50 ms

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

  • Minify JavaScript

    21 KiB

    21 KiB could be saved by minifying JavaScript.

  • Duplicated JavaScript

    11 KiB

    11 KiB JavaScript is shipped twice across bundles.

  • 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 CSS

    2 KiB

    2 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 92 ms

    92 ms

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

Core Web Vitals

11 to fix67
  • 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.

  • Real-user LCP: 5.0 s

    5.0 s

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

  • Real-user FCP: 4.1 s

    4.1 s

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

  • Largest Contentful Paint: 8.6 s

    8.6 s

    Your largest element takes 8.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

  • Time to Interactive: 23.4 s

    23.4 s

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

  • Speed Index: 7.6 s

    7.6 s

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

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

    +32%

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

  • Real-user TTFB: 1.2 s

    1.2 s

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

  • Total Blocking Time: 376 ms

    376 ms

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

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

  • 1 image without width and height

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

  • Tap response (INP) got 10% slower for real visitors

    +10%

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

3 checks passed
  • Real-user INP: 192 ms

    192 ms

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

  • Real-user CLS: 0.01

    0.01

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

  • Cumulative Layout Shift: 0.001

    0.001

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

Images and page weight

1 to fix70
  • Page weight: 28.2 MB in 389 requests

    28.2 MB

    Your homepage downloads 28.2 MB in 389 requests on a phone: media 23.2 MB (3), scripts 2.3 MB (111) and other files 1.2 MB (202). Under 2 MB keeps phones on slow connections fast.

  • About 8.0 g of CO₂ per visit

    8.00 g

    By the Sustainable Web Design model, a visit to your homepage emits about 8.00 g of CO₂e: 959.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • 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

8 to fixGoogle 8891
  • 3 tap targets too small

    3 tap targets are too small or too close together to hit reliably with a finger.

  • 2 images without alt text

    2 images have no alt text, which hurts accessibility and image search.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (2 elements)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 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.

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

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

  • 50 links without text

    50 visible links have no text or label, so screen readers cannot say where they go.

  • 3 form fields without a label

    3 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

1 checks passed
  • 50 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 57 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 7 failed. 5 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 8588
  • Title is long (68 characters)

    Your title is 68 characters, so Google will cut it off around 60: “Beulah London | Fighting Slavery Through Fashion | Luxury Womenswear”.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 3 links with vague text

    3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 225 internal links, 7 external

    The homepage links to 225 pages on beulahlondon.com and 7 external pages.

6 checks passed
  • Meta description: 158 characters

    Your meta description is 158 characters: “Beulah London is a British fashion brand with a social mission. We design timeless, feminine clothes, providing employm…”.

  • One H1 headline

    Your main headline reads: “Beulah London”.

  • Canonical URL set

    The canonical URL is https://www.beulahlondon.com/.

  • Structured data in place

    Structured data found: BreadcrumbList, Organization and WebSite.

  • 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.beulahlondon.com/sitemap.xml.

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing logo, 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.

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.

  • Text is in the HTML

    Your server sends the page's text in the HTML (2,907 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

4 to fix53
  • 1 linked page is broken

    Your homepage links to https://www.beulahlondon.com/collections/dresses, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 1 page points its canonical at the homepage

    https://www.beulahlondon.com/home declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

  • 2 pages share a title

    / and https://www.beulahlondon.com/home all use the title “Beulah London | Fighting Slavery Through Fashion | Luxury Womenswear”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 1 page without a meta description

    https://www.beulahlondon.com/collections/beulah-x-anna-bromilow has no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages slow to respond

    https://www.beulahlondon.com/collections/shop-all and https://www.beulahlondon.com/collections/the-neutrals-edit took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

3 checks passed
  • 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 14 pages that loaded have a <title>.

Best practices

3 to fixGoogle 7785
  • 15 small tap targets

    15 of 58 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 (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).

  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix69
  • No call to action on the first screen

    On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

  • 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 708 words of copy

    The homepage carries about 708 words of visible text.

5 checks passed
  • 12 calls to action

    The homepage has 12 calls to action, for example “Shop the new autumn collection”, “Shop All” and “Shop The Catalogue”.

  • 5 short forms

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

  • Analytics in place

    Analytics detected: Google Tag Manager and Hotjar.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 1 email link.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

1 to fix
  • 7 trackers load before any consent

    7

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Klaviyo and 2 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.

  • 21 cookies set on arrival

    21

    Opening the homepage sets 21 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.

  • 56 other companies contacted

    Loading the homepage contacts 56 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 beulahlondon.com, 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 17 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Consentmo Gdpr · Klaviyo Email Marketing Sms · Gorgias Live Chat Helpdesk · Boost Ai Search Filter · Mlv Recently Viewed Products · Gempages Builder · Gdpr Backpack · Pre Order · Orbe Geolocation · Iwish · oxiapps.com · rakuten.com · rakutenadvertising.io · global-e.com · virtueimpact.com · 9gtb.com · amazonaws.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
jQuery
E-commerce
Shopify
Analytics
Google Tag Manager | Hotjar
Hosting
Shopify

Company

Founded
2011
Headquarters
London

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 beulahlondon.com, including 22 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

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