Website review, no card needed
1908brands.com website review
Visit site (opens in a new tab)Reviewed 21 November 202640 issues · 86 checks
This review found 40 issues worth fixing on 1908brands.com, 17 of them high impact, across 86 checks. The most urgent: use efficient cache lifetimes. 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
75C- #81,157 of 123,957 reviewed websitesbeats 30%
- #51,517 of 69,728 online storesbeats 22%
- #1,413 of 2,898 WooCommerce storesbeats 45%
Closest competitors among WooCommerce stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 1.6 s |
| Jun 6, 2026 | 1.8 s |
| Jun 13, 2026 | 1.8 s |
| Jun 20, 2026 | 1.8 s |
| Jun 27, 2026 | 1.9 s |
| Jul 4, 2026 | 1.8 s |
| Jul 11, 2026 | 1.9 s |
| Jul 18, 2026 | 2.0 s |
| Jul 25, 2026 | 2.0 s |
| Aug 1, 2026 | 2.0 s |
| Aug 8, 2026 | 1.9 s |
| Aug 15, 2026 | 1.9 s |
| Aug 22, 2026 | 1.8 s |
| Aug 29, 2026 | 1.7 s |
| Sep 5, 2026 | 1.7 s |
| Sep 12, 2026 | 1.8 s |
| Sep 19, 2026 | 1.9 s |
| Sep 26, 2026 | 2.1 s |
| Oct 3, 2026 | 2.1 s |
| Oct 10, 2026 | 2.2 s |
| Oct 17, 2026 | 2.2 s |
| Oct 24, 2026 | 2.0 s |
| Oct 31, 2026 | 2.1 s |
| Nov 7, 2026 | 1.9 s |
| Nov 14, 2026 | 2.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 62 ms |
| Jun 6, 2026 | 63 ms |
| Jun 13, 2026 | 69 ms |
| Jun 20, 2026 | 64 ms |
| Jun 27, 2026 | 63 ms |
| Jul 4, 2026 | 63 ms |
| Jul 11, 2026 | 61 ms |
| Jul 18, 2026 | 64 ms |
| Jul 25, 2026 | 66 ms |
| Aug 1, 2026 | 62 ms |
| Aug 8, 2026 | 64 ms |
| Aug 15, 2026 | 62 ms |
| Aug 22, 2026 | 62 ms |
| Sep 5, 2026 | 62 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
Use efficient cache lifetimes
6.6 s · 11.1 MB79 files are served with short cache lifetimes, so returning visitors download them again (11.1 MB).
Reduce unused JavaScript
6.0 s · 708 KiBAbout 708 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 6.0 s faster on a phone.
Render-blocking requests
4.2 s34 files block the first paint until they finish downloading. Deferring or inlining them could save about 4.2 s.
Reduce unused CSS
1.1 s · 143 KiBAbout 143 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.1 s 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.
7 third-party services on the page
7 third-party services load with your homepage (Google CDN, Other Google APIs/SDKs and JSDelivr CDN and others), adding 1.3 MB and 410 ms of main-thread time.
Improve image delivery
300 ms · 234 KiB10 images could be 234 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.
Google CDN adds 341 ms
341 msGoogle CDN costs a phone 341 ms of main-thread work and 1.1 MB 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
150 ms · 11 KiBPolyfills for old browsers add 11 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Minify CSS
150 ms · 2 KiB2 KiB could be saved by minifying CSS.
Minify JavaScript
150 ms · 2 KiB2 KiB could be saved by minifying JavaScript.
Font display
100 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).
5 long tasks on the main thread
5 long tasks block the main thread while loading, the longest for 84 ms. During a long task the page ignores taps.
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.
2 checks passed
Main-thread work: 1.3 s
A phone's processor spends 1.3 s on main-thread work while loading, 766 ms of it running JavaScript. That is comfortably low.
Server response: 29 ms
29 msYour server sent the HTML in 29 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 TTFB: 1.9 s
1.9 sReal visitors wait 1.9 s for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 10.7 s
10.7 sThe first text or image appears after 10.7 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 16.4 s
16.4 sYour largest element takes 16.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “High Performance Plant-Based Laundry Detergents Proud partn…”.
Time to Interactive: 16.6 s
16.6 sThe page becomes fully interactive after 16.6 s. Good is under 3.8 s.
Speed Index: 10.7 s
10.7 sVisually, the page fills in at 10.7 s (Speed Index). Good is under 3.4 s.
Real-user FCP: 2.1 s
2.1 sReal visitors see the first content after 2.1 s (75th percentile). Good is under 1.8 s.
25 images without width and height
25 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
-1%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 62 ms to 62 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 16% slower for real visitors
+16%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 1.6 s to 2.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user LCP: 2.3 s
2.3 sReal visitors wait 2.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Total Blocking Time: 65 ms
65 msScripts block the page for only 65 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: 12.8 MB in 107 requests
12.8 MBYour homepage downloads 12.8 MB in 107 requests on a phone: media 9.4 MB (2), scripts 1.3 MB (30) and images 871 KiB (30). Under 2 MB keeps phones on slow connections fast.
11 images below the first screen load straight away
11 images further down the page (473 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
2 images far larger than shown
88 KiB2 images are downloaded at several times the size a phone draws them, for example Shopify-Blog-FeaturedImage_JAN27_1200x460_crop_center.webp at 1,200 px wide, shown at 251 px. Resized copies would save about 88 KiB.
5 images in older formats
5 images (325 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 3.6 g of CO₂ per visit
3.62 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.62 g of CO₂e: 434.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
2 text elements with low contrast
2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
22 images without alt text
22 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (10 elements)
All page content should be contained by landmarks: 10 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.
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.
18 links without text
18 visible links have no text or label, so screen readers cannot say where they go.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h2 → h5), which makes the page harder to scan with a screen reader.
1 checks passed
41 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 47 WCAG 2.2 A/AA and best-practice rules on the phone render: 41 passed and 6 failed. 5 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No social preview image
No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
2 links crawlers can't follow
2 links have no real href, so search engines can't follow them.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
45 internal links, 4 external
The homepage links to 45 pages on 1908brands.com and 4 external pages.
4 checks passed
Title: 38 characters
Your title is a healthy 38 characters: “BClean – Clean Laundry Care Essentials”.
Canonical URL set
The canonical URL is https://bclean.com/.
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://bclean.com/wp-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://bclean.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 (452 words), so crawlers that don't run JavaScript still read it.
Other pages
15 pages without a meta description
https://bclean.com/product-category/cleaning-kits, https://bclean.com/product-category/refill-tablets, https://bclean.com/product-category/laundry, https://bclean.com/about, https://bclean.com/contact-us and https://bclean.com/refund_returns and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.
7 pages without an H1
https://bclean.com/product-category/cleaning-kits, https://bclean.com/product-category/refill-tablets, https://bclean.com/product-category/laundry, https://bclean.com/about, https://bclean.com/contact-us and https://bclean.com/news and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.
5 pages with very little text
https://bclean.com/product-category/cleaning-kits, https://bclean.com/product-category/refill-tablets, https://bclean.com/product-category/laundry, https://bclean.com/contact-us and https://bclean.com/news 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 23 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.
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.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
4 small tap targets
4 of 11 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
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_TUNNEL_CONNECTION_FAILED”.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
Missing source maps
Large scripts ship without source maps.
1 checks passed
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.
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 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 400 words of copy
The homepage carries about 400 words of visible text.
2 checks passed
7 calls to action
The homepage has 7 calls to action, for example “Shop”, “Contact Us” and “SHOP TABLETS NOW”.
1 short form
A short form (3 fields at most) is right on the homepage, asking for an email.
Privacy and tracking
11 cookies set on arrival
11Opening the homepage sets 11 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.
9 other companies contacted
Loading the homepage contacts 9 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 1908brands.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- WordPress
- Framework
- jQuery
- E-commerce
- WooCommerce
- Hosting
- IONOS
Company
- Headquarters
- Aurora
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 40 issues on 1908brands.com, including 16 speed issues, 5 SEO issues and 4 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.