flowersbywebster.com website review

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

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

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

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

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

6 third-party services load with your homepage (pop-convert.com, Shopify and supergiftoptions.com and others), adding 687 KiB and 110 ms of main-thread time.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

2 KiB could be saved by minifying JavaScript.

Your largest element takes 6.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

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

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

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

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.5 MB in 284 requests on a phone: other files 1.0 MB (172), images 714 KiB (15) and scripts 358 KiB (59). Under 2 MB keeps phones on slow connections fast.

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

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

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

All page content should be contained by landmarks: 4 elements on the page fail this check, rated moderate by axe-core.

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

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

Your <h1> is empty.

The homepage links to 99 pages on flowersbywebster.com and 7 external pages.

https://flowersbywebster.com/collections/all, https://flowersbywebster.com/collections/floral-arrangements-non-holiday, https://flowersbywebster.com/collections/silk-flower-wreaths, https://flowersbywebster.com/collections/art-supplies, https://flowersbywebster.com/collections/greeting-cards-1 and https://flowersbywebster.com/collections/birthday-gifts and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://flowersbywebster.com/pages/sympathy, https://flowersbywebster.com/pages/weddings-baby-showers and https://flowersbywebster.com/pages/contact have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

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 ()”.

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

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

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

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

The homepage shows no opening hours. If customers visit or call, show when.

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

Opening the homepage sets 6 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 11 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.