kimberbell.com website review

25 files are served with short cache lifetimes, so returning visitors download them again (1.0 MB).

9 images could be 792 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.8 s faster on a phone.

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

Your mobile performance score is 54 (desktop: 74). Pages that score under 90 lose visitors before the first paint.

8 third-party services load with your homepage (Facebook, Shopify and Hubspot and others), adding 1.8 MB and 701 ms of main-thread time.

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

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

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

Facebook costs a phone 303 ms of main-thread work and 288 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.

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

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

Attentive costs a phone 64 ms of main-thread work and 789 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 KiB could be saved by minifying JavaScript.

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

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

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

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

Your largest element takes 23.2 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 23.5 s. Good is under 3.8 s.

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

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

Over the last 25 four-week periods to 2026-10-17, 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).

Your homepage downloads 4.6 MB in 343 requests on a phone: images 2.0 MB (35), scripts 1.4 MB (128) and other files 876 KiB (157). Under 2 MB keeps phones on slow connections fast.

stitching-edited.png 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 stitching-edited.png at 2,000 px wide, shown at 390 px. Resized copies would save about 132 KiB.

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

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

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

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

The homepage links to 199 pages on kimberbell.com and 17 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://kimberbell.com/pages/coming-soon-for-shops and https://kimberbell.com/pages/tiny-hugs-initiative have no meta description, so Google writes the search snippet from whatever text it finds.

https://kimberbell.com/pages/coming-soon-for-shops and https://kimberbell.com/pages/kimberbell-me-collections have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

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

The page uses urgency cues (a countdown or limited-time wording).

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and Meta Pixel and 2 mores (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 24 cookies (measured from a US location before any click).

Loading the homepage contacts 40 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.