Website review, no card needed
smokea.com website review
Visit site (opens in a new tab)Reviewed 7 November 202626 issues · 83 checks
This review found 26 issues worth fixing on smokea.com, 5 of them high impact, across 83 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
93A- #449 of 99,217 reviewed websitesbeats 99%
- #153 of 54,321 online storesbeats 99%
- #146 of 49,285 Shopify storesbeats 99%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 857 ms |
| May 23, 2026 | 852 ms |
| May 30, 2026 | 846 ms |
| Jun 6, 2026 | 836 ms |
| Jun 13, 2026 | 851 ms |
| Jun 20, 2026 | 852 ms |
| Jun 27, 2026 | 853 ms |
| Jul 4, 2026 | 851 ms |
| Jul 11, 2026 | 846 ms |
| Jul 18, 2026 | 836 ms |
| Jul 25, 2026 | 826 ms |
| Aug 1, 2026 | 825 ms |
| Aug 8, 2026 | 817 ms |
| Aug 15, 2026 | 820 ms |
| Aug 22, 2026 | 825 ms |
| Aug 29, 2026 | 826 ms |
| Sep 5, 2026 | 833 ms |
| Sep 12, 2026 | 848 ms |
| Sep 19, 2026 | 851 ms |
| Sep 26, 2026 | 845 ms |
| Oct 3, 2026 | 840 ms |
| Oct 10, 2026 | 833 ms |
| Oct 17, 2026 | 836 ms |
| Oct 24, 2026 | 838 ms |
| Oct 31, 2026 | 836 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 135 ms |
| May 23, 2026 | 136 ms |
| May 30, 2026 | 136 ms |
| Jun 6, 2026 | 137 ms |
| Jun 13, 2026 | 141 ms |
| Jun 20, 2026 | 141 ms |
| Jun 27, 2026 | 144 ms |
| Jul 4, 2026 | 144 ms |
| Jul 11, 2026 | 144 ms |
| Jul 18, 2026 | 145 ms |
| Jul 25, 2026 | 145 ms |
| Aug 1, 2026 | 147 ms |
| Aug 8, 2026 | 147 ms |
| Aug 15, 2026 | 150 ms |
| Aug 22, 2026 | 150 ms |
| Aug 29, 2026 | 150 ms |
| Sep 5, 2026 | 152 ms |
| Sep 12, 2026 | 153 ms |
| Sep 19, 2026 | 154 ms |
| Sep 26, 2026 | 151 ms |
| Oct 3, 2026 | 148 ms |
| Oct 10, 2026 | 146 ms |
| Oct 17, 2026 | 146 ms |
| Oct 24, 2026 | 146 ms |
| Oct 31, 2026 | 146 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.4 s17 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.4 s.
Improve image delivery
484 KiB7 images could be 484 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Use efficient cache lifetimes
292 KiB12 files are served with short cache lifetimes, so returning visitors download them again (292 KiB).
1,952 HTML elements
The page has 1,952 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Shopify adds 0 ms
0 msShopify costs a phone 0 ms of main-thread work and 624 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.
8 third-party services on the page
8 third-party services load with your homepage (blink-script.com, FontAwesome CDN and Shopify and others), adding 810 KiB and 12 ms of main-thread time.
Reduce unused CSS
86 KiBAbout 86 KiB of CSS is downloaded but never applied on this page.
Minify CSS
6 KiB6 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.
3 checks passed
Mobile performance score: 95
95/100Your mobile performance score is 95. That is in Google's “good” band (90 and up).
Main-thread work: 0.3 s
A phone's processor spends 0.3 s on main-thread work while loading, 32 ms of it running JavaScript. That is comfortably low.
Server response: 8 ms
8 msYour server sent the HTML in 8 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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.
4 images without width and height
4 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+8%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 135 ms to 146 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-2%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 0.9 s to 0.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
11 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 1.0 s
1.0 sReal visitors wait 1.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 177 ms
177 msReal visitors wait 177 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.10
0.10For real visitors the layout shifts by 0.10 (75th percentile). Good is under 0.1.
Real-user FCP: 1.0 s
1.0 sReal visitors see the first content after 1.0 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 485 ms
485 msReal visitors wait 485 ms for your server to start answering (75th percentile). Good is under 800 ms.
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.
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.
Time to Interactive: 2.4 s
2.4 sThe page is fully interactive after 2.4 s.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 0 ms
0 msScripts block the page for only 0 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 2.6 MB in 77 requests
2.6 MBYour homepage downloads 2.6 MB in 77 requests on a phone: images 1.6 MB (25), scripts 765 KiB (35) and stylesheets 118 KiB (10). Under 2 MB keeps phones on slow connections fast.
11 images below the first screen load straight away
11 images further down the page (840 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
4 images far larger than shown
344 KiB4 images are downloaded at several times the size a phone draws them, for example smokea-mushroom-gummy-cubes.jpg at 1,600 px wide, shown at 310 px. Resized copies would save about 344 KiB.
2 images in older formats
2 images (469 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 0.7 g of CO₂ per visit
0.74 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.74 g of CO₂e: 88.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
189 text elements with low contrast
189 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Links look like plain text
30 links inside paragraphs rely on colour alone to stand out.
25 tap targets too small
25 tap targets are too small or too close together to hit reliably with a finger.
Orphan list items
Some list items are not inside a list.
All page content should be contained by landmarks (319 elements)
All page content should be contained by landmarks: 319 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.
4 form fields without a label
4 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.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (6 elements).
2 checks passed
Every image has alt text
All 49 images in the HTML carry an alt attribute.
41 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 41 passed and 7 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Structured data has 2 problems
Structured data found (Organization and WebSite) but with 2 problems, for example “Organization: missing name”.
6 links with vague text
6 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
242 internal links, 12 external
The homepage links to 242 pages on smokea.com and 12 external pages.
7 checks passed
Meta description: 149 characters
Your meta description is 149 characters: “Welcome to SMOKEA®, the world's best online smoke shop, with a wide selection of glass pipes, bongs, rigs, vaporizers, …”.
One H1 headline
Your main headline reads: “Welcome to SMOKEA Online Head and Smoke Shop”.
Title: 44 characters
Your title is a healthy 44 characters: “The World's Best Online Smoke Shop | SMOKEA®”.
Canonical URL set
The canonical URL is https://smokea.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://smokea.com/sitemap.xml.
AI search readiness
Organization data is thin (2 of 6 facts)
Your Organization JSON-LD is missing name, sameAs (social profiles), 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 (4,938 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://smokea.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
2 pages without a meta description
https://smokea.com/blogs/knowledge-base and https://smokea.com/pages/frequently-asked-questions have no meta description, so Google writes the search snippet from whatever text it finds.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 142 found) and read each the way a search engine does.
6 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.
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
6 small tap targets
6 of 28 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Refused to execute script from 'https://smokea.com/' because its MIME type ('text/html') is not executable, and strict …”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
About 5,117 words of copy
The homepage carries about 5,117 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 BY”.
6 calls to action
The homepage has 6 calls to action, for example “Shop By”, “Shop by Brand” and “Order today”.
12 short forms
12 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 48 testimonial or review blocks and 1 trust badge.
Analytics in place
Analytics detected: Google Tag Manager and TikTok Pixel.
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
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Amplitude, FullStory, Google Ads, Google Analytics and Google Tag Manager 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.
23 cookies set on arrival
23Opening the homepage sets 23 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.
58 other companies contacted
Loading the homepage contacts 58 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 smokea.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 15 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Wyllo Formerly Nofraud · Reamaze Live Chat Helpdesk · Route Protection Tracking · Upsell Koala Discount · Pushowl · Watchlist · zoorix.com · trustpilot.com · trafficmanager.net · azureedge.net · printful.com · smile.io · b-cdn.net · kxcdn.com · Swym Wishlist Plus
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 Tag Manager | FullStory
- Hosting
- Shopify
Company
- Headquarters
- O'Fallon
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 26 issues on smokea.com, including 7 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.