Website review, no card needed
floraflex.com website review
Visit site (opens in a new tab)Reviewed 16 November 202630 issues · 79 checks
This review found 30 issues worth fixing on floraflex.com, 10 of them high impact, across 79 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
82B- #33,329 of 118,362 reviewed websitesbeats 66%
- #22,239 of 67,243 online storesbeats 60%
- #21,502 of 61,313 Shopify storesbeats 58%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 916 ms |
| Jun 6, 2026 | 913 ms |
| Jun 13, 2026 | 913 ms |
| Jun 20, 2026 | 905 ms |
| Jun 27, 2026 | 911 ms |
| Jul 4, 2026 | 915 ms |
| Jul 11, 2026 | 901 ms |
| Jul 18, 2026 | 914 ms |
| Jul 25, 2026 | 901 ms |
| Aug 1, 2026 | 873 ms |
| Aug 8, 2026 | 875 ms |
| Aug 15, 2026 | 853 ms |
| Aug 22, 2026 | 961 ms |
| Aug 29, 2026 | 1.5 s |
| Sep 5, 2026 | 2.7 s |
| Sep 12, 2026 | 3.8 s |
| Sep 19, 2026 | 4.0 s |
| Sep 26, 2026 | 4.1 s |
| Oct 3, 2026 | 4.3 s |
| Oct 10, 2026 | 4.4 s |
| Oct 17, 2026 | 4.5 s |
| Oct 24, 2026 | 4.5 s |
| Oct 31, 2026 | 4.7 s |
| Nov 7, 2026 | 5.4 s |
| Nov 14, 2026 | 6.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 92 ms |
| Jun 6, 2026 | 93 ms |
| Jun 13, 2026 | 92 ms |
| Jun 20, 2026 | 93 ms |
| Jun 27, 2026 | 96 ms |
| Jul 4, 2026 | 100 ms |
| Jul 11, 2026 | 100 ms |
| Jul 18, 2026 | 99 ms |
| Jul 25, 2026 | 98 ms |
| Aug 1, 2026 | 95 ms |
| Aug 8, 2026 | 95 ms |
| Aug 15, 2026 | 95 ms |
| Aug 22, 2026 | 96 ms |
| Aug 29, 2026 | 96 ms |
| Sep 5, 2026 | 99 ms |
| Sep 12, 2026 | 99 ms |
| Sep 19, 2026 | 95 ms |
| Sep 26, 2026 | 89 ms |
| Oct 3, 2026 | 87 ms |
| Oct 10, 2026 | 80 ms |
| Oct 17, 2026 | 87 ms |
| Oct 24, 2026 | 95 ms |
| Oct 31, 2026 | 111 ms |
| Nov 7, 2026 | 133 ms |
| Nov 14, 2026 | 131 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.1 s
2.2 s
3.2 s
4.3 s
5.4 s
6.5 s
7.6 s
8.7 s
Speed
Improve image delivery
1.9 s · 1.1 MB5 images could be 1.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.9 s faster on a phone.
Mobile performance score: 71
71/100Your mobile performance score is 71. Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
950 ms3 files block the first paint until they finish downloading. Deferring or inlining them could save about 950 ms.
Reduce unused JavaScript
568 KiBAbout 568 KiB of JavaScript is downloaded but never used on this page.
Reduce unused CSS
300 ms · 70 KiBAbout 70 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
3 long tasks on the main thread
3 long tasks block the main thread while loading, the longest for 111 ms. During a long task the page ignores taps.
2 third-party services on the page
2 third-party services load with your homepage (cloudflare.com and Google Fonts), adding 88 KiB and 6 ms of main-thread time.
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.
2 checks passed
Main-thread work: 0.9 s
A phone's processor spends 0.9 s on main-thread work while loading, 292 ms of it running JavaScript. That is comfortably low.
Server response: 6 ms
6 msYour server sent the HTML in 6 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 LCP: 5.8 s
5.8 sReal visitors wait 5.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 5.8 s
5.8 sReal visitors see the first content after 5.8 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 5.0 s
5.0 sReal visitors wait 5.0 s for your server to start answering (75th percentile). Good is under 800 ms.
Speed Index: 12.7 s
12.7 sVisually, the page fills in at 12.7 s (Speed Index). Good is under 3.4 s.
Largest Contentful Paint: 4.9 s
4.9 sYour largest element takes 4.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “FloraFlex QuickFill 1 Gal coco bag, coco discs, black Quick…”. Most of its time is resource load delay (7.2 s).
Time to Interactive: 8.0 s
8.0 sThe page becomes fully interactive after 8.0 s. Good is under 3.8 s.
Tap response (INP) got 43% slower for real visitors
+43%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 92 ms to 131 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 525% slower for real visitors
+525%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 0.9 s to 6.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 1.8 s
1.8 sThe first text or image appears after 1.8 s on a phone. Good is under 1.8 s.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
4 checks passed
Real-user INP: 155 ms
155 msReal visitors wait 155 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.08
0.08For real visitors the layout shifts by 0.08 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 48 ms
48 msScripts block the page for only 48 ms while loading. Good is under 200 ms.
Images and page weight
1 image over 500 KB
quickfill-lineup-white.webp weighs 702 KiB. On a phone connection a single image that size takes seconds.
Page weight: 2.2 MB in 26 requests
2.2 MBYour homepage downloads 2.2 MB in 26 requests on a phone: images 1.2 MB (5), scripts 841 KiB (4) and stylesheets 105 KiB (3). Under 2 MB keeps phones on slow connections fast.
1 image far larger than shown
313 KiB1 image is downloaded at several times the size a phone draws it, for example quickfill-lineup-white.webp at 1,419 px wide, shown at 352 px. Resized copies would save about 313 KiB.
1 image in older formats
1 image (36 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 0.6 g of CO₂ per visit
0.63 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.63 g of CO₂e: 76.1 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
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 8 images in the HTML carry an alt attribute.
51 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 51 passed and 0 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Structured data has 1 problem
Structured data found (FAQPage and Organization) but with 1 problem, for example “Organization: sameAs is an empty list”.
44 internal links, 1 external
The homepage links to 44 pages on floraflex.com and 1 external page.
7 checks passed
Meta description: 146 characters
Your meta description is 146 characters: “FloraFlex QuickFill coco coir grow bags, dry nutrients and LED grow lights for commercial growers. Find an authorized r…”.
One H1 headline
Your main headline reads: “The root zone, made repeatable.”.
Title: 54 characters
Your title is a healthy 54 characters: “FloraFlex | Coco Coir, Dry Nutrients & LED Grow Lights”.
Canonical URL set
The canonical URL is https://www.floraflex.com/.
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.floraflex.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 (1,187 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.floraflex.com/llms.txt (5 KiB, 0 links), a plain-text guide to the site for AI tools.
Other pages
2 pages share a title
https://www.floraflex.com/shop-online and https://www.floraflex.com/find-a-reseller all use the title “Shop FloraFlex online | Authorized online resellers”. Search engines can't tell which page to show for a search, so each competes with the others.
2 pages share a meta description
https://www.floraflex.com/shop-online and https://www.floraflex.com/find-a-reseller use the same meta description. A description written for each page earns more clicks.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.floraflex.com/find-a-reseller, whose canonical is https://www.floraflex.com/shop-online. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
14 pages slow to respond
https://www.floraflex.com/find-a-reseller, https://www.floraflex.com/request-quote, https://www.floraflex.com/quickfill, https://www.floraflex.com/dry-nutrients, https://www.floraflex.com/900w-led and https://www.floraflex.com/blogs/floraflex-media and 8 others took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 20 found) and read each the way a search engine does.
5 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Every page has a meta description
All 15 pages that loaded have a meta description.
Every page has an H1
Each page we checked has a main headline.
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
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Connecting to 'https://fonts.googleapis.com/css2?family=Inter:wght@400;500;600;700;800;900&family=Lato:ital,wght@0,300;…”.
Browser-reported issues
Chrome logged issues while loading the page (“Content security policy”).
Missing source maps
Large scripts ship without source maps.
2 checks passed
Tap targets are thumb-sized
20 of 22 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
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.
About 897 words of copy
The homepage carries about 897 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
3 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Shop Online Now →” and “Quote”.
11 calls to action
The homepage has 11 calls to action, for example “Shop Online Now →”, “Buy near youFind a reseller” and “WholesaleRequest a Quote”.
1 short form
A short form (1 field at most) is right on the homepage.
Privacy and tracking
3 cookies set on arrival
3Opening the homepage sets 3 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.
3 other companies contacted
Loading the homepage contacts 3 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 floraflex.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Tailwind CSS
- E-commerce
- Shopify;Shopify Local Pickup;Shopify Plus;Shopify POS
- Hosting
- Cloudflare
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 30 issues on floraflex.com, including 16 speed issues, 1 SEO issue and 5 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.