cammie.com website review

52 images could be 2.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

7 third-party services load with your homepage (Klaviyo, jQuery CDN and Shopify and others), adding 11.5 MB and 178 ms of main-thread time.

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

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

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

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

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

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

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

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

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.

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

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

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

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

Your largest element takes 2.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We and our partners, including Shopify, use cookies and oth…”. Most of its time is element render delay (2.5 s).

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

Your homepage downloads 14.1 MB in 256 requests on a phone: media 9.5 MB (1), images 3.3 MB (99) and other files 623 KiB (62). Under 2 MB keeps phones on slow connections fast.

24 images are downloaded at several times the size a phone draws them, for example fair-orchid-bed.jpg at 1,000 px wide, shown at 281 px. Resized copies would save about 1.0 MB.

31 images further down the page (2.7 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

1 image (59 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 4.00 g of CO₂e: 479.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

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

Your title is 69 characters, so Google will cut it off around 60: “100% Organic Cotton Sheets, Custom Bedding Sets with 400 TC 40 Colors”.

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

12 links have no real href, so search engines can't follow them.

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

The homepage links to 84 pages on cammie.com and 12 external pages.

robots.txt blocks GPTBot, Google-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.

https://www.cammie.com/pages/twin-size-organic-cotton-bedding-ensemble/beach-house and https://www.cammie.com/pages/queen-size-organic-cotton-bedding-ensemble/golden-eye all use the title “Create Own Organic Cotton Bedding Ensemble with 11 Palettes and 40 Co…”. Search engines can't tell which page to show for a search, so each competes with the others.

Your homepage links to 3 pages by a URL that isn't their canonical one, for example https://www.cammie.com/pages/twin-size-organic-cotton-bedding-ensemble/beach-house, whose canonical is https://www.cammie.com/collections/twin-size-organic-cotton-bedding-ensemble/beach-house. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.cammie.com/pages/twin-size-organic-cotton-bedding-ensemble/beach-house, https://www.cammie.com/pages/twin-size-organic-cotton-sheets-set/boho-chic and https://www.cammie.com/pages/queen-size-organic-cotton-bedding-ensemble/golden-eye have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

40 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

The homepage carries about 579 words of visible text.

Before a visitor clicks anything, the page loads Klaviyo (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 14 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.