Website review, no card needed

lilaandhayes.com logo

lilaandhayes.com website review

Visit site (opens in a new tab)Reviewed 22 November 202636 issues · 90 checks

This review found 36 issues worth fixing on lilaandhayes.com, 13 of them high impact, across 90 checks. The most urgent: page weight: 53.5 MB in 335 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.6 s1.2 sMay 30Nov 142.0 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20261.4 s
Jun 6, 20261.4 s
Jun 13, 20261.8 s
Jun 20, 20262.1 s
Jun 27, 20261.9 s
Jul 4, 20262.0 s
Jul 11, 20261.7 s
Jul 18, 20261.8 s
Jul 25, 20261.6 s
Aug 1, 20261.6 s
Aug 8, 20261.6 s
Aug 15, 20261.7 s
Aug 22, 20261.9 s
Aug 29, 20262.0 s
Sep 5, 20262.0 s
Sep 12, 20262.0 s
Sep 19, 20262.1 s
Sep 26, 20261.9 s
Oct 3, 20262.0 s
Oct 10, 20262.1 s
Oct 17, 20262.0 s
Oct 24, 20262.4 s
Oct 31, 20262.4 s
Nov 7, 20262.4 s
Nov 14, 20262.0 s
Real-visitor tap response (INP)75th percentile, phones
215 ms77 msMay 30Nov 14158 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 202693 ms
Jun 6, 2026101 ms
Jun 13, 2026128 ms
Jun 20, 2026150 ms
Jun 27, 2026160 ms
Jul 4, 2026178 ms
Jul 11, 2026180 ms
Jul 18, 2026169 ms
Jul 25, 2026160 ms
Aug 1, 2026150 ms
Aug 8, 2026149 ms
Aug 15, 2026153 ms
Aug 22, 2026158 ms
Aug 29, 2026171 ms
Sep 5, 2026167 ms
Sep 12, 2026179 ms
Sep 19, 2026193 ms
Sep 26, 2026187 ms
Oct 3, 2026199 ms
Oct 10, 2026196 ms
Oct 17, 2026179 ms
Oct 24, 2026183 ms
Oct 31, 2026178 ms
Nov 7, 2026176 ms
Nov 14, 2026158 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 lilaandhayes.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

9 to fix63
  • Render-blocking requests

    1.6 s

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

  • 7,884 HTML elements

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

  • Main-thread work: 5.1 s

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

  • Improve image delivery

    1.8 MB

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

  • Use efficient cache lifetimes

    900 ms · 221 KiB

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

  • Mobile performance score: 63

    63/100

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

  • Reduce unused JavaScript

    300 ms · 200 KiB

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

  • 10 long tasks on the main thread

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

  • Shopify adds 168 ms

    168 ms

    Shopify costs a phone 168 ms of main-thread work and 334 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.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Shopify, termly.io and cloudfront.net and others), adding 640 KiB and 329 ms of main-thread time.

  • Reduce unused CSS

    150 ms · 36 KiB

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

  • Duplicated JavaScript

    15 KiB

    15 KiB JavaScript is shipped twice across bundles.

  • Legacy JavaScript

    10 KiB

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

  • Minify JavaScript

    3 KiB

    3 KiB could be saved by minifying JavaScript.

  • Minify CSS

    2 KiB

    2 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 31 ms

    31 ms

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

Core Web Vitals

6 to fix100
  • Largest Contentful Paint: 6.5 s

    6.5 s

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

  • Time to Interactive: 10.0 s

    10.0 s

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

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

    +72%

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

  • Largest content (LCP) got 56% slower for real visitors

    +56%

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

  • Total Blocking Time: 483 ms

    483 ms

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

  • Speed Index: 3.8 s

    3.8 s

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

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

    1.8 s

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

  • Real-user INP: 163 ms

    163 ms

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

  • Real-user CLS: 0.01

    0.01

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

    532 ms

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

  • First Contentful Paint: 1.4 s

    1.4 s

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

2 to fix64
  • Page weight: 53.5 MB in 335 requests

    53.5 MB

    Your homepage downloads 53.5 MB in 335 requests on a phone: media 47.8 MB (4), images 3.6 MB (108) and other files 1,008 KiB (132). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    60_9bcd2d50-d329-4d9c-be71-83cc30c59652.png 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).

  • About 15.2 g of CO₂ per visit

    15.15 g

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

9 to fixGoogle 8087
  • Elements must only use permitted ARIA attributes (225 elements)

    Elements must only use permitted ARIA attributes: 225 elements on the page fail this check, rated serious by axe-core.

  • Certain ARIA roles must contain particular children (12 elements)

    Certain ARIA roles must contain particular children: 12 elements on the page fail this check, rated critical by axe-core.

  • 15 text elements with low contrast

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

  • Hidden but focusable

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

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

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

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

  • 7 links without text

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

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

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

  • 2 form fields without a label

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

  • Headings skip levels

    Headings skip levels (h1 → h4), 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
  • 46 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 8 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 10095
  • One H1 headline

    Your <h1> is empty.

  • 297 internal links, 3 external

    The homepage links to 297 pages on lilaandhayes.com and 3 external pages.

7 checks passed
  • Meta description: 157 characters

    Your meta description is 157 characters: “Shop Lila & Hayes for premium Pima cotton clothing for babies, kids, women and families. Discover timeless designs, eve…”.

  • Title: 64 characters

    Your title is a healthy 64 characters: “Lila & Hayes – Premium Pima Cotton Clothing for the Whole Family”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: Organization, WebSite and localbusiness.

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

  • llms.txt published

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

Other pages

4 to fix68
  • 1 page without a title

    https://www.lilaandhayes.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

  • 1 linked page hidden from search

    https://www.lilaandhayes.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 1 page without a meta description

    https://www.lilaandhayes.com/customer_authentication/redirect has no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://www.lilaandhayes.com/customer_authentication/redirect has 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 103 found) and read each the way a search engine does.

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

Best practices

2 to fixGoogle 9291
  • 3 JavaScript errors while loading

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

  • 8 distorted images

    8 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

2 checks passed
  • Tap targets are thumb-sized

    31 of 38 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix78
  • 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.

  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • Thin social proof

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

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

  • About 476 words of copy

    The homepage carries about 476 words of visible text.

6 checks passed
  • 57 calls to action

    The homepage has 57 calls to action, for example “Shop All Holiday”, “Shop All Fall” and “Shop All Clubhouse Prints”.

  • 13 short forms

    13 short forms (0 fields at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Microsoft Clarity.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 1 email link.

  • Opening hours shown

    Your opening hours are on the homepage.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

  • 4 trackers load before any consent

    4

    Before a visitor clicks anything, the page loads Klaviyo, Meta Pixel, Microsoft Clarity and Pinterest Tag (measured from a US location before any click). A consent tool (Termly) is installed; check it blocks these until visitors agree where the law requires it.

  • 14 cookies set on arrival

    14

    Opening the homepage sets 14 cookies (measured from a US location before any click).

  • 21 other companies contacted

    Loading the homepage contacts 21 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • Consent tool: Termly

    A consent management tool (Termly) 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 lilaandhayes.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 16 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Microsoft Clarity · Ta Mappy Store Locator Maps · Okendo · Gorgias Live Chat Helpdesk · Klaviyo Email Marketing Sms · Selleasy · Loop Returns · cloudfront.net · privy.com · w3apps.co · chimpstatic.com · laralancer.com · luckyorange.com · shareasale.com · hextom.com · nfcube.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
Analytics
Microsoft Clarity
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 36 issues on lilaandhayes.com, including 15 speed issues, 1 SEO issue and 3 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