Website review, no card needed

hatchcollection.com logo

hatchcollection.com website review

Visit site (opens in a new tab)Reviewed 20 November 202634 issues · 82 checks

This review found 34 issues worth fixing on hatchcollection.com, 13 of them high impact, across 82 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
2.2 s1.5 sMay 30Nov 141.9 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20262.1 s
Jun 6, 20262.1 s
Jun 13, 20262.1 s
Jun 20, 20262.0 s
Jun 27, 20261.8 s
Jul 4, 20261.7 s
Jul 11, 20261.6 s
Jul 18, 20261.6 s
Jul 25, 20261.6 s
Aug 1, 20261.6 s
Aug 8, 20261.5 s
Aug 15, 20261.6 s
Aug 22, 20261.6 s
Aug 29, 20261.6 s
Sep 5, 20261.7 s
Sep 12, 20261.7 s
Sep 19, 20261.6 s
Sep 26, 20261.6 s
Oct 3, 20261.6 s
Oct 10, 20261.6 s
Oct 17, 20261.7 s
Oct 24, 20261.7 s
Oct 31, 20261.7 s
Nov 7, 20261.8 s
Nov 14, 20261.9 s
Real-visitor tap response (INP)75th percentile, phones
487 ms143 msMay 30Nov 14447 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026229 ms
Jun 6, 2026253 ms
Jun 13, 2026269 ms
Jun 20, 2026288 ms
Jun 27, 2026261 ms
Jul 4, 2026252 ms
Jul 11, 2026241 ms
Jul 18, 2026221 ms
Jul 25, 2026212 ms
Aug 1, 2026199 ms
Aug 8, 2026183 ms
Aug 15, 2026211 ms
Aug 22, 2026235 ms
Aug 29, 2026255 ms
Sep 5, 2026313 ms
Sep 12, 2026351 ms
Sep 19, 2026380 ms
Sep 26, 2026411 ms
Oct 3, 2026404 ms
Oct 10, 2026398 ms
Oct 17, 2026410 ms
Oct 24, 2026417 ms
Oct 31, 2026414 ms
Nov 7, 2026437 ms
Nov 14, 2026447 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 hatchcollection.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. hatchcollection.com at 0.4 s0.4 s
  2. hatchcollection.com at 0.8 s0.8 s
  3. hatchcollection.com at 1.1 s1.1 s
  4. hatchcollection.com at 1.5 s1.5 s
  5. hatchcollection.com at 1.9 s1.9 s
  6. hatchcollection.com at 2.3 s2.3 s
  7. hatchcollection.com at 2.6 s2.6 s
  8. hatchcollection.com at 3.0 s3.0 s

Speed

13 to fix47
  • Use efficient cache lifetimes

    6.5 s · 1.6 MB

    100 files are served with short cache lifetimes, so returning visitors download them again (1.6 MB).

  • Reduce unused JavaScript

    5.1 s · 1.8 MB

    About 1.8 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.1 s faster on a phone.

  • Improve image delivery

    1.4 s · 910 KiB

    15 images could be 910 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.4 s faster on a phone.

  • Render-blocking requests

    1.1 s

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

  • Mobile performance score: 47

    47/100

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

  • Main-thread work: 8.4 s

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

  • 3,440 HTML elements

    The page has 3,440 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 (Google Tag Manager, Klaviyo and heyamplify.com and others), adding 2.9 MB and 1.1 s of main-thread time.

  • Google Tag Manager adds 485 ms

    485 ms

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

    450 ms · 112 KiB

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

  • Reduce unused CSS

    300 ms · 88 KiB

    About 88 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.

  • Klaviyo adds 164 ms

    164 ms

    Klaviyo costs a phone 164 ms of main-thread work and 567 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.

  • Shopify adds 88 ms

    88 ms

    Shopify costs a phone 88 ms of main-thread work and 582 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 193 ms. During a long task the page ignores taps.

  • Duplicated JavaScript

    150 ms · 20 KiB

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

  • Minify JavaScript

    34 KiB

    34 KiB could be saved by minifying JavaScript.

  • Minify CSS

    13 KiB

    13 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: 26 ms

    26 ms

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

Core Web Vitals

7 to fix100
  • Largest Contentful Paint: 28.4 s

    28.4 s

    Your largest element takes 28.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: 41.8 s

    41.8 s

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

  • Speed Index: 10.6 s

    10.6 s

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

  • First Contentful Paint: 4.1 s

    4.1 s

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

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

    +83%

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

  • Total Blocking Time: 443 ms

    443 ms

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

  • 1 image without width and height

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

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 s

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

  • Real-user INP: 170 ms

    170 ms

    Real visitors wait 170 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.7 s

    1.7 s

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

  • Real-user TTFB: 510 ms

    510 ms

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

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

    -12%

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

  • Cumulative Layout Shift: 0.036

    0.036

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

Images and page weight

3 to fix53
  • Page weight: 8.3 MB in 507 requests

    8.3 MB

    Your homepage downloads 8.3 MB in 507 requests on a phone: scripts 4.7 MB (210), images 1.8 MB (35) and other files 1.1 MB (217). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    mobile-HP-2.jpg 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).

  • 1 image far larger than shown

    16 KiB

    1 image is downloaded at several times the size a phone draws it, for example mobile-HP-2.jpg at 1,200 px wide, shown at 390 px. Resized copies would save about 16 KiB.

  • About 2.4 g of CO₂ per visit

    2.36 g

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

1 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

2 to fixGoogle 9497
  • 8 images without alt text

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

  • Alternative text of images should not be repeated as text (6 elements)

    Alternative text of images should not be repeated as text: 6 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

    Headings skip levels (h1 → h3), 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. (1 element).

1 checks passed
  • 48 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 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 9297
  • No social preview image

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

  • 155 internal links, 8 external

    The homepage links to 155 pages on hatchcollection.com and 8 external pages.

7 checks passed
  • Meta description: 152 characters

    Your meta description is 152 characters: “Find Fashionable Maternity Clothing for every stage of your pregnancy at HATCH. From dresses and bras to nursing wear a…”.

  • One H1 headline

    Your main headline reads: “HATCH Collection”.

  • Title: 63 characters

    Your title is a healthy 63 characters: “Stylish Maternity Clothing | Nursing Clothes | HATCH Collection”.

  • Canonical URL set

    The canonical URL is https://www.hatchcollection.com/.

  • Structured data in place

    Structured data found: BreadcrumbList, Organization and WebSite.

  • 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.hatchcollection.com/sitemap.xml.

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing logo, description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

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

  • llms.txt published

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

Other pages

2 to fix90
  • 7 pages without a meta description

    https://www.hatchcollection.com/collections/matching-set, https://www.hatchcollection.com/collections/hospital-ready, https://www.hatchcollection.com/collections/bundles-1, https://www.hatchcollection.com/collections/fall-collection, https://www.hatchcollection.com/collections/the-holiday-edit and https://www.hatchcollection.com/collections/the-travel-edit and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 pages without an H1

    https://www.hatchcollection.com/collections/view-all, https://www.hatchcollection.com/collections/new-arrivals, https://www.hatchcollection.com/collections/best-sellers, https://www.hatchcollection.com/collections/matching-set, https://www.hatchcollection.com/collections/work-wear-edit and https://www.hatchcollection.com/collections/hospital-ready and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://www.hatchcollection.com/collections/the-holiday-edit has 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.

  • 15 internal pages checked

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

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

Best practices

2 to fixGoogle 9687
  • 10 small tap targets

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

  • 5 JavaScript errors while loading

    5 errors were logged to the browser console while the page loaded, for example “NAC is not defined”.

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: 63 testimonial or review blocks. 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 344 words of copy

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

  • 15 calls to action

    The homepage has 15 calls to action, for example “SHOP BY CATEGORY”, “SHOP ALL MATERNITY” and “Shop All Postpartum”.

  • 4 short forms

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

  • Analytics in place

    Analytics detected: Meta Pixel and TikTok Pixel.

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, Hotjar and Klaviyo 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.

  • 52 cookies set on arrival

    52

    Opening the homepage sets 52 cookies, 1 of them by other companies (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.

  • 74 other companies contacted

    Loading the homepage contacts 74 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 hatchcollection.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 24 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Intelligems A B Testing · Eg Auto Add To Cart · Helium Customer Fields · Triplewhale · Yotpo Product Reviews · Redo · Amplify Bundles Upsell · Sc Easy 404 Ai Redirects · Checkmate · Accentuate · Elevar Conversion Tracking · Linkedoption · Malachyte Hatch Collection · Bubblehouse Hatch Collection · Nosto · Sortd Merchandiser · Klaviyo Email Marketing Sms · Covet Instagram Feed Reviews · Avada Cookie Bar · rise-ai.com · noibu.com · getredo.com · amazonaws.com · global-e.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

Framework
jQuery
E-commerce
Shopify
Hosting
Shopify

Hiring

Hiring
12 open roles
Job board
adp

Company

Headquarters
New York

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 34 issues on hatchcollection.com, including 20 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