Recipe for: a fast recipe page
Recipe pages that load before the oven heats.
We speed up your top recipe pages on phones, with you, without removing your ads. You pay after Google's lab test shows the main content loads in under 2.5 seconds.
Ingredients
- Your top 10 recipe pages (we find them together in Google Analytics or Search Console)
- A temporary WordPress admin user that you create for us, and delete after
- Access to your host's control panel or a staging copy of your site
- Your recipe card plugin, such as WP Recipe Maker or Tasty Recipes, left in place
- Your ad network, such as Mediavine or Raptive, left in place
- 1 to 2 weeks
your ads stay, your speed improves
Pay after
it works
The problem
The problem: your recipe pages are slow on phones
- Most readers open your recipe on a phone, often in the kitchen, often on a weak signal.
- Large hero photos, many plugins, ad scripts and video players all compete to load first.
- Search Console shows 'Poor' or 'Needs improvement' URLs in the Core Web Vitals report.
- You have tried a caching plugin, and the score still looks red.
Why it matters
What it costs your blog
- Readers who wait leave before they reach the recipe card. Fewer page views mean fewer ad impressions and a lower RPM.
- Core Web Vitals are part of the page experience signals Google uses. A slow page gives a competing recipe one more advantage.
- Slow pages make your ad network's ads load later, so they earn less.
- During Thanksgiving and holiday baking traffic, a slow or overloaded site loses the readers you worked all year to reach.
Method
Method
-
Step 1: Measure first
We run Google's PageSpeed Insights on your top 10 recipe pages on mobile and save the results. You get a copy. This is the starting point.
-
Step 2: Find the slow parts
We look at what loads first and what blocks the page: images, fonts, plugins, ad and video scripts, and your host's response time.
-
Step 3: Fix on a copy
We make the changes on a staging copy where we can. Typical fixes: right-sized images, a preloaded hero photo, fewer plugins, cleaner caching, and scripts that wait their turn.
-
Step 4: Go live, then test again
We move the changes to your live site and run the same test on the same pages. You see the before and after side by side.
-
Step 5: See under 2.5 s, then pay
When the lab test shows mobile LCP under 2.5 seconds on your top recipe pages, we send the invoice. If it does not, you pay nothing.
Price: Speed fix
USD 1,200
one time
You pay after Google's lab test (PageSpeed Insights) shows mobile LCP under 2.5 seconds on your top recipe pages
If it does not work, you pay nothing.
Check my blog's email firstWhat are Core Web Vitals, and why do they matter for a food blog?
Core Web Vitals are three numbers Google uses to describe how a page feels to a real reader. Think of them as three kitchen timers.
LCP, Largest Contentful Paint, times how long the main part of the page takes to appear. On a recipe post, that is usually the hero photo or the title. Google calls 2.5 seconds or less “good”.
INP, Interaction to Next Paint, times how fast the page reacts when a reader taps, for example on “Jump to Recipe” or a checkbox in the ingredient list. Google calls 200 milliseconds or less “good”. INP replaced the older FID metric in 2024.
CLS, Cumulative Layout Shift, measures how much the page jumps around while it loads. A reader who taps “Print” and hits an ad instead has met CLS. Google calls 0.1 or less “good”.
Google measures these numbers at the 75th percentile of real visits. That means 3 out of 4 visits must be as fast as the target or faster. You can see your own numbers in Search Console under “Core Web Vitals”, and for one page at a time in PageSpeed Insights.
Why are food blogs often slow?
A recipe post carries a lot: large photos, a recipe card with structured data, a video player, social share buttons, a newsletter form, and display ads from Mediavine, Raptive or another network. Each piece is useful. Together, they fight to load first. On a phone in a kitchen, the reader feels every extra second.
What does a speed fix change?
Most of the gain comes from a few plain changes. We make the hero photo the right size and tell the browser to load it first. We let ad, video and share scripts load after the recipe text. We remove plugins that do the same job twice. We set up caching so your server does less work on each visit. We do not remove your ads, and we do not change how your blog looks.
How do you know it worked?
We test the same pages before and after, with the same tool, PageSpeed Insights on mobile. You pay only when the after test shows LCP under 2.5 seconds on your top recipe pages. The Search Console report follows a few weeks later, because it uses 28 days of real visits.
FAQ
Questions people ask
What is LCP?
LCP, Largest Contentful Paint, is the time until the biggest thing on the screen, usually your hero photo or the recipe title, has loaded. Google calls 2.5 seconds or less 'good'.
Will you change how my blog looks?
No. Your design, your recipe card and your ads stay the same. We change how the page loads, not what it shows.
Do I have to switch hosts?
Usually not. If your host is the main cause, we show you the test results and you decide.
Which pages do you test?
We agree on your top 10 recipe pages before we start, usually the pages with the most sessions in the last 90 days.
What if the test does not pass?
Then you pay nothing, and we give you our notes on what still slows the page.
Goes well with
Related fixes
We fix it with you, and you pay after it works. If it does not work, you pay nothing.
We want to be your technology partner. We do not want to take your money for work that does not help.