Website review, no card needed
baysmokes.com website review
Visit site (opens in a new tab)Reviewed 4 November 202627 issues · 84 checks
This review found 27 issues worth fixing on baysmokes.com, 6 of them high impact, across 84 checks. The most urgent: page weight: 17.8 MB in 144 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- #21,761 of 121,612 reviewed websitesbeats 77%
- #14,098 of 68,795 online storesbeats 73%
- #13,678 of 62,685 Shopify storesbeats 72%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.1 s |
| May 23, 2026 | 1.1 s |
| May 30, 2026 | 1.1 s |
| Jun 6, 2026 | 1.0 s |
| Jun 13, 2026 | 1.0 s |
| Jun 20, 2026 | 1.1 s |
| Jun 27, 2026 | 1.1 s |
| Jul 4, 2026 | 1.2 s |
| Jul 11, 2026 | 1.2 s |
| Jul 18, 2026 | 1.2 s |
| Jul 25, 2026 | 1.2 s |
| Aug 1, 2026 | 1.2 s |
| Aug 8, 2026 | 1.2 s |
| Aug 15, 2026 | 1.2 s |
| Aug 22, 2026 | 1.2 s |
| Aug 29, 2026 | 1.2 s |
| Sep 5, 2026 | 1.2 s |
| Sep 12, 2026 | 1.2 s |
| Sep 19, 2026 | 1.2 s |
| Sep 26, 2026 | 1.1 s |
| Oct 3, 2026 | 1.1 s |
| Oct 10, 2026 | 1.1 s |
| Oct 17, 2026 | 1.1 s |
| Oct 24, 2026 | 1.2 s |
| Oct 31, 2026 | 1.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 237 ms |
| May 23, 2026 | 236 ms |
| May 30, 2026 | 234 ms |
| Jun 6, 2026 | 236 ms |
| Jun 13, 2026 | 238 ms |
| Jun 20, 2026 | 244 ms |
| Jun 27, 2026 | 241 ms |
| Jul 4, 2026 | 244 ms |
| Jul 11, 2026 | 236 ms |
| Jul 18, 2026 | 226 ms |
| Jul 25, 2026 | 215 ms |
| Aug 1, 2026 | 200 ms |
| Aug 8, 2026 | 195 ms |
| Aug 15, 2026 | 191 ms |
| Aug 22, 2026 | 192 ms |
| Aug 29, 2026 | 192 ms |
| Sep 5, 2026 | 196 ms |
| Sep 12, 2026 | 201 ms |
| Sep 19, 2026 | 206 ms |
| Sep 26, 2026 | 208 ms |
| Oct 3, 2026 | 202 ms |
| Oct 10, 2026 | 199 ms |
| Oct 17, 2026 | 196 ms |
| Oct 24, 2026 | 194 ms |
| Oct 31, 2026 | 192 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
750 ms3 files block the first paint until they finish downloading. Deferring or inlining them could save about 750 ms.
Improve image delivery
454 KiB10 images could be 454 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
1,811 HTML elements
The page has 1,811 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Use efficient cache lifetimes
121 KiB10 files are served with short cache lifetimes, so returning visitors download them again (121 KiB).
8 third-party services on the page
8 third-party services load with your homepage (IPONWEB, mm-uxrv.com and Shopify and others), adding 476 KiB and 60 ms of main-thread time.
1 long task on the main thread
1 long task block the main thread while loading, the longest for 63 ms. During a long task the page ignores taps.
Reduce unused CSS
42 KiBAbout 42 KiB of CSS is downloaded but never applied on this page.
Reduce unused JavaScript
21 KiBAbout 21 KiB of JavaScript is downloaded but never used on this page.
Legacy JavaScript
19 KiBPolyfills for old browsers add 19 KiB JavaScript that modern phones do not need.
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.
3 checks passed
Mobile performance score: 94
94/100Your mobile performance score is 94. That is in Google's “good” band (90 and up).
Main-thread work: 0.7 s
A phone's processor spends 0.7 s on main-thread work while loading, 133 ms of it running JavaScript. That is comfortably low.
Server response: 24 ms
24 msYour server sent the HTML in 24 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: 7.5 s
7.5 sThe page becomes fully interactive after 7.5 s. Good is under 3.8 s.
Real-user INP: 207 ms
207 msReal visitors wait 207 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
58 images without width and height
58 images have no width and height attributes, so the layout jumps as each one loads.
First Contentful Paint: 2.4 s
2.4 sThe first text or image appears after 2.4 s on a phone. Good is under 1.8 s.
Largest content (LCP) held steady for real visitors
+9%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.1 s to 1.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
9 checks passed
Real-user LCP: 1.5 s
1.5 sReal visitors wait 1.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.02
0.02For real visitors the layout shifts by 0.02 (75th percentile). Good is under 0.1.
Real-user FCP: 1.4 s
1.4 sReal visitors see the first content after 1.4 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 711 ms
711 msReal visitors wait 711 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 18% faster for real visitors
-18%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 237 ms to 192 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest Contentful Paint: 2.4 s
2.4 sYour largest element renders in 2.4 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “🔄”.
Cumulative Layout Shift: 0.053
0.053The layout barely moves while loading (CLS 0.053, good is under 0.1).
Speed Index: 2.4 s
2.4 sVisually, the page fills in at 2.4 s (Speed Index), inside the 3.4 s “good” threshold.
Total Blocking Time: 7 ms
7 msScripts block the page for only 7 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 17.8 MB in 144 requests
17.8 MBYour homepage downloads 17.8 MB in 144 requests on a phone: media 15.3 MB (6), images 1.2 MB (47) and scripts 837 KiB (33). Under 2 MB keeps phones on slow connections fast.
2 images far larger than shown
229 KiB2 images are downloaded at several times the size a phone draws them, for example Group_2087328117_1.png at 2,166 px wide, shown at 390 px. Resized copies would save about 229 KiB.
About 5.1 g of CO₂ per visit
5.06 gBy the Sustainable Web Design model, a visit to your homepage emits about 5.06 g of CO₂e: 606.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 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.
Accessibility
28 text elements with low contrast
28 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
8 images without alt text
8 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (7 elements)
All page content should be contained by landmarks: 7 elements on the page fail this check, rated moderate 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.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
Alternative text of images should not be repeated as text (1 element)
Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.
1 checks passed
50 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: 50 passed and 5 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.
Meta description is long (252 characters)
Your meta description is 252 characters; Google truncates after about 160, so the end of your pitch is cut.
Structured data has 2 problems
Structured data found (FAQPage, Organization, Product and WebSite) but with 2 problems, for example “Product: no offers (price) block”.
146 internal links, 13 external
The homepage links to 146 pages on baysmokes.com and 13 external pages.
5 checks passed
Title: 49 characters
Your title is a healthy 49 characters: “Bay Smokes | Shop THCa Cannabis Flower & Products”.
Canonical URL set
The canonical URL is https://baysmokes.com/.
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://baysmokes.com/sitemap.xml.
AI search readiness
No llms.txt
There is no https://baysmokes.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.
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.
Organization data: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (1,888 words), so crawlers that don't run JavaScript still read it.
Other pages
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://baysmokes.com/collections/thca-carts, whose canonical is https://baysmokes.com/collections. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 49 found) and read each the way a search engine does.
6 checks passed
Linked pages load
4 pages of 15 loaded without an error (the rest turned automated requests away).
Every page has a meta description
All 4 pages that loaded have a meta description.
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 4 pages that loaded have a <title>.
Best practices
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
10 distorted images
10 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
2 checks passed
Tap targets are thumb-sized
23 of 25 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 analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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,183 words of copy
The homepage carries about 1,183 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
6 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP TOP FLOWER” and “SHOP ALL”.
26 calls to action
The homepage has 26 calls to action, for example “Contact Us”, “Shop All” and “Shop”.
7 short forms
7 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 35 testimonial or review blocks, 3 customer or partner logos, a star rating, 4 trust badges and “40,000+ Reviews”.
Direct contact links
Visitors can reach you directly: 0 phone links and 2 email links.
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.
8 cookies set on arrival
8Opening the homepage sets 8 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.
21 other companies contacted
Loading the homepage contacts 21 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 baysmokes.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 20 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Yotpo Product Reviews · Triplewhale · Yotpo Loyalty Rewards · Klaviyo Email Marketing Sms · Vitals · Applovin Shop Integration · Pushowl · Aftersell · Freegifts · Age Checker · Upcart · rechargecdn.com · printful.com · route.com · trustpilot.com · socialsnowball.io · bogos.io · govx.com · kount.com · googleapis.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
- Gatsby
- E-commerce
- Shopify
- Hosting
- Shopify
Company
- Headquarters
- Miami
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 27 issues on baysmokes.com, including 8 speed issues, 3 SEO issues and 3 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.