Website review, no card needed

maxicosi.com logo

maxicosi.com website review

Visit site (opens in a new tab)Reviewed 7 November 202635 issues · 86 checks

This review found 35 issues worth fixing on maxicosi.com, 16 of them high impact, across 86 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
1.8 s1.3 sMay 16Oct 311.4 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.5 s
May 23, 20261.5 s
May 30, 20261.5 s
Jun 6, 20261.5 s
Jun 13, 20261.5 s
Jun 20, 20261.6 s
Jun 27, 20261.6 s
Jul 4, 20261.7 s
Jul 11, 20261.7 s
Jul 18, 20261.7 s
Jul 25, 20261.7 s
Aug 1, 20261.6 s
Aug 8, 20261.6 s
Aug 15, 20261.6 s
Aug 22, 20261.6 s
Aug 29, 20261.6 s
Sep 5, 20261.6 s
Sep 12, 20261.6 s
Sep 19, 20261.5 s
Sep 26, 20261.4 s
Oct 3, 20261.3 s
Oct 10, 20261.4 s
Oct 17, 20261.4 s
Oct 24, 20261.4 s
Oct 31, 20261.4 s
Real-visitor tap response (INP)75th percentile, phones
135 ms109 msMay 16Oct 31112 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026122 ms
May 23, 2026124 ms
May 30, 2026126 ms
Jun 6, 2026127 ms
Jun 13, 2026129 ms
Jun 20, 2026129 ms
Jun 27, 2026129 ms
Jul 4, 2026130 ms
Jul 11, 2026130 ms
Jul 18, 2026132 ms
Jul 25, 2026130 ms
Aug 1, 2026131 ms
Aug 8, 2026129 ms
Aug 15, 2026127 ms
Aug 22, 2026123 ms
Aug 29, 2026120 ms
Sep 5, 2026120 ms
Sep 12, 2026120 ms
Sep 19, 2026120 ms
Sep 26, 2026120 ms
Oct 3, 2026119 ms
Oct 10, 2026117 ms
Oct 17, 2026114 ms
Oct 24, 2026113 ms
Oct 31, 2026112 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

No screenshot is available for this review.

Speed

14 to fix44
  • Use efficient cache lifetimes

    2.5 s · 606 KiB

    22 files are served with short cache lifetimes, so returning visitors download them again (606 KiB).

  • Reduce unused JavaScript

    1.4 s · 221 KiB

    About 221 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.4 s faster on a phone.

  • Render-blocking requests

    1.4 s

    9 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.4 s.

  • Signyfyd adds 1.0 s

    1.0 s

    Signyfyd costs a phone 1.0 s of main-thread work and 281 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Mobile performance score: 44

    44/100

    Your mobile performance score is 44. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Main-thread work: 5.3 s

    A phone's processor spends 5.3 s on main-thread work while loading, 3.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • 3,885 HTML elements

    The page has 3,885 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Improve image delivery

    300 ms · 1.9 MB

    41 images could be 1.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. 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 (Signyfyd, Osano CMP and Klaviyo and others), adding 2.5 MB and 1.9 s of main-thread time.

  • 15 long tasks on the main thread

    15 long tasks block the main thread while loading, the longest for 634 ms. During a long task the page ignores taps.

  • Minify JavaScript

    550 ms · 66 KiB

    66 KiB could be saved by minifying JavaScript.

  • Osano CMP adds 257 ms

    257 ms

    Osano CMP costs a phone 257 ms of main-thread work and 100 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.

  • Dash Hudson adds 93 ms

    93 ms

    Dash Hudson costs a phone 93 ms of main-thread work and 1.5 MB 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.

  • Klaviyo adds 203 ms

    203 ms

    Klaviyo costs a phone 203 ms of main-thread work and 330 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

    230 ms · 82 KiB

    About 82 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 230 ms faster on a phone.

  • Legacy JavaScript

    150 ms · 23 KiB

    Polyfills for old browsers add 23 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

  • Duplicated JavaScript

    150 ms · 11 KiB

    11 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 150 ms faster on a phone.

  • Font display

    100 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).

  • Minify CSS

    14 KiB

    14 KiB could be saved by minifying CSS.

  • 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: 9 ms

    9 ms

    Your server sent the HTML in 9 ms, well inside Google's 600 ms guideline.

Core Web Vitals

5 to fix100
  • Largest Contentful Paint: 19.4 s

    19.4 s

    Your largest element takes 19.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • Time to Interactive: 22.7 s

    22.7 s

    The page becomes fully interactive after 22.7 s. Good is under 3.8 s.

  • Speed Index: 9.5 s

    9.5 s

    Visually, the page fills in at 9.5 s (Speed Index). Good is under 3.4 s.

  • First Contentful Paint: 3.6 s

    3.6 s

    The first text or image appears after 3.6 s on a phone. Good is under 1.8 s.

  • Total Blocking Time: 638 ms

    638 ms

    Scripts block taps and scrolling for 638 ms in total while the page loads. Good is under 200 ms.

  • Tap response (INP) held steady for real visitors

    -9%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 122 ms to 112 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) held steady for real visitors

    -7%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.5 s to 1.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

7 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.7 s

    1.7 s

    Real visitors wait 1.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 101 ms

    101 ms

    Real visitors wait 101 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.6 s

    1.6 s

    Real visitors see the first content after 1.6 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 771 ms

    771 ms

    Real visitors wait 771 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

1 to fix70
  • Page weight: 5.0 MB in 325 requests

    5.0 MB

    Your homepage downloads 5.0 MB in 325 requests on a phone: images 2.3 MB (79), scripts 1.5 MB (94) and other files 852 KiB (126). Under 2 MB keeps phones on slow connections fast.

  • About 1.4 g of CO₂ per visit

    1.42 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.42 g of CO₂e: 170.4 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

5 to fixGoogle 9692
  • 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.

  • 18 images without alt text

    18 images have 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 (2 elements)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.

  • 2 links without text

    2 visible links have no text or label, so screen readers cannot say where they go.

  • Headings skip levels

    Headings skip levels (h3 → h5), 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. (3 elements).

1 checks passed
  • 39 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 43 WCAG 2.2 A/AA and best-practice rules on the phone render: 39 passed and 4 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 10090
  • Meta description is long (292 characters)

    Your meta description is 292 characters; Google truncates after about 160, so the end of your pitch is cut.

  • One H1 headline

    Your <h1> is empty.

  • 163 internal links, 25 external

    The homepage links to 163 pages on maxicosi.com and 25 external pages.

6 checks passed
  • Title: 65 characters

    Your title is a healthy 65 characters: “Maxi-Cosi™ US Site | Car Seats, Strollers, Bassinets, Baby Swings”.

  • Canonical URL set

    The canonical URL is https://maxicosi.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://maxicosi.com/sitemap.xml.

AI search readiness

100
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 (987 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://maxicosi.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

5 to fix63
  • 1 page without a title

    https://maxicosi.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

  • 1 linked page hidden from search

    https://maxicosi.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 1 page without a meta description

    https://maxicosi.com/customer_authentication/redirect has no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://maxicosi.com/collections/bundles-car-seats/Car-Seats, whose canonical is https://maxicosi.com/collections/bundles-car-seats. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 13 pages without an H1

    https://maxicosi.com/collections/gliders-recliners, https://maxicosi.com/pages/military-discount, https://maxicosi.com/collections/car-seats, https://maxicosi.com/collections/strollers-travel-systems, https://maxicosi.com/collections/at-home and https://maxicosi.com/collections/furniture and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages slow to respond

    https://maxicosi.com/collections/car-seats and https://maxicosi.com/collections/strollers-travel-systems took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 92 found) and read each the way a search engine does.

2 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.

Best practices

1 to fixGoogle 9693
  • 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://maxicosi.com/cdn/shop/t/92/assets/bundle.index.css?v=16158' because its MIME type …”.

2 checks passed
  • Tap targets are thumb-sized

    43 of 51 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix83
  • 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 522 words of copy

    The homepage carries about 522 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”.

  • 17 calls to action

    The homepage has 17 calls to action, for example “Shop >”, “Shop All Car Seats” and “Shop All Strollers & Travel Systems”.

  • 3 short forms

    3 short forms (1 field at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 76 testimonial or review blocks and 3 trust badges.

Privacy and tracking

  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads Klaviyo (measured from a US location before any click). A consent tool (Osano) is installed; check it blocks these until visitors agree where the law requires it.

  • 8 cookies set on arrival

    8

    Opening the homepage sets 8 cookies (measured from a US location before any click).

  • 19 other companies contacted

    Loading the homepage contacts 19 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • Consent tool: Osano

    A consent management tool (Osano) 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 maxicosi.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 5 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Klaviyo Email Marketing Sms · Aspire Affiliates App · Freegifts · signifyd.com · bazaarvoice.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

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 35 issues on maxicosi.com, including 19 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25