Website review, no card needed
1800flowers.ca website review
Visit site (opens in a new tab)Reviewed 11 November 202644 issues · 89 checks
This review found 44 issues worth fixing on 1800flowers.ca, 17 of them high impact, across 89 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
60DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 3.0 s |
| May 30, 2026 | 2.9 s |
| Jun 6, 2026 | 2.9 s |
| Jun 13, 2026 | 2.9 s |
| Jun 20, 2026 | 3.0 s |
| Jun 27, 2026 | 3.1 s |
| Jul 4, 2026 | 3.3 s |
| Jul 11, 2026 | 3.4 s |
| Jul 18, 2026 | 3.4 s |
| Jul 25, 2026 | 3.3 s |
| Aug 1, 2026 | 3.4 s |
| Aug 8, 2026 | 3.4 s |
| Aug 15, 2026 | 3.4 s |
| Aug 22, 2026 | 3.5 s |
| Aug 29, 2026 | 3.5 s |
| Sep 5, 2026 | 3.5 s |
| Sep 12, 2026 | 3.5 s |
| Sep 19, 2026 | 3.5 s |
| Sep 26, 2026 | 3.5 s |
| Oct 3, 2026 | 3.5 s |
| Oct 10, 2026 | 3.6 s |
| Oct 17, 2026 | 3.6 s |
| Oct 24, 2026 | 3.6 s |
| Oct 31, 2026 | 3.5 s |
| Nov 7, 2026 | 3.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 479 ms |
| May 30, 2026 | 478 ms |
| Jun 6, 2026 | 470 ms |
| Jun 13, 2026 | 520 ms |
| Jun 20, 2026 | 546 ms |
| Jun 27, 2026 | 536 ms |
| Jul 4, 2026 | 504 ms |
| Jul 11, 2026 | 486 ms |
| Jul 18, 2026 | 445 ms |
| Jul 25, 2026 | 422 ms |
| Aug 1, 2026 | 433 ms |
| Aug 8, 2026 | 440 ms |
| Aug 15, 2026 | 444 ms |
| Aug 22, 2026 | 452 ms |
| Aug 29, 2026 | 460 ms |
| Sep 5, 2026 | 464 ms |
| Sep 12, 2026 | 466 ms |
| Sep 19, 2026 | 492 ms |
| Sep 26, 2026 | 525 ms |
| Oct 3, 2026 | 544 ms |
| Oct 10, 2026 | 563 ms |
| Oct 17, 2026 | 570 ms |
| Oct 24, 2026 | 566 ms |
| Oct 31, 2026 | 561 ms |
| Nov 7, 2026 | 543 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
How it loaded on a phone
1.3 s
2.6 s
3.9 s
5.2 s
6.5 s
7.8 s
9.1 s
10.4 s
Speed
Render-blocking requests
1.4 s7 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.4 s.
Mobile performance score: 32
32/100Your mobile performance score is 32. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 8.7 s
A phone's processor spends 8.7 s on main-thread work while loading, 5.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Reduce unused JavaScript
750 ms · 2.1 MBAbout 2.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 750 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Facebook and Amplitude Mobile Analytics and others), adding 1.9 MB and 2.0 s of main-thread time.
Use efficient cache lifetimes
300 ms · 1.1 MB45 files are served with short cache lifetimes, so returning visitors download them again (1.1 MB).
Google Tag Manager adds 826 ms
826 msGoogle Tag Manager costs a phone 826 ms of main-thread work and 846 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 862 ms. During a long task the page ignores taps.
Legacy JavaScript
450 ms · 235 KiBPolyfills for old browsers add 235 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 450 ms faster on a phone.
Improve image delivery
413 KiB5 images could be 413 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Facebook adds 265 ms
265 msFacebook costs a phone 265 ms of main-thread work and 284 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.
Amplitude Mobile Analytics adds 256 ms
256 msAmplitude Mobile Analytics costs a phone 256 ms of main-thread work and 145 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.
Duplicated JavaScript
150 ms · 27 KiB27 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 150 ms faster on a phone.
Reduce unused CSS
150 ms · 10 KiBAbout 10 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Minify JavaScript
17 KiB17 KiB could be saved by minifying JavaScript.
Minify CSS
6 KiB6 KiB could be saved by minifying CSS.
Chained critical requests
Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.
1 checks passed
Server response: 19 ms
19 msYour server sent the HTML in 19 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
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-user CLS: 0.39
0.39For real visitors the layout shifts by 0.39 (75th percentile). Good is under 0.1.
Time to Interactive: 44.3 s
44.3 sThe page becomes fully interactive after 44.3 s. Good is under 3.8 s.
Largest Contentful Paint: 8.1 s
8.1 sYour largest element takes 8.1 s to render on a phone. Google's threshold for “good” is 2.5 s.
Speed Index: 12.9 s
12.9 sVisually, the page fills in at 12.9 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 3.1 s
3.1 sScripts block taps and scrolling for 3.1 s in total while the page loads. Good is under 200 ms.
Real-user FCP: 2.0 s
2.0 sReal visitors see the first content after 2.0 s (75th percentile). Good is under 1.8 s.
First Contentful Paint: 2.7 s
2.7 sThe first text or image appears after 2.7 s on a phone. Good is under 1.8 s.
Tap response (INP) got 15% slower for real visitors
+15%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 479 ms to 543 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 18% slower for real visitors
+18%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 3.0 s to 3.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
1 checks passed
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 6.4 MB in 293 requests
6.4 MBYour homepage downloads 6.4 MB in 293 requests on a phone: scripts 5.3 MB (135), images 513 KiB (31) and fonts 370 KiB (7). Under 2 MB keeps phones on slow connections fast.
5 images far larger than shown
270 KiB5 images are downloaded at several times the size a phone draws them, for example 191167xlx-mob.jpg at 344 px wide, shown at 77 px. Resized copies would save about 270 KiB.
4 images in older formats
4 images (289 KiB) 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.
About 1.8 g of CO₂ per visit
1.82 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.82 g of CO₂e: 218.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
Hidden but focusable
1 element hidden from screen readers can still receive keyboard focus.
All page content should be contained by landmarks (7 elements)
All page content should be contained by landmarks: 7 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
Users should be able to zoom and scale the text up to 500% (1 element)
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.
2 checks passed
Every image has alt text
All 23 images in the HTML carry an alt attribute.
39 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 44 WCAG 2.2 A/AA and best-practice rules on the phone render: 39 passed and 5 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Structured data has 3 problems
Structured data found (Organization and WebSite) but with 3 problems, for example “WebSite: missing name”.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
31 internal links, 2 external
The homepage links to 31 pages on 1800flowers.ca and 2 external pages.
7 checks passed
Meta description: 148 characters
Your meta description is 148 characters: “Send flowers to Canada to celebrate holidays, birthdays, and more! Order fresh floral arrangements, plants, or gift bas…”.
One H1 headline
Your main headline reads: “Canadian Flower Delivery”.
Title: 36 characters
Your title is a healthy 36 characters: “Send Flowers to Canada | 1800Flowers”.
Canonical URL set
The canonical URL is https://www.1800flowers.com/canada.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://www.1800flowers.com/sitemap.xml.
AI search readiness
Parts of the site are closed to 6 AI crawlers
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.
2 checks passed
Organization data: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.
llms.txt published
The site publishes https://www.1800flowers.com/llms.txt (7 KiB, 37 links), a plain-text guide to the site for AI tools.
Other pages
12 pages without a title
https://www.1800flowers.com/australia, https://www.1800flowers.com/ireland, https://www.1800flowers.com/brazil, https://www.1800flowers.com/italy, https://www.1800flowers.com/japan and https://www.1800flowers.com/france and 6 others have no <title>, so Google invents the link text in results.
12 pages without a meta description
https://www.1800flowers.com/australia, https://www.1800flowers.com/ireland, https://www.1800flowers.com/brazil, https://www.1800flowers.com/italy, https://www.1800flowers.com/japan and https://www.1800flowers.com/france and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.
13 pages without an H1
https://www.1800flowers.com/australia, https://www.1800flowers.com/ireland, https://www.1800flowers.com/brazil, https://www.1800flowers.com/italy, https://www.1800flowers.com/japan and https://www.1800flowers.com/france and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.
13 pages with very little text
https://www.1800flowers.com/australia, https://www.1800flowers.com/ireland, https://www.1800flowers.com/brazil, https://www.1800flowers.com/italy, https://www.1800flowers.com/japan and https://www.1800flowers.com/france 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.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 21 found) and read each the way a search engine does.
4 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Titles are unique
Every page we checked has its own title.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Best practices
2 broken images
2 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=505671678.
2 third-party cookies
2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Fenced Frame API is deprecated and scheduled for removal.”).
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “[object Object]”.
5 distorted images
5 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
Missing source maps
Large scripts ship without source maps.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
2 checks passed
Tap targets are thumb-sized
10 of 12 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
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 calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
Local business without LocalBusiness data
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 phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
Only about 100 words
The homepage has only about 100 words of visible text; thin pages give Google and first-time buyers little to go on.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
No risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
1 checks passed
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
13 trackers load before any consent
13Before 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.
48 cookies set on arrival
48Opening the homepage sets 48 cookies, 1 of them by other companies (measured from a US location before any click).
77 other companies contacted
Loading the homepage contacts 77 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: TrustArc
A consent management tool (TrustArc) loads with the page.
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at 1800flowers.ca, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- React
- Analytics
- Google Tag Manager
- Hosting
- Fastly
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 44 issues on 1800flowers.ca, including 20 speed issues, 1 SEO issue and 7 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.