Your homepage is usually the heaviest page on your website. It has the big hero image, the slider, the logo carousel, the testimonials, the video and the Instagram feed, because everyone wants to show their best work on the first page. The result is that the page most visitors see first is often the slowest one.
This article walks down a typical WordPress homepage from top to bottom, the same way a visitor's browser loads it. At each part, you will see what slows it down and what to change, so the main content appears in about two seconds on a normal phone.
Why Two Seconds Is the Right Goal
Google measures loading speed with Largest Contentful Paint, or LCP. This is the moment the biggest thing at the top of the page, usually the hero image or the main heading, becomes visible. Google calls an LCP of 2.5 seconds or less "good", and it judges your site by the slowest 25% of real visits, not by your own fast test on office Wi-Fi.
New data from real Chrome users shows how hard this is for WordPress sites. PageSpeed Matters compared about 3 million WordPress sites with 6.6 million other sites, using Google's field data from May of this year.
| Mobile result | WordPress sites | Other sites |
|---|---|---|
| Pass all three Core Web Vitals | 38.4% | 44.1% |
| Good LCP (loads fast enough) | 59.2% | 72.5% |
| Good INP (reacts fast to taps) | 93.8% | 81.0% |
| Good CLS (layout stays still) | 91.5% | 86.7% |
| Median LCP | 2.3 seconds | 1.8 seconds |
The table tells a clear story. WordPress sites react to taps and keep their layout still better than the rest of the web. They fail mainly on one thing, which is how fast the main content appears. In the same study, WordPress had the lowest pass rate of all the website builders measured, below Wix, Squarespace and Webflow.
A median of 2.3 seconds also explains the two second goal. If your homepage shows its main content in about two seconds in your own tests, you have a small safety margin for slower phones and weaker networks, and the slowest 25% of your visitors should still stay under 2.5 seconds.
The Top of the Page Decides Your Score
The first screen a visitor sees matters more than everything below it. The header and the hero area are where most WordPress homepages lose their LCP score, so start here.
The slider. This is the most common problem we see, and a support thread from August shows why. A site owner using Smart Slider 3 had a mobile LCP of 16.4 seconds on the homepage. Changing the lazy loading settings only brought it to about 14.4 seconds. The plugin's own support team explained that the slider needs its JavaScript to run before it can show anything, and part of that code only runs after the rest of the page has loaded. No setting could fix that. Their advice was to replace the top slider with a single static image and keep sliders lower on the page.
That advice works for almost every slider plugin. Very few visitors wait for the third slide anyway, so one strong image with a clear headline usually does better for both speed and sales.
The hero image. When the hero is a normal image, it is often 1 to 3 MB because someone uploaded the original photo from a camera or a stock site. A few changes fix most of it.
- Resize it to the size it is shown at. A hero that is 1,600 pixels wide on screen does not need a 5,000 pixel file.
- Use WebP or AVIF. Most image plugins can convert files for you, and all modern browsers support both formats.
- Do not lazy load it. Lazy loading is good for images further down, but it delays the one image Google is waiting for. WordPress usually handles this, but some themes and plugins add lazy loading to everything.
- Give it high priority. Adding fetchpriority="high" to the hero image tells the browser to download it first.
The header. A sticky header with a mega menu, a search popup and a top bar for offers can load more code than the whole hero section. Keep only what visitors use.
The Middle of the Page Is Where the Weight Hides
The sections below the first screen do not affect LCP directly, but they still slow the page down. The browser has to download their code, run it and build the layout, and on a cheap phone that work competes with the hero for time.
These are the homepage parts that most often add the most weight, in the order we usually find them.
- Embedded videos. One YouTube embed loads several hundred kilobytes of player code before anyone clicks play. Show a preview image instead and load the real player only when the visitor clicks.
- Social feeds. Instagram and Facebook feed plugins load images and scripts from other servers that you cannot cache. A row of six static photos that link to your profile looks almost the same and loads much faster.
- Animations. Fade-in and slide-in effects from page builders add JavaScript and can make text appear later than it should. Use them on one or two elements at most.
- Too many sections. Many homepages have twelve or more sections because each one was added for a different reason. If a section does not help a visitor choose you, remove it or move it to an inner page.
- Fonts. Each font family and weight is a separate file. Two families with three weights each is usually enough. Host them on your own server instead of loading them from Google Fonts.
If your homepage is built with Elementor or another page builder, keep an eye on the number of nested containers. Every extra wrapper makes the page heavier for the browser to build, and builder sites often use three or four levels where one would do.
Want a faster homepage without redesigning it? Our WordPress speed optimization service finds what slows your homepage down and fixes it, with before and after results from real tests.
The Parts You Do Not See
Some speed problems are not on the page at all. They happen on the server before the first byte reaches the visitor, and no image work can fix them.
Page caching is the most important one. Without it, WordPress builds the homepage from the database on every visit, which can take a second or more on shared hosting before anything starts loading. With caching, the server sends a ready copy of the page in a fraction of that time. Our comparison of WordPress caching plugins explains which one fits your hosting.
After caching, look at the plugins that load on every page. A contact form plugin, a slider library or a popup tool often loads its files on the homepage even when that page does not use them. Many performance plugins let you turn off a plugin's files on pages where it is not needed. And if your hosting is slow even with caching, a better host or a CDN such as Cloudflare will help visitors in other countries most.
How to Test Your Homepage the Right Way
Run your homepage through PageSpeed Insights and look at the top part first. That part shows real data from Chrome users over the last 28 days, if your site has enough visitors. The score below it is a lab test, which is useful for finding problems but is not what Google uses for ranking.
In the lab test, open the section that names your LCP element. It tells you exactly which image or heading Google waits for, and that is where your work should start. Test the mobile result, because it is slower and it is what most visitors use. After each change, test again and keep a short note of the result, so you know which change helped.
Real data takes about four weeks to update fully, so do not panic if the top section does not change the next day. For a deeper look at the other two metrics, read our guide to WordPress Core Web Vitals. If you are planning a new homepage anyway, our guide to planning a WordPress business website shows how to keep speed in mind from the first sketch, and our WordPress website design team builds every new homepage with these limits from the start. To keep it fast after launch, speed checks are part of every WordPress maintenance plan we run.
