Website review, no card needed
bloombarflowers.com website review
Visit site (opens in a new tab)Reviewed 7 November 202634 issues · 84 checks
This review found 34 issues worth fixing on bloombarflowers.com, 14 of them high impact, across 84 checks. The most urgent: improve image delivery. 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
80B- #48,365 of 124,214 reviewed websitesbeats 55%
- #31,956 of 69,818 online storesbeats 48%
- #30,703 of 63,493 Shopify storesbeats 45%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.7 s |
| May 23, 2026 | 1.6 s |
| May 30, 2026 | 1.5 s |
| Jun 6, 2026 | 1.7 s |
| Jun 13, 2026 | 1.7 s |
| Jun 20, 2026 | 1.9 s |
| Jun 27, 2026 | 1.9 s |
| Jul 4, 2026 | 1.8 s |
| Jul 11, 2026 | 1.7 s |
| Jul 18, 2026 | 1.7 s |
| Jul 25, 2026 | 1.6 s |
| Aug 1, 2026 | 1.5 s |
| Aug 8, 2026 | 1.5 s |
| Aug 15, 2026 | 1.4 s |
| Aug 22, 2026 | 1.5 s |
| Aug 29, 2026 | 1.4 s |
| Sep 5, 2026 | 1.4 s |
| Sep 12, 2026 | 1.4 s |
| Sep 19, 2026 | 1.4 s |
| Sep 26, 2026 | 1.6 s |
| Oct 3, 2026 | 1.6 s |
| Oct 10, 2026 | 1.6 s |
| Oct 17, 2026 | 1.6 s |
| Oct 24, 2026 | 1.6 s |
| Oct 31, 2026 | 1.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 109 ms |
| May 23, 2026 | 107 ms |
| May 30, 2026 | 109 ms |
| Jun 6, 2026 | 104 ms |
| Jun 13, 2026 | 112 ms |
| Jun 20, 2026 | 113 ms |
| Jun 27, 2026 | 129 ms |
| Jul 4, 2026 | 128 ms |
| Jul 11, 2026 | 117 ms |
| Jul 18, 2026 | 122 ms |
| Aug 1, 2026 | 111 ms |
| Aug 8, 2026 | 113 ms |
| Aug 15, 2026 | 104 ms |
| Aug 22, 2026 | 104 ms |
| Aug 29, 2026 | 104 ms |
| Sep 5, 2026 | 104 ms |
| Sep 12, 2026 | 105 ms |
| Sep 19, 2026 | 109 ms |
| Sep 26, 2026 | 120 ms |
| Oct 3, 2026 | 127 ms |
| Oct 10, 2026 | 123 ms |
| Oct 17, 2026 | 122 ms |
| Oct 31, 2026 | 113 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
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Improve image delivery
1.2 s · 627 KiB13 images could be 627 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.2 s faster on a phone.
Reduce unused JavaScript
1.5 s · 246 KiBAbout 246 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.
Render-blocking requests
1.0 s6 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.0 s.
Mobile performance score: 58
58/100Your mobile performance score is 58. Pages that score under 90 lose visitors before the first paint.
Use efficient cache lifetimes
300 ms · 137 KiB22 files are served with short cache lifetimes, so returning visitors download them again (137 KiB).
2,483 HTML elements
The page has 2,483 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Main-thread work: 2.2 s
A phone's processor spends 2.2 s on main-thread work while loading, 796 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Google CDN adds 137 ms
137 msGoogle CDN costs a phone 137 ms of main-thread work and 298 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.
Shopify adds 121 ms
121 msShopify costs a phone 121 ms of main-thread work and 391 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 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Google CDN and Shopify and others), adding 1,006 KiB and 466 ms of main-thread time.
Reduce unused CSS
150 ms · 51 KiBAbout 51 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.
3 long tasks on the main thread
3 long tasks block the main thread while loading, the longest for 175 ms. During a long task the page ignores taps.
Legacy JavaScript
150 ms · 19 KiBPolyfills for old browsers add 19 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
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.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
Minify JavaScript
3 KiB3 KiB could be saved by minifying JavaScript.
Minify CSS
2 KiB2 KiB could be saved by minifying CSS.
1 checks passed
Server response: 8 ms
8 msYour server sent the HTML in 8 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 12.7 s
12.7 sYour largest element takes 12.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “fresh flowers”.
Time to Interactive: 12.8 s
12.8 sThe page becomes fully interactive after 12.8 s. Good is under 3.8 s.
First Contentful Paint: 4.1 s
4.1 sThe first text or image appears after 4.1 s on a phone. Good is under 1.8 s.
Speed Index: 6.4 s
6.4 sVisually, the page fills in at 6.4 s (Speed Index). Good is under 3.4 s.
Tap response (INP) held steady for real visitors
+9%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 109 ms to 113 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-3%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.7 s to 1.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
8 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 1.6 s
1.6 sReal visitors wait 1.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 113 ms
113 msReal visitors wait 113 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.6 s
1.6 sReal visitors see the first content after 1.6 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 793 ms
793 msReal visitors wait 793 ms for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 186 ms
186 msScripts block the page for only 186 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 4.1 MB in 328 requests
4.1 MBYour homepage downloads 4.1 MB in 328 requests on a phone: images 1.9 MB (28), scripts 1.1 MB (164) and other files 873 KiB (120). Under 2 MB keeps phones on slow connections fast.
6 images below the first screen load straight away
6 images further down the page (446 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
1 image in older formats
1 image (135 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.
About 1.2 g of CO₂ per visit
1.15 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.15 g of CO₂e: 138.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Hidden but focusable
9 elements hidden from screen readers can still receive keyboard focus.
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
4 images without alt text
4 images have no alt text, which hurts accessibility and image search.
24 links without text
24 visible links have no text or label, so screen readers cannot say where they go.
Headings should not be empty (4 elements)
Headings should not be empty: 4 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h3 → h6, h2 → h6 and h2 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
44 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 6 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (74 characters)
Your title is 74 characters, so Google will cut it off around 60: “Florist Adelaide | Same Day Delivery | BloomBar Flowers – Bloombar Flowers”.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
137 internal links, 5 external
The homepage links to 137 pages on bloombarflowers.com and 5 external pages.
6 checks passed
Meta description: 154 characters
Your meta description is 154 characters: “The florist Adelaide loves for fresh, feel-good flowers. Visit our shop or order online for same day flower delivery. F…”.
One H1 headline
Your main headline reads: “Bloombar Flowers”.
Canonical URL set
The canonical URL is https://bloombarflowers.com/.
Structured data in place
Structured data found: Organization.
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://bloombarflowers.com/sitemap.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
3 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Text is in the HTML
Your server sends the page's text in the HTML (562 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://bloombarflowers.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page points its canonical at the homepage
https://bloombarflowers.com/products/phalaenopsis-orchids-old declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.
2 pages share a title
/ and https://bloombarflowers.com/products/phalaenopsis-orchids-old all use the title “Florist Adelaide | Same Day Delivery | BloomBar Flowers – Bloombar Fl…”. Search engines can't tell which page to show for a search, so each competes with the others.
1 page without a meta description
https://bloombarflowers.com/collections/baby-flowers has no meta description, so Google writes the search snippet from whatever text it finds.
6 pages without an H1
https://bloombarflowers.com/collections/bloombar-by-studio, https://bloombarflowers.com/collections/anniversary-flowers, https://bloombarflowers.com/collections/baby-flowers, https://bloombarflowers.com/collections/birthday-flowers, https://bloombarflowers.com/collections/congratulations-flowers and https://bloombarflowers.com/collections/get-well-soon-flowers have no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 53 found) and read each the way a search engine does.
3 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
15 of 15 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 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 190 words
The homepage has only about 190 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
4 checks passed
10 calls to action
The homepage has 10 calls to action, for example “Shop all Flowers”, “Shop by” and “Shop Gifts”.
13 short forms
13 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Analytics.
Opening hours shown
Your opening hours are on the homepage.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo 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.
15 cookies set on arrival
15Opening the homepage sets 15 cookies (measured from a US location before any click).
No consent tool detected
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.
27 other companies contacted
Loading the homepage contacts 27 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
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 bloombarflowers.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Apps on your store
Your storefront loads 5 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Klaviyo Email Marketing Sms · Google Youtube · chimpstatic.com · getsitecontrol.com · useifsapp.com
Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info
Upkeep, stack and company
Stack
- E-commerce
- Shopify
- Analytics
- Google Analytics
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 34 issues on bloombarflowers.com, including 13 speed issues, 2 SEO issues and 6 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.