Website review, no card needed
beamwholesale.com website review
Visit site (opens in a new tab)Reviewed 12 November 202649 issues · 90 checks
This review found 49 issues worth fixing on beamwholesale.com, 16 of them high impact, across 90 checks. The most urgent: reduce unused JavaScript. 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
70C- #91,158 of 108,839 reviewed websitesbeats 14%
- #55,519 of 61,763 online storesbeats 8%
- #51,507 of 56,363 Shopify storesbeats 7%
Closest competitors among Shopify stores
Compare side by sideOne 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
Reduce unused JavaScript
10.5 s · 1.2 MBAbout 1.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 10.5 s faster on a phone.
Render-blocking requests
1.8 s15 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.8 s.
Use efficient cache lifetimes
1.1 s · 181 KiB11 files are served with short cache lifetimes, so returning visitors download them again (181 KiB).
8 third-party services on the page
8 third-party services load with your homepage (YouTube, Bold Commerce and Google CDN and others), adding 3.0 MB and 1.0 s of main-thread time.
Improve image delivery
700 ms · 532 KiB11 images could be 532 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 700 ms faster on a phone.
YouTube adds 821 ms
821 msYouTube costs a phone 821 ms of main-thread work and 2.0 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.
Mobile performance score: 51
51/100Your mobile performance score is 51. Pages that score under 90 lose visitors before the first paint.
Reduce unused CSS
750 ms · 134 KiBAbout 134 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 750 ms faster on a phone.
Main-thread work: 2.7 s
A phone's processor spends 2.7 s on main-thread work while loading, 1.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Shopify adds 17 ms
17 msShopify costs a phone 17 ms of main-thread work and 644 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
250 ms · 45 KiBPolyfills for old browsers add 45 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 250 ms faster on a phone.
8 long tasks on the main thread
8 long tasks block the main thread while loading, the longest for 186 ms. During a long task the page ignores taps.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Minify JavaScript
9 KiB9 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.
Duplicated JavaScript
1 KiB1 KiB JavaScript is shipped twice across bundles.
1 checks passed
Server response: 13 ms
13 msYour server sent the HTML in 13 ms, well inside Google's 600 ms guideline.
Core Web Vitals
First Contentful Paint: 12.5 s
12.5 sThe first text or image appears after 12.5 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 24.6 s
24.6 sYour largest element takes 24.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 25.9 s
25.9 sThe page becomes fully interactive after 25.9 s. Good is under 3.8 s.
Speed Index: 12.5 s
12.5 sVisually, the page fills in at 12.5 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 222 ms
222 msScripts block taps and scrolling for 222 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.
Not enough real-visitor data yet
Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.
1 checks passed
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 4.7 MB in 225 requests
4.7 MBYour homepage downloads 4.7 MB in 225 requests on a phone: scripts 2.4 MB (74), images 1.0 MB (48) and other files 639 KiB (77). Under 2 MB keeps phones on slow connections fast.
7 images far larger than shown
376 KiB7 images are downloaded at several times the size a phone draws them, for example imgpsh_fullsize_anim_30.png at 1,976 px wide, shown at 130 px. Resized copies would save about 376 KiB.
4 images below the first screen load straight away
4 images further down the page (284 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.3 g of CO₂ per visit
1.33 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.33 g of CO₂e: 160.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
3 buttons without a name
3 buttons have no accessible name, so screen readers announce just “button”.
Invalid ARIA attributes
2 elements use ARIA attributes their role does not allow, which confuses screen readers.
13 text elements with low contrast
13 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Hidden but focusable
5 elements hidden from screen readers can still receive keyboard focus.
2 tap targets too small
2 tap targets are too small or too close together to hit reliably with a finger.
26 images without alt text
26 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (11 elements)
All page content should be contained by landmarks: 11 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.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
4 links without text
4 visible links have no text or label, so screen readers cannot say where they go.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
1 checks passed
44 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 10 failed. 1 more 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 (14 characters)
Your title is only 14 characters: “BEAM Wholesale”. 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.
No social preview image
No Open Graph image (also missing: og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
5 links crawlers can't follow
5 links have no real href, so search engines can't follow them.
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
One H1 headline
Your <h1> is empty.
61 internal links, 14 external
The homepage links to 61 pages on beamwholesale.com and 14 external pages.
3 checks passed
Canonical URL set
The canonical URL is https://beamwholesale.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://beamwholesale.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.
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 (698 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://beamwholesale.com/llms.txt (5 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
2 pages without a meta description
https://beamwholesale.com/products/beam-flyers and https://beamwholesale.com/collections/frontpage have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages share a meta description
https://beamwholesale.com/products/insta-lytes and https://beamwholesale.com/products/2oz-insta-lytes%E2%84%A2 use the same meta description. A description written for each page earns more clicks.
6 links to non-canonical URLs
Your homepage links to 6 pages by a URL that isn't their canonical one, for example https://beamwholesale.com/products/electrolyze%E2%84%A2%EF%B8%8F-full-case, whose canonical is https://beamwholesale.com/products/electrolyze%e2%84%a2%ef%b8%8f-full-case. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
1 page with very little text
https://beamwholesale.com/products/beam-flyers 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 25 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.
Titles are unique
Every page we checked has its own title.
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
3 broken images
3 images failed to load on a phone, for example https://cdn.shopify.com/s/files/1/0483/9728/7582/files/121624439_391228068928049_845616559354070719_n.jpg?v=1602948453.
Scrolls sideways on phones
On a 390 px-wide phone the page scrolls sideways, a sign that something is wider than the screen.
8 small tap targets
8 of 31 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
5 third-party cookies
5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “Refused to apply style from 'https://beamwholesale.com/cdn/shop/t/2/assets/tiny.content.min.css?v=5779' because its MIM…”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
1 checks passed
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.
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.
Only about 186 words
The homepage has only about 186 words of visible text; thin pages give Google and first-time buyers little to go on.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
Phone number is not tap-to-call
Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.
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.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Contact Form” and “REQUEST INFO”.
3 calls to action
The homepage has 3 calls to action, for example “Request Info” and “Start shopping”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Phone number on the homepage
Your phone number is on the homepage.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Google Ads and 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.
12 cookies set on arrival
12Opening the homepage sets 12 cookies, 2 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.
25 other companies contacted
Loading the homepage contacts 25 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 beamwholesale.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Go beyond the website
What your $25 Growth Playbook adds
This review found 49 issues on beamwholesale.com, including 16 speed issues, 7 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.