kaceywelch.com website review

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

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

39 images could be 1.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.

8 third-party services load with your homepage (commoninja.com, Affirm and Klaviyo and others), adding 2.3 MB and 1.2 s of main-thread time.

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

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

commoninja.com costs a phone 449 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.

Affirm costs a phone 378 ms of main-thread work and 171 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.

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

Klaviyo costs a phone 255 ms of main-thread work and 426 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 265 ms. During a long task the page ignores taps.

Shopify costs a phone 62 ms of main-thread work and 345 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 58 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 210 ms faster on a phone.

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

10 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.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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.

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

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

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

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

Scripts block taps and scrolling for 374 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' largest content (lcp) went from 1.1 s to 1.2 s 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 6.1 MB in 302 requests on a phone: images 3.1 MB (60), scripts 1.9 MB (93) and other files 843 KiB (133). Under 2 MB keeps phones on slow connections fast.

15 images (1.6 MB) 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.

NewColorLaunch2026_HomepageBanner_Mobile__1500x1500_73ec3355 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).

7 images further down the page (319 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

6 elements hidden from screen readers can still receive keyboard focus.

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

9 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: 7 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.

Elements with visible text labels do not have matching accessible names. (3 elements).

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is only 22 characters: “The Kacey Welch Method”. Between 30 and 65 characters leaves room to say what you do and for whom.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

1 link has no real href, so search engines can't follow it.

The homepage links to 109 pages on kaceywelch.com and 18 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.

/ and https://kaceywelch.com/pages/the-kacey-welch-method all use the title “The Kacey Welch Method”. Search engines can't tell which page to show for a search, so each competes with the others.

https://kaceywelch.com/collections/all-products, https://kaceywelch.com/collections/silk-wefts, https://kaceywelch.com/collections/petite-silk-wefts, https://kaceywelch.com/collections/tape-ins, https://kaceywelch.com/collections/clipins and https://kaceywelch.com/collections/flat-tip-individuals and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://kaceywelch.com/pages/certified-artist-directory, https://kaceywelch.com/pages/education, https://kaceywelch.com/pages/the-kacey-welch-method and https://kaceywelch.com/pages/faq have no <h1> headline, so visitors and search engines get no clear main topic.

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

3 errors were logged to the browser console while the page loaded, for example “Refused to apply style from 'https://kaceywelch.com/cdn/shop/t/25/assets/tiny.content.min.css?v=4882' because its MIME …”.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

Social proof on the homepage: 1 testimonial or review block. 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.

The homepage carries about 300 words of visible text.

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