Website review, no card needed

7amenfant.com logo

7amenfant.com website review

Visit site (opens in a new tab)Reviewed 29 October 202633 issues · 83 checks

This review found 33 issues worth fixing on 7amenfant.com, 12 of them high impact, across 83 checks. The most urgent: page weight: 15.4 MB in 523 requests. 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.2 sMay 9Oct 241.3 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20261.4 s
May 16, 20261.4 s
May 23, 20261.4 s
May 30, 20261.6 s
Jun 6, 20261.6 s
Jun 13, 20261.3 s
Jun 20, 20261.3 s
Jun 27, 20261.2 s
Jul 4, 20261.2 s
Jul 11, 20261.5 s
Jul 18, 20261.5 s
Jul 25, 20261.7 s
Aug 1, 20261.5 s
Aug 8, 20261.5 s
Aug 15, 20261.4 s
Aug 22, 20261.5 s
Aug 29, 20261.5 s
Sep 5, 20261.5 s
Sep 12, 20261.5 s
Sep 19, 20261.6 s
Sep 26, 20261.6 s
Oct 3, 20261.6 s
Oct 10, 20261.5 s
Oct 17, 20261.4 s
Oct 24, 20261.3 s
Real-visitor tap response (INP)75th percentile, phones
108 ms93 msMay 9Oct 24105 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026104 ms
May 16, 2026104 ms
May 23, 202696 ms
May 30, 202696 ms
Jun 6, 202696 ms
Jun 13, 202696 ms
Jun 20, 202696 ms
Jun 27, 202695 ms
Jul 4, 202695 ms
Jul 11, 202697 ms
Jul 18, 2026103 ms
Jul 25, 2026104 ms
Aug 1, 2026103 ms
Aug 8, 2026101 ms
Aug 15, 2026100 ms
Aug 22, 2026102 ms
Aug 29, 2026104 ms
Sep 5, 2026105 ms
Sep 12, 2026104 ms
Sep 19, 2026106 ms
Sep 26, 2026104 ms
Oct 3, 2026103 ms
Oct 10, 2026103 ms
Oct 17, 2026103 ms
Oct 24, 2026105 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 7amenfant.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. 7amenfant.com at 1.2 s1.2 s
  2. 7amenfant.com at 2.4 s2.4 s
  3. 7amenfant.com at 3.6 s3.6 s
  4. 7amenfant.com at 4.7 s4.7 s
  5. 7amenfant.com at 5.9 s5.9 s
  6. 7amenfant.com at 7.1 s7.1 s
  7. 7amenfant.com at 8.3 s8.3 s
  8. 7amenfant.com at 9.5 s9.5 s

Speed

8 to fix52
  • 6,964 HTML elements

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

  • Main-thread work: 6.2 s

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

  • Mobile performance score: 52

    52/100

    Your mobile performance score is 52. Pages that score under 90 lose visitors before the first paint.

  • Reduce unused JavaScript

    450 ms · 548 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Klaviyo, Yotpo and Clarity and others), adding 1.3 MB and 666 ms of main-thread time.

  • Use efficient cache lifetimes

    150 ms · 524 KiB

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

  • Improve image delivery

    150 ms · 468 KiB

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

  • Klaviyo adds 159 ms

    159 ms

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

    250 ms

    3 files block the first paint until they finish downloading. Deferring or inlining them could save about 250 ms.

  • Minify JavaScript

    150 ms · 71 KiB

    71 KiB could be saved by minifying JavaScript.

  • 16 long tasks on the main thread

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

  • Reduce unused CSS

    47 KiB

    About 47 KiB of CSS is downloaded but never applied on this page.

  • Legacy JavaScript

    26 KiB

    Polyfills for old browsers add 26 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: 13 ms

    13 ms

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

Core Web Vitals

8 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 LCP: 5.7 s

    5.7 s

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

  • Real-user FCP: 4.7 s

    4.7 s

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

  • Largest Contentful Paint: 40.4 s

    40.4 s

    Your largest element takes 40.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: 54.2 s

    54.2 s

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

  • Speed Index: 12.6 s

    12.6 s

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

  • First Contentful Paint: 2.9 s

    2.9 s

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

  • Total Blocking Time: 359 ms

    359 ms

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

  • Tap response (INP) held steady for real visitors

    0%

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

  • Largest content (LCP) held steady for real visitors

    -3%

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

4 checks passed
  • Real-user INP: 133 ms

    133 ms

    Real visitors wait 133 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 TTFB: 457 ms

    457 ms

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

  • Cumulative Layout Shift: 0.027

    0.027

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

Images and page weight

5 to fix38
  • Page weight: 15.4 MB in 523 requests

    15.4 MB

    Your homepage downloads 15.4 MB in 523 requests on a phone: images 12.5 MB (291), scripts 1.8 MB (108) and other files 882 KiB (109). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    IMG_8189.gif weighs 3.3 MB. On a phone connection a single image that size takes seconds.

  • 35 images in older formats

    35 images (6.5 MB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

  • An image on the first screen is lazy-loaded

    7AM_FW26_Mountain0909_763777ac-7dc1-4d70-adb0-43c06130a1a1.j is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • 9 images below the first screen load straight away

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

  • About 4.4 g of CO₂ per visit

    4.36 g

    By the Sustainable Web Design model, a visit to your homepage emits about 4.36 g of CO₂e: 523.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 checks passed
  • Images are sized for phones

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

Accessibility

3 to fixGoogle 9797
  • Links must have discernible text (1 element)

    Links must have discernible text: 1 element on the page fails this check, rated serious 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.

  • ARIA role should be appropriate for the element (1 element)

    ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.

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

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

2 checks passed
  • Every image has alt text

    All 302 images in the HTML carry an alt attribute.

  • 55 automated accessibility rules passed

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

SEO

1 to fixGoogle 9298
  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • 470 internal links, 9 external

    The homepage links to 470 pages on 7amenfant.com and 9 external pages.

8 checks passed
  • Meta description: 156 characters

    Your meta description is 156 characters: “Winter must-have accessories for keeping baby safe, warm & chic on any given stroll. It is possible to snuggle your way…”.

  • One H1 headline

    Your main headline reads: “7AM Enfant”.

  • Title: 44 characters

    Your title is a healthy 44 characters: “7AM Enfant | Style & Peace of Mind On-The-Go”.

  • Canonical URL set

    The canonical URL is https://www.7amenfant.com/.

  • Structured data in place

    Structured data found: BreadcrumbList, 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://www.7amenfant.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 (10,736 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

2 to fix90
  • 2 pages without a meta description

    https://www.7amenfant.com/collections/starter-set and https://www.7amenfant.com/collections/gifts-under-70-dollars have no meta description, so Google writes the search snippet from whatever text it finds.

  • 6 pages without an H1

    https://www.7amenfant.com/collections/stack-save, https://www.7amenfant.com/collections/all-products, https://www.7amenfant.com/collections/new-arrivals, https://www.7amenfant.com/collections/all-enfant, https://www.7amenfant.com/collections/starter-set and https://www.7amenfant.com/collections/gifts-under-70-dollars 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 181 found) and read each the way a search engine does.

5 checks passed
  • Linked pages load

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

  • 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 6 pages that loaded have a <title>.

Best practices

3 to fixGoogle 7785
  • 50 small tap targets

    50 of 98 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 (“Unload event listeners are deprecated and will be removed.”).

  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “Carousel navigation component requires an aria-controls attribute that refers to the controlled carousel.”.

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix79
  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

  • About 2,803 words of copy

    The homepage carries about 2,803 words of visible text.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SHOP” and “SHOP NOW”.

  • 55 calls to action

    The homepage has 55 calls to action, for example “Shop All”, “Shop By Product” and “Shop By Gear”.

  • 4 short forms

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

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

1 to fix
  • 8 trackers load before any consent

    8

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

  • 42 other companies contacted

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

Upkeep, stack and company

Stack

E-commerce
Shopify
Analytics
Google Tag Manager
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 33 issues on 7amenfant.com, including 16 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

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