refinedwithcaroline.com website review

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

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

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

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

5 third-party services load with your homepage (Shopify, Klaviyo and Google Fonts and others), adding 600 KiB and 237 ms of main-thread time.

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

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

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

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

29 KiB could be saved by minifying CSS.

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

Polyfills for old browsers add 19 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.

5 KiB JavaScript is shipped twice across bundles.

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.

Your largest element takes 4.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “An illustrated holiday market stall with a striped awning, …”.

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

The layout shifts by 0.182 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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 2.6 MB in 246 requests on a phone: images 996 KiB (41), other files 776 KiB (84) and scripts 552 KiB (78). Under 2 MB keeps phones on slow connections fast.

rwc-microchanneling-spa-banner-1760x640_1800x.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 rwc-microchanneling-spa-banner-1760x640_1800x.jpg at 1,760 px wide, shown at 390 px. Resized copies would save about 105 KiB.

1 image further down the page (38 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

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

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

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

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

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

The homepage links to 189 pages on refinedwithcaroline.com and 6 external pages.

https://refinedwithcaroline.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://refinedwithcaroline.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://refinedwithcaroline.com/collections/all, https://refinedwithcaroline.com/customer_authentication/redirect and https://refinedwithcaroline.com/policies/shipping-policy have no meta description, so Google writes the search snippet from whatever text it finds.

https://refinedwithcaroline.com/customer_authentication/redirect has no <h1> headline, so visitors and search engines get no clear main topic.

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

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

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 phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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.

The homepage carries about 704 words of visible text.

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