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.
| What it lists | Meta ad landing pages whose mobile Largest Contentful Paint exceeds the slow threshold AND whose conversion rate sits meaningfully below the account average. Each row is a specific URL. |
| Why mobile specifically | Meta delivery is overwhelmingly mobile and in-app (Facebook and Instagram feeds, Stories, Reels). Desktop web-vitals can look fine while the mobile experience that most of your paid traffic actually sees is poor. |
| The web-vitals source | Mobile Core Web Vitals from the connected website-performance data (field and lab signals), chiefly LCP, alongside layout stability and responsiveness where available. |
| The conversion source | The landing page’s conversion rate from the Meta and analytics data, compared to the account average for a like-for-like read. |
| Why it matters | On mobile, every additional second of load time depresses conversion. Paying Meta CPC to send mobile users to a slow page wastes the click at the last step, the most expensive place to lose a customer. |
| Chart type | Table. Each row names the URL, its mobile LCP, its conversion rate, and the gap to account average. |
| Alert trigger | Any landing page with mobile LCP above the slow threshold (around 4 seconds) AND a conversion rate below roughly half the account average. Both thresholds are tunable per profile in the Sensitivity tab. |
| Currency | Not currency-denominated; the unit is a count of pages, with seconds and percentages per row. |
| Time window | 30D (30-day rolling). |
| Roles | owner, marketing, engineering |
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.| Landing URL | Mobile LCP | Conversion rate | Gap to avg | Flagged |
|---|---|---|---|---|
| /collections/new-in | 5.8s | 0.9% | -65% | Yes |
| /products/serum-hero | 4.4s | 1.1% | -58% | Yes |
| /products/cleanser | 2.1s | 2.8% | +8% | No |
| /collections/bestsellers | 3.2s | 2.5% | -4% | No |
- 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.
- 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.
- 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.
- 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.
- 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.
- 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
| Card | Why pair it with Mobile Landing Pages with Poor Web Vitals | What the combination tells you |
|---|---|---|
| Landing Page Performance | The Meta-internal landing-page view. | Which destinations carry the most spend, so you fix the highest-traffic slow page first. |
| Landing Page Conv. Rate | The conversion side of the join. | Confirms the page is underconverting, not just slow. |
| Website Performance LCP | The site-wide Largest Contentful Paint reading. | Whether the slow page is an outlier or part of a site-wide mobile speed problem. |
| Website Performance Slowest LCP URLs | The ranked slowest pages on the site. | Whether your slow ad landing pages are also your slowest pages overall. |
| Website Performance LCP by Template | The template-level diagnosis. | Whether a whole template (all product or all collection pages) is the root cause. |
| GA4 LCP-to-Conversion Correlation | The independent link between speed and conversion. | Quantifies how much conversion the slow LCP is likely costing. |
| Google Ads Landing Page LCP vs Conversion | The same join on paid search. | Whether slow pages are hurting both paid channels, justifying a shared fix. |
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.
| Reason | Direction | Why |
|---|---|---|
| Field vs lab data | Variable | Web vitals can come from real-user field data or synthetic lab tests. Field data reflects actual mobile devices and networks; lab data is a controlled run. The two can differ for the same page. |
| Mobile-only filter | Lower LCP elsewhere | This card reads mobile vitals specifically. A page that looks healthy on a desktop or blended report can be slow on mobile, which is where Meta traffic lands. |
| In-app browser | Ours may read worse | Much Meta traffic opens in the Facebook or Instagram in-app browser, which can perform differently from a standalone mobile browser. The card aims to reflect the experience paid users actually get. |
| Conversion attribution | Direction depends | The conversion-rate side inherits Meta’s attribution window, so the gap-to-average read shifts with the configured window. |
| Card | Expected relationship | What causes legitimate divergence |
|---|---|---|
website_performance.lcp | A flagged page should appear slow in the site-wide LCP data | A page slow only in the in-app browser may read better in a standalone-browser site test. |
website_performance.slowest_lcp_urls | Slow ad landing pages often appear on the slowest-URL list | A page can be a slow outlier for paid mobile traffic without topping the whole-site ranking. |
google_analytics.lcp_to_conversion_correlation | Confirms the speed-to-conversion link the card relies on | Pages where conversion is weak for non-speed reasons will show a weaker correlation. |