Recipe sites
Why recipe websites crash, reload and jump around on your phone
Your hands are covered in flour, the page reloads, and you're back at the top of someone's life story. Here's what's happening inside your phone, and how to stop it.
You've creamed the butter and sugar. Step three says to add the eggs one at a time, so you crack the first one, glance at your phone propped against the flour canister, and watch the page go blank, reload, and drop you back at the very top, above a photo of a lake.
Now you're scrolling with a knuckle, because the rest of your fingers have egg on them, past the lake, past the ads, hunting for step three. You find it. You look away to grab the second egg. The page jumps again.
This is so common that it has its own search suggestions. Start typing "why do recipe websites" and the phone finishes it for you: always crash, constantly refresh, always reload. Here's what's actually going on, and how to cook without fighting it.
Two steps in, and it reloads
The first thing to know is that the reload usually isn't the website's fault in the way it feels like it is. Nobody built a recipe page that deliberately reloads when you look away. What's happening is that your phone quietly gave up on the page and started over.
There are really three separate annoyances here, and they have different causes:
- The reload. The page goes white and starts again from the top. That's memory.
- The jump. The page doesn't reload, but the text suddenly shoves down or up while you're reading. That's late-loading content.
- The bounce. You tap Jump to Recipe, land somewhere, and a moment later you're not where you meant to be. That's both of the above, teaming up.
Take them one at a time.
Memory: why phones throw pages away
A phone has a fixed amount of working memory, and everything open shares it: your messages, the timer app, the camera, the music, and every browser tab you opened in the last three weeks and forgot about.
When memory runs short, the phone doesn't ask. It quietly unloads whatever it thinks you're not using. A browser tab you've switched away from is a prime candidate, even if you only switched away for ten seconds to set a timer. Google's own developer documentation for Chrome describes a "discarded" state, when a page "is unloaded by the browser in order to conserve resources," and notes that discarded pages have to be reloaded when you come back. That reload is the white flash you see.
Sometimes the page itself is the problem. If a single page uses so much memory that it can't run, Safari reloads it and tells you so. Mac users on Apple's own support forums have quoted the message "This webpage was reloaded because it was using significant memory." If it keeps happening on the same page, Safari stops trying and shows "A problem repeatedly occurred," followed by the web address. That's the browser saying, politely, that this page is too much for it right now.
Recipe pages are especially good at being too much. A modern web page is heavier than most people imagine. The HTTP Archive, which measures millions of sites every year, found in its 2025 Web Almanac that the median mobile home page had grown to around 2.6 MB, roughly triple its weight a decade earlier. And that's the typical page, not a recipe page with a video player, a dozen ad slots and photos of every step. Each ad slot runs its own little program, loads its own images and sometimes its own video, and some of them keep refreshing for as long as the page is open.
The jump: ads that arrive late shove the page
The jump is a different problem with a technical name: layout shift. Google's web developer guide defines it simply: a layout shift happens "any time a visible element changes its position from one rendered frame to the next." Among the common causes it lists are "third-party ads or widgets that dynamically resize themselves," images that load without a reserved space, and content added to the page after it first appears.
On a recipe page, here's how that plays out. The text arrives first, because text is small and fast. You start reading. Then an ad finishes loading above where you're reading, and it needs 250 pixels of space it didn't have a second ago. Everything below it gets shoved down. Your step three is now somewhere below the bottom of the screen.
Good sites reserve space for their ads in advance, so the box is already there, empty, before the ad fills it. Plenty of sites do this well. But ads come from many companies, in many sizes, and a slot that's sometimes filled by a small banner and sometimes by a tall video is very hard to plan around. Google even publishes a layout-shift score for sites to aim at. The fact that it needs one tells you how common the problem is.
Why Jump to Recipe sends you back
"Why does the jump to recipe button never work" is one of the most heartfelt search suggestions on the internet, punctuation and all.
The button is just a link to a spot further down the page. When you tap it, the browser calculates where that spot is right now and scrolls there. The trouble is that "right now" is a moving target. If the page is still loading, ads, images and videos above the recipe keep arriving after the browser has done its math. Each one pushes the recipe further down. The browser scrolled you to where the recipe was half a second ago, and now you're looking at a paragraph about cast iron.
The other version is worse: you jump, you find the recipe, you switch apps to start a timer, and the phone discards the page to free up memory. When you come back, it reloads from the top. As far as the browser is concerned, it's a brand-new visit. Your place is gone.
None of this is the creator ignoring you. The button exists because they know you want the recipe. The long story above it is why recipe websites have life stories in the first place, and the ads are what pay for it.
Fixes that work
You can't change how a site is built, but you can change how you read it.
- Let the page finish loading before you jump. Give it a few seconds, until the spinners stop. Then tap Jump to Recipe. The math is much more likely to hold.
- Use Reader view. Safari's Reader and Chrome's reading mode pull out the main text and drop most of the rest. It's lighter, so it's less likely to be thrown away, and nothing moves. Look for it in the browser's page menu near the address bar. It doesn't work on every page, but recipe pages often qualify.
- Use the recipe card's Print button. Most food blogs use a recipe card with a Print link. It opens a stripped-down page with just the ingredients and steps, and you don't have to actually print it. That page is small, stable and fits on a phone.
- Close the tabs you aren't using. All of them. Fewer open tabs means more memory for the one you're cooking from.
- Don't leave the browser mid-recipe. Set timers with your voice, or use the clock on the oven. Every app switch is a chance for the page to get thrown away.
- Save a copy before you start. Copy the ingredients and steps into a note, or take a few screenshots of the recipe card, before the butter goes in the pan. Keep the link with it so you can find the original again.
Blockers have a cost
The obvious fix people reach for is an ad blocker, and it's worth being honest about what that does.
Blockers do make pages lighter and calmer. They also cut off the main way most recipe bloggers get paid for a recipe they tested, photographed and gave you for free. Many of those creators have told reporters they're already losing readers as search engines answer more questions without sending anyone to their site. If a blog's recipes are good enough to cook from every week, it's worth letting that site show its ads, or supporting it some other way: buy the cookbook, join the newsletter, leave a comment that says the recipe worked.
The fixes above work without blocking anything. Reader view and the Print button still count your visit.
The cook's rule: never cook from a live webpage
Here's the habit that solves all of it: read the recipe on the website, then cook from a copy.
A live webpage is built for browsing. It's designed to load more, show more, and keep you scrolling. That's fine on the couch. It's terrible on a counter, where you need the same eight lines to sit still for forty minutes while you get butter on everything.
A copy doesn't move. It doesn't reload, it doesn't jump, and it's still there if the recipe goes offline or the creator changes it. That's true of a recipe from a website and doubly true of one from a video, which is why it pays to learn how to save recipes from TikTok and similar apps before the video disappears. Keep the creator's name and the link on your copy, so credit and the comment section are one tap away.
Tonight, before you start cooking, open the recipe, wait for it to finish loading, tap the recipe card's Print button and copy what's there into your notes with the link at the top. Then close every other tab. Your eggs will thank you.