overnightflowerdelivery.com website review

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

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

8 third-party services load with your homepage (Google Tag Manager, FullStory and Clarity and others), adding 1.0 MB and 821 ms of main-thread time.

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

14 images could be 263 KiB 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.

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

Google Tag Manager costs a phone 531 ms of main-thread work and 516 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.

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

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

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

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.

4 KiB could be saved by minifying JavaScript.

Your largest element takes 11.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “autumn flower arrangement on fall decorated table”.

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

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

Scripts block taps and scrolling for 555 ms in total while the page loads. Good is under 200 ms.

The first text or image appears after 2.6 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.3 MB in 181 requests on a phone: scripts 892 KiB (54), images 703 KiB (20) and other files 632 KiB (73). Under 2 MB keeps phones on slow connections fast.

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

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

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

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

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

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

Headings skip levels (h2 → h4 and h1 → h3), which makes the page harder to scan with a screen reader.

Structured data found (LocalBusiness, Organization and WebSite) but with 3 problems, for example “LocalBusiness: logo is not an absolute URL ("//overnightflowerdelivery.com/cdn/shop/files/OVERNIGHT…”.

The homepage links to 119 pages on overnightflowerdelivery.com and 1 external page.

https://overnightflowerdelivery.com/pages/wedding-page has no <title>, so Google invents the link text in results.

https://overnightflowerdelivery.com/pages/wedding-page has no meta description, so Google writes the search snippet from whatever text it finds.

https://overnightflowerdelivery.com/pages/wedding-page has no <h1> headline, so visitors and search engines get no clear main topic.

https://overnightflowerdelivery.com/collections/thanksgivingus, https://overnightflowerdelivery.com/collections/autumn, https://overnightflowerdelivery.com/collections/hanukkah and https://overnightflowerdelivery.com/collections/birthday took over 3 s to send their HTML from our server.

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

1 error was logged to the browser console while the page loaded, for example “Could not resolve value for site ID”.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

Social proof on the homepage: 1 testimonial or review block. Pairing it with named testimonials or customer logos makes it far more convincing.

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

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

The homepage carries about 778 words of visible text.

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