Website review, no card needed
owletcare.ca website review
Visit site (opens in a new tab)Reviewed 8 November 202625 issues · 75 checks
This review found 25 issues worth fixing on owletcare.ca, 5 of them high impact, across 75 checks. The most urgent: page weight: 26.2 MB in 257 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
89B- #2,995 of 93,740 reviewed websitesbeats 95%
- #1,478 of 50,153 online storesbeats 95%
- #1,431 of 45,298 Shopify storesbeats 95%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 971 ms |
| May 23, 2026 | 971 ms |
| May 30, 2026 | 940 ms |
| Jun 6, 2026 | 907 ms |
| Jun 13, 2026 | 863 ms |
| Jun 20, 2026 | 872 ms |
| Jun 27, 2026 | 904 ms |
| Jul 4, 2026 | 881 ms |
| Jul 11, 2026 | 872 ms |
| Jul 18, 2026 | 842 ms |
| Jul 25, 2026 | 806 ms |
| Aug 1, 2026 | 804 ms |
| Aug 8, 2026 | 797 ms |
| Aug 15, 2026 | 831 ms |
| Aug 22, 2026 | 832 ms |
| Aug 29, 2026 | 843 ms |
| Sep 5, 2026 | 849 ms |
| Sep 12, 2026 | 856 ms |
| Sep 19, 2026 | 848 ms |
| Sep 26, 2026 | 834 ms |
| Oct 3, 2026 | 808 ms |
| Oct 10, 2026 | 829 ms |
| Oct 17, 2026 | 833 ms |
| Oct 24, 2026 | 843 ms |
| Oct 31, 2026 | 866 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 103 ms |
| May 23, 2026 | 97 ms |
| May 30, 2026 | 104 ms |
| Jun 6, 2026 | 108 ms |
| Jun 13, 2026 | 112 ms |
| Jun 20, 2026 | 112 ms |
| Jun 27, 2026 | 105 ms |
| Jul 4, 2026 | 104 ms |
| Jul 11, 2026 | 104 ms |
| Jul 18, 2026 | 104 ms |
| Jul 25, 2026 | 111 ms |
| Aug 1, 2026 | 112 ms |
| Aug 8, 2026 | 113 ms |
| Aug 15, 2026 | 113 ms |
| Aug 22, 2026 | 113 ms |
| Aug 29, 2026 | 113 ms |
| Sep 5, 2026 | 107 ms |
| Sep 12, 2026 | 101 ms |
| Sep 19, 2026 | 101 ms |
| Sep 26, 2026 | 103 ms |
| Oct 3, 2026 | 109 ms |
| Oct 10, 2026 | 112 ms |
| Oct 17, 2026 | 113 ms |
| Oct 24, 2026 | 115 ms |
| Oct 31, 2026 | 115 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
1.0 s22 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.0 s.
Mobile performance score: 89
89/100Your mobile performance score is 89. Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
300 ms · 184 KiBAbout 184 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.
8 third-party services on the page
8 third-party services load with your homepage (Klaviyo, 506.io and Bazaarvoice and others), adding 400 KiB and 189 ms of main-thread time.
Reduce unused CSS
150 ms · 29 KiBAbout 29 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
Improve image delivery
121 KiB7 images could be 121 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Use efficient cache lifetimes
68 KiB11 files are served with short cache lifetimes, so returning visitors download them again (68 KiB).
2 long tasks on the main thread
2 long tasks block the main thread while loading, the longest for 57 ms. During a long task the page ignores taps.
Legacy JavaScript
53 KiBPolyfills for old browsers add 53 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: 1.1 s
A phone's processor spends 1.1 s on main-thread work while loading, 392 ms of it running JavaScript. That is comfortably low.
Server response: 6 ms
6 msYour server sent the HTML in 6 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Speed Index: 5.5 s
5.5 sVisually, the page fills in at 5.5 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.6 s
2.6 sThe first text or image appears after 2.6 s on a phone. Good is under 1.8 s.
Time to Interactive: 5.6 s
5.6 sThe page becomes fully interactive after 5.6 s. Good is under 3.8 s.
Largest Contentful Paint: 2.6 s
2.6 sYour largest element takes 2.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “O”. Most of its time is element render delay (2.4 s).
Tap response (INP) got 15% slower for real visitors
+15%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 103 ms to 115 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
9 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: 0.8 s
0.8 sReal visitors wait 0.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 121 ms
121 msReal visitors wait 121 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
Real-user FCP: 0.8 s
0.8 sReal visitors see the first content after 0.8 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 310 ms
310 msReal visitors wait 310 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 12% faster for real visitors
-12%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.0 s to 0.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 8 ms
8 msScripts block the page for only 8 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 26.2 MB in 257 requests
26.2 MBYour homepage downloads 26.2 MB in 257 requests on a phone: media 24.2 MB (2), other files 836 KiB (113) and scripts 681 KiB (89). Under 2 MB keeps phones on slow connections fast.
About 7.4 g of CO₂ per visit
7.42 gBy the Sustainable Web Design model, a visit to your homepage emits about 7.42 g of CO₂e: 890.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 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.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
All page content should be contained by landmarks (2 elements)
All page content should be contained by landmarks: 2 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.
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 (h1 → h5), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 23 images in the HTML carry an alt attribute.
43 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: 43 passed and 4 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (67 characters)
Your title is 67 characters, so Google will cut it off around 60: “Dream Sock: Baby Oxygen Monitor & Heart Rate Monitor – Owlet Canada”.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
39 internal links, 10 external
The homepage links to 39 pages on owletcare.ca and 10 external pages.
6 checks passed
Meta description: 145 characters
Your meta description is 145 characters: “Owlet has created a baby heart rate and oxygen monitor to help give parents some peace of mind. Want to know more? Visi…”.
One H1 headline
Your main headline reads: “M o n i t o r W h a t M a t t e r s M o s t”.
Canonical URL set
The canonical URL is https://owletcare.ca/.
Structured data in place
Structured data found: Organization and WebSite.
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://owletcare.ca/sitemap.xml.
AI search readiness
4 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 (225 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://owletcare.ca/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a title
https://owletcare.ca/customer_authentication/redirect has no <title>, so Google invents the link text in results.
1 linked page hidden from search
https://owletcare.ca/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
4 pages without a meta description
https://owletcare.ca/customer_authentication/redirect, https://owletcare.ca/policies/privacy-policy, https://owletcare.ca/policies/terms-of-service and https://owletcare.ca/policies/refund-policy have no meta description, so Google writes the search snippet from whatever text it finds.
8 pages without an H1
https://owletcare.ca/products/dream-sight-camera-floor-stand, https://owletcare.ca/products/dream-duo-3, https://owletcare.ca/products/dream-sight, https://owletcare.ca/products/owlet-dream-sock, https://owletcare.ca/collections/all and https://owletcare.ca/customer_authentication/redirect and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.
11 internal pages checked
We fetched 11 pages linked from your homepage and read each the way a search engine does.
3 checks passed
Linked pages load
All 11 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.
Best practices
9 small tap targets
9 of 17 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Refused to apply style from 'https://owletcare.ca/cdn/shop/t/200/assets/tiny.content.min.css?v=47501' because its MIME …”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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.
Only about 188 words
The homepage has only about 188 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
3 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Shop Now” and “Shop Dream Sock”.
8 calls to action
The homepage has 8 calls to action, for example “Shop Now”, “Shop All” and “Shop Dream Sock”.
6 short forms
6 short forms (2 fields at most) are right on the homepage.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta 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.
12 cookies set on arrival
12Opening the homepage sets 12 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.
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 owletcare.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 8 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Klaviyo Email Marketing Sms · Geoip Country Redirect · Eg Auto Add To Cart · bazaarvoice.com · yellow.ai · cloudfront.net · spicegems.org · refersion.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
- E-commerce
- Shopify
- Hosting
- Shopify
Company
- Headquarters
- Surrey
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 25 issues on owletcare.ca, including 7 speed issues, 2 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.