Website review, no card needed
whatacrockmeals.com website review
Visit site (opens in a new tab)Reviewed 9 November 202634 issues · 87 checks
This review found 34 issues worth fixing on whatacrockmeals.com, 14 of them high impact, across 87 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
84B- #22,442 of 125,932 reviewed websitesbeats 77%
- #14,324 of 70,307 online storesbeats 74%
- #13,887 of 63,856 Shopify storesbeats 72%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 1.8 s |
| May 30, 2026 | 1.8 s |
| Jun 6, 2026 | 1.8 s |
| Jun 13, 2026 | 1.8 s |
| Jun 20, 2026 | 1.8 s |
| Jun 27, 2026 | 1.8 s |
| Jul 4, 2026 | 1.8 s |
| Jul 11, 2026 | 1.8 s |
| Jul 18, 2026 | 1.8 s |
| Jul 25, 2026 | 1.8 s |
| Aug 1, 2026 | 1.8 s |
| Aug 8, 2026 | 1.7 s |
| Aug 15, 2026 | 1.7 s |
| Aug 22, 2026 | 1.6 s |
| Aug 29, 2026 | 1.6 s |
| Sep 5, 2026 | 1.6 s |
| Sep 12, 2026 | 1.6 s |
| Sep 19, 2026 | 1.7 s |
| Sep 26, 2026 | 1.7 s |
| Oct 3, 2026 | 1.7 s |
| Oct 10, 2026 | 1.8 s |
| Oct 17, 2026 | 1.8 s |
| Oct 24, 2026 | 1.8 s |
| Oct 31, 2026 | 1.8 s |
| Nov 7, 2026 | 1.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 215 ms |
| May 30, 2026 | 194 ms |
| Jun 6, 2026 | 191 ms |
| Jun 13, 2026 | 194 ms |
| Jun 20, 2026 | 177 ms |
| Jun 27, 2026 | 178 ms |
| Jul 4, 2026 | 178 ms |
| Jul 11, 2026 | 171 ms |
| Jul 18, 2026 | 180 ms |
| Jul 25, 2026 | 185 ms |
| Aug 1, 2026 | 180 ms |
| Aug 8, 2026 | 180 ms |
| Aug 15, 2026 | 179 ms |
| Aug 22, 2026 | 168 ms |
| Aug 29, 2026 | 163 ms |
| Sep 5, 2026 | 154 ms |
| Sep 12, 2026 | 146 ms |
| Sep 19, 2026 | 153 ms |
| Sep 26, 2026 | 154 ms |
| Oct 3, 2026 | 163 ms |
| Oct 10, 2026 | 177 ms |
| Oct 17, 2026 | 186 ms |
| Oct 24, 2026 | 183 ms |
| Oct 31, 2026 | 182 ms |
| Nov 7, 2026 | 174 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
How it loaded on a phone
1.3 s
2.6 s
3.8 s
5.1 s
6.4 s
7.7 s
8.9 s
10.2 s
Speed
Render-blocking requests
1.3 s8 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.3 s.
Main-thread work: 6.9 s
A phone's processor spends 6.9 s on main-thread work while loading, 3.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (rebuyengine.com, shgcdn2.com and Clarity and others), adding 1.5 MB and 888 ms of main-thread time.
Mobile performance score: 53
53/100Your mobile performance score is 53. Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
787 KiBAbout 787 KiB of JavaScript is downloaded but never used on this page.
15 long tasks on the main thread
15 long tasks block the main thread while loading, the longest for 705 ms. During a long task the page ignores taps.
Reduce unused CSS
450 ms · 108 KiBAbout 108 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.
rebuyengine.com adds 216 ms
216 msrebuyengine.com costs a phone 216 ms of main-thread work and 731 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.
2,860 HTML elements
The page has 2,860 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Improve image delivery
150 ms · 19 KiB1 image could be 19 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.
Use efficient cache lifetimes
120 KiB17 files are served with short cache lifetimes, so returning visitors download them again (120 KiB).
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Legacy JavaScript
48 KiBPolyfills for old browsers add 48 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.
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 msYour server sent the HTML in 13 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 23.3 s
23.3 sThe page becomes fully interactive after 23.3 s. Good is under 3.8 s.
Speed Index: 10.1 s
10.1 sVisually, the page fills in at 10.1 s (Speed Index). Good is under 3.4 s.
Largest Contentful Paint: 6.2 s
6.2 sYour largest element takes 6.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Total Blocking Time: 625 ms
625 msScripts block taps and scrolling for 625 ms in total while the page loads. Good is under 200 ms.
10 images without width and height
10 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
-4%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.8 s to 1.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
9 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: 1.8 s
1.8 sReal visitors wait 1.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 142 ms
142 msReal visitors wait 142 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.3 s
1.3 sReal visitors see the first content after 1.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 437 ms
437 msReal visitors wait 437 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 13% faster for real visitors
-13%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 215 ms to 174 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 1.2 s
1.2 sThe first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.004
0.004The layout barely moves while loading (CLS 0.004, good is under 0.1).
Images and page weight
Page weight: 4.5 MB in 224 requests
4.5 MBYour homepage downloads 4.5 MB in 224 requests on a phone: scripts 1.8 MB (105), images 1.5 MB (23) and other files 708 KiB (60). Under 2 MB keeps phones on slow connections fast.
2 images far larger than shown
17 KiB2 images are downloaded at several times the size a phone draws them, for example landing_page_slide_template_mobile_hp_02_1200x1089.png at 1,200 px wide, shown at 390 px. Resized copies would save about 17 KiB.
2 images below the first screen load straight away
2 images further down the page (62 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.3 g of CO₂ per visit
1.29 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.29 g of CO₂e: 154.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
4 tap targets too small
4 tap targets are too small or too close together to hit reliably with a finger.
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.
Elements must only use permitted ARIA attributes (1 element)
Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.
Invalid ARIA attributes
3 elements use ARIA attributes their role does not allow, which confuses screen readers.
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.
3 links without text
3 visible links have no text or label, so screen readers cannot say where they go.
Alternative text of images should not be repeated as text (3 elements)
Alternative text of images should not be repeated as text: 3 elements on the page fail 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. (1 element).
2 checks passed
Every image has alt text
All 44 images in the HTML carry an alt attribute.
52 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 58 WCAG 2.2 A/AA and best-practice rules on the phone render: 52 passed and 6 failed. 5 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Meta description is long (298 characters)
Your meta description is 298 characters; Google truncates after about 160, so the end of your pitch is cut.
240 internal links, 7 external
The homepage links to 240 pages on whatacrockmeals.com and 7 external pages.
6 checks passed
Title: 60 characters
Your title is a healthy 60 characters: “What a Crock Meals | Comfort Food Meal, Soup & Gift Delivery”.
Canonical URL set
The canonical URL is https://www.whatacrockmeals.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://www.whatacrockmeals.com/sitemap.xml.
AI search readiness
4 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: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
Text is in the HTML
Your server sends the page's text in the HTML (1,901 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.whatacrockmeals.com/llms.txt (5 KiB, 0 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a title
https://www.whatacrockmeals.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.
1 linked page hidden from search
https://www.whatacrockmeals.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
1 page without a meta description
https://www.whatacrockmeals.com/customer_authentication/redirect has no meta description, so Google writes the search snippet from whatever text it finds.
4 pages without an H1
https://www.whatacrockmeals.com/pages/contact-us, https://www.whatacrockmeals.com/products/gift-cards, https://www.whatacrockmeals.com/pages/10-off-first-order and https://www.whatacrockmeals.com/customer_authentication/redirect 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 84 found) and read each the way a search engine does.
3 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.
Best practices
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
2 checks passed
Tap targets are thumb-sized
41 of 47 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
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.
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 1,209 words of copy
The homepage carries about 1,209 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
5 checks passed
31 calls to action
The homepage has 31 calls to action, for example “Contact us”, “Start A Subscription & Save Up To 25%” and “Contact Us”.
3 short forms
3 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 109 testimonial or review blocks and “52,000+ Customers”.
Analytics in place
Analytics detected: Google Tag Manager, Microsoft Clarity, Hotjar and LinkedIn Insight.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager, Hotjar, Klaviyo and LinkedIn Insight 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.
18 cookies set on arrival
18Opening the homepage sets 18 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.
44 other companies contacted
Loading the homepage contacts 44 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 whatacrockmeals.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 11 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Klaviyo Email Marketing Sms · Gorgias Live Chat Helpdesk · Impact Com · Minmaxify Order Limits · Microsoft Clarity · Judge Me Reviews · Rebuy Personalization Engine · Joy Loyalty Program · rechargecdn.com · shareasale.com · avada.io
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
- Analytics
- Google Tag Manager | Hotjar | Microsoft Clarity
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 34 issues on whatacrockmeals.com, including 14 speed issues, 2 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.