Website review, no card needed

graceloveslace.eu logo

graceloveslace.eu website review

Visit site (opens in a new tab)Reviewed 5 November 202642 issues · 94 checks

This review found 42 issues worth fixing on graceloveslace.eu, 16 of them high impact, across 94 checks. The most urgent: reduce unused JavaScript. 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.2 s1.9 sMay 16Oct 312.0 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.1 s
May 23, 20262.1 s
May 30, 20262.2 s
Jun 6, 20262.2 s
Jun 13, 20262.2 s
Jun 20, 20262.1 s
Jun 27, 20262.0 s
Jul 4, 20262.0 s
Jul 11, 20262.0 s
Jul 18, 20262.1 s
Jul 25, 20262.0 s
Aug 1, 20262.1 s
Aug 8, 20262.1 s
Aug 15, 20262.0 s
Aug 22, 20262.1 s
Aug 29, 20262.0 s
Sep 5, 20262.1 s
Sep 12, 20262.1 s
Sep 19, 20262.0 s
Sep 26, 20262.0 s
Oct 3, 20262.0 s
Oct 10, 20262.0 s
Oct 17, 20262.1 s
Oct 24, 20262.0 s
Oct 31, 20262.0 s
Real-visitor tap response (INP)75th percentile, phones
162 ms119 msMay 16Oct 31150 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026137 ms
May 23, 2026130 ms
May 30, 2026135 ms
Jun 6, 2026140 ms
Jun 13, 2026136 ms
Jun 20, 2026140 ms
Jun 27, 2026137 ms
Jul 4, 2026136 ms
Jul 11, 2026136 ms
Jul 18, 2026135 ms
Jul 25, 2026133 ms
Aug 1, 2026132 ms
Aug 8, 2026130 ms
Aug 15, 2026129 ms
Aug 22, 2026124 ms
Aug 29, 2026126 ms
Sep 5, 2026126 ms
Sep 12, 2026126 ms
Sep 19, 2026133 ms
Sep 26, 2026138 ms
Oct 3, 2026148 ms
Oct 10, 2026150 ms
Oct 17, 2026157 ms
Oct 24, 2026153 ms
Oct 31, 2026150 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 graceloveslace.eu (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. graceloveslace.eu at 0.4 s0.4 s
  2. graceloveslace.eu at 0.9 s0.9 s
  3. graceloveslace.eu at 1.3 s1.3 s
  4. graceloveslace.eu at 1.7 s1.7 s
  5. graceloveslace.eu at 2.2 s2.2 s
  6. graceloveslace.eu at 2.6 s2.6 s
  7. graceloveslace.eu at 3.0 s3.0 s
  8. graceloveslace.eu at 3.5 s3.5 s

Speed

12 to fix40
  • Reduce unused JavaScript

    1.4 s · 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 1.4 s faster on a phone.

  • Use efficient cache lifetimes

    1.2 s · 799 KiB

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

  • Google Tag Manager adds 1.5 s

    1.5 s

    Google Tag Manager costs a phone 1.5 s of main-thread work and 1.0 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Mobile performance score: 40

    40/100

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

  • Main-thread work: 7.0 s

    A phone's processor spends 7.0 s on main-thread work while loading, 3.8 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, Stripe and Shopify and others), adding 2.4 MB and 2.6 s of main-thread time.

  • Render-blocking requests

    750 ms

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

  • Reduce unused CSS

    420 ms · 82 KiB

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

  • 20 long tasks on the main thread

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

  • Shopify adds 302 ms

    302 ms

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

  • Stripe adds 312 ms

    312 ms

    Stripe costs a phone 312 ms of main-thread work and 284 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.

  • Improve image delivery

    255 KiB

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

  • Duplicated JavaScript

    150 ms · 8 KiB

    8 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 150 ms faster on a phone.

  • Legacy JavaScript

    40 KiB

    Polyfills for old browsers add 40 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.

  • Minify JavaScript

    2 KiB

    2 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 18 ms

    18 ms

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

Core Web Vitals

5 to fix100
  • Largest Contentful Paint: 9.6 s

    9.6 s

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

  • Time to Interactive: 27.2 s

    27.2 s

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

  • Total Blocking Time: 2.2 s

    2.2 s

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

  • Speed Index: 6.7 s

    6.7 s

    Visually, the page fills in at 6.7 s (Speed Index). Good is under 3.4 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 13% slower for real visitors

    +13%

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

  • Largest content (LCP) held steady for real visitors

    -4%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.1 s to 2.0 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: 2.0 s

    2.0 s

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

  • Real-user INP: 152 ms

    152 ms

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

  • Real-user CLS: 0.07

    0.07

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

  • Real-user FCP: 1.1 s

    1.1 s

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

  • Real-user TTFB: 434 ms

    434 ms

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

  • First Contentful Paint: 1.4 s

    1.4 s

    The first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0.006

    0.006

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

Images and page weight

3 to fix60
  • Page weight: 4.8 MB in 304 requests

    4.8 MB

    Your homepage downloads 4.8 MB in 304 requests on a phone: scripts 2.7 MB (101), other files 1.1 MB (157) and images 689 KiB (22). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    gll-logo-mobile.png 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).

  • 1 image far larger than shown

    141 KiB

    1 image is downloaded at several times the size a phone draws it, for example grace-loves-lace-pr-quotes-banner-mobile.jpg at 4,500 px wide, shown at 390 px. Resized copies would save about 141 KiB.

  • 1 image below the first screen load straight away

    1 image further down the page (151 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 1.4 g of CO₂ per visit

    1.37 g

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

9 to fixGoogle 8089
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • 17 tap targets too small

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

  • 4 text elements with low contrast

    4 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 31 images without alt text

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

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

  • 2 form fields without a label

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

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • Elements marked as presentational should be consistently ignored (6 elements)

    Elements marked as presentational should be consistently ignored: 6 elements on the page fail this check, rated minor by axe-core.

  • Headings should not be empty (3 elements)

    Headings should not be empty: 3 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

    Headings skip levels (h2 → h4 and h3 → h6), which makes the page harder to scan with a screen reader.

  • 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
  • 48 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: 48 passed and 9 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 8594
  • Structured data has 2 problems

    Structured data found (ClothingStore, Organization and WebSite) but with 2 problems, for example “Organization: logo is not an absolute URL ("//graceloveslace.eu/cdn/shop/t/93/assets/gll-logo.png?v…”.

  • 10 links with vague text

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

  • 301 internal links, 6 external

    The homepage links to 301 pages on graceloveslace.eu and 6 external pages.

7 checks passed
  • Meta description: 146 characters

    Your meta description is 146 characters: “Grace Loves Lace specialises in luxurious, comfortable & sustainable wedding dresses. Shop bridal gowns online with glo…”.

  • One H1 headline

    Your main headline reads: “Explore the Range”.

  • Title: 63 characters

    Your title is a healthy 63 characters: “Bridal Boutique | Ethical Wedding Dresses – Grace Loves Lace EU”.

  • Canonical URL set

    The canonical URL is https://graceloveslace.eu/.

  • 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://graceloveslace.eu/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 (812 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

5 to fix63
  • 1 page without a title

    https://graceloveslace.eu/customer_authentication/redirect has no <title>, so Google invents the link text in results.

  • 1 linked page hidden from search

    https://graceloveslace.eu/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://graceloveslace.eu/customer_authentication/redirect has no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://graceloveslace.eu/pages/swym-wishlist, whose canonical is https://graceloveslace.eu/pages/wishlist. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 6 pages without an H1

    https://graceloveslace.eu/collections/wedding-dresses, https://graceloveslace.eu/collections/new-arrivals, https://graceloveslace.eu/collections/bridesmaids-occasionwear, https://graceloveslace.eu/customer_authentication/redirect, https://graceloveslace.eu/pages/swym-wishlist and https://graceloveslace.eu/collections/bridal-party have no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages slow to respond

    https://graceloveslace.eu/collections/accessories and https://graceloveslace.eu/collections/bridesmaids-occasionwear took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

2 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Titles are unique

    Every page we checked has its own title.

Best practices

1 to fixGoogle 9693
  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Cannot redefine property: playing Object.defineProperty (<anonymous>)”.

2 checks passed
  • Tap targets are thumb-sized

    30 of 37 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix72
  • 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 phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

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

    The homepage carries about 493 words of visible text.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Learn more” and “SHOP WEDDING DRESSES”.

  • 24 calls to action

    The homepage has 24 calls to action, for example “Shop Bridal Party”, “Shop Now” and “SHOP ALL”.

  • 6 short forms

    6 short forms (3 fields at most) are right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Microsoft Clarity.

  • Opening hours shown

    Your opening hours are on the homepage.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

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

  • 25 cookies set on arrival

    25

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

  • 40 other companies contacted

    Loading the homepage contacts 40 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 graceloveslace.eu, 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 10 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Pandectes Gdpr · Triplewhale · Klaviyo Email Marketing Sms · Reamaze Live Chat Helpdesk · Gdpr Cookie Consent · Apo Product Options · Swym Wishlist Plus · mageworx.com · weglot.com · nfcube.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
Hosting
Shopify

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 42 issues on graceloveslace.eu, including 17 speed issues, 2 SEO issues and 4 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