lilyarkwright.com website review

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

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

8 third-party services load with your homepage (chatra.io, getdeviceinf.com and Clarity and others), adding 1.1 MB and 1.2 s of main-thread time.

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

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

chatra.io costs a phone 388 ms of main-thread work and 331 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.

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

getdeviceinf.com costs a phone 316 ms of main-thread work and 174 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.

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

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

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

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

14 KiB JavaScript is shipped twice across bundles.

1 image could be 7 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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.

5 KiB could be saved by minifying CSS.

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

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

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

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

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

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

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

Book_a_Showroom_Appointment.webp weighs 608 KiB. On a phone connection a single image that size takes seconds.

Your homepage downloads 3.7 MB in 480 requests on a phone: scripts 1.2 MB (70), images 1.2 MB (137) and other files 1.1 MB (260). Under 2 MB keeps phones on slow connections fast.

2 images (672 KiB) are 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.04 g of CO₂e: 125.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

1 element hidden from screen readers can still receive keyboard focus.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.

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

The homepage links to 497 pages on lilyarkwright.com and 15 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

https://lilyarkwright.com/en-us and https://lilyarkwright.com/collections/lab-diamond all use the title “Lab Grown Diamond Engagement Rings | Lily Arkwright”. Search engines can't tell which page to show for a search, so each competes with the others.

Your homepage links to 4 pages by a URL that isn't their canonical one, for example https://lilyarkwright.com/pages/consultation, whose canonical is https://lilyarkwright.com/en-us/pages/consultation. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://lilyarkwright.com/collections/engagement-rings, https://lilyarkwright.com/collections/lab-diamond, https://lilyarkwright.com/en-us/collections/round-engagement-rings, https://lilyarkwright.com/en-us/collections/oval-engagement-rings, https://lilyarkwright.com/en-us/collections/radiant-engagement-rings and https://lilyarkwright.com/en-us/collections/elongated-cushion-engagement-rings and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://cdn.slpht.com/widget/stylesheets/slpht_d46b6d5c37697a9435ff484c42e1460f.css' from …”.

The homepage carries about 980 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Microsoft Clarity (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 18 cookies, 2 of them by other companies (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 30 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.