Website review, no card needed

nunababy.com logo

nunababy.com website review

Visit site (opens in a new tab)Reviewed 17 November 202637 issues · 80 checks

This review found 37 issues worth fixing on nunababy.com, 15 of them high impact, across 80 checks. The most urgent: reduce unused JavaScript. 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
3.7 s2.4 sMay 30Nov 143.0 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20263.6 s
Jun 6, 20263.1 s
Jun 13, 20263.1 s
Jun 20, 20263.1 s
Jun 27, 20263.1 s
Jul 4, 20263.2 s
Jul 11, 20263.1 s
Jul 18, 20262.9 s
Jul 25, 20262.8 s
Aug 1, 20262.6 s
Aug 8, 20262.6 s
Aug 15, 20262.6 s
Aug 22, 20262.6 s
Aug 29, 20262.7 s
Sep 5, 20262.7 s
Sep 12, 20262.8 s
Sep 19, 20262.8 s
Sep 26, 20262.8 s
Oct 3, 20262.8 s
Oct 10, 20262.7 s
Oct 17, 20262.7 s
Oct 24, 20262.7 s
Oct 31, 20262.7 s
Nov 7, 20262.9 s
Nov 14, 20263.0 s
Real-visitor tap response (INP)75th percentile, phones
140 ms99 msMay 30Nov 14134 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026106 ms
Jun 6, 2026104 ms
Jun 13, 2026105 ms
Jun 20, 2026106 ms
Jun 27, 2026108 ms
Jul 4, 2026111 ms
Jul 11, 2026112 ms
Jul 18, 2026113 ms
Jul 25, 2026118 ms
Aug 1, 2026121 ms
Aug 8, 2026124 ms
Aug 15, 2026128 ms
Aug 22, 2026128 ms
Aug 29, 2026128 ms
Sep 5, 2026128 ms
Sep 12, 2026128 ms
Sep 19, 2026129 ms
Sep 26, 2026129 ms
Oct 3, 2026129 ms
Oct 10, 2026130 ms
Oct 17, 2026131 ms
Oct 24, 2026134 ms
Oct 31, 2026135 ms
Nov 7, 2026135 ms
Nov 14, 2026134 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

Full-page screenshot of nunababy.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. nunababy.com at 0.4 s0.4 s
  2. nunababy.com at 0.9 s0.9 s
  3. nunababy.com at 1.3 s1.3 s
  4. nunababy.com at 1.7 s1.7 s
  5. nunababy.com at 2.1 s2.1 s
  6. nunababy.com at 2.6 s2.6 s
  7. nunababy.com at 3.0 s3.0 s
  8. nunababy.com at 3.4 s3.4 s

Speed

13 to fix35
  • Reduce unused JavaScript

    3.3 s · 635 KiB

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

  • Render-blocking requests

    3.0 s

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

  • Use efficient cache lifetimes

    1.4 s · 380 KiB

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

  • Mobile performance score: 35

    35/100

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

  • Main-thread work: 8.1 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Osano CMP, New Relic and Google Tag Manager and others), adding 1.6 MB and 2.1 s of main-thread time.

  • Improve image delivery

    1.1 MB

    12 images could be 1.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Osano CMP adds 849 ms

    849 ms

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

  • 14 long tasks on the main thread

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

  • Reduce unused CSS

    470 ms · 128 KiB

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

  • New Relic adds 412 ms

    412 ms

    New Relic costs a phone 412 ms of main-thread work and 24 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 259 ms

    259 ms

    Google Tag Manager costs a phone 259 ms of main-thread work and 515 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.

  • ZenDesk adds 154 ms

    154 ms

    ZenDesk costs a phone 154 ms of main-thread work and 396 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.

  • Legacy JavaScript

    150 ms · 27 KiB

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

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

1 checks passed
  • Server response: 17 ms

    17 ms

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

Core Web Vitals

10 to fix67
  • Fails Core Web Vitals for real visitors

    Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

  • Largest Contentful Paint: 21.3 s

    21.3 s

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

  • Time to Interactive: 25.6 s

    25.6 s

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

  • Total Blocking Time: 1.4 s

    1.4 s

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

  • First Contentful Paint: 4.2 s

    4.2 s

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

  • Speed Index: 7.1 s

    7.1 s

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

  • Real-user LCP: 2.7 s

    2.7 s

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

  • Tap response (INP) got 28% slower for real visitors

    +28%

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

  • Real-user FCP: 2.4 s

    2.4 s

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

  • 16 images without width and height

    16 images have no width and height attributes, so the layout jumps as each one loads.

5 checks passed
  • Real-user INP: 181 ms

    181 ms

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

  • Real-user CLS: 0.08

    0.08

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

  • Real-user TTFB: 492 ms

    492 ms

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

  • Largest content (LCP) got 13% faster for real visitors

    -13%

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

  • 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: 4.7 MB in 404 requests

    4.7 MB

    Your homepage downloads 4.7 MB in 404 requests on a phone: scripts 2.2 MB (302), images 1.9 MB (33) and fonts 447 KiB (10). Under 2 MB keeps phones on slow connections fast.

  • 3 images below the first screen load straight away

    3 images further down the page (98 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 1.3 g of CO₂ per visit

    1.34 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.34 g of CO₂e: 160.9 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 are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

1 to fixGoogle 9598
  • 1 tap target too small

    1 tap target is too small or too close together to hit reliably with a finger.

  • Headings skip levels

    Headings skip levels (h2 → h4, h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 52 images in the HTML carry an alt attribute.

  • 48 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: 48 passed and 2 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 10083
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No XML sitemap

    No XML sitemap at https://nunababy.eu/pub/media/sitemap_nuna_fr.xml, so Google discovers your pages only by following links.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 121 internal links, 25 external

    The homepage links to 121 pages on nunababy.com and 25 external pages.

5 checks passed
  • Meta description: 154 characters

    Your meta description is 154 characters: “At Nuna Baby, we curate practical & functional designs for every step of your parenting journey. Mindfully manufactured…”.

  • Title: 58 characters

    Your title is a healthy 58 characters: “Nuna | Functional Car Seats, Premium Strollers & Baby Gear”.

  • Canonical URL set

    The canonical URL is https://nunababy.com/usa.

  • Structured data in place

    Structured data found: WebPage and WebSite.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

AI search readiness

1 to fix88
  • 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.

  • No llms.txt

    There is no https://nunababy.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.

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

Other pages

3 to fix73
  • 1 page without a title

    https://nunababy.com/usa/regionselector has no <title>, so Google invents the link text in results.

  • 2 pages share a title

    / and https://nunababy.com/usa all use the title “Nuna | Functional Car Seats, Premium Strollers & Baby Gear”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 1 page without an H1

    https://nunababy.com/usa has no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page slow to respond

    https://nunababy.com/usa/home-and-travel-gear took over 3 s to send its HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 60 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.

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

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

Best practices

3 to fixGoogle 7385
  • 6 small tap targets

    6 of 12 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_TUNNEL_CONNECTION_FAILED”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Content security policy”).

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

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

  • 19 calls to action

    The homepage has 19 calls to action, for example “Contact us”, “Register Products” and “Register Car Seat”.

  • 3 short forms

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

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Meta Pixel.

Privacy and tracking

  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads Google Ads and Google Tag Manager (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.

  • 9 cookies set on arrival

    9

    Opening the homepage sets 9 cookies, 1 of them by other companies (measured from a US location before any click).

  • 24 other companies contacted

    Loading the homepage contacts 24 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 nunababy.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
jQuery
E-commerce
Magento
Analytics
Google Analytics | Google Tag Manager
Hosting
Fastly

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 37 issues on nunababy.com, including 23 speed issues, 3 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