Website review, no card needed
bakedbags.com website review
Visit site (opens in a new tab)Reviewed 19 November 202637 issues · 80 checks
This review found 37 issues worth fixing on bakedbags.com, 13 of them high impact, across 80 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
74C- #87,192 of 124,937 reviewed websitesbeats 26%
- #54,692 of 70,069 online storesbeats 18%
- #51,359 of 63,683 Shopify storesbeats 16%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 2.5 s |
| Jun 6, 2026 | 2.5 s |
| Jun 13, 2026 | 2.5 s |
| Jun 20, 2026 | 2.5 s |
| Jun 27, 2026 | 2.5 s |
| Jul 4, 2026 | 2.6 s |
| Jul 11, 2026 | 2.6 s |
| Jul 18, 2026 | 2.6 s |
| Jul 25, 2026 | 2.7 s |
| Aug 1, 2026 | 2.7 s |
| Aug 8, 2026 | 2.7 s |
| Aug 15, 2026 | 2.7 s |
| Aug 22, 2026 | 2.7 s |
| Aug 29, 2026 | 2.6 s |
| Sep 5, 2026 | 2.6 s |
| Sep 12, 2026 | 2.5 s |
| Sep 19, 2026 | 2.6 s |
| Sep 26, 2026 | 2.7 s |
| Oct 3, 2026 | 2.8 s |
| Oct 10, 2026 | 2.8 s |
| Oct 17, 2026 | 2.7 s |
| Oct 24, 2026 | 2.7 s |
| Oct 31, 2026 | 2.7 s |
| Nov 7, 2026 | 2.7 s |
| Nov 14, 2026 | 2.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 212 ms |
| Jun 6, 2026 | 205 ms |
| Jun 13, 2026 | 201 ms |
| Jun 20, 2026 | 195 ms |
| Jun 27, 2026 | 189 ms |
| Jul 4, 2026 | 194 ms |
| Jul 11, 2026 | 194 ms |
| Jul 18, 2026 | 196 ms |
| Jul 25, 2026 | 204 ms |
| Aug 1, 2026 | 207 ms |
| Aug 8, 2026 | 211 ms |
| Aug 15, 2026 | 208 ms |
| Aug 22, 2026 | 205 ms |
| Aug 29, 2026 | 200 ms |
| Sep 5, 2026 | 199 ms |
| Sep 12, 2026 | 198 ms |
| Sep 19, 2026 | 208 ms |
| Sep 26, 2026 | 212 ms |
| Oct 3, 2026 | 214 ms |
| Oct 10, 2026 | 214 ms |
| Oct 17, 2026 | 214 ms |
| Oct 24, 2026 | 215 ms |
| Oct 31, 2026 | 216 ms |
| Nov 7, 2026 | 216 ms |
| Nov 14, 2026 | 212 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.8 s
1.6 s
2.5 s
3.3 s
4.1 s
4.9 s
5.7 s
6.6 s
Speed
Reduce unused JavaScript
4.1 s · 1.1 MBAbout 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.1 s faster on a phone.
Use efficient cache lifetimes
1.1 s · 592 KiB36 files are served with short cache lifetimes, so returning visitors download them again (592 KiB).
Mobile performance score: 41
41/100Your mobile performance score is 41. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 4.5 s
A phone's processor spends 4.5 s on main-thread work while loading, 2.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
3,210 HTML elements
The page has 3,210 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Improve image delivery
750 ms · 964 KiB24 images could be 964 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 750 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Shopify and loox.io and others), adding 2.3 MB and 1.3 s of main-thread time.
Reduce unused CSS
800 ms · 78 KiBAbout 78 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 800 ms faster on a phone.
Google Tag Manager adds 559 ms
559 msGoogle Tag Manager costs a phone 559 ms of main-thread work and 718 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.
Minify JavaScript
460 ms · 89 KiB89 KiB could be saved by minifying JavaScript.
Shopify adds 313 ms
313 msShopify costs a phone 313 ms of main-thread work and 666 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.
Render-blocking requests
300 ms5 files block the first paint until they finish downloading. Deferring or inlining them could save about 300 ms.
zeropartyforms.com adds 86 ms
86 mszeropartyforms.com costs a phone 86 ms of main-thread work and 390 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.
10 long tasks on the main thread
10 long tasks block the main thread while loading, the longest for 241 ms. During a long task the page ignores taps.
Legacy JavaScript
150 ms · 68 KiBPolyfills for old browsers add 68 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
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: 33 ms
33 msYour server sent the HTML in 33 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: 23.0 s
23.0 sYour largest element takes 23.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “LIFE IS BETTER BAKED.”.
Time to Interactive: 31.6 s
31.6 sThe page becomes fully interactive after 31.6 s. Good is under 3.8 s.
Speed Index: 10.9 s
10.9 sVisually, the page fills in at 10.9 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 5.2 s
5.2 sThe first text or image appears after 5.2 s on a phone. Good is under 1.8 s.
Real-user INP: 203 ms
203 msReal visitors wait 203 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 1.9 s
1.9 sReal visitors see the first content after 1.9 s (75th percentile). Good is under 1.8 s.
Total Blocking Time: 598 ms
598 msScripts block taps and scrolling for 598 ms in total while the page loads. Good is under 200 ms.
5 images without width and height
5 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+3%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 212 ms to 212 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+8%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 2.5 s to 2.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user LCP: 2.1 s
2.1 sReal visitors wait 2.1 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.
Real-user TTFB: 560 ms
560 msReal visitors wait 560 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.002
0.002The layout barely moves while loading (CLS 0.002, good is under 0.1).
Images and page weight
Page weight: 42.8 MB in 342 requests
42.8 MBYour homepage downloads 42.8 MB in 342 requests on a phone: media 37.2 MB (4), scripts 2.9 MB (125) and images 1.3 MB (54). Under 2 MB keeps phones on slow connections fast.
1 image in older formats
1 image (82 KiB) 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.
About 12.1 g of CO₂ per visit
12.13 gBy the Sustainable Web Design model, a visit to your homepage emits about 12.13 g of CO₂e: 1455.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
4 images without alt text
4 images have no alt text, which hurts accessibility and image search.
1 checks passed
36 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 36 WCAG 2.2 A/AA and best-practice rules on the phone render: 36 passed and 0 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (10 characters)
Your title is only 10 characters: “Baked Bags”. 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.
4 H1 headlines
There are 4 <h1> headlines (“.logo_image { max-height: unset!important; width:…”, “.logo_image { max-height: unset!important; width:…” and “LIFE IS BETTER BAKED.”). One clear main headline is easier for people and search engines.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
159 internal links, 6 external
The homepage links to 159 pages on bakedbags.com and 6 external pages.
5 checks passed
Meta description: 125 characters
Your meta description is 125 characters: “Baked Bags offers unique Delta-9, products that are as delicious as they are calming. Click here to shop and order your…”.
Canonical URL set
The canonical URL is https://www.bakedbags.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://www.bakedbags.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 (1,265 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.bakedbags.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page points its canonical at the homepage
https://www.bakedbags.com/discount/VIPBEVS declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.
4 pages share 2 titles
/ and https://www.bakedbags.com/discount/VIPBEVS all use the title “Baked Bags”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.
7 pages without a meta description
https://www.bakedbags.com/collections/all, https://www.bakedbags.com/pages/all-products, https://www.bakedbags.com/collections/beverages, https://www.bakedbags.com/collections/variety-packs-bundles, https://www.bakedbags.com/pages/bundle-builder and https://www.bakedbags.com/pages/reward and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.
4 pages without an H1
https://www.bakedbags.com/pages/all-products, https://www.bakedbags.com/pages/bundle-builder, https://www.bakedbags.com/pages/about-us and https://www.bakedbags.com/pages/wholesale-application have no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 49 found) and read each the way a search engine does.
3 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
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
21 small tap targets
21 of 48 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_CERT_AUTHORITY_INVALID”.
Missing source maps
Large scripts ship without source maps.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
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 836 words of copy
The homepage carries about 836 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP CONED MILK CHOCOLATE”.
14 calls to action
The homepage has 14 calls to action, for example “Return to shop”, “Shop all” and “SHOP CONED MILK CHOCOLATE $34.99”.
1 short form
A short form (1 field at most) is right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 8 testimonial or review blocks, 5 customer or partner logos, a star rating and “340,000+ happy customers”.
Analytics in place
Analytics detected: Google Tag Manager and Microsoft Clarity.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 1 more (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.
61 cookies set on arrival
61Opening the homepage sets 61 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.
54 other companies contacted
Loading the homepage contacts 54 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 bakedbags.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 17 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Intelligems A B Testing · Digioh · Wingify · Klaviyo Email Marketing Sms · Hulk Form Builder · Assortion · Uppromote Affiliate · Videowise Video Commerce · Rivo Loyalty Rewards Referrals · Affliate By Secomapp · Stape Remix · Revenuehunt · hulkapps.com · loox.io · amazonaws.com · retention.com · socialsnowball.io
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
- Google Tag Manager | Microsoft Clarity
- Hosting
- Cloudflare
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 37 issues on bakedbags.com, including 22 speed issues, 4 SEO issues and 1 conversion gap. 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.