Website review, no card needed
wildridecarrier.com website review
Visit site (opens in a new tab)Reviewed 8 November 202632 issues · 88 checks
This review found 32 issues worth fixing on wildridecarrier.com, 13 of them high impact, across 88 checks. The most urgent: improve image delivery. 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
85B- #16,549 of 123,216 reviewed websitesbeats 82%
- #10,438 of 69,453 online storesbeats 80%
- #10,136 of 63,227 Shopify storesbeats 78%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.5 s |
| May 23, 2026 | 1.4 s |
| May 30, 2026 | 1.4 s |
| Jun 6, 2026 | 1.4 s |
| Jun 13, 2026 | 1.4 s |
| Jun 20, 2026 | 1.4 s |
| Jun 27, 2026 | 1.4 s |
| Jul 4, 2026 | 1.4 s |
| Jul 11, 2026 | 1.4 s |
| Jul 18, 2026 | 1.4 s |
| Jul 25, 2026 | 1.4 s |
| Aug 1, 2026 | 1.4 s |
| Aug 8, 2026 | 1.4 s |
| Aug 15, 2026 | 1.4 s |
| Aug 22, 2026 | 1.5 s |
| Aug 29, 2026 | 1.5 s |
| Sep 5, 2026 | 1.5 s |
| Sep 12, 2026 | 1.5 s |
| Sep 19, 2026 | 1.5 s |
| Sep 26, 2026 | 1.4 s |
| Oct 3, 2026 | 1.4 s |
| Oct 10, 2026 | 1.4 s |
| Oct 17, 2026 | 1.4 s |
| Oct 24, 2026 | 1.5 s |
| Oct 31, 2026 | 1.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 164 ms |
| May 23, 2026 | 155 ms |
| May 30, 2026 | 154 ms |
| Jun 6, 2026 | 155 ms |
| Jun 13, 2026 | 154 ms |
| Jun 20, 2026 | 156 ms |
| Jun 27, 2026 | 155 ms |
| Jul 4, 2026 | 159 ms |
| Jul 11, 2026 | 162 ms |
| Jul 18, 2026 | 162 ms |
| Jul 25, 2026 | 163 ms |
| Aug 1, 2026 | 163 ms |
| Aug 8, 2026 | 167 ms |
| Aug 15, 2026 | 170 ms |
| Aug 22, 2026 | 166 ms |
| Aug 29, 2026 | 161 ms |
| Sep 5, 2026 | 150 ms |
| Sep 12, 2026 | 142 ms |
| Sep 19, 2026 | 141 ms |
| Sep 26, 2026 | 139 ms |
| Oct 3, 2026 | 140 ms |
| Oct 10, 2026 | 138 ms |
| Oct 17, 2026 | 140 ms |
| Oct 24, 2026 | 152 ms |
| Oct 31, 2026 | 158 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
4.1 s
8.1 s
12.2 s
16.3 s
20.3 s
24.4 s
28.5 s
32.5 s
Speed
Improve image delivery
4.9 s · 1.6 MB4 images could be 1.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 4.9 s faster on a phone.
Main-thread work: 18.3 s
A phone's processor spends 18.3 s on main-thread work while loading, 8.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
11,441 HTML elements
The page has 11,441 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
8 third-party services on the page
8 third-party services load with your homepage (Clarity, Google Tag Manager and Shopify and others), adding 2.0 MB and 1.6 s of main-thread time.
Reduce unused JavaScript
1.1 MBAbout 1.1 MB of JavaScript is downloaded but never used on this page.
Mobile performance score: 54
54/100Your mobile performance score is 54. Pages that score under 90 lose visitors before the first paint.
Clarity adds 677 ms
677 msClarity costs a phone 677 ms of main-thread work and 30 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.
Use efficient cache lifetimes
419 KiB14 files are served with short cache lifetimes, so returning visitors download them again (419 KiB).
Shopify adds 321 ms
321 msShopify costs a phone 321 ms of main-thread work and 784 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.
Google Tag Manager adds 344 ms
344 msGoogle Tag Manager costs a phone 344 ms of main-thread work and 499 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 ms14 files block the first paint until they finish downloading. Deferring or inlining them could save about 300 ms.
16 long tasks on the main thread
16 long tasks block the main thread while loading, the longest for 255 ms. During a long task the page ignores taps.
Klaviyo adds 164 ms
164 msKlaviyo costs a phone 164 ms of main-thread work and 345 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.
Reduce unused CSS
150 ms · 53 KiBAbout 53 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.
Duplicated JavaScript
100 ms · 10 KiB10 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 100 ms faster on a phone.
Minify JavaScript
27 KiB27 KiB could be saved by minifying JavaScript.
Legacy JavaScript
19 KiBPolyfills for old browsers add 19 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.
1 checks passed
Server response: 15 ms
15 msYour server sent the HTML in 15 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 11.3 s
11.3 sYour largest element takes 11.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 28.1 s
28.1 sThe page becomes fully interactive after 28.1 s. Good is under 3.8 s.
Speed Index: 13.9 s
13.9 sVisually, the page fills in at 13.9 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 439 ms
439 msScripts block taps and scrolling for 439 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) held steady for real visitors
-3%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 164 ms to 158 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+1%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.5 s to 1.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
8 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.9 s
1.9 sReal visitors wait 1.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 142 ms
142 msReal visitors wait 142 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.4 s
1.4 sReal visitors see the first content after 1.4 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 520 ms
520 msReal visitors wait 520 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 1.4 s
1.4 sThe first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.008
0.008The layout barely moves while loading (CLS 0.008, good is under 0.1).
Images and page weight
Page weight: 7.3 MB in 441 requests
7.3 MBYour homepage downloads 7.3 MB in 441 requests on a phone: images 3.2 MB (22), scripts 2.3 MB (113) and other files 1.3 MB (265). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
firstride-bowie-baby-carrier-houndstooth-4-5_a82dd4b8-df15-4 weighs 738 KiB. On a phone connection a single image that size takes seconds.
1 image far larger than shown
563 KiB1 image is downloaded at several times the size a phone draws it, for example firstride-bowie-baby-carrier-houndstooth-4-5_a82dd4b8-df15-4 at 2,400 px wide, shown at 390 px. Resized copies would save about 563 KiB.
About 2.1 g of CO₂ per visit
2.06 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.06 g of CO₂e: 247.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 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.
Accessibility
3 text elements with low contrast
3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Scrollable region must have keyboard access (1 element)
Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.
Summary elements must have discernible text (1 element)
Summary elements must have discernible text: 1 element on the page fails this check, rated serious by axe-core.
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
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.
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 links without text
4 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h2 → h4 and h2 → h5), which makes the page harder to scan with a screen reader.
1 checks passed
53 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 61 WCAG 2.2 A/AA and best-practice rules on the phone render: 53 passed and 8 failed. 5 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
4 links with vague text
4 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
122 internal links, 7 external
The homepage links to 122 pages on wildridecarrier.com and 7 external pages.
8 checks passed
Meta description: 142 characters
Your meta description is 142 characters: “Looking for a trendy hip carrier for your child? Discover the comfort of the Wildride baby hip carrier with a compact d…”.
One H1 headline
Your main headline reads: “WILDRIDE”.
Title: 62 characters
Your title is a healthy 62 characters: “The ultimate hip carrier for toddlers | Wildride – wildridecom”.
Canonical URL set
The canonical URL is https://wildridecarrier.com/.
Structured data in place
Structured data found: Organization and WebSite.
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://wildridecarrier.com/sitemap.xml.
AI search readiness
No llms.txt
There is no https://wildridecarrier.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.
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.
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 (1,961 words), so crawlers that don't run JavaScript still read it.
Other pages
3 pages without an H1
https://wildridecarrier.com/collections/new-arrivals, https://wildridecarrier.com/collections/quick-order and https://wildridecarrier.com/collections/wildride-exclusive have no <h1> headline, so visitors and search engines get no clear main topic.
3 pages slow to respond
https://wildridecarrier.com/collections/quick-order, https://wildridecarrier.com/collections/firstride-bowie-baby-carriers and https://wildridecarrier.com/collections/wildride-toddler-carrier took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 40 found) and read each the way a search engine does.
6 checks passed
Linked pages load
5 pages of 15 loaded without an error (the rest turned automated requests away).
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 5 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 5 pages that loaded have a <title>.
Best practices
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_SOCKET_NOT_CONNECTED”.
Missing source maps
Large scripts ship without source maps.
2 checks passed
Tap targets are thumb-sized
43 of 47 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.
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 993 words of copy
The homepage carries about 993 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 now” and “SHOP TODDLER CARRIERS”.
15 calls to action
The homepage has 15 calls to action, for example “SHOP”, “SHOP TODDLER CARRIERS” and “SHOP BOWIE CARRIERS”.
7 short forms
7 short forms (2 fields at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager and Microsoft Clarity.
Privacy and tracking
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Microsoft Clarity and 2 mores (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.
27 cookies set on arrival
27Opening the homepage sets 27 cookies (measured from a US location before any click).
48 other companies contacted
Loading the homepage contacts 48 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Cookiebot
A consent management tool (Cookiebot) loads with the page.
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 wildridecarrier.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 14 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Instafeed · Xo Insert Code · Tagfly Tag Manager · Elevate Ab Testing · Yotpo Product Reviews · Gorgias Live Chat Helpdesk · Microsoft Clarity · Klaviyo Email Marketing Sms · Orbe Geolocation · Forms · Stape Remix · Upcart · Fokkio Gift With Purchase · cloudfront.net
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
- Analytics
- Google Tag Manager | Microsoft Clarity
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 32 issues on wildridecarrier.com, including 17 speed issues, 1 SEO issue 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.