1800flowers.com website review

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

Amplitude Mobile Analytics costs a phone 1.8 s of main-thread work and 144 KiB of downloads while your page loads. That alone is enough to make taps feel slow. 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 14.7 s on main-thread work while loading, 10.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

Google Tag Manager costs a phone 1.4 s of main-thread work and 843 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

Your mobile performance score is 28. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

8 third-party services load with your homepage (Amplitude Mobile Analytics, Google Tag Manager and Facebook and others), adding 1.7 MB and 4.0 s of main-thread time.

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

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

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

Polyfills for old browsers add 232 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.

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

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

34 KiB JavaScript is shipped twice across bundles.

17 KiB could be saved by minifying JavaScript.

About 10 KiB of CSS is downloaded but never applied on this page.

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

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

Real visitors wait 594 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

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

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

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

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

For real visitors the layout shifts by 0.22 (75th percentile). Good is under 0.1.

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

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

Your homepage downloads 6.8 MB in 355 requests on a phone: scripts 5.2 MB (138), images 785 KiB (61) and fonts 400 KiB (8). Under 2 MB keeps phones on slow connections fast.

1 image (34 KiB) is 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.

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

1 button has no accessible name, so screen readers announce just “button”.

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

Users should be able to zoom and scale the text up to 500%: 1 element on the page fails this check, rated minor by axe-core.

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is 66 characters, so Google will cut it off around 60: “Flowers, Flower Delivery, Fresh Flowers Online – 1-800-Flowers.com”.

Structured data found (Organization and WebSite) but with 1 problem, for example “WebSite: missing name”.

4 links have no real href, so search engines can't follow them.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 22 pages on 1800flowers.com and 1 external page.

Your robots.txt lets ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Claude search (Claude-SearchBot), Claude (Claude-User), Perplexity (PerplexityBot) and Perplexity (Perplexity-User) read the homepage but closes other sections to them, so answers about those pages can't cite you.

/bestsellingflowers, /birthday-flowers-10359, /Sympathy, /all-flower-arrangements, /plants and /flowers-same-day-delivery and 6 others have no <title>, so Google invents the link text in results.

/bestsellingflowers, /birthday-flowers-10359, /Sympathy, /all-flower-arrangements, /plants and /flowers-same-day-delivery and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.

/bestsellingflowers, /birthday-flowers-10359, /Sympathy, /occasions, /all-flower-arrangements and /plants and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

/bestsellingflowers, /birthday-flowers-10359, /Sympathy, /all-flower-arrangements, /plants and /flowers-same-day-delivery and 7 others have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

We fetched 14 pages linked from your homepage and read each the way a search engine does.

4 images failed to load on a phone, for example https://veritone-14-adswizz.attribution.adswizz.com/fire?pixelId=d2af2aff-57f4-4b7d-9919-754bf6dd9f4c&type=sitevisit&subtype=HomePage&gdpr=true&_rnd=664326495.

2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

6 errors were logged to the browser console while the page loaded, for example “[object Object]”.

Large scripts ship without source maps.

Chrome logged issues while loading the page (“Cookie”).

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

1800flowers.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

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

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

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.

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

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

The homepage has only about 54 words of visible text; thin pages give Google and first-time buyers little to go on.

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

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.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Before a visitor clicks anything, the page loads Amplitude, Criteo, FullStory, Google Ads and Google Tag Manager and 8 mores (measured from a US location before any click). A consent tool (TrustArc) is installed; check it blocks these until visitors agree where the law requires it.

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

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