Website review, no card needed

daily-veggies.com logo

daily-veggies.com website review

Visit site (opens in a new tab)Reviewed 29 October 202631 issues · 77 checks

This review found 31 issues worth fixing on daily-veggies.com, 8 of them high impact, across 77 checks. The most urgent: fails Core Web Vitals for real visitors. 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

Full-page screenshot of daily-veggies.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

4 to fix71
  • Mobile performance score: 71

    71/100

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

  • Use efficient cache lifetimes

    300 ms · 183 KiB

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

  • Reduce unused CSS

    300 ms · 26 KiB

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

  • ucarecdn.com adds 0 ms

    0 ms

    ucarecdn.com costs a phone 0 ms of main-thread work and 692 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

    250 ms

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Klaviyo, cloudfront.net and Cloudflare and others), adding 884 KiB and 74 ms of main-thread time.

  • Minify CSS

    150 ms · 7 KiB

    7 KiB could be saved by minifying CSS.

  • Reduce unused JavaScript

    80 KiB

    About 80 KiB of JavaScript is downloaded but never used on this page.

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 72 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

    36 KiB

    Polyfills for old browsers add 36 KiB JavaScript that modern phones do not need.

  • Improve image delivery

    17 KiB

    1 image could be 17 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Minify JavaScript

    13 KiB

    13 KiB could be saved by minifying JavaScript.

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

2 checks passed
  • Main-thread work: 0.6 s

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

  • Server response: 4 ms

    4 ms

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

Core Web Vitals

10 to fix0
  • 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: 7.4 s

    7.4 s

    Your largest element takes 7.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “OUR LOCATIONS Daily Veggies operates facilities in the U.S.…”.

  • Time to Interactive: 7.4 s

    7.4 s

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

  • Real-user LCP: 2.8 s

    2.8 s

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

  • Real-user INP: 269 ms

    269 ms

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

  • Real-user CLS: 0.22

    0.22

    For real visitors the layout shifts by 0.22 (75th percentile). Good is under 0.1.

  • Real-user FCP: 2.0 s

    2.0 s

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

  • Real-user TTFB: 943 ms

    943 ms

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

  • Speed Index: 5.4 s

    5.4 s

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

  • 1 image without width and height

    1 image have no width and height attributes, so the layout jumps as each one loads.

3 checks passed
  • First Contentful Paint: 1.7 s

    1.7 s

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

  • Cumulative Layout Shift: 0.002

    0.002

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

  • Total Blocking Time: 22 ms

    22 ms

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

Images and page weight

100
  • About 0.3 g of CO₂ per visit

    0.33 g

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

4 checks passed
  • Page weight: 1.2 MB in 58 requests

    1.2 MB

    Your homepage downloads 1.2 MB in 58 requests on a phone: images 712 KiB (6), scripts 336 KiB (33) and fonts 75 KiB (3). That is a lean page.

  • 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

4 to fixGoogle 9594
  • 4 text elements with low contrast

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

  • 2 images without alt text

    2 images have no alt text, which hurts accessibility and image search.

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate 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 → h3 and h1 → h4), which makes the page harder to scan with a screen reader.

1 checks passed
  • 47 automated accessibility rules passed

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

SEO

3 to fixGoogle 9278
  • No meta description

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

  • Title is short (13 characters)

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

  • 4 H1 headlines

    There are 4 <h1> headlines (“<img src="https://cdn.shopify.com/s/files/1/0269/…”, “FRESH VEGGIES,” and “EVERYDAY.”). One clear main headline is easier for people and search engines.

  • 36 internal links, 1 external

    The homepage links to 36 pages on daily-veggies.com and 1 external page.

5 checks passed
  • Canonical URL set

    The canonical URL is https://www.daily-veggies.com/.

  • Structured data in place

    Structured data found: Organization and WebSite.

  • 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://daily-veggies.com/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://daily-veggies.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.

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.

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

Other pages

3 to fix75
  • 8 pages without a title

    https://daily-veggies.com/pages/quality-assurance, https://daily-veggies.com/pages/story, https://daily-veggies.com/pages/social-responsibility, https://daily-veggies.com/pages/distribution-area, https://daily-veggies.com/pages/contact and https://daily-veggies.com/pages/locations and 2 others have no <title>, so Google invents the link text in results.

  • 8 pages without a meta description

    https://daily-veggies.com/pages/quality-assurance, https://daily-veggies.com/pages/story, https://daily-veggies.com/pages/social-responsibility, https://daily-veggies.com/pages/distribution-area, https://daily-veggies.com/pages/contact and https://daily-veggies.com/pages/locations and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 10 pages without an H1

    https://daily-veggies.com/pages/asian-vegetables, https://daily-veggies.com/pages/classic-vegetables, https://daily-veggies.com/pages/quality-assurance, https://daily-veggies.com/pages/story, https://daily-veggies.com/pages/social-responsibility and https://daily-veggies.com/pages/distribution-area and 4 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 8 pages with very little text

    https://daily-veggies.com/pages/quality-assurance, https://daily-veggies.com/pages/story, https://daily-veggies.com/pages/social-responsibility, https://daily-veggies.com/pages/distribution-area, https://daily-veggies.com/pages/contact and https://daily-veggies.com/pages/locations and 2 others 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.

  • 11 internal pages checked

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

4 checks passed
  • Linked pages load

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

Best practices

3 to fixGoogle 9285
  • 6 small tap targets

    6 of 13 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: the server responded with a status of 404 ()”.

  • 2 distorted images

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix71
  • 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 111 words

    The homepage has only about 111 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.

4 checks passed
  • Clear next step on the first screen

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

  • 9 calls to action

    The homepage has 9 calls to action, for example “Contact”, “SUBSCRIBE” and “Get started today”.

  • 5 short forms

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

  • Analytics in place

    Analytics detected: Cloudflare Web Analytics.

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads Klaviyo (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.

  • 15 other companies contacted

    Loading the homepage contacts 15 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 daily-veggies.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 © 2022.

Stack

Framework
jQuery
E-commerce
Shopify
Hosting
Cloudflare

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 31 issues on daily-veggies.com, including 14 speed issues, 3 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