Above the Fold.

The phrase comes from newspaper printing, where it described the top half of the front page — the part still visible once the paper was folded on the newsstand, and therefore the place reserved for the biggest headlines. Transferred to the web, above the fold means everything a visitor sees the moment a page finishes loading, before touching the scroll wheel. Whatever sits below the fold appears only once they scroll. The metaphor survived because the underlying problem did: attention is scarce at the top of a page and scarcer still further down.

That first screen matters because visitors decide within a few seconds whether a page is relevant to them. It is where the core message belongs, together with a clear statement of benefit and a visible call to action. A hero section that answers 'what is this, and is it for me?' at a glance lowers the bounce rate and steers people towards the next step. A hero section that is full of decoration and empty of substance does the opposite, however good it looks in the design file.

There is no single fold any more. Where it falls depends entirely on screen size and device: on a phone the immediately visible area is a fraction of what a large desktop monitor shows, and a tablet in landscape sits somewhere in between. Responsive design therefore has to guarantee that the key message lands in the first viewport on every device, not only on the one the layout was built in. Checking on a real handset rather than a resized browser window usually reveals how little actually fits.

There is a performance angle as well. The largest element above the fold is often exactly what Google measures as Largest Contentful Paint (LCP), one of the Core Web Vitals. Optimising the first screen therefore pays twice: better user experience and a better measured load time. A big, uncompressed hero image is the classic offender — it should be prioritised, served in a modern format at sensible dimensions, and never lazy-loaded. Replacing an oversized JPEG hero with a correctly sized WebP frequently moves LCP more than any other single change.