Website review, no card needed

shopfavoritedaughter.com logo

shopfavoritedaughter.com website review

Visit site (opens in a new tab)Reviewed 8 November 202628 issues · 84 checks

This review found 28 issues worth fixing on shopfavoritedaughter.com, 12 of them high impact, across 84 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.4 sMay 16Oct 312.5 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.6 s
May 23, 20262.7 s
May 30, 20262.7 s
Jun 6, 20262.7 s
Jun 13, 20262.8 s
Jun 20, 20262.7 s
Jun 27, 20262.7 s
Jul 4, 20262.6 s
Jul 11, 20262.6 s
Jul 18, 20262.6 s
Jul 25, 20262.6 s
Aug 1, 20262.5 s
Aug 8, 20262.5 s
Aug 15, 20262.5 s
Aug 22, 20262.5 s
Aug 29, 20262.5 s
Sep 5, 20262.6 s
Sep 12, 20262.6 s
Sep 19, 20262.6 s
Sep 26, 20262.5 s
Oct 3, 20262.5 s
Oct 10, 20262.4 s
Oct 17, 20262.4 s
Oct 24, 20262.5 s
Oct 31, 20262.5 s
Real-visitor tap response (INP)75th percentile, phones
190 ms111 msMay 16Oct 31175 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026120 ms
May 23, 2026121 ms
May 30, 2026126 ms
Jun 6, 2026127 ms
Jun 13, 2026128 ms
Jun 20, 2026129 ms
Jun 27, 2026134 ms
Jul 4, 2026141 ms
Jul 11, 2026141 ms
Jul 18, 2026142 ms
Jul 25, 2026146 ms
Aug 1, 2026151 ms
Aug 8, 2026165 ms
Aug 15, 2026173 ms
Aug 22, 2026177 ms
Aug 29, 2026179 ms
Sep 5, 2026179 ms
Sep 12, 2026175 ms
Sep 19, 2026172 ms
Sep 26, 2026171 ms
Oct 3, 2026178 ms
Oct 10, 2026179 ms
Oct 17, 2026181 ms
Oct 24, 2026181 ms
Oct 31, 2026175 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 shopfavoritedaughter.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

2 to fix95
  • Render-blocking requests

    1.8 s

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

  • 4,366 HTML elements

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

  • Use efficient cache lifetimes

    155 KiB

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

  • Reduce unused CSS

    152 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (shgcdn3.com, cloudfront.net and negate.io and others), adding 194 KiB and 37 ms of main-thread time.

  • Font display

    50 ms

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

  • Improve image delivery

    21 KiB

    2 images could be 21 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

    5 KiB

    5 KiB could be saved by minifying CSS.

3 checks passed
  • Mobile performance score: 95

    95/100

    Your mobile performance score is 95. That is in Google's “good” band (90 and up).

  • Main-thread work: 0.6 s

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

  • Server response: 26 ms

    26 ms

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

Core Web Vitals

5 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: 2.7 s

    2.7 s

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

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

    +48%

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

  • First Contentful Paint: 2.3 s

    2.3 s

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

  • Speed Index: 3.5 s

    3.5 s

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

  • Largest content (LCP) held steady for real visitors

    -5%

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

8 checks passed
  • Real-user INP: 195 ms

    195 ms

    Real visitors wait 195 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: 445 ms

    445 ms

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

  • Largest Contentful Paint: 2.3 s

    2.3 s

    Your largest element renders in 2.3 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “25% OFF EVERYTHING. HAPPY DAUGHTERS DAY”.

  • Time to Interactive: 2.3 s

    2.3 s

    The page is fully interactive after 2.3 s.

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 0 ms

    0 ms

    Scripts block the page for only 0 ms while loading. Good is under 200 ms.

Images and page weight

1 to fix93
  • 15 images below the first screen load straight away

    15 images further down the page (1.2 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 0.5 g of CO₂ per visit

    0.50 g

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

3 checks passed
  • Page weight: 1.8 MB in 70 requests

    1.8 MB

    Your homepage downloads 1.8 MB in 70 requests on a phone: scripts 710 KiB (39), fonts 428 KiB (5) and images 393 KiB (12). That is a lean page.

  • 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 8786
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • 6 text elements with low contrast

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

  • ARIA input fields must have an accessible name (4 elements)

    ARIA input fields must have an accessible name: 4 elements on the page fail this check, rated serious by axe-core.

  • Interactive controls must not be nested (3 elements)

    Interactive controls must not be nested: 3 elements on the page fail this check, rated serious by axe-core.

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

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • 1 tap target too small

    1 tap target is too small or too close together to hit reliably with a finger.

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

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

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

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

  • Headings skip levels

    Headings skip levels (h1 → h4, h2 → h6 and h2 → 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).

2 checks passed
  • Every image has alt text

    All 15 images in the HTML carry an alt attribute.

  • 49 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 59 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 10 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 10089
  • Title is short (17 characters)

    Your title is only 17 characters: “Favorite Daughter”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Structured data has 1 problem

    Structured data found (Organization and WebSite) but with 1 problem, for example “Organization: logo is not an absolute URL ("//shopfavoritedaughter.com/cdn/shop/files/logo.jpg?v=16…”.

  • 204 internal links, 13 external

    The homepage links to 204 pages on shopfavoritedaughter.com and 13 external pages.

6 checks passed
  • Meta description: 144 characters

    Your meta description is 144 characters: “Save your favorite women’s clothing and accessories in one place. Keep track of the styles you love and come back whene…”.

  • One H1 headline

    Your main headline reads: “Favorite Daughter”.

  • Canonical URL set

    The canonical URL is https://shopfavoritedaughter.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://shopfavoritedaughter.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: 5 of 6 facts

    Your Organization JSON-LD gives name, url, logo, description and contact details; sameAs (social profiles) would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (2,303 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

2 to fix90
  • 6 pages without a meta description

    https://shopfavoritedaughter.com/pages/rewards, https://shopfavoritedaughter.com/collections/coats-1, https://shopfavoritedaughter.com/collections/skirts-shorts, https://shopfavoritedaughter.com/collections/tees-tanks, https://shopfavoritedaughter.com/collections/vests and https://shopfavoritedaughter.com/collections/sweatshirts have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 pages without an H1

    https://shopfavoritedaughter.com/collections/new-arrivals, https://shopfavoritedaughter.com/pages/rewards, https://shopfavoritedaughter.com/collections/denim, https://shopfavoritedaughter.com/collections/petite, https://shopfavoritedaughter.com/collections/coats-1 and https://shopfavoritedaughter.com/collections/jackets and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 5 pages slow to respond

    https://shopfavoritedaughter.com/collections/skirts-shorts, https://shopfavoritedaughter.com/collections/tops, https://shopfavoritedaughter.com/collections/sweaters, https://shopfavoritedaughter.com/collections/tees-tanks and https://shopfavoritedaughter.com/collections/vests took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

3 to fixGoogle 10071
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=56313593&tm=gtm002&Ver=2&mid=ceafb3e9-99e4-4361-a44d-45420db5db24&bo=1&sid=06315060db8711f184f0191cdacae18f&vid=06317840db8711f1b70089055bf2b661&vids=1&msclkid=N&pi=91.

  • 21 small tap targets

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

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_EMPTY_RESPONSE”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix67
  • 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: 1 trust badge. 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 315 words of copy

    The homepage carries about 315 words of visible text.

  • Urgency cues

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

3 checks passed
  • 21 calls to action

    The homepage has 21 calls to action, for example “SUBSCRIBE”, “Shop .cls-1{fill:#231f20} expand” and “SHOP BY OCCASION”.

  • 7 short forms

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

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

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, Klaviyo and Microsoft Ads (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.

  • 25 cookies set on arrival

    25

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

  • 51 other companies contacted

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

Apps your storefront loads

Consentmo Gdpr · Tapcart Mobile App · Littledata The Data Layer · Attentive · Triplewhale · Product Filters Search · Checkmate · Klaviyo Email Marketing Sms · Yotpo Loyalty Rewards · Tapita Seo Speed · Gdpr Backpack · Loop Returns · Back In Stock · pepperjam.com · bluecore.com · attn.tv · gorgias.chat · bazaarvoice.com · amazonaws.com · 9gtb.com · googleapis.com · nfcube.com · Swym Wishlist Plus

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
Google Analytics | Google Tag Manager
Hosting
Shopify

Hiring

Hiring
50 open roles
Job board
icims

Company

Headquarters
Compton

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 28 issues on shopfavoritedaughter.com, including 7 speed issues, 2 SEO issues 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