Website review, no card needed

daveshopchicken.com logo

daveshopchicken.com website review

Visit site (opens in a new tab)Reviewed 12 November 202628 issues · 73 checks

This review found 28 issues worth fixing on daveshopchicken.com, 9 of them high impact, across 73 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
822 ms689 msMay 23Nov 7807 ms
Show as table
DateReal-visitor load time (LCP)
May 23, 2026712 ms
May 30, 2026705 ms
Jun 6, 2026704 ms
Jun 13, 2026713 ms
Jun 20, 2026723 ms
Jun 27, 2026734 ms
Jul 4, 2026716 ms
Jul 11, 2026719 ms
Jul 18, 2026745 ms
Jul 25, 2026738 ms
Aug 1, 2026749 ms
Aug 8, 2026760 ms
Aug 15, 2026725 ms
Aug 22, 2026726 ms
Aug 29, 2026736 ms
Sep 5, 2026727 ms
Sep 12, 2026735 ms
Sep 19, 2026751 ms
Sep 26, 2026775 ms
Oct 3, 2026767 ms
Oct 10, 2026734 ms
Oct 17, 2026766 ms
Oct 24, 2026787 ms
Oct 31, 2026779 ms
Nov 7, 2026807 ms
Real-visitor tap response (INP)75th percentile, phones
89 ms73 msMay 23Nov 779 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 202675 ms
May 30, 202679 ms
Jun 6, 202679 ms
Jun 13, 202680 ms
Jul 18, 202678 ms
Jul 25, 202679 ms
Aug 1, 202679 ms
Aug 8, 202680 ms
Aug 22, 202681 ms
Aug 29, 202687 ms
Oct 10, 202679 ms
Oct 17, 202679 ms
Oct 24, 202679 ms
Oct 31, 202679 ms
Nov 7, 202679 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 daveshopchicken.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

6 to fix62
  • Reduce unused JavaScript

    4.5 s · 597 KiB

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

  • Avoid multiple page redirects

    3.6 s

    The page goes through 1 redirect before it starts loading, costing about 3.6 s. Link and advertise the final URL directly.

  • Mobile performance score: 62

    62/100

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

  • 7 third-party services on the page

    7 third-party services load with your homepage (Google Tag Manager, Facebook and audioeye.com and others), adding 1.6 MB and 831 ms of main-thread time.

  • Google Tag Manager adds 582 ms

    582 ms

    Google Tag Manager costs a phone 582 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.

  • Main-thread work: 2.1 s

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

  • Use efficient cache lifetimes

    224 KiB

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

  • Improve image delivery

    150 ms · 48 KiB

    3 images could be 48 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. 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 137 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).

  • Legacy JavaScript

    22 KiB

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

1 checks passed
  • Server response: 5 ms

    5 ms

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

Core Web Vitals

6 to fix100
  • Largest Contentful Paint: 11.8 s

    11.8 s

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

  • Time to Interactive: 16.5 s

    16.5 s

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

  • Total Blocking Time: 378 ms

    378 ms

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

  • Speed Index: 4.0 s

    4.0 s

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

  • First Contentful Paint: 2.0 s

    2.0 s

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

  • 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 75 ms to 79 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

    +12%

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

7 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: 0.7 s

    0.7 s

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

  • Real-user INP: 72 ms

    72 ms

    Real visitors wait 72 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: 0.5 s

    0.5 s

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

  • Real-user TTFB: 139 ms

    139 ms

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

1 to fix85
  • Page weight: 3.3 MB in 200 requests

    3.3 MB

    Your homepage downloads 3.3 MB in 200 requests on a phone: scripts 2.1 MB (84), other files 752 KiB (94) and images 269 KiB (8). Under 2 MB keeps phones on slow connections fast.

  • About 0.9 g of CO₂ per visit

    0.93 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • 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

2 to fixGoogle 9297
  • 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.

  • 4 links without text

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

2 checks passed
  • Every image has alt text

    All 3 images in the HTML carry an alt attribute.

  • 41 automated accessibility rules passed

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

SEO

4 to fixGoogle 9274
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • Title is short (8 characters)

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

  • No structured data

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

  • One H1 headline

    Your <h1> is empty.

  • 16 internal links, 0 external

    The homepage links to 16 pages on daveshopchicken.com and 0 external pages.

4 checks passed
  • Canonical URL set

    The canonical URL is https://daveshopchicken.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://daveshopchicken.com/sitemap.xml.

AI search readiness

1 to fix83
  • 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.

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

  • llms.txt published

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

Other pages

1 to fix95
  • 4 pages without a meta description

    https://daveshopchicken.com/collections/all-products, https://daveshopchicken.com/policies/privacy-policy, https://daveshopchicken.com/policies/refund-policy and https://daveshopchicken.com/policies/shipping-policy have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page with very little text

    https://daveshopchicken.com/collections/all-products 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.

  • 4 internal pages checked

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

6 checks passed
  • Linked pages load

    All 4 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 4 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 3 small tap targets

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

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • No calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

  • Only about 53 words

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

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

2 checks passed
  • 2 short forms

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

  • Analytics in place

    Analytics detected: Google Analytics and Meta Pixel.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

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

  • 12 cookies set on arrival

    12

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

  • 12 other companies contacted

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 28 issues on daveshopchicken.com, including 12 speed issues, 4 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