Skip to main content
Metrics type: Cross-Platform Metrics • Category: Ad Platform

​
At a glance

The Meta landing pages that are slow on mobile and converting below par. Meta traffic skews heavily mobile and in-app, so a landing page that loads slowly on a phone loses sales that a fast page would keep. This card joins your Meta ad destinations to mobile Core Web Vitals (chiefly Largest Contentful Paint) and to the page’s conversion rate, then names each page that is both slow and underperforming, so the developer can fix the exact URL the same day. Caveat: a slow page is one cause of weak conversion among several (offer, audience, creative match), so use this card to shortlist pages for a fix rather than to assert that speed alone is the problem.

​
Calculation

Calculated automatically from your Meta Ads (Facebook) destinations joined to mobile web-vitals and conversion data. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading.

​
Worked example

A UK beauty brand running Advantage+ Shopping and DPA to a mix of collection and product pages. Reading taken on 14 Mar 26 over the trailing 30 days. Account-average mobile conversion rate is about 2.6%. All figures are illustrative.
  1. Two pages fire. The new-in collection and the hero-serum product page are both slow on mobile (LCP above 4s) and converting at less than half the account average. The other two are either fast or converting normally, so they pass.
  2. The new-in collection is the priority. It is the slowest (5.8s) and the worst-converting, and it is receiving cold Advantage+ traffic, the audience least forgiving of a slow first impression. Fix this URL first.
  3. Speed is a strong suspect, not a proven sole cause. The hero-serum page is slow and weak, but it may also have a creative-to-page mismatch or a weak offer. The card shortlists it; the developer and the marketer confirm the cause together.
  4. The fix is a specific URL handed to engineering. Because the card names the exact page and its mobile LCP, the developer can profile that one template (often an oversized hero image or render-blocking script) rather than guessing across the whole site.
  5. The payoff is recovered conversion on existing spend. No extra budget is needed; bringing these two pages under the LCP threshold lifts the conversion rate on traffic you are already paying for, which is the cheapest revenue gain available.
Quick reads:
  • Slow mobile LCP + low conversion + cold audience = top priority. Cold traffic punishes slow pages hardest.
  • Slow LCP + normal conversion = monitor, not urgent. Speed is not yet costing conversions here.
  • Fast LCP + low conversion = the problem is not speed. Look at offer, creative match, or audience.

​
Sibling cards merchants should reference together

​
Reconciling against Meta Ads Manager

Where to look in Meta Ads Manager: Meta Ads Manager does not measure Core Web Vitals, it has no native page-speed reporting. The in-platform proxies are partial:
  • Meta Ads Manager → Ads → Destination / landing page shows which URL each ad points to, so you can see your destinations, but not their speed.
  • The landing-page-view to purchase ratio in Ads Manager hints at a drop-off after the click, which a slow page can cause, but it does not isolate speed from other causes.
The authoritative speed signal lives outside Meta entirely, in the website-performance (Core Web Vitals) data this card joins in. Meta tells you where the traffic goes; the web-vitals source tells you whether the page can hold it. Why the Vortex IQ value may legitimately differ: Cross-connector reconciliation:

​
Known limitations / merchant FAQs

Why mobile only and not desktop? Because Meta delivery is overwhelmingly mobile and in-app. A desktop or blended web-vitals report can look healthy while the mobile experience that most of your paid traffic sees is poor. Reading mobile vitals specifically matches the device your spend actually reaches. Does a slow page definitely mean speed is hurting conversion? Not on its own. Speed is one cause of weak conversion among several, including offer, audience match, and creative-to-page consistency. The card requires both a slow mobile LCP and a below-average conversion rate to fire, which strengthens the case, but the final diagnosis is a developer-and-marketer call. The page tests fine for me but is flagged. Why? Two common reasons. First, you may be testing on a fast device and connection, while the field data reflects a range of real mobile users. Second, much Meta traffic opens inside the Facebook or Instagram in-app browser, which can render slower than a standalone mobile browser. The card aims to reflect the paid-user experience, not a single test run. What usually makes an ad landing page slow on mobile? Frequently an oversized or unoptimised hero image, render-blocking scripts, heavy third-party tags, or a layout that shifts as content loads. Because the card names the exact URL, the developer can profile that one template rather than guessing across the site. How do I prioritise which flagged page to fix first? Sort by spend and audience temperature. A slow page receiving high cold-prospecting spend loses the most, because cold audiences are the least patient. Pair with Landing Page Performance to see which flagged URL carries the most budget. Can I tune the thresholds? Yes. Both the LCP slow threshold and the conversion-gap threshold are configurable per profile in the Alert Rules tab. Tighten them to surface more pages for a proactive speed programme, or loosen them to focus only on the worst offenders.

​
Tracked live in Vortex IQ Nerve Centre

Mobile Landing Pages with Poor Web Vitals is one of hundreds of KPI pulses Vortex IQ tracks across Meta Ads (Facebook) and 70+ other ecommerce connectors. Nerve Centre runs the detection layer; Vortex Mind investigates the cause when something moves; Ask Viq lets you interrogate any number in plain English. Start for free or book a demo to see this metric running on your own data.