Above-the-fold content: what to load first for speed
Short answer Load the biggest thing a visitor sees first, usually the top photo or headline. Google calls it the LCP element. Put it straight in the page's HTML, give an image high fetch priority, and never lazy-load it. Lazy-load images and embeds lower down. Heading order and content layout don't change how fast a page loads.
Want help applying this to your business? Talk it through on a free 30-minute call.
Book a callWhat should load first above the fold?
The one big thing a visitor sees when the page opens. Google's speed metric for it is LCP (Largest Contentful Paint): the time until the largest image, text block or video in the screen shows up. On most service business pages that's the hero photo (the big picture at the top) or the main headline. Google's target is 2.5 seconds or less for at least 75% of visits (web.dev: Largest Contentful Paint).
So the rule is about load order, not page layout:
| Where on the page | What to do |
|---|---|
| Top photo or headline (your LCP element) | In the HTML itself, high fetch priority, never lazy-loaded |
| Other images in the first screen | Load normally, with width and height set |
| Images, videos and map embeds lower down | Lazy-load: they wait until the visitor scrolls near them |
| Chat widgets, trackers, pop-up scripts | Load after the page, not in the head |
Google's performance guide says it plainly:
"Never lazy-load your LCP image, as that will always lead to unnecessary resource load delay, and will have a negative impact on LCP." (web.dev: Optimize Largest Contentful Paint)
How speed affects ranking, and the pass and fail numbers for all three Core Web Vitals, are in Core Web Vitals and Google ranking. This page is about the fix at the top of the screen.
Does content hierarchy make a page load faster?
No. Headings, bullet lists and a tidy outline help people scan, but they don't tell the browser what to download first. A browser reads the HTML top to bottom and fetches files as it finds them. What slows the first screen is a large image, an image the browser finds late, or stylesheets and scripts that block drawing the page.
Google's own guide on optimizing LCP names blockers such as:
- An image the browser can't see in the HTML: one added by JavaScript, or set as a CSS background image.
- Scripts and styles that stop drawing. Putting scripts without the async or defer setting in the page's head "will almost always have a negative impact on performance" (same guide).
Heading order isn't a ranking rule either:
"Having your headings in semantic order is fantastic for screen readers, but from Google Search perspective, it doesn't matter if you're using them out of order." (Google Search Central: SEO Starter Guide)
Keep a clear H1 and H2 outline for readers and screen readers. Just don't expect it to fix a slow page.
Where is the fold on a phone?
There isn't a fixed line. Google's web.dev team defines above the fold as everything visible before scrolling and adds:
"There is no universally defined pixel height of what is considered above the fold content since there is a myriad of devices and screen sizes." (web.dev: Extract critical CSS)
Check the first screen on a real phone, held upright. If your photo is in view there, treat it as above the fold, even if on a laptop it sits lower.
How do I find my LCP element?
Run the page in PageSpeed Insights, set to mobile. Its lab test uses Lighthouse (PageSpeed Insights: About), which shows two insights for the top of the page:
- LCP breakdown names the element and splits its time into four parts.
- LCP request discovery checks the three image rules: found in the HTML, high priority, not lazy-loaded (Chrome for Developers: LCP request discovery).
| Part of LCP time | What it means | Usual fix |
|---|---|---|
| Time to first byte | Server sends the first bit of the page | Better hosting, fewer redirects |
| Resource load delay | Gap before the image starts downloading | Put it in the HTML; remove lazy loading; add high priority |
| Resource load duration | The download itself | Smaller, compressed image |
| Element render delay | Image arrived but isn't drawn yet | Cut blocking scripts and stylesheets |
Parts from Chrome for Developers: LCP breakdown. Google advises spending most LCP time on the download, not the delays (same page). If the LCP element is plain text in a system font, the two image parts are zero.
Should I lazy-load images?
Yes, below the first screen. Lazy loading is built into all major browsers: it's the loading="lazy" setting on an image or an iframe (an embedded box, such as a Google Map or YouTube video) (web.dev: Browser-level image lazy loading; web.dev: lazy-load offscreen iframes). WordPress adds it for you; on other builders, check the image settings.
Two limits:
"Don't lazy-load images that are likely to be in-viewport when the page loads, especially LCP images." (web.dev: Browser-level image lazy loading)
Google Search also needs lazy content to load without scrolling, because its crawler doesn't scroll or click. It says to load content "whenever it is visible in the viewport," and names browser lazy loading as one fine way to do it (Google Search Central: Fix lazy-loaded content). The same page warns that lazy-loading what's visible at once makes it "take longer to load."
Hero sliders, background images and fetch priority
Fetch priority is a hint (fetchpriority="high") that tells the browser to download an image ahead of others. Google says to use it on the image likely to be your LCP element, and warns that marking more than one or two images high stops helping (web.dev: Optimize Largest Contentful Paint).
- Sliders. Only the first slide is seen at load. Give it high priority and the other slides low (web.dev: Fetch Priority API). Better still, use one still photo.
- Background images. A hero set as a CSS background can't be found by the browser in the HTML, so it starts late. Use a normal image, or preload it with high priority (Chrome for Developers: LCP request discovery).
- Layout jumps. Images and embeds without set sizes are a top cause of the page jumping as it loads (web.dev: Optimize Cumulative Layout Shift). Set width and height.
On WordPress 6.3 or later, core adds high fetch priority to the image it judges most likely to be the LCP image and tries to leave lazy loading off images in the first screen (Make WordPress Core, July 2023). A theme or plugin can override that, so still check PageSpeed Insights. On a hosted builder you can't edit the code, but you choose the top image, its file size, and whether it's a slider. More on platforms: Wix, Squarespace or WordPress for SEO.
Example
Illustrative cases, not measured results.
A plumber whose hero photo was lazy-loaded
A speed plugin lazy-loads every image, the 1,600-pixel van photo at the top included. PageSpeed Insights flags it under LCP request discovery. He excludes that one image from lazy loading, compresses it from 2 MB to about 200 KB, and leaves lazy loading on for the gallery below.
A dental office with a four-slide hero
Each slide is a CSS background image. The office swaps the slider for one photo of the team as a normal image with high priority, and the booking button now shows in the first screen on a phone.
A law firm whose LCP is its headline
The top of the page is text in a system font, so LCP is the headline. The image parts of the breakdown are zero; the delay is a chat widget script in the head. Moving it to load after the page fixes the render delay.
FAQ
Do I need a developer to fix above-the-fold loading?
Not always. Swapping a slider for one compressed photo is a settings job. Moving scripts or preloading a background image usually needs someone who edits code.
Does Google index lazy-loaded images?
Yes, if they load once visible, with no scroll or click needed. Google names the browser's built-in lazy loading as one method that works.
Should my phone number or booking button be above the fold?
Usually yes, for people. Google sets no rule for it. Make it real text or a button, not part of the photo, so it shows first.
Different for you?
- Want to know whether speed affects ranking at all: Core Web Vitals and Google ranking.
- Fast page, still no calls: website not getting leads.
- Building a trade site that loads fast on a phone: HVAC and plumber website design.
- Your builder won't let you change the top of the page: Wix, Squarespace or WordPress for SEO.
- Want the page built and kept fast for you: Website Agent.