Website review, no card needed
buceplant.com website review
Visit site (opens in a new tab)Reviewed 5 November 202632 issues · 83 checks
This review found 32 issues worth fixing on buceplant.com, 10 of them high impact, across 83 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
84B- #20,853 of 115,138 reviewed websitesbeats 77%
- #13,754 of 66,397 online storesbeats 73%
- #13,360 of 60,723 Shopify storesbeats 72%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.6 s |
| May 23, 2026 | 1.6 s |
| May 30, 2026 | 1.6 s |
| Jun 6, 2026 | 1.6 s |
| Jun 13, 2026 | 1.6 s |
| Jun 20, 2026 | 1.7 s |
| Jun 27, 2026 | 1.7 s |
| Jul 4, 2026 | 1.7 s |
| Jul 11, 2026 | 1.7 s |
| Jul 18, 2026 | 1.7 s |
| Jul 25, 2026 | 1.7 s |
| Aug 1, 2026 | 1.7 s |
| Aug 8, 2026 | 1.7 s |
| Aug 15, 2026 | 1.7 s |
| Aug 22, 2026 | 1.6 s |
| Aug 29, 2026 | 1.6 s |
| Sep 5, 2026 | 1.6 s |
| Sep 12, 2026 | 1.6 s |
| Sep 19, 2026 | 1.6 s |
| Sep 26, 2026 | 1.5 s |
| Oct 3, 2026 | 1.4 s |
| Oct 10, 2026 | 1.4 s |
| Oct 17, 2026 | 1.3 s |
| Oct 24, 2026 | 1.3 s |
| Oct 31, 2026 | 1.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 119 ms |
| May 23, 2026 | 119 ms |
| May 30, 2026 | 118 ms |
| Jun 6, 2026 | 121 ms |
| Jun 13, 2026 | 121 ms |
| Jun 20, 2026 | 121 ms |
| Jun 27, 2026 | 123 ms |
| Jul 4, 2026 | 124 ms |
| Jul 11, 2026 | 122 ms |
| Jul 18, 2026 | 123 ms |
| Jul 25, 2026 | 123 ms |
| Aug 1, 2026 | 121 ms |
| Aug 8, 2026 | 122 ms |
| Aug 15, 2026 | 121 ms |
| Aug 22, 2026 | 120 ms |
| Aug 29, 2026 | 118 ms |
| Sep 5, 2026 | 115 ms |
| Sep 12, 2026 | 113 ms |
| Sep 19, 2026 | 112 ms |
| Sep 26, 2026 | 111 ms |
| Oct 3, 2026 | 104 ms |
| Oct 10, 2026 | 104 ms |
| Oct 17, 2026 | 104 ms |
| Oct 24, 2026 | 104 ms |
| Oct 31, 2026 | 104 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
Speed
Render-blocking requests
1.0 s4 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.0 s.
Main-thread work: 5.4 s
A phone's processor spends 5.4 s on main-thread work while loading, 2.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
3,625 HTML elements
The page has 3,625 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Reduce unused JavaScript
450 ms · 606 KiBAbout 606 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.
Mobile performance score: 55
55/100Your mobile performance score is 55. Pages that score under 90 lose visitors before the first paint.
8 third-party services on the page
8 third-party services load with your homepage (Azure Web Services, Shopify and Yotpo and others), adding 1.8 MB and 605 ms of main-thread time.
4 long tasks on the main thread
4 long tasks block the main thread while loading, the longest for 594 ms. During a long task the page ignores taps.
Improve image delivery
350 ms · 173 KiB5 images could be 173 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 350 ms faster on a phone.
Reduce unused CSS
300 ms · 142 KiBAbout 142 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.
Use efficient cache lifetimes
266 KiB29 files are served with short cache lifetimes, so returning visitors download them again (266 KiB).
Shopify adds 112 ms
112 msShopify costs a phone 112 ms of main-thread work and 607 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.
Legacy JavaScript
43 KiBPolyfills for old browsers add 43 KiB JavaScript that modern phones do not need.
Minify JavaScript
32 KiB32 KiB could be saved by minifying JavaScript.
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.
1 checks passed
Server response: 11 ms
11 msYour server sent the HTML in 11 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 21.0 s
21.0 sThe page becomes fully interactive after 21.0 s. Good is under 3.8 s.
Largest Contentful Paint: 6.3 s
6.3 sYour largest element takes 6.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Aquatic Plants Make your tank pop with color Get Growing”.
Speed Index: 7.9 s
7.9 sVisually, the page fills in at 7.9 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 597 ms
597 msScripts block taps and scrolling for 597 ms in total while the page loads. Good is under 200 ms.
4 images without width and height
4 images have no width and height attributes, so the layout jumps as each one loads.
10 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: 2.1 s
2.1 sReal visitors wait 2.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 104 ms
104 msReal visitors wait 104 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
Real-user FCP: 1.0 s
1.0 sReal visitors see the first content after 1.0 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 505 ms
505 msReal visitors wait 505 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 13% faster for real visitors
-13%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 119 ms to 104 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 21% faster for real visitors
-21%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.6 s to 1.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.011
0.011The layout barely moves while loading (CLS 0.011, good is under 0.1).
First Contentful Paint: 1.1 s
1.1 sThe first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.
Images and page weight
Page weight: 3.7 MB in 395 requests
3.7 MBYour homepage downloads 3.7 MB in 395 requests on a phone: scripts 1.7 MB (216), other files 913 KiB (129) and images 505 KiB (16). Under 2 MB keeps phones on slow connections fast.
About 1.0 g of CO₂ per visit
1.04 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.04 g of CO₂e: 124.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
7 text elements with low contrast
7 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
7 tap targets too small
7 tap targets are too small or too close together to hit reliably with a finger.
ARIA tooltip nodes must have an accessible name (1 element)
ARIA tooltip nodes must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
Alternative text of images should not be repeated as text (13 elements)
Alternative text of images should not be repeated as text: 13 elements on the page fail this check, rated minor by axe-core.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
2 checks passed
Every image has alt text
All 67 images in the HTML carry an alt attribute.
49 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 56 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 7 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
295 internal links, 8 external
The homepage links to 295 pages on buceplant.com and 8 external pages.
7 checks passed
Meta description: 151 characters
Your meta description is 151 characters: “Buce Plant is home to everything aquascaping! We are the premier shop for all your freshwater aquascaping supplies. Che…”.
Title: 56 characters
Your title is a healthy 56 characters: “Aquascaping Supplies | Aquarium Aquascaping | Buce Plant”.
Canonical URL set
The canonical URL is https://buceplant.com/.
Structured data in place
Structured data found: WebSite.
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://buceplant.com/sitemap.xml.
AI search readiness
No Organization structured data
There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.
No llms.txt
There is no https://buceplant.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.
2 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,914 words), so crawlers that don't run JavaScript still read it.
Other pages
1 page without an H1
https://buceplant.com/pages/rewards has 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 117 found) and read each the way a search engine does.
6 checks passed
Linked pages load
7 pages of 15 loaded without an error (the rest turned automated requests away).
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 7 pages that loaded have a meta description.
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.
Every page has a title
All 7 pages that loaded have a <title>.
Best practices
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
Requests the notification permission on page load
Requests the notification permission on page load.
2 checks passed
Tap targets are thumb-sized
55 of 61 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 2 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
About 1,031 words of copy
The homepage carries about 1,031 words of visible text.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Earn when you shop”.
23 calls to action
The homepage has 23 calls to action, for example “Earn when you shop”, “Shop All Plant Packs” and “Quick shop”.
3 short forms
3 short forms (1 field at most) are right on the homepage.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads Klaviyo (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.
19 cookies set on arrival
19Opening the homepage sets 19 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.
43 other companies contacted
Loading the homepage contacts 43 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 buceplant.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 18 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Attentive · Bm Country Blocker Ip Blocker · Klaviyo Email Marketing Sms · Yotpo Product Reviews · Boostymark Regionblock · Selleasy · Pushowl · Swym Wishlist Plus · klarnapayments.com · herokuapp.com · smile.io · azureedge.net · oxiapps.com · gorgias.chat · attn.tv · 9gtb.com · googleapis.com · kxcdn.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
- Hosting
- Shopify
Hiring
- Hiring
- 1 open role
- Job board
- careers page
- Careers page
- buceplant.com/pages/careers (opens in a new tab)
Company
- Headquarters
- Los Angeles
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 32 issues on buceplant.com, including 16 speed issues, 2 SEO issues and 2 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.