Website review, no card needed

donnasrecipe.com logo

donnasrecipe.com website review

Visit site (opens in a new tab)Reviewed 8 November 202643 issues · 90 checks

This review found 43 issues worth fixing on donnasrecipe.com, 14 of them high impact, across 90 checks. The most urgent: reduce unused JavaScript. 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.1 s1.7 sMay 16Oct 312.0 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.8 s
May 23, 20261.8 s
May 30, 20261.8 s
Jun 6, 20261.8 s
Jun 13, 20261.8 s
Jun 20, 20261.8 s
Jun 27, 20261.8 s
Jul 4, 20261.8 s
Jul 11, 20261.8 s
Jul 18, 20261.8 s
Jul 25, 20261.7 s
Aug 1, 20261.8 s
Aug 8, 20261.8 s
Aug 15, 20261.8 s
Aug 22, 20261.8 s
Aug 29, 20261.8 s
Sep 5, 20261.9 s
Sep 12, 20261.9 s
Sep 19, 20262.0 s
Sep 26, 20262.0 s
Oct 3, 20262.0 s
Oct 10, 20262.1 s
Oct 17, 20262.1 s
Oct 24, 20262.0 s
Oct 31, 20262.0 s
Real-visitor tap response (INP)75th percentile, phones
159 ms125 msMay 16Oct 31155 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026135 ms
May 23, 2026131 ms
May 30, 2026130 ms
Jun 6, 2026130 ms
Jun 13, 2026137 ms
Jun 20, 2026141 ms
Jun 27, 2026146 ms
Jul 4, 2026145 ms
Jul 11, 2026138 ms
Jul 18, 2026136 ms
Jul 25, 2026129 ms
Aug 1, 2026132 ms
Aug 8, 2026138 ms
Aug 15, 2026136 ms
Aug 22, 2026137 ms
Aug 29, 2026137 ms
Sep 5, 2026132 ms
Sep 12, 2026135 ms
Sep 19, 2026136 ms
Sep 26, 2026137 ms
Oct 3, 2026138 ms
Oct 10, 2026146 ms
Oct 17, 2026153 ms
Oct 24, 2026152 ms
Oct 31, 2026155 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 donnasrecipe.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. donnasrecipe.com at 1.2 s1.2 s
  2. donnasrecipe.com at 2.4 s2.4 s
  3. donnasrecipe.com at 3.6 s3.6 s
  4. donnasrecipe.com at 4.8 s4.8 s
  5. donnasrecipe.com at 6.0 s6.0 s
  6. donnasrecipe.com at 7.1 s7.1 s
  7. donnasrecipe.com at 8.3 s8.3 s
  8. donnasrecipe.com at 9.5 s9.5 s

Speed

12 to fix62
  • Reduce unused JavaScript

    5.0 s · 1.1 MB

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

  • Improve image delivery

    3.5 s · 734 KiB

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

  • Main-thread work: 5.7 s

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

  • 3,443 HTML elements

    The page has 3,443 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 (Shopify, Klaviyo and Google CDN and others), adding 2.5 MB and 1.1 s of main-thread time.

  • Mobile performance score: 62

    62/100

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

  • Use efficient cache lifetimes

    650 ms · 172 KiB

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

  • Shopify adds 516 ms

    516 ms

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

  • Klaviyo adds 398 ms

    398 ms

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

    450 ms

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

  • Google CDN adds 104 ms

    104 ms

    Google CDN costs a phone 104 ms of main-thread work and 299 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.

  • rechargecdn.com adds 64 ms

    64 ms

    rechargecdn.com costs a phone 64 ms of main-thread work and 296 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 · 66 KiB

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

  • 5 long tasks on the main thread

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

  • Legacy JavaScript

    100 ms · 25 KiB

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

  • Minify CSS

    6 KiB

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

    13 ms

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

  • Largest Contentful Paint: 24.5 s

    24.5 s

    Your largest element takes 24.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: 24.5 s

    24.5 s

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

  • Speed Index: 12.0 s

    12.0 s

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

  • Real-user LCP: 2.9 s

    2.9 s

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

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

    +15%

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

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

    +13%

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

7 checks passed
  • 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.4 s

    1.4 s

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

  • Real-user TTFB: 707 ms

    707 ms

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

  • Total Blocking Time: 199 ms

    199 ms

    Scripts block the page for only 199 ms while loading. Good is under 200 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

3 to fix45
  • Page weight: 16.0 MB in 536 requests

    16.0 MB

    Your homepage downloads 16.0 MB in 536 requests on a phone: media 10.8 MB (2), scripts 2.5 MB (229) and other files 1.2 MB (224). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    249ffabb-1b0b-4a67-9c3a-5b6c21e79a71.png weighs 817 KiB. On a phone connection a single image that size takes seconds.

  • 1 image in older formats

    1 image (817 KiB) is 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.

  • About 4.5 g of CO₂ per visit

    4.52 g

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

2 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

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

Accessibility

6 to fixGoogle 8793
  • Images must have alternative text (1 element)

    Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.

  • 3 text elements with low contrast

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

  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

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

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

  • 2 links without text

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

  • Headings should not be empty (1 element)

    Headings should not be empty: 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. (2 elements).

1 checks passed
  • 57 automated accessibility rules passed

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

SEO

5 to fixGoogle 8581
  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • Meta description is long (222 characters)

    Your meta description is 222 characters; Google truncates after about 160, so the end of your pitch is cut.

  • No social preview image

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

  • 2 links with vague text

    2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • One H1 headline

    Your <h1> is empty.

  • 104 internal links, 26 external

    The homepage links to 104 pages on donnasrecipe.com and 26 external pages.

4 checks passed
  • Title: 33 characters

    Your title is a healthy 33 characters: “Donna's Recipe || Hair Care Brand”.

  • Canonical URL set

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

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

AI search readiness

1 to fix88
  • No Organization structured data

    There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

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

  • llms.txt published

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

Other pages

2 to fix90
  • 1 page without a meta description

    https://www.donnasrecipe.com/pages/loyalty-program has no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages without an H1

    https://www.donnasrecipe.com/pages/reviews and https://www.donnasrecipe.com/pages/loyalty-program 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 42 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 9271
  • 1 broken image

    1 image failed to load on a phone, for example https://cdnjs.cloudflare.com/ajax/libs/flag-icon-css/4.1.4/flags/4x3/us.svg.

  • 18 small tap targets

    18 of 41 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 “Failed to load resource: net::ERR_FAILED”.

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix69
  • 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.

  • No phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • Thin social proof

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

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • 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 opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • 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 2,727 words of copy

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

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Shop Now”.

  • 11 calls to action

    The homepage has 11 calls to action, for example “SHOP”, “Apply” and “Shop Now”.

  • 5 short forms

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

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

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

  • 29 cookies set on arrival

    29

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

  • 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 donnasrecipe.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 15 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Klaviyo Email Marketing Sms · Judge Me Reviews · Gempages Builder · Instafeed · Uppromote Affiliate · Gorgias Live Chat Helpdesk · Google Youtube · Forms · Rivo Loyalty Rewards Referrals · Affliate By Secomapp · rechargecdn.com · herokuapp.com · electricsms.com · nfcube.com · 9gtb.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

E-commerce
Shopify
Hosting
Shopify

Company

Headquarters
Los Angeles

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 43 issues on donnasrecipe.com, including 17 speed issues, 5 SEO issues and 5 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