sweetbloomcoffee.com website review

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

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

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

About 75 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 380 ms faster on a phone.

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

5 third-party services load with your homepage (Shopify, Mailchimp and intuit.com and others), adding 187 KiB and 75 ms of main-thread time.

1 long task block the main thread while loading, the longest for 66 ms. During a long task the page ignores taps.

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.

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

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

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

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

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.1 s to 1.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 6.6 MB in 228 requests on a phone: images 5.2 MB (29), other files 832 KiB (110) and scripts 310 KiB (57). Under 2 MB keeps phones on slow connections fast.

gif3.gif weighs 5.4 MB. On a phone connection a single image that size takes seconds.

6 images (6.4 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.

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

6 images are downloaded at several times the size a phone draws them, for example 130598_8eff7b8a844d65b830c0d03f288db5bf_408e26a0-4947-4da6-8 at 390 px wide, shown at 94 px. Resized copies would save about 326 KiB.

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

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

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

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

12 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: 4 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.

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

Your title is only 18 characters: “Sweet Bloom Coffee”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 107 pages on sweetbloomcoffee.com and 4 external pages.

https://sweetbloomcoffee.com/pages/subscription, https://sweetbloomcoffee.com/collections/all, https://sweetbloomcoffee.com/pages/locations, https://sweetbloomcoffee.com/pages/wholesale, https://sweetbloomcoffee.com/collections/coffee-archives and https://sweetbloomcoffee.com/collections/apparel and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://sweetbloomcoffee.com/pages/subscription, https://sweetbloomcoffee.com/collections/coffee, https://sweetbloomcoffee.com/collections/all, https://sweetbloomcoffee.com/pages/locations, https://sweetbloomcoffee.com/pages/giving-back and https://sweetbloomcoffee.com/pages/about and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://sweetbloomcoffee.com/collections/all took over 3 s to send its HTML from our server.

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

Social proof on the homepage: 1 trust badge. 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.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage carries about 508 words of visible text.

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