graceandlace.com website review

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

About 908 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.4 s faster on a phone.

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

8 third-party services load with your homepage (Klaviyo, heyamplify.com and Shopify and others), adding 2.7 MB and 525 ms of main-thread time.

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

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

pickystory.com costs a phone 67 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.

Klaviyo costs a phone 127 ms of main-thread work and 353 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.

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

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

6 images could be 236 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

About 171 KiB of CSS is downloaded but never applied on this page.

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

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

15 KiB could be saved by minifying CSS.

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

Your largest element takes 21.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Four women modeling graphic holiday graphic tees in a studi…”.

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

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

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

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

Your homepage downloads 5.5 MB in 396 requests on a phone: scripts 2.6 MB (149), images 1.1 MB (38) and other files 1.1 MB (161). Under 2 MB keeps phones on slow connections fast.

GL_-_Slider_-_Mobile_-_November_Graphic_Tees.jpg 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 is downloaded at several times the size a phone draws it, for example 7318c6d5-aba8-4196-a8b7-40196cd30152.png at 4,500 px wide, shown at 141 px. Resized copies would save about 160 KiB.

1 image (162 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.

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

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

Some list items are not inside a list.

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

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.

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 on the page fails this check, rated moderate by axe-core.

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

Alternative text of images should not be repeated as text: 6 elements on the page fail this check, rated minor by axe-core.

ARIA role should be appropriate for the element: 5 elements on the page fail this check, rated minor by axe-core.

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

Your title is only 14 characters: “Grace and Lace”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

Your <h1> is empty.

The homepage links to 176 pages on graceandlace.com and 13 external pages.

https://www.graceandlace.com/policies/shipping-policy and https://www.graceandlace.com/pages/shop-the-look have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.graceandlace.com/collections/all and https://www.graceandlace.com/pages/shop-the-look have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 image failed to load on a phone, for example https://www.graceandlace.com/cdn/shop/files/kelly-green_60x.jpg?v=182110.

13 of 34 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

5 errors were logged to the browser console while the page loaded, for example “$ is not defined”.

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 phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

The homepage carries about 440 words of visible text.

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

Opening the homepage sets 25 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 50 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.