Website review, no card needed
yogibo.ca website review
Visit site (opens in a new tab)Reviewed 11 November 202628 issues · 77 checks
This review found 28 issues worth fixing on yogibo.ca, 3 of them high impact, across 77 checks. The most urgent: 2 text elements with low contrast. 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
86B- #9,628 of 96,043 reviewed websitesbeats 86%
- #5,658 of 51,940 online storesbeats 84%
- #5,483 of 47,037 Shopify storesbeats 83%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 979 ms |
| May 30, 2026 | 946 ms |
| Jun 6, 2026 | 941 ms |
| Jun 13, 2026 | 962 ms |
| Jun 20, 2026 | 966 ms |
| Jun 27, 2026 | 975 ms |
| Jul 4, 2026 | 989 ms |
| Jul 11, 2026 | 976 ms |
| Jul 18, 2026 | 942 ms |
| Jul 25, 2026 | 879 ms |
| Aug 1, 2026 | 809 ms |
| Aug 8, 2026 | 728 ms |
| Aug 15, 2026 | 725 ms |
| Aug 22, 2026 | 746 ms |
| Aug 29, 2026 | 754 ms |
| Sep 5, 2026 | 761 ms |
| Sep 12, 2026 | 755 ms |
| Sep 19, 2026 | 739 ms |
| Sep 26, 2026 | 745 ms |
| Oct 3, 2026 | 760 ms |
| Oct 10, 2026 | 756 ms |
| Oct 17, 2026 | 763 ms |
| Oct 24, 2026 | 746 ms |
| Oct 31, 2026 | 756 ms |
| Nov 7, 2026 | 760 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 88 ms |
| May 30, 2026 | 88 ms |
| Jun 6, 2026 | 90 ms |
| Jun 13, 2026 | 93 ms |
| Jun 20, 2026 | 92 ms |
| Jun 27, 2026 | 93 ms |
| Jul 4, 2026 | 94 ms |
| Jul 11, 2026 | 95 ms |
| Jul 18, 2026 | 94 ms |
| Jul 25, 2026 | 87 ms |
| Aug 1, 2026 | 82 ms |
| Aug 8, 2026 | 78 ms |
| Aug 15, 2026 | 76 ms |
| Aug 22, 2026 | 75 ms |
| Aug 29, 2026 | 74 ms |
| Sep 5, 2026 | 74 ms |
| Sep 12, 2026 | 72 ms |
| Sep 19, 2026 | 73 ms |
| Sep 26, 2026 | 73 ms |
| Oct 3, 2026 | 72 ms |
| Oct 10, 2026 | 73 ms |
| Oct 17, 2026 | 72 ms |
| Oct 24, 2026 | 71 ms |
| Oct 31, 2026 | 73 ms |
| Nov 7, 2026 | 79 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
Use efficient cache lifetimes
900 ms · 155 KiB10 files are served with short cache lifetimes, so returning visitors download them again (155 KiB).
Mobile performance score: 74
74/100Your mobile performance score is 74. Pages that score under 90 lose visitors before the first paint.
Improve image delivery
400 ms · 478 KiB8 images could be 478 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 400 ms faster on a phone.
Reduce unused JavaScript
300 ms · 75 KiBAbout 75 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.
Google Fonts adds 0 ms
0 msGoogle Fonts costs a phone 0 ms of main-thread work and 299 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 (govx.com, 9gtb.com and shoppinggives.com and others), adding 594 KiB and 132 ms of main-thread time.
Legacy JavaScript
8 KiBPolyfills for old browsers add 8 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.
2 checks passed
Main-thread work: 0.9 s
A phone's processor spends 0.9 s on main-thread work while loading, 342 ms of it running JavaScript. That is comfortably low.
Server response: 4 ms
4 msYour server sent the HTML in 4 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 7.4 s
7.4 sYour largest element takes 7.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Woman relaxing on a Yogibo Max in a cozy holiday living roo…”.
Time to Interactive: 7.5 s
7.5 sThe page becomes fully interactive after 7.5 s. Good is under 3.8 s.
Speed Index: 3.5 s
3.5 sVisually, the page fills in at 3.5 s (Speed Index). Good is under 3.4 s.
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.1 s
1.1 sReal visitors wait 1.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 85 ms
85 msReal visitors wait 85 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.06
0.06For real visitors the layout shifts by 0.06 (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: 468 ms
468 msReal visitors wait 468 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 14% faster for real visitors
-14%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 88 ms to 79 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 21% faster for real visitors
-21%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.0 s to 0.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 1.8 s
1.8 sThe first text or image appears after 1.8 s, inside the 1.8 s “good” threshold.
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.4 MB in 138 requests
2.4 MBYour homepage downloads 2.4 MB in 138 requests on a phone: images 989 KiB (16), other files 717 KiB (73) and scripts 357 KiB (37). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
hero-hol-4.webp is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
4 images in older formats
4 images (899 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.
4 images far larger than shown
360 KiB4 images are downloaded at several times the size a phone draws them, for example hero-hol-4.webp at 1,534 px wide, shown at 390 px. Resized copies would save about 360 KiB.
About 0.7 g of CO₂ per visit
0.67 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.67 g of CO₂e: 80.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
2 text elements with low contrast
2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
All page content should be contained by landmarks (9 elements)
All page content should be contained by landmarks: 9 elements on the page fail this check, rated moderate by axe-core.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
2 checks passed
Every image has alt text
All 17 images in the HTML carry an alt attribute.
44 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 47 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 3 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (79 characters)
Your title is 79 characters, so Google will cut it off around 60: “Yogibo - Best Bean Bag Chairs, Life Adaptable Furniture, and Comforts — Yogibo®”.
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 (“The Max.HibernationSeason.”, “Gather Round.Settle In.Stay Late.” and “No Plans.No Regrets.”). One clear main headline is easier for people and search engines.
Meta description is long (310 characters)
Your meta description is 310 characters; Google truncates after about 160, so the end of your pitch is cut.
No social preview image
No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
124 internal links, 4 external
The homepage links to 124 pages on yogibo.ca and 4 external pages.
3 checks passed
Canonical URL set
The canonical URL is https://yogibo.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://yogibo.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 (696 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://yogibo.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
4 pages share a meta description
https://yogibo.com/collections/modju-bundles, https://yogibo.com/collections/all, https://yogibo.com/pages/collabs-events and https://yogibo.com/pages/sensory use the same meta description. A description written for each page earns more clicks.
2 pages without an H1
https://yogibo.com/collections/modju-bundles and https://yogibo.com/collections/all have no <h1> headline, so visitors and search engines get no clear main topic.
5 pages slow to respond
https://yogibo.com/products/yogibo-double-short, https://yogibo.com/products/yogibo-pod-x, https://yogibo.com/products/yogibo-lounger, https://yogibo.com/products/yogibo-mini and https://yogibo.com/pages/sensory took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 24 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.
Every page has a meta description
All 15 pages that loaded have a meta description.
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 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.
2 checks passed
Tap targets are thumb-sized
68 of 80 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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 929 words of copy
The homepage carries about 929 words of visible text.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP THE MAX” and “SHOP ALL”.
11 calls to action
The homepage has 11 calls to action, for example “Shop the Max”, “Shop All” and “Shop Now”.
2 short forms
2 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 a star rating.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, Meta Pixel, Pinterest Tag and TikTok Pixel (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.
16 cookies set on arrival
16Opening the homepage sets 16 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.
29 other companies contacted
Loading the homepage contacts 29 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 yogibo.ca, 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 7 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
govx.com · gorgias.chat · loox.io · shoppinggives.com · amazonaws.com · 9gtb.com · vizbl.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
- CMS
- WordPress
- E-commerce
- Shopify
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 28 issues on yogibo.ca, including 8 speed issues, 6 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.