Website review, no card needed
recipetineats.com website review
Visit site (opens in a new tab)Reviewed 11 October 202642 issues · 90 checks
This review found 42 issues worth fixing on recipetineats.com, 11 of them high impact, across 90 checks. The most urgent: aRIA roles used must conform to valid values (1 element). 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
81BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Apr 18, 2026 | 1.2 s |
| Apr 25, 2026 | 1.2 s |
| May 2, 2026 | 1.2 s |
| May 9, 2026 | 1.2 s |
| May 16, 2026 | 1.2 s |
| May 23, 2026 | 1.2 s |
| May 30, 2026 | 1.2 s |
| Jun 6, 2026 | 1.2 s |
| Jun 13, 2026 | 1.2 s |
| Jun 20, 2026 | 1.2 s |
| Jun 27, 2026 | 1.2 s |
| Jul 4, 2026 | 1.2 s |
| Jul 11, 2026 | 1.2 s |
| Jul 18, 2026 | 1.2 s |
| Jul 25, 2026 | 1.2 s |
| Aug 1, 2026 | 1.2 s |
| Aug 8, 2026 | 1.2 s |
| Aug 15, 2026 | 1.2 s |
| Aug 22, 2026 | 1.2 s |
| Aug 29, 2026 | 1.2 s |
| Sep 5, 2026 | 1.2 s |
| Sep 12, 2026 | 1.2 s |
| Sep 19, 2026 | 1.2 s |
| Sep 26, 2026 | 1.2 s |
| Oct 3, 2026 | 1.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Apr 18, 2026 | 129 ms |
| Apr 25, 2026 | 129 ms |
| May 2, 2026 | 128 ms |
| May 9, 2026 | 127 ms |
| May 16, 2026 | 127 ms |
| May 23, 2026 | 127 ms |
| May 30, 2026 | 128 ms |
| Jun 6, 2026 | 129 ms |
| Jun 13, 2026 | 129 ms |
| Jun 20, 2026 | 129 ms |
| Jun 27, 2026 | 128 ms |
| Jul 4, 2026 | 127 ms |
| Jul 11, 2026 | 127 ms |
| Jul 18, 2026 | 126 ms |
| Jul 25, 2026 | 126 ms |
| Aug 1, 2026 | 125 ms |
| Aug 8, 2026 | 125 ms |
| Aug 15, 2026 | 125 ms |
| Aug 22, 2026 | 124 ms |
| Aug 29, 2026 | 123 ms |
| Sep 5, 2026 | 124 ms |
| Sep 12, 2026 | 127 ms |
| Sep 19, 2026 | 130 ms |
| Sep 26, 2026 | 137 ms |
| Oct 3, 2026 | 142 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
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Improve image delivery
800 ms · 795 KiB22 images could be 795 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 800 ms faster on a phone.
Mobile performance score: 79
79/100Your mobile performance score is 79 (desktop: 97). Pages that score under 90 lose visitors before the first paint.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, adthrive.com and slickstream.com and others), adding 1.0 MB and 565 ms of main-thread time.
Reduce unused JavaScript
574 KiBAbout 574 KiB of JavaScript is downloaded but never used on this page.
Use efficient cache lifetimes
484 KiB4 files are served with short cache lifetimes, so returning visitors download them again (484 KiB).
adthrive.com adds 230 ms
230 msadthrive.com costs a phone 230 ms of main-thread work and 527 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.
Google Tag Manager adds 236 ms
236 msGoogle Tag Manager costs a phone 236 ms of main-thread work and 326 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.
6 long tasks on the main thread
6 long tasks block the main thread while loading, the longest for 251 ms. During a long task the page ignores taps.
2,017 HTML elements
The page has 2,017 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Render-blocking requests
150 ms1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 150 ms.
Duplicated JavaScript
48 KiB48 KiB JavaScript is shipped twice across bundles.
Reduce unused CSS
32 KiBAbout 32 KiB of CSS is downloaded but never applied on this page.
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.
2 checks passed
Main-thread work: 1.6 s
A phone's processor spends 1.6 s on main-thread work while loading, 616 ms of it running JavaScript. That is comfortably low.
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: 11.7 s
11.7 sThe page becomes fully interactive after 11.7 s. Good is under 3.8 s.
Largest Contentful Paint: 4.4 s
4.4 sYour largest element takes 4.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Close up of Barbecue Pork Ribs cooked in Oven with sticky b…”.
Total Blocking Time: 251 ms
251 msScripts block taps and scrolling for 251 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) held steady for real visitors
+8%Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' tap response (inp) went from 129 ms to 142 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+6%Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' largest content (lcp) went from 1.2 s to 1.2 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.0 s
1.0 sReal visitors wait 1.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 104 ms
104 msReal visitors wait 104 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: 0.8 s
0.8 sReal visitors see the first content after 0.8 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 405 ms
405 msReal visitors wait 405 ms for your server to start answering (75th percentile). Good is under 800 ms.
Speed Index: 3.4 s
3.4 sVisually, the page fills in at 3.4 s (Speed Index), inside the 3.4 s “good” threshold.
First Contentful Paint: 1.7 s
1.7 sThe first text or image appears after 1.7 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 3.4 MB in 99 requests
3.4 MBYour homepage downloads 3.4 MB in 99 requests on a phone: images 1.9 MB (49), scripts 1.1 MB (26) and fonts 159 KiB (5). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
Spinach-Ricotta-Cannelloni.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
1 image below the first screen load straight away
1 image further down the page (108 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 1.0 g of CO₂ per visit
0.96 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.96 g of CO₂e: 115.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
ARIA roles used must conform to valid values (1 element)
ARIA roles used must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.
10 text elements with low contrast
10 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 (9 elements)
Elements must only use permitted ARIA attributes: 9 elements on the page fail this check, rated serious by axe-core.
2 tap targets too small
2 tap targets are too small or too close together to hit reliably with a finger.
Interactive controls must not be nested (1 element)
Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.
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 (176 elements)
All page content should be contained by landmarks: 176 elements on the page fail this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (2 elements)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.
Contentinfo landmark should not be contained in another landmark (1 element)
Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.
Document should not have more than one contentinfo landmark (1 element)
Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
5 links without text
5 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h3 → h5 and h3 → h5), which makes the page harder to scan with a screen reader.
1 checks passed
38 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 38 passed and 15 failed. 3 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.
Title is long (67 characters)
Your title is 67 characters, so Google will cut it off around 60: “RecipeTin Eats - A Food Blog Serving Up Quick & Easy Dinner Recipes”.
Meta description is long (180 characters)
Your meta description is 180 characters; Google truncates after about 160, so the end of your pitch is cut.
Structured data has 1 problem
Structured data found (BreadcrumbList, ImageObject, WebPage and WebSite) but with 1 problem, for example “WebPage: keywords is an empty list”.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
307 internal links, 14 external
The homepage links to 307 pages on recipetineats.com and 14 external pages.
3 checks passed
Canonical URL set
The canonical URL is https://www.recipetineats.com/.
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.recipetineats.com/sitemap_index.xml.
AI search readiness
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.
No llms.txt
There is no https://www.recipetineats.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.
Opted out of AI training for 1 crawler
robots.txt blocks CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.
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.
Text is in the HTML
Your server sends the page's text in the HTML (1,122 words), so crawlers that don't run JavaScript still read it.
Other pages
11 pages without a meta description
https://www.recipetineats.com/cookbooks, https://www.recipetineats.com/category/chicken-recipes, https://www.recipetineats.com/category/beef-recipes, https://www.recipetineats.com/category/pork-recipes, https://www.recipetineats.com/category/lamb-recipes and https://www.recipetineats.com/category/turkey-recipes and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 150 found) and read each the way a search engine does.
6 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.
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 15 pages that loaded have a <title>.
Best practices
20 small tap targets
20 of 61 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://ads.adthrive.com/sites/55cb7e3b4bc841bd0c4ea577/ads.min.css' from origin 'https://…”.
1 checks passed
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.
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.
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 745 words of copy
The homepage carries about 745 words of visible text.
3 checks passed
6 calls to action
The homepage has 6 calls to action, for example “Contact”, “LEARN MORE” and “Subscribe”.
3 short forms
3 short forms (2 fields at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Comscore, Criteo, Google Ads, Google Analytics and Google Tag Manager 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.
14 cookies set on arrival
14Opening the homepage sets 14 cookies, 2 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.
33 other companies contacted
Loading the homepage contacts 33 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 recipetineats.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- WordPress
- Framework
- jQuery
- Analytics
- Google Tag Manager
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 42 issues on recipetineats.com, including 12 speed issues, 6 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.