Website review, no card needed

theoniontreemealprep.com logo

theoniontreemealprep.com website review

Visit site (opens in a new tab)Reviewed 10 November 202636 issues · 80 checks

This review found 36 issues worth fixing on theoniontreemealprep.com, 13 of them high impact, across 80 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

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

How it loaded on a phone

  1. theoniontreemealprep.com at 0.4 s0.4 s
  2. theoniontreemealprep.com at 0.8 s0.8 s
  3. theoniontreemealprep.com at 1.3 s1.3 s
  4. theoniontreemealprep.com at 1.7 s1.7 s
  5. theoniontreemealprep.com at 2.1 s2.1 s
  6. theoniontreemealprep.com at 2.5 s2.5 s
  7. theoniontreemealprep.com at 2.9 s2.9 s
  8. theoniontreemealprep.com at 3.4 s3.4 s

Speed

11 to fix57
  • Reduce unused JavaScript

    1.1 s · 550 KiB

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

  • Render-blocking requests

    1.0 s

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

  • Main-thread work: 4.7 s

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

  • Improve image delivery

    450 ms · 2.9 MB

    14 images could be 2.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Shopify, Klaviyo and loox.io and others), adding 1.9 MB and 1.2 s of main-thread time.

  • Mobile performance score: 57

    57/100

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

  • Shopify adds 511 ms

    511 ms

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

  • Klaviyo adds 238 ms

    238 ms

    Klaviyo costs a phone 238 ms of main-thread work and 421 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.

  • loox.io adds 140 ms

    140 ms

    loox.io costs a phone 140 ms of main-thread work and 335 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.

  • 1,666 HTML elements

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

  • smile.io adds 47 ms

    47 ms

    smile.io costs a phone 47 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 · 38 KiB

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

  • 11 long tasks on the main thread

    11 long tasks block the main thread while loading, the longest for 154 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).

  • Use efficient cache lifetimes

    35 KiB

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

  • Minify JavaScript

    28 KiB

    28 KiB could be saved by minifying JavaScript.

  • Legacy JavaScript

    25 KiB

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

  • Minify CSS

    12 KiB

    12 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: 8 ms

    8 ms

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

Core Web Vitals

6 to fix52
  • Largest Contentful Paint: 12.2 s

    12.2 s

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

  • Time to Interactive: 15.9 s

    15.9 s

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

  • Speed Index: 6.2 s

    6.2 s

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

  • Cumulative Layout Shift: 0.184

    0.184

    The layout shifts by 0.184 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Total Blocking Time: 208 ms

    208 ms

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

  • 8 images without width and height

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

1 checks passed
  • First Contentful Paint: 1.1 s

    1.1 s

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

Images and page weight

4 to fix25
  • Page weight: 5.9 MB in 294 requests

    5.9 MB

    Your homepage downloads 5.9 MB in 294 requests on a phone: images 3.2 MB (22), scripts 1.5 MB (110) and other files 850 KiB (123). Under 2 MB keeps phones on slow connections fast.

  • 4 images over 500 KB

    4 images weigh 3.5 MB together. On a phone connection a single image that size takes seconds.

  • 4 images far larger than shown

    2.2 MB

    4 images are downloaded at several times the size a phone draws them, for example 4.gif at 640 px wide, shown at 128 px. Resized copies would save about 2.2 MB.

  • 4 images in older formats

    4 images (3.5 MB) are 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 1.7 g of CO₂ per visit

    1.67 g

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

1 checks passed
  • Images load when needed

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

Accessibility

5 to fixGoogle 9795
  • 23 text elements with low contrast

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

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

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

  • Document should not have more than one banner landmark (1 element)

    Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

  • 3 form fields without a label

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

2 checks passed
  • Every image has alt text

    All 31 images in the HTML carry an alt attribute.

  • 51 automated accessibility rules passed

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

SEO

4 to fixGoogle 9275
  • No meta description

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

  • Title is short (23 characters)

    Your title is only 23 characters: “The Oniontree meal Prep”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No social preview image

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

  • One H1 headline

    Your <h1> is empty.

  • 54 internal links, 7 external

    The homepage links to 54 pages on theoniontreemealprep.com and 7 external pages.

4 checks passed
  • Canonical URL set

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

  • Structured data in place

    Structured data found: Organization and WebSite.

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

AI search readiness

100
  • No llms.txt

    There is no https://www.theoniontreemealprep.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.

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.

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

Other pages

3 to fix88
  • 3 pages without a meta description

    https://www.theoniontreemealprep.com/collections/meal-plans, https://www.theoniontreemealprep.com/collections/ala-carte and https://www.theoniontreemealprep.com/pages/contact have no meta description, so Google writes the search snippet from whatever text it finds.

  • 4 pages share a meta description

    https://www.theoniontreemealprep.com/products/5-meal-plan-indian-menu, https://www.theoniontreemealprep.com/products/6-meal-plan-indian-menu, https://www.theoniontreemealprep.com/products/7-meal-plan-indian-menu and https://www.theoniontreemealprep.com/products/10-meal-plan-indian-menu use the same meta description. A description written for each page earns more clicks.

  • 5 pages without an H1

    https://www.theoniontreemealprep.com/products/5-meal-plan-indian-menu, https://www.theoniontreemealprep.com/products/6-meal-plan-indian-menu, https://www.theoniontreemealprep.com/products/7-meal-plan-indian-menu, https://www.theoniontreemealprep.com/products/10-meal-plan-indian-menu and https://www.theoniontreemealprep.com/pages/contact 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 20 found) and read each the way a search engine does.

5 checks passed
  • Linked pages load

    8 pages of 15 loaded without an error (the rest turned automated requests away).

  • 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 8 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9684
  • 2 broken images

    2 images failed to load on a phone, for example https://www.theoniontreemealprep.com/.

3 checks passed
  • No console errors

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

  • Tap targets are thumb-sized

    17 of 19 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix83
  • No social proof

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

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

  • About 576 words of copy

    The homepage carries about 576 words of visible text.

5 checks passed
  • Clear next step on the first screen

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

  • 6 calls to action

    The homepage has 6 calls to action, for example “Contact”, “Order Online” and “Contact information”.

  • 3 short forms

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

  • Analytics in place

    Analytics detected: Microsoft Clarity.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

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

  • 11 cookies set on arrival

    11

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

  • 26 other companies contacted

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

Upkeep, stack and company

Stack

E-commerce
10 Shopify Products;Shopify;Shopify Plus
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 theoniontreemealprep.com, including 17 speed issues, 4 SEO issues and 1 conversion gap. 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