Website review, no card needed
beforecompany.com website review
Visit site (opens in a new tab)Reviewed 7 November 202638 issues · 86 checks
This review found 38 issues worth fixing on beforecompany.com, 6 of them high impact, across 86 checks. The most urgent: page weight: 9.1 MB in 319 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
88B- #5,714 of 120,366 reviewed websitesbeats 93%
- #3,135 of 68,142 online storesbeats 93%
- #3,035 of 62,097 Shopify storesbeats 93%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.3 s |
| May 23, 2026 | 1.3 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 | 2.3 s |
| Jul 4, 2026 | 2.6 s |
| Jul 11, 2026 | 2.5 s |
| Jul 18, 2026 | 2.5 s |
| Jul 25, 2026 | 2.0 s |
| Aug 1, 2026 | 1.5 s |
| Aug 8, 2026 | 1.6 s |
| Aug 15, 2026 | 1.4 s |
| Aug 22, 2026 | 1.4 s |
| Aug 29, 2026 | 1.3 s |
| Sep 5, 2026 | 1.1 s |
| Sep 12, 2026 | 1.1 s |
| Sep 19, 2026 | 1.2 s |
| Sep 26, 2026 | 1.1 s |
| Oct 3, 2026 | 1.2 s |
| Oct 10, 2026 | 1.3 s |
| Oct 17, 2026 | 1.3 s |
| Oct 24, 2026 | 1.5 s |
| Oct 31, 2026 | 1.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 106 ms |
| May 23, 2026 | 106 ms |
| May 30, 2026 | 109 ms |
| Jun 6, 2026 | 105 ms |
| Jun 13, 2026 | 109 ms |
| Jun 20, 2026 | 116 ms |
| Jun 27, 2026 | 131 ms |
| Jul 4, 2026 | 140 ms |
| Jul 11, 2026 | 121 ms |
| Jul 18, 2026 | 119 ms |
| Jul 25, 2026 | 112 ms |
| Aug 1, 2026 | 112 ms |
| Aug 8, 2026 | 131 ms |
| Aug 22, 2026 | 146 ms |
| Sep 5, 2026 | 138 ms |
| Sep 12, 2026 | 123 ms |
| Sep 19, 2026 | 128 ms |
| Sep 26, 2026 | 121 ms |
| Oct 3, 2026 | 121 ms |
| Oct 10, 2026 | 128 ms |
| Oct 17, 2026 | 120 ms |
| Oct 24, 2026 | 132 ms |
| Oct 31, 2026 | 138 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
350 ms · 4.7 MB25 images could be 4.7 MB 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.
8 third-party services on the page
8 third-party services load with your homepage (Yotpo, Klaviyo and Google Tag Manager and others), adding 1.4 MB and 873 ms of main-thread time.
Mobile performance score: 69
69/100Your mobile performance score is 69. Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
150 ms · 616 KiBAbout 616 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.
Render-blocking requests
450 ms13 files block the first paint until they finish downloading. Deferring or inlining them could save about 450 ms.
Use efficient cache lifetimes
332 KiB21 files are served with short cache lifetimes, so returning visitors download them again (332 KiB).
Main-thread work: 3.3 s
A phone's processor spends 3.3 s on main-thread work while loading, 1.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Yotpo adds 270 ms
270 msYotpo costs a phone 270 ms of main-thread work and 397 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.
Klaviyo adds 190 ms
190 msKlaviyo costs a phone 190 ms of main-thread work and 426 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.
2,015 HTML elements
The page has 2,015 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
6 long tasks on the main thread
6 long tasks block the main thread while loading, the longest for 138 ms. During a long task the page ignores taps.
Reduce unused CSS
64 KiBAbout 64 KiB of CSS is downloaded but never applied on this page.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Minify JavaScript
21 KiB21 KiB could be saved by minifying JavaScript.
Legacy JavaScript
19 KiBPolyfills for old browsers add 19 KiB JavaScript that modern phones do not need.
Minify CSS
9 KiB9 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.
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: 8 ms
8 msYour server sent the HTML in 8 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.
Time to Interactive: 19.4 s
19.4 sThe page becomes fully interactive after 19.4 s. Good is under 3.8 s.
Largest Contentful Paint: 7.6 s
7.6 sYour largest element takes 7.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Brilliant Breath MouthWash”.
Tap response (INP) got 27% slower for real visitors
+27%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 106 ms to 138 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 2.2 s
2.2 sReal visitors see the first content after 2.2 s (75th percentile). Good is under 1.8 s.
61 images without width and height
61 images have no width and height attributes, so the layout jumps as each one loads.
Speed Index: 4.7 s
4.7 sVisually, the page fills in at 4.7 s (Speed Index). Good is under 3.4 s.
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.
Largest content (LCP) got 18% slower for real visitors
+18%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.3 s to 1.6 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.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
Total Blocking Time: 191 ms
191 msScripts block the page for only 191 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: 9.1 MB in 319 requests
9.1 MBYour homepage downloads 9.1 MB in 319 requests on a phone: images 6.2 MB (56), scripts 1.6 MB (102) and other files 791 KiB (113). Under 2 MB keeps phones on slow connections fast.
11 images far larger than shown
1.4 MB11 images are downloaded at several times the size a phone draws them, for example Zoe_Pawlak.webp at 2,400 px wide, shown at 146 px. Resized copies would save about 1.4 MB.
9 images in older formats
9 images (1.3 MB) 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.
9 images below the first screen load straight away
9 images further down the page (404 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 2.6 g of CO₂ per visit
2.58 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.58 g of CO₂e: 310.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
1 tap target too small
1 tap target is too small or too close together to hit reliably with a finger.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 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.
2 links without text
2 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 should not be empty (3 elements)
Headings should not be empty: 3 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h5), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 123 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 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 6 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (16 characters)
Your title is only 16 characters: “Before Oral Care”. Between 30 and 65 characters leaves room to say what you do and for whom.
2 H1 headlines
There are 2 <h1> headlines (“” and “Before”). One clear main headline is easier for people and search engines.
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.
84 internal links, 17 external
The homepage links to 84 pages on beforecompany.com and 17 external pages.
6 checks passed
Meta description: 103 characters
Your meta description is 103 characters: “Award-winning oral care engineered with a relentless focus on product quality and environmental impact.”.
Canonical URL set
The canonical URL is https://beforecompany.com/.
Structured data in place
Structured data found: Organization and 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://beforecompany.com/sitemap.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing logo, 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,218 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://beforecompany.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
6 pages without a meta description
https://beforecompany.com/collections/mouthwash, https://beforecompany.com/collections/shop, https://beforecompany.com/pages/our-story, https://beforecompany.com/pages/beforecares, https://beforecompany.com/blogs/self_other and https://beforecompany.com/pages/store-locator have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages share a meta description
https://beforecompany.com/products/nano-hydroyapatite-toothpaste-whitening-supermint-us and https://beforecompany.com/products/nano-hydroyapatite-toothpaste-whitening-supermint-travel-size-us use the same meta description. A description written for each page earns more clicks.
14 pages without an H1
https://beforecompany.com/collections/mouthwash, https://beforecompany.com/collections/shop, https://beforecompany.com/pages/our-story, https://beforecompany.com/pages/beforecares, https://beforecompany.com/blogs/self_other and https://beforecompany.com/products/nano-hydroyapatite-toothpaste-whitening-supermint-us and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.
1 page slow to respond
https://beforecompany.com/pages/beforecares took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 35 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
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
2 checks passed
Tap targets are thumb-sized
33 of 34 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 595 words of copy
The homepage carries about 595 words of visible text.
6 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Shop Now”.
12 calls to action
The homepage has 12 calls to action, for example “Shop”, “Shop Now” and “Learn More”.
4 short forms
4 short forms (1 field at most) are right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 24 testimonial or review blocks and 60 customer or partner logos.
Analytics in place
Analytics detected: Google Analytics.
Direct contact links
Visitors can reach you directly: 0 phone links and 2 email links.
Privacy and tracking
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 2 mores (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.
22 cookies set on arrival
22Opening the homepage sets 22 cookies, 1 of them by other companies (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.
45 other companies contacted
Loading the homepage contacts 45 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 beforecompany.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 11 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Yotpo Product Reviews · Klaviyo Email Marketing Sms · Yotpo Loyalty Rewards · Timesact Pre Order · Hulk Form Builder · rechargecdn.com · shareasale.com · gorgias.chat · nfcube.com · cloudfront.net · 9gtb.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
- Framework
- jQuery
- 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 38 issues on beforecompany.com, including 18 speed issues and 3 SEO issues. 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.