joandominique.com website review

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

Squarespace costs a phone 1.6 s of main-thread work and 1.4 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.

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

7 third-party services load with your homepage (Squarespace, Google Tag Manager and weglot.com and others), adding 2.8 MB and 1.9 s of main-thread time.

3 images could be 1,011 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

About 757 KiB of JavaScript is downloaded but never used on this page.

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

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

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

squarespace-cdn.com costs a phone 0 ms of main-thread work and 1.2 MB 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.

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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

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

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

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

Your largest element takes 2.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Now accepting private bridal appointments for 2027–2028.”.

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

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.

Screenshot+2026-04-21+at+5.25.35 PM.png weighs 606 KiB. On a phone connection a single image that size takes seconds.

Your homepage downloads 3.0 MB in 78 requests on a phone: scripts 1.5 MB (50), images 1.1 MB (5) and stylesheets 166 KiB (10). Under 2 MB keeps phones on slow connections fast.

Screenshot+2026-04-21+at+5.25.35 PM.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).

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

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

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

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

Structured data found (LocalBusiness, Organization and WebSite) but with 2 problems, for example “WebSite: image is not an absolute URL ("//images.squarespace-cdn.com/content/v1/660ad85f134e1556be4…”.

The homepage links to 38 pages on joandominique.com and 15 external pages.

Your Organization JSON-LD is missing name, url, logo and description. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

There is no https://www.joandominique.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

https://www.joandominique.com/wedding-gowns and https://www.joandominique.com/the-experience-1 all use the title “Bespoke Bridal — Joan Dominique Bridal & Beauty”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.joandominique.com/contact-us, https://www.joandominique.com/wedding-gowns, https://www.joandominique.com/new-blog and https://www.joandominique.com/the-experience-1 have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.joandominique.com/the-experience-1, whose canonical is https://www.joandominique.com/wedding-gowns. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.joandominique.com/contact-us, https://www.joandominique.com/wedding-gowns, https://www.joandominique.com/joan-dominique-beauty, https://www.joandominique.com/the-experience-1, https://www.joandominique.com/new-page-1 and https://www.joandominique.com/faqs and 4 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.joandominique.com/contact-us, https://www.joandominique.com/joan-dominique-beauty, https://www.joandominique.com/measurement and https://www.joandominique.com/privacy 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.

We fetched 11 pages linked from your homepage and read each the way a search engine does.

5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 401 ()”.

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 testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

The homepage has only about 139 words of visible text; thin pages give Google and first-time buyers little to go on.

There is no form on the homepage, so every lead has to click through to another page first.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

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

Opening the homepage sets 4 cookies (measured from a US location before any click).

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.

Loading the homepage contacts 12 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.