jewelrybygresham.com website review

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

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

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

8 third-party services load with your homepage (Shopify, Heroku and mycustomizer.com and others), adding 714 KiB and 548 ms of main-thread time.

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

Shopify costs a phone 240 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.

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

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

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

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

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

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

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

28 KiB JavaScript is shipped twice across bundles.

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.

3 KiB could be saved by minifying JavaScript.

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

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

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

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

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

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.

Your homepage downloads 3.0 MB in 406 requests on a phone: scripts 934 KiB (185), other files 924 KiB (166) and images 734 KiB (29). Under 2 MB keeps phones on slow connections fast.

Gresham-Mulberry-Mobile-1600x2000.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).

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

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

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

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

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

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

Your title is only 15 characters: “Gresham Jewelry”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

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

Your <h1> is empty.

The homepage links to 287 pages on jewelrybygresham.com and 3 external pages.

https://jewelrybygresham.com/collections/all-bracelets, https://jewelrybygresham.com/collections/all-earrings, https://jewelrybygresham.com/collections/all-necklaces, https://jewelrybygresham.com/collections/all-silicone, https://jewelrybygresham.com/collections/gj-accessories and https://jewelrybygresham.com/collections/bags and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://jewelrybygresham.com/collections/all-bracelets, https://jewelrybygresham.com/collections/pendants-charms, https://jewelrybygresham.com/collections/all-earrings, https://jewelrybygresham.com/collections/all-necklaces, https://jewelrybygresham.com/collections/all-silicone and https://jewelrybygresham.com/collections/gj-accessories have no <h1> headline, so visitors and search engines get no clear main topic.

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

Social proof on the homepage: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

Your longest form asks for 37 fields (0 required). Every extra field lowers completion.

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 683 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Pinterest Tag (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 14 cookies, 1 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 26 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.