Skip to main content
Metrics type: Key Metrics • Category: Cross-Platform: Revenue at Risk

​
At a glance

A cross-platform card that joins your LinkedIn landing-page destinations to web-vitals data from a connected performance source, and flags the pages where slow loading is quietly killing conversion. LinkedIn campaigns very often land on long-form B2B content: gated whitepapers, webinar registrations, demo-request pages, heavy resource hubs. Those pages tend to be image-rich, script-heavy, and slow. When the largest content element takes too long to paint, a meaningful share of expensive LinkedIn clicks bounce before the form even loads. You paid a premium CPC for a verified job-title visitor, and the page lost them to a loading spinner. The card lists landing pages with poor web vitals where the conversion rate has also dropped well below the account average, so you can fix the destinations that are costing you the most pipeline.

​
Calculation

Calculated automatically from your LinkedIn Ads 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 B2B consultancy running LinkedIn campaigns to senior operations leaders, each campaign landing on a long-form gated resource (industry report, webinar replay, ROI calculator). Account currency GBP. The account-average landing-page conversion rate is about 4.5%. The card evaluates a 30-day window joining web vitals to per-page conversion. Two pages combine a poor main-content paint with a conversion rate well under half the account average. The card lists them, worst first.
  1. The slow pages are bleeding pipeline before the form even loads. The supply-chain report page paints its main content in roughly six seconds. A senior operations leader who clicked an expensive LinkedIn ad waits, then leaves. The conversion rate (1.8% versus a 4.5% account average) reflects visitors lost to the load, not lost to the offer.
  2. Long-form B2B content is the usual culprit. Gated reports and webinar pages carry large hero images, embedded video, tracking scripts, and chat widgets, all of which delay the main paint. The very format LinkedIn campaigns favour is the format most prone to poor vitals.
  3. The fix is engineering, not media. Compress and lazy-load hero imagery, defer non-critical scripts, move the form above the fold so it renders early, and trim third-party widgets. These pages already earn premium traffic; making them load fast converts spend you are already paying into pipeline you are currently losing.
  4. This is a cross-connector card. It needs a connected web-performance source to read vitals. The poor-paint flag uses field data where available; lab data is a fallback. The conversion side comes from LinkedIn per-page performance. The card only fires where both a slow page and a depressed conversion rate coincide, so it points at pages where speed is plausibly the cause, not merely slow pages that convert fine anyway.
Quick triage when this card fires:
  • Poor paint + conversion well below average = fix the page; speed is plausibly costing conversions.
  • Poor paint + conversion near average = speed is not the binding constraint here; deprioritise.
  • Good paint + low conversion = the problem is the offer, the form, or the audience match, not speed; this card will not flag it.
  • Many pages flagged on one template = a shared template or shared heavy script is the root cause; fix once, fix all.

​
Sibling cards merchants should reference together

This card joins LinkedIn destinations to web performance, so pair it across both:

​
Reconciling against LinkedIn Campaign Manager

Where to look in LinkedIn Campaign Manager: LinkedIn Campaign Manager → Campaigns → Performance Chart shows clicks and conversions per campaign, and you can see destination URLs in the creative setup, but Campaign Manager does not measure page speed. To reconcile, confirm the per-page click and conversion figures for the flagged landing pages in Campaign Manager over the same 30-day window, then check the web-vitals reading for those URLs in your performance source (a CrUX / PageSpeed-style field report, or your connected analytics performance view). The card joins the two: slow pages that also convert poorly. LinkedIn alone cannot show the speed half. Things to confirm during reconciliation:
  • URL matching. Ensure the landing-page URL in the vitals source matches the campaign destination exactly, including any query parameters or redirects that change the measured page.
  • Field versus lab data. Field data reflects real visitors and is preferred; lab data is a fallback and can read differently. Know which your source is using.
  • Conversion definition. The per-page conversion rate uses your configured conversion event; confirm it matches what Campaign Manager reports.
Why our number may legitimately differ from LinkedIn: Cross-connector reconciliation: This card only exists as a join, so reconciliation spans LinkedIn and the performance source:

​
Known limitations / merchant FAQs

Why does page speed matter so much for LinkedIn specifically? Because LinkedIn clicks are so expensive. On a cheap channel, losing some visitors to a slow page is a minor leak. On LinkedIn, where each click can cost many times a Google click and the audience is a hard-to-reach, high-value buyer, a page that bounces visitors before the form loads wastes premium spend and a scarce audience. Speed is also one of the few destination factors fully in your control. The card flags a slow page that still converts fine. Should I worry? This card is designed not to flag that case. It only fires where a poor loading speed coincides with a conversion rate well below the account average. A slow page that converts at or near average will not appear, because speed is not the binding constraint there. If you see a slow-but-converting page elsewhere, treat it as a lower priority. Field data or lab data, which does the card use? It prefers real-user field data where available, because that reflects what your actual LinkedIn visitors experienced, including their devices and networks. Lab data is a synthetic fallback for pages with too little field traffic to measure. Field and lab readings can differ, so know which your source is reporting. My pages are long-form B2B content. They are always going to be heavy. What can I realistically do? A lot, without stripping the content. Compress and lazy-load hero images, defer non-critical and third-party scripts, render the form early and above the fold so the conversion path appears before the rest of the page finishes, and prune chat or tracking widgets you do not strictly need. Long-form does not have to mean slow main paint. Many pages got flagged at once. Is that a measurement glitch? More likely they share a template or a heavy script. When a single page template, hero component, or third-party tag is the bottleneck, every page built on it loads slowly together. Fix the shared root cause once and the whole set improves. The card is not showing for my account. Why? It needs a connected web-performance source to read web vitals. Without one, the speed half of the join cannot be measured, so the card stays quiet. Connect a performance source to enable it.

​
Tracked live in Vortex IQ Nerve Centre

Landing Pages with Poor Web Vitals is one of hundreds of KPI pulses Vortex IQ tracks across LinkedIn Ads 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.