Website review, no card needed

gradybabyco.com logo

gradybabyco.com website review

Visit site (opens in a new tab)Reviewed 13 November 202635 issues · 85 checks

This review found 35 issues worth fixing on gradybabyco.com, 9 of them high impact, across 85 checks. The most urgent: render-blocking 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
2.8 s2.3 sOct 3Nov 72.6 s
Show as table
DateReal-visitor load time (LCP)
Oct 3, 20262.7 s
Oct 10, 20262.4 s
Oct 17, 20262.5 s
Oct 24, 20262.4 s
Oct 31, 20262.3 s
Nov 7, 20262.6 s
Real-visitor tap response (INP)75th percentile, phones
105 ms95 msOct 3Nov 7101 ms
Show as table
DateReal-visitor tap response (INP)
Oct 3, 202696 ms
Oct 10, 2026103 ms
Oct 17, 2026104 ms
Oct 24, 2026104 ms
Nov 7, 2026101 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 gradybabyco.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. gradybabyco.com at 0.4 s0.4 s
  2. gradybabyco.com at 0.8 s0.8 s
  3. gradybabyco.com at 1.2 s1.2 s
  4. gradybabyco.com at 1.7 s1.7 s
  5. gradybabyco.com at 2.1 s2.1 s
  6. gradybabyco.com at 2.5 s2.5 s
  7. gradybabyco.com at 2.9 s2.9 s
  8. gradybabyco.com at 3.3 s3.3 s

Speed

10 to fix48
  • Render-blocking requests

    7.3 s

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

  • Reduce unused JavaScript

    3.7 s · 767 KiB

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

  • Mobile performance score: 48

    48/100

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

  • Improve image delivery

    850 ms · 638 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Squarespace, Google Tag Manager and Facebook and others), adding 3.0 MB and 956 ms of main-thread time.

  • Use efficient cache lifetimes

    750 ms · 143 KiB

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

  • Squarespace adds 599 ms

    599 ms

    Squarespace costs a phone 599 ms of main-thread work and 1.2 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.

  • Legacy JavaScript

    300 ms · 44 KiB

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

  • squarespace-cdn.com adds 0 ms

    0 ms

    squarespace-cdn.com costs a phone 0 ms of main-thread work and 1,012 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.

  • Adobe TypeKit adds 6 ms

    6 ms

    Adobe TypeKit costs a phone 6 ms of main-thread work and 320 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

    150 ms · 137 KiB

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

  • 9 long tasks on the main thread

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

  • Font display

    50 ms

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

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

2 checks passed
  • Main-thread work: 1.9 s

    A phone's processor spends 1.9 s on main-thread work while loading, 914 ms of it running JavaScript. That is comfortably low.

  • Server response: 39 ms

    39 ms

    Your server sent the HTML in 39 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.

  • Largest Contentful Paint: 18.5 s

    18.5 s

    Your largest element takes 18.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “55B416B4-EB18-4153-80F1-04949F404857.jpg”.

  • First Contentful Paint: 6.9 s

    6.9 s

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

  • Time to Interactive: 18.7 s

    18.7 s

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

  • Speed Index: 8.8 s

    8.8 s

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

  • Real-user LCP: 2.6 s

    2.6 s

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

  • Total Blocking Time: 358 ms

    358 ms

    Scripts block taps and scrolling for 358 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.

  • Tap response (INP) held steady for real visitors

    +3%

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

  • Largest content (LCP) held steady for real visitors

    -4%

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

5 checks passed
  • Real-user INP: 96 ms

    96 ms

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

  • Real-user CLS: 0.09

    0.09

    For real visitors the layout shifts by 0.09 (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: 632 ms

    632 ms

    Real visitors wait 632 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

3 to fix68
  • Page weight: 3.2 MB in 153 requests

    3.2 MB

    Your homepage downloads 3.2 MB in 153 requests on a phone: scripts 1.6 MB (51), images 1.0 MB (32) and fonts 305 KiB (16). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    104 KiB

    1 image is downloaded at several times the size a phone draws it, for example gb_boy_logo_blue+3.PNG at 1,500 px wide, shown at 100 px. Resized copies would save about 104 KiB.

  • 3 images below the first screen load straight away

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

  • About 0.9 g of CO₂ per visit

    0.91 g

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

5 to fixGoogle 9294
  • All page content should be contained by landmarks (3 elements)

    All page content should be contained by landmarks: 3 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 (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.

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • 2 text elements with low contrast

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

  • 2 links without text

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

2 checks passed
  • Every image has alt text

    All 13 images in the HTML carry an alt attribute.

  • 38 automated accessibility rules passed

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

SEO

2 to fixGoogle 10089
  • Title is short (13 characters)

    Your title is only 13 characters: “Grady Baby Co”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Structured data has 2 problems

    Structured data found (LocalBusiness and WebSite) but with 2 problems, for example “WebSite: image is not an absolute URL ("//images.squarespace-cdn.com/content/v1/5bcf152d34c4e2cc540…”.

  • 33 internal links, 1 external

    The homepage links to 33 pages on gradybabyco.com and 1 external page.

6 checks passed
  • Meta description: 90 characters

    Your meta description is 90 characters: “Grady Baby Co. and Apparel is a family-run and owned business founded by Albritton Family.”.

  • One H1 headline

    Your main headline reads: “Home”.

  • Canonical URL set

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

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

AI search readiness

1 to fix83
  • Organization data is thin (0 of 6 facts)

    Your Organization JSON-LD is missing name, url, logo, sameAs (social profiles), 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.

  • No llms.txt

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

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

Other pages

1 to fix95
  • 6 pages without a meta description

    https://www.gradybabyco.com/about, https://www.gradybabyco.com/shop, https://www.gradybabyco.com/press, https://www.gradybabyco.com/contact, https://www.gradybabyco.com/shop/ina2bovnh2qdshvf8ddxblucv7p4e5-hjdde-jm298-pax2l-zr4aa-5cz6f-wrs8x-pzflh-l6tfx-3k2sk-ctxff-h48dc-jgh27-fh9mf and https://www.gradybabyco.com/privacypolicy have no meta description, so Google writes the search snippet from whatever text it finds.

  • 4 pages with very little text

    https://www.gradybabyco.com/press, https://www.gradybabyco.com/contact, https://www.gradybabyco.com/shop/ina2bovnh2qdshvf8ddxblucv7p4e5-hjdde-ba4s3-22222-tknj2-lst8d-ktnz6-ctfmm-rn7g3 and https://www.gradybabyco.com/shop/ina2bovnh2qdshvf8ddxblucv7p4e5-hjdde-jm298-pax2l-zr4aa-5cz6f-wrs8x-pzflh-l6tfx-3k2sk-ctxff-h48dc-jgh27-fh9mf 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.

  • 8 internal pages checked

    We fetched 8 pages linked from your homepage and read each the way a search engine does.

6 checks passed
  • Linked pages load

    All 8 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.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 8 pages that loaded have a <title>.

Best practices

2 to fixGoogle 10078
  • 1 broken image

    1 image failed to load on a phone, for example https://d.adroll.com/uev/SUQ356VN3RHFXFG6TZXGC7/ZKE7PMPN6NFUTATICC6K6D/?adroll_tpc=lx3%3Dlex-875dcf7e-8824-4efd-8dd5-36b3b8e5e127&af0=0fe6f973&adroll_fpc=b885d70a3dfa0c9478283896b4957aab-1794558916896.

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://static1.squarespace.com/static/sitecss/5bcf152d34c4e2cc540a9390/163/5bdfc14d40ec9a…”.

2 checks passed
  • Tap targets are thumb-sized

    10 of 11 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix88
  • Thin social proof

    Social proof on the homepage: 1 testimonial or review block. Pairing it with named testimonials or customer logos makes it far more convincing.

  • Only about 93 words

    The homepage has only about 93 words of visible text; thin pages give Google and first-time buyers little to go on.

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

6 checks passed
  • Clear next step on the first screen

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

  • 7 calls to action

    The homepage has 7 calls to action, for example “Shop”, “Contact” and “Shop Now”.

  • Analytics in place

    Analytics detected: Google Analytics and Meta Pixel.

  • Opening hours shown

    Your opening hours are on the homepage.

  • Phone number on the homepage

    Your phone number is on the homepage.

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

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

  • 8 cookies set on arrival

    8

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

  • 16 other companies contacted

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

Upkeep, stack and company

  • The footer still says © 2023.

Stack

CMS
Squarespace
Analytics
Google Analytics
Hosting
Squarespace

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 gradybabyco.com, including 18 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