Quick Answer: You don't need a rebuild to fix a bad Landing Page Experience rating. You need subtraction. Remove the hero slider, delay third-party scripts, compress oversized images, and cut extra sections. Re-test PageSpeed after each removal. Most bloated WordPress pages jump 20 to 30 points from removals alone, and Quality Score follows relevance and speed, not aesthetics.
The situation almost nobody admits
You're running Google Ads to an existing homepage. WordPress, probably Elementor. Mobile PageSpeed sits somewhere between 50 and 60. Google flags your Landing Page Experience as below average, Quality Score sags, and CPCs creep up month after month.
You know a purpose-built landing page would fix it. But a redesign isn't on the table. The client won't pay for it, the dev queue is three months deep, or the founder is attached to the current design. So you're stuck optimizing a page you don't fully control.
Here's the good news. The fastest gains on a bloated page come from removing things, not adding them. And removals are the one change nobody has to approve a redesign for.
Why subtraction beats redesign for paid traffic
Paid traffic is impatient. Someone clicked your ad with a specific problem. Every second of load time and every distracting element between them and the answer costs you money you already spent on the click.
Hero sliders, autoplay animations, chat widgets, heatmap scripts, five font families, a gallery of 40 images. Each one adds load time and adds zero conversions. In PPC, clean and fast beats pretty and busy every time.
There's a second benefit. Landing Page Experience is one of the three components of Quality Score, alongside Expected CTR and ad relevance. You can't directly see how Google weighs page speed, but you can watch CPCs and impression share respond after the page gets faster. Speed is the lever you actually control this week.
The removal order
Work through these in sequence. After each step, run the page through PageSpeed Insights again and note the score. Stop when mobile hits 85 or better, or when you run out of things to safely cut.
Step 1: Kill the hero slider
Sliders are the single worst offender. They load multiple large images, ship their own JavaScript, and almost nobody clicks past slide one. Replace it with one static image and one clear headline. This alone often moves mobile PageSpeed 10+ points.
Step 2: Cut animations and motion effects
Elementor makes it easy to animate every section on scroll. Each effect adds script weight and layout shifts that hurt Core Web Vitals. Turn them all off. Paid visitors don't need entrance animations. They need the offer.
Step 3: Delay or remove third-party scripts
Open the page source or your GTM container and list every script. Chat widgets, heatmaps, session recorders, social pixels, random plugins. Keep conversion tracking. Delay or delete everything else, or set scripts to load on interaction instead of on page load. This is usually the biggest JavaScript win.
Step 4: Compress and resize images
Export images at the exact dimensions they display, not the 4000px original. Convert to WebP. If there's a big gallery section, cut it to three images or remove it entirely. Slow load hurts you far more than fewer gallery photos ever will.
Step 5: Cut sections and fonts
Fewer sections, one clear CTA, one or two fonts. Everything above the fold should point at the main action. If a section doesn't help a paid visitor decide, it's dead weight. Delete it.
Step 6: Re-test and log every change
Run PageSpeed Insights after each removal and write down the score. Two reasons. You'll know which change actually moved the number, and you'll have proof for the client when they ask why the slider is gone.
What this won't fix
Be honest about the ceiling. WordPress plus a page builder caps how fast you can get. If the search terms hitting the page are junk, or the offer doesn't match the ad, no PageSpeed score saves you. Landing Page Experience also weighs relevance, so make sure the page headline echoes the keyword the visitor searched. Speed gets you in the game. Relevance and offer win it.
The page can be fast and the campaign can still bleed if the keywords sending traffic to it are wrong. That's a research problem, not a design problem. I put together a free course called Stop Flying Blind that walks through building a keyword list you can actually trust, so the visitors hitting your stripped-down page are the ones who came to buy. Five modules, free with an account.
FAQ
Does PageSpeed directly change Quality Score?
Google doesn't publish the formula. Landing Page Experience considers load time, mobile friendliness, and relevance. In practice, accounts that move mobile PageSpeed from the 50s into the 80s usually see Landing Page Experience ratings improve within a few weeks, and CPCs ease as Quality Score recovers.
Should I just build a dedicated landing page instead?
Eventually, yes. A dedicated page built for one campaign will beat a shared homepage almost every time. But if a rebuild isn't approved, subtraction gets you 70 percent of the benefit now. Do the removals first, then make the case for a dedicated page with the before and after data.
What if the client pushes back on removing the slider?
Show them the PageSpeed score before and after, plus CPC trend. Frame it as a paid traffic decision, not a design opinion. The homepage can keep its slider for organic visitors if you eventually split paid traffic to its own page.
How fast is fast enough?
Aim for 85+ on mobile PageSpeed Insights. Past that, returns shrink and you're better off spending the time on ad relevance, search terms, and the offer itself.