rebuiltmeals.com website review

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

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

7 third-party services load with your homepage (Google Tag Manager, Shopify and Yotpo and others), adding 10.2 MB and 589 ms of main-thread time.

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

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

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

Google Tag Manager costs a phone 375 ms of main-thread work and 504 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.

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

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

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

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

7 KiB could be saved by minifying JavaScript.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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

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

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

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

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

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

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

Your homepage downloads 10.5 MB in 94 requests on a phone: images 8.9 MB (36), scripts 777 KiB (33) and fonts 378 KiB (3). Under 2 MB keeps phones on slow connections fast.

5 images weigh 8.1 MB together. On a phone connection a single image that size takes seconds.

6 images are downloaded at several times the size a phone draws them, for example 8L1-ChimichurriSearedFlatIronSteak2.png at 3,000 px wide, shown at 51 px. Resized copies would save about 8.1 MB.

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

1 image (30 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.

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

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

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

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

Headings skip levels (h2 → h4 and h2 → h5), which makes the page harder to scan with a screen reader.

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

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

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

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 30 pages on rebuiltmeals.com and 3 external pages.

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.

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

https://www.rebuiltmeals.com/pages/contact-us and https://www.rebuiltmeals.com/contact all use the title “Contact Rebuilt Meals”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.rebuiltmeals.com/products/pick-your-plan, https://www.rebuiltmeals.com/about, https://www.rebuiltmeals.com/pages/contact-us, https://www.rebuiltmeals.com/mealplan, https://www.rebuiltmeals.com/reviews and https://www.rebuiltmeals.com/pickuplocation and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.rebuiltmeals.com/products/pick-your-plan and https://www.rebuiltmeals.com/mealplan have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.rebuiltmeals.com/products/pick-your-plan, https://www.rebuiltmeals.com/mealplan and https://www.rebuiltmeals.com/faqs 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.

We fetched 15 pages linked from your homepage (of 16 found) and read each the way a search engine does.

3 errors were logged to the browser console while the page loaded, for example “Connecting to 'https://ad.doubleclick.net/ccm/s/collect?auid=1866696791.1794411062&gtm=45He6b91h1v9244680471za200zd9244…”.

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

Chrome logged issues while loading the page (“Content security policy”).

Large scripts ship without source maps.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 592 words of visible text.

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

Opening the homepage sets 4 cookies (measured from a US location before any click).

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.

Loading the homepage contacts 10 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.