Website review, no card needed
oolabe.com website review
Visit site (opens in a new tab)Reviewed 20 November 202623 issues · 69 checks
This review found 23 issues worth fixing on oolabe.com, 3 of them high impact, across 69 checks. The most urgent: aRIA attributes must conform to valid values (2 elements). 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
88B- #5,714 of 120,410 reviewed websitesbeats 93%
- #3,135 of 68,161 online storesbeats 93%
- #3,035 of 62,115 Shopify storesbeats 93%
Closest competitors among Shopify stores
Compare side by sideOne score from every part of this review. How it works
Speed
Render-blocking requests
300 ms3 files block the first paint until they finish downloading. Deferring or inlining them could save about 300 ms.
2,980 HTML elements
The page has 2,980 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
3 third-party services on the page
3 third-party services load with your homepage (Shopify, smile.io and shop.app), adding 1.1 MB and 42 ms of main-thread time.
Shopify adds 30 ms
30 msShopify costs a phone 30 ms of main-thread work and 924 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.
Improve image delivery
145 KiB1 image could be 145 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
2 long tasks on the main thread
2 long tasks block the main thread while loading, the longest for 107 ms. During a long task the page ignores taps.
Reduce unused CSS
35 KiBAbout 35 KiB of CSS is downloaded but never applied on this page.
Use efficient cache lifetimes
7 KiB4 files are served with short cache lifetimes, so returning visitors download them again (7 KiB).
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: 93
93/100Your mobile performance score is 93. That is in Google's “good” band (90 and up).
Main-thread work: 2.0 s
A phone's processor spends 2.0 s on main-thread work while loading, 495 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.3 s
5.3 sVisually, the page fills in at 5.3 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 5.7 s
5.7 sThe page becomes fully interactive after 5.7 s. Good is under 3.8 s.
First Contentful Paint: 2.0 s
2.0 sThe first text or image appears after 2.0 s on a phone. Good is under 1.8 s.
Not enough real-visitor data yet
Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.
3 checks passed
Largest Contentful Paint: 2.0 s
2.0 sYour largest element renders in 2.0 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “CURATED KIDS’ CONSIGNMENT BOUTIQUE — FROM NEWBORN TO TEEN. …”.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 52 ms
52 msScripts block the page for only 52 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 2.3 MB in 461 requests
2.3 MBYour homepage downloads 2.3 MB in 461 requests on a phone: images 894 KiB (254), other files 663 KiB (55) and scripts 464 KiB (144). Under 2 MB keeps phones on slow connections fast.
About 0.6 g of CO₂ per visit
0.65 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.65 g of CO₂e: 77.7 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
ARIA attributes must conform to valid values (2 elements)
ARIA attributes must conform to valid values: 2 elements on the page fail this check, rated critical by axe-core.
Hidden but focusable
2 elements hidden from screen readers can still receive keyboard focus.
All page content should be contained by landmarks (13 elements)
All page content should be contained by landmarks: 13 elements on the page fail this check, rated moderate by axe-core.
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 (8 elements)
Alternative text of images should not be repeated as text: 8 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h4 → h6), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 266 images in the HTML carry an alt attribute.
46 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 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
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
3 H1 headlines
There are 3 <h1> headlines (“Oolabe”, “Curated kids’ consignment boutique — from newborn…” and “Stay in the loop with juicy updates - sign up now!”). One clear main headline is easier for people and search engines.
40 internal links, 5 external
The homepage links to 40 pages on oolabe.com and 5 external pages.
6 checks passed
Meta description: 119 characters
Your meta description is 119 characters: “Consign and buy gently used baby and kids' clothing, maternity, nursery essentials, gear, toys, puzzles, books and more”.
Title: 42 characters
Your title is a healthy 42 characters: “OOLABE Kids' Consignment Boutique – Oolabe”.
Canonical URL set
The canonical URL is https://oolabe.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://oolabe.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,194 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://oolabe.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
5 pages without a meta description
https://oolabe.com/collections/all, https://oolabe.com/blogs/5-under-oolabethrift, https://oolabe.com/collections/christmas-holiday, https://oolabe.com/collections/toys and https://oolabe.com/collections/furniture have no meta description, so Google writes the search snippet from whatever text it finds.
4 links to non-canonical URLs
Your homepage links to 4 pages by a URL that isn't their canonical one, for example https://oolabe.com/collections/nursery-essentials/products/ways-to-play-4-in-1-walker-ford-mustang-fa0f9, whose canonical is https://oolabe.com/products/ways-to-play-4-in-1-walker-ford-mustang-fa0f9. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
6 pages without an H1
https://oolabe.com/collections/christmas-holiday, https://oolabe.com/collections/infant-outerwear, https://oolabe.com/collections/toys, https://oolabe.com/collections/books-books-books, https://oolabe.com/collections/nursery-essentials and https://oolabe.com/collections/furniture 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 24 found) and read each the way a search engine does.
4 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
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
22 of 24 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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 477 words of copy
The homepage carries about 477 words of visible text.
4 checks passed
7 calls to action
The homepage has 7 calls to action, for example “Quick shop”, “Shop Gently Used” and “Shop Maternity”.
6 short forms
6 short forms (2 fields at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 22 testimonial or review blocks and a star rating.
Direct contact links
Visitors can reach you directly: 1 phone link and 0 email links.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Google Tag Manager 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.
9 cookies set on arrival
9Opening the homepage sets 9 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.
10 other companies contacted
Loading the homepage contacts 10 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 oolabe.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Apps on your store
No apps were seen in the code your storefront loads.
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
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 23 issues on oolabe.com, including 7 speed issues, 2 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.