Website review, no card needed

cartersoshkosh.com.mx logo

cartersoshkosh.com.mx website review

Visit site (opens in a new tab)Reviewed 11 November 202648 issues · 91 checks

This review found 48 issues worth fixing on cartersoshkosh.com.mx, 16 of them high impact, across 91 checks. The most urgent: mobile performance score: 38. 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.3 s2.6 sMay 23Nov 72.7 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20263.0 s
May 30, 20262.9 s
Jun 6, 20262.8 s
Jun 13, 20262.8 s
Jun 20, 20262.8 s
Jun 27, 20263.0 s
Jul 4, 20263.2 s
Jul 11, 20263.1 s
Jul 18, 20263.1 s
Jul 25, 20263.0 s
Aug 1, 20263.1 s
Aug 8, 20263.0 s
Aug 15, 20263.0 s
Aug 22, 20262.9 s
Aug 29, 20262.9 s
Sep 5, 20262.8 s
Sep 12, 20262.9 s
Sep 19, 20262.9 s
Sep 26, 20262.8 s
Oct 3, 20262.8 s
Oct 10, 20262.8 s
Oct 17, 20262.8 s
Oct 24, 20262.8 s
Oct 31, 20262.7 s
Nov 7, 20262.7 s
Real-visitor tap response (INP)75th percentile, phones
199 ms155 msMay 23Nov 7177 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026170 ms
May 30, 2026169 ms
Jun 6, 2026170 ms
Jun 13, 2026170 ms
Jun 20, 2026171 ms
Jun 27, 2026172 ms
Jul 4, 2026170 ms
Jul 11, 2026163 ms
Jul 18, 2026161 ms
Jul 25, 2026160 ms
Aug 1, 2026162 ms
Aug 8, 2026165 ms
Aug 15, 2026164 ms
Aug 22, 2026163 ms
Aug 29, 2026164 ms
Sep 5, 2026164 ms
Sep 12, 2026171 ms
Sep 19, 2026179 ms
Sep 26, 2026182 ms
Oct 3, 2026191 ms
Oct 10, 2026194 ms
Oct 17, 2026189 ms
Oct 24, 2026187 ms
Oct 31, 2026178 ms
Nov 7, 2026177 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 cartersoshkosh.com.mx (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. cartersoshkosh.com.mx at 0.6 s0.6 s
  2. cartersoshkosh.com.mx at 1.2 s1.2 s
  3. cartersoshkosh.com.mx at 1.8 s1.8 s
  4. cartersoshkosh.com.mx at 2.4 s2.4 s
  5. cartersoshkosh.com.mx at 3.0 s3.0 s
  6. cartersoshkosh.com.mx at 3.6 s3.6 s
  7. cartersoshkosh.com.mx at 4.2 s4.2 s
  8. cartersoshkosh.com.mx at 4.9 s4.9 s

Speed

10 to fix38
  • Mobile performance score: 38

    38/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (vtexassets.com, Google Tag Manager and Clarity and others), adding 3.7 MB and 1.8 s of main-thread time.

  • Reduce unused JavaScript

    600 ms · 676 KiB

    About 676 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 600 ms faster on a phone.

  • Improve image delivery

    450 ms · 477 KiB

    16 images could be 477 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.

  • vtexassets.com adds 669 ms

    669 ms

    vtexassets.com costs a phone 669 ms of main-thread work and 2.3 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.

  • Use efficient cache lifetimes

    798 KiB

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

  • Google Tag Manager adds 542 ms

    542 ms

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

  • Main-thread work: 3.9 s

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

  • Reduce unused CSS

    300 ms · 71 KiB

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

  • 1,654 HTML elements

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

  • 8 long tasks on the main thread

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

  • Legacy JavaScript

    13 KiB

    Polyfills for old browsers add 13 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.

  • Minify JavaScript

    4 KiB

    4 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 14 ms

    14 ms

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

Core Web Vitals

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

  • Real-user CLS: 0.96

    0.96

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

  • Largest Contentful Paint: 10.1 s

    10.1 s

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

  • Time to Interactive: 23.8 s

    23.8 s

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

  • Cumulative Layout Shift: 0.697

    0.697

    The layout shifts by 0.697 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Speed Index: 8.2 s

    8.2 s

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

  • Real-user TTFB: 933 ms

    933 ms

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

  • 32 images without width and height

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

  • Total Blocking Time: 262 ms

    262 ms

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

  • Tap response (INP) held steady for real visitors

    +5%

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

  • Largest content (LCP) held steady for real visitors

    -8%

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

4 checks passed
  • Real-user LCP: 2.2 s

    2.2 s

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

  • Real-user INP: 167 ms

    167 ms

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

  • Real-user FCP: 1.3 s

    1.3 s

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

  • First Contentful Paint: 1.5 s

    1.5 s

    The first text or image appears after 1.5 s, inside the 1.8 s “good” threshold.

Images and page weight

2 to fix63
  • Page weight: 4.0 MB in 185 requests

    4.0 MB

    Your homepage downloads 4.0 MB in 185 requests on a phone: scripts 2.4 MB (63), images 1.2 MB (50) and HTML 148 KiB (2). Under 2 MB keeps phones on slow connections fast.

  • 10 images below the first screen load straight away

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

  • About 1.1 g of CO₂ per visit

    1.13 g

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

12 to fixGoogle 7381
  • 3 buttons without a name

    3 buttons have no accessible name, so screen readers announce just “button”.

  • 14 text elements with low contrast

    14 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 8 tap targets too small

    8 tap targets are too small or too close together to hit reliably with a finger.

  • Orphan list items

    Some list items are not inside a list.

  • Hidden but focusable

    2 elements hidden from screen readers can still receive keyboard focus.

  • 34 images without alt text

    34 images have no alt text, which hurts accessibility and image search.

  • All page content should be contained by landmarks (15 elements)

    All page content should be contained by landmarks: 15 elements on the page fail this check, rated moderate by axe-core.

  • Heading levels should only increase by one (1 element)

    Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

  • 31 links without text

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

  • 2 form fields without a label

    2 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (2 elements).

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

SEO

2 to fixGoogle 9291
  • 4 H1 headlines

    There are 4 <h1> headlines (“Compra por descuento:”, “Ofertas Increíbles” and “¡Aprovecha las ofertas de temporada!”). One clear main headline is easier for people and search engines.

  • Structured data has 1 problem

    Structured data found (WebSite) but with 1 problem, for example “WebSite: missing name”.

  • 67 internal links, 5 external

    The homepage links to 67 pages on cartersoshkosh.com.mx and 5 external pages.

6 checks passed
  • Meta description: 159 characters

    Your meta description is 159 characters: “Encuentra en Carter's todo lo que necesitan tus pequeños en cada etapa, desde pañaleros, mamelucos, hasta tenis y ropa …”.

  • Title: 41 characters

    Your title is a healthy 41 characters: “Ropa para bebés y niños | Carter's México”.

  • Canonical URL set

    The canonical URL is https://www.carters.com.mx/.

  • 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://www.carters.com.mx/sitemap.xml.

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.

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

  • llms.txt published

    The site publishes https://www.carters.com.mx/llms.txt (2 KiB, 0 links), a plain-text guide to the site for AI tools.

Other pages

3 to fix86
  • 6 pages share a title

    /, https://www.carters.com.mx/carters, https://www.carters.com.mx/otter-avenue, https://www.carters.com.mx/tiendas, https://www.carters.com.mx/centro-de-ayuda and https://www.carters.com.mx/ninos all use the title “Ropa para bebés y niños | Carter's México”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 9 pages share a meta description

    https://www.carters.com.mx/carters, https://www.carters.com.mx/otter-avenue, https://www.carters.com.mx/tiendas, https://www.carters.com.mx/centro-de-ayuda, https://www.carters.com.mx/ninos and https://www.carters.com.mx/todo-carters and 3 others use the same meta description. A description written for each page earns more clicks.

  • 7 pages without an H1

    https://www.carters.com.mx/skiphop, https://www.carters.com.mx/otter-avenue, https://www.carters.com.mx/tiendas, https://www.carters.com.mx/centro-de-ayuda, https://www.carters.com.mx/bebe and https://www.carters.com.mx/preescolar and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

  • 3 pages with very little text

    https://www.carters.com.mx/skiphop, https://www.carters.com.mx/tiendas and https://www.carters.com.mx/centro-de-ayuda have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 7 pages slow to respond

    https://www.carters.com.mx/oshkosh, https://www.carters.com.mx/skiphop, https://www.carters.com.mx/little-planet, https://www.carters.com.mx/bebe, https://www.carters.com.mx/ninos and https://www.carters.com.mx/todo-carters and 1 other took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

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

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

4 to fixGoogle 7370
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=211018497&Ver=2&mid=98d426e1-d142-4200-9dce-1a91df8b132f&bo=1&sid=7a7e4320de1711f18eb359c39b2dc8d6&vid=7a7e5d50de1711f18849f5aea4f9c054&vids=1&msclkid=N&pi=918639831&l.

  • 37 small tap targets

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

  • 1 third-party cookie

    1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'id')”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix64
  • 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.

  • Thin social proof

    Social proof on the homepage: 5 customer or partner logos. 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.

  • Only about 156 words

    The homepage has only about 156 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
  • 1 call to action

    The homepage has 1 call to action, for example “Baby Shower Shop”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager, Meta Pixel, Microsoft Clarity and Hotjar.

Privacy and tracking

1 to fix
  • 8 trackers load before any consent

    8

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

  • 23 cookies set on arrival

    23

    Opening the homepage sets 23 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.

  • 36 other companies contacted

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

Upkeep, stack and company

Stack

Framework
React
Analytics
Google Tag Manager | Hotjar | Microsoft Clarity
Hosting
Safenames Ltd.

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 48 issues on cartersoshkosh.com.mx, including 19 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

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