Website review, no card needed
beyondalpha.co website review
Visit site (opens in a new tab)Reviewed 12 November 202646 issues · 87 checks
This review found 46 issues worth fixing on beyondalpha.co, 13 of them high impact, across 87 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
77C- #61,319 of 109,075 reviewed websitesbeats 39%
- #39,756 of 61,793 online storesbeats 31%
- #37,876 of 56,373 Shopify storesbeats 28%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 2.5 s |
| May 30, 2026 | 2.4 s |
| Jun 6, 2026 | 2.5 s |
| Jun 13, 2026 | 2.6 s |
| Jun 20, 2026 | 2.7 s |
| Jun 27, 2026 | 2.8 s |
| Jul 4, 2026 | 3.0 s |
| Jul 11, 2026 | 3.1 s |
| Jul 18, 2026 | 3.2 s |
| Jul 25, 2026 | 3.1 s |
| Aug 1, 2026 | 3.0 s |
| Aug 8, 2026 | 3.1 s |
| Aug 15, 2026 | 3.1 s |
| Aug 22, 2026 | 3.1 s |
| Aug 29, 2026 | 3.2 s |
| Sep 5, 2026 | 3.2 s |
| Sep 12, 2026 | 3.3 s |
| Sep 19, 2026 | 3.3 s |
| Sep 26, 2026 | 3.4 s |
| Oct 3, 2026 | 3.3 s |
| Oct 10, 2026 | 3.3 s |
| Oct 17, 2026 | 3.2 s |
| Oct 24, 2026 | 3.1 s |
| Oct 31, 2026 | 3.1 s |
| Nov 7, 2026 | 3.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 121 ms |
| May 30, 2026 | 120 ms |
| Jun 6, 2026 | 124 ms |
| Jun 13, 2026 | 131 ms |
| Jun 20, 2026 | 137 ms |
| Jun 27, 2026 | 145 ms |
| Jul 4, 2026 | 145 ms |
| Jul 11, 2026 | 145 ms |
| Jul 18, 2026 | 145 ms |
| Jul 25, 2026 | 139 ms |
| Aug 1, 2026 | 137 ms |
| Aug 8, 2026 | 137 ms |
| Aug 15, 2026 | 138 ms |
| Aug 22, 2026 | 143 ms |
| Aug 29, 2026 | 154 ms |
| Sep 5, 2026 | 162 ms |
| Sep 12, 2026 | 170 ms |
| Sep 19, 2026 | 166 ms |
| Sep 26, 2026 | 172 ms |
| Oct 3, 2026 | 173 ms |
| Oct 10, 2026 | 169 ms |
| Oct 17, 2026 | 171 ms |
| Oct 24, 2026 | 170 ms |
| Oct 31, 2026 | 164 ms |
| Nov 7, 2026 | 163 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
2.3 s31 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.3 s.
Use efficient cache lifetimes
1.2 s · 321 KiB28 files are served with short cache lifetimes, so returning visitors download them again (321 KiB).
Main-thread work: 4.1 s
A phone's processor spends 4.1 s on main-thread work while loading, 2.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (Shopify, Facebook and Klaviyo and others), adding 2.5 MB and 751 ms of main-thread time.
Mobile performance score: 55
55/100Your mobile performance score is 55. Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
450 ms · 420 KiBAbout 420 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.
Improve image delivery
780 KiB7 images could be 780 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Legacy JavaScript
600 ms · 51 KiBPolyfills for old browsers add 51 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 600 ms faster on a phone.
Reduce unused CSS
520 ms · 95 KiBAbout 95 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 520 ms faster on a phone.
Shopify adds 245 ms
245 msShopify costs a phone 245 ms of main-thread work and 1.6 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.
8 long tasks on the main thread
8 long tasks block the main thread while loading, the longest for 250 ms. During a long task the page ignores taps.
2,303 HTML elements
The page has 2,303 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Klaviyo adds 108 ms
108 msKlaviyo costs a phone 108 ms of main-thread work and 326 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.
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.
1 checks passed
Server response: 21 ms
21 msYour server sent the HTML in 21 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.
Largest Contentful Paint: 15.7 s
15.7 sYour largest element takes 15.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Over 2724 Five Star Reviews Never Settle Try Beyond Alpha t…”.
Time to Interactive: 20.1 s
20.1 sThe page becomes fully interactive after 20.1 s. Good is under 3.8 s.
Speed Index: 9.2 s
9.2 sVisually, the page fills in at 9.2 s (Speed Index). Good is under 3.4 s.
Real-user LCP: 2.5 s
2.5 sReal visitors wait 2.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Tap response (INP) got 36% slower for real visitors
+36%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 121 ms to 163 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 32% slower for real visitors
+32%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 2.5 s to 3.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 2.3 s
2.3 sReal visitors see the first content after 2.3 s (75th percentile). Good is under 1.8 s.
First Contentful Paint: 2.6 s
2.6 sThe first text or image appears after 2.6 s on a phone. Good is under 1.8 s.
Total Blocking Time: 337 ms
337 msScripts block taps and scrolling for 337 ms in total while the page loads. Good is under 200 ms.
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: 171 ms
171 msReal visitors wait 171 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.02
0.02For real visitors the layout shifts by 0.02 (75th percentile). Good is under 0.1.
Real-user TTFB: 554 ms
554 msReal visitors wait 554 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.007
0.007The layout barely moves while loading (CLS 0.007, good is under 0.1).
Images and page weight
Page weight: 6.3 MB in 364 requests
6.3 MBYour homepage downloads 6.3 MB in 364 requests on a phone: images 3.3 MB (47), scripts 1.5 MB (114) and other files 954 KiB (151). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
95227d5d30f245e33532bc6f4925cdd301484a3e.jpg weighs 1.3 MB. On a phone connection a single image that size takes seconds.
1 image in older formats
1 image (1.3 MB) 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.
7 images below the first screen load straight away
7 images further down the page (780 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
5 images far larger than shown
335 KiB5 images are downloaded at several times the size a phone draws them, for example TB.webp at 1,600 px wide, shown at 390 px. Resized copies would save about 335 KiB.
About 1.8 g of CO₂ per visit
1.78 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.78 g of CO₂e: 213.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
11 text elements with low contrast
11 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
4 images without alt text
4 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (2 elements)
All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.
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.
Headings skip levels
Headings skip levels (h1 → h6 and h1 → h3), which makes the page harder to scan with a screen reader.
1 checks passed
47 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 5 failed. 4 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.
Title is short (12 characters)
Your title is only 12 characters: “Beyond Alpha”. Between 30 and 65 characters leaves room to say what you do and for whom.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
27 H1 headlines
There are 27 <h1> headlines (“Beyond Alpha”, “Mystery Halloween SALE!” and “FATHER’S DAY DEALS”). One clear main headline is easier for people and search engines.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
82 internal links, 6 external
The homepage links to 82 pages on beyondalpha.co and 6 external pages.
3 checks passed
Canonical URL set
The canonical URL is https://beyondalpha.co/.
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://beyondalpha.co/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.
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,560 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://beyondalpha.co/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
4 pages without a meta description
https://beyondalpha.co/pages/reviews, https://beyondalpha.co/collections/fathers-day-campaign, https://beyondalpha.co/blogs/articles and https://beyondalpha.co/collections/all-products have no meta description, so Google writes the search snippet from whatever text it finds.
4 pages without an H1
https://beyondalpha.co/pages/ingredients, https://beyondalpha.co/pages/reviews, https://beyondalpha.co/blogs/articles and https://beyondalpha.co/products/alpha-gut-reset have no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://beyondalpha.co/products/alpha-gut-reset has 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 29 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
1 broken image
1 image failed to load on a phone, for example https://d3k81ch9hvuctc.cloudfront.net/company/Wj6q8f/images/3fb17079-6d8a-4662-945e-c5ac71f3f62a.png.
5 JavaScript errors while loading
5 errors were logged to the browser console while the page loaded, for example “Uncaught TypeError: Cannot read properties of undefined (reading 'replaceAll')”.
2 checks passed
Tap targets are thumb-sized
11 of 12 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 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.
About 1,386 words of copy
The homepage carries about 1,386 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
7 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP PRODUCTS”.
17 calls to action
The homepage has 17 calls to action, for example “Get Started”, “Shop” and “SHOP PRODUCTS”.
6 short forms
6 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 3 testimonial or review blocks and 17 trust badges.
Analytics in place
Analytics detected: Meta Pixel and Microsoft Clarity.
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
8 trackers load before any consent
8Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 3 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.
36 cookies set on arrival
36Opening the homepage sets 36 cookies, 3 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.
55 other companies contacted
Loading the homepage contacts 55 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 beyondalpha.co, 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 12 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Intelligems A B Testing · Instant Ai Page Builder · Okendo · Klaviyo Email Marketing Sms · Gempages Builder · Triplewhale · Eg Auto Add To Cart · Rivo Loyalty Rewards Referrals · Applovin Shop Integration · Loop Returns · rechargecdn.com · useamp.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
- Bootstrap
- E-commerce
- Shopify
- Analytics
- Microsoft Clarity
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 46 issues on beyondalpha.co, including 24 speed issues, 5 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.