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

​
At a glance

The Snapchat landing pages that are slow on mobile and converting below par. Snapchat Ads run only inside the Snapchat mobile app, so 100% of your paid traffic lands on a phone, opening in the in-app browser straight off a swipe-up. A page that loads slowly on mobile loses sales that a fast page would keep. This card joins your Snapchat ad destinations (single image/video, Story, Collection and Dynamic Ad landing URLs) 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-to-page 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 Snapchat Ads 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

Driftline Swim, a UK Gen-Z swimwear brand running Snapchat Story Ads and Dynamic Collection Ads to a mix of collection and product pages. Reading taken on 14 Apr 26 over the trailing 30 days. Account-average mobile conversion rate is about 2.4%. All figures are illustrative.
  1. Two pages fire. The summer-drop collection and the reversible one-piece 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 summer-drop collection is the priority. It is the slowest (6.1s) and the worst-converting, and it is the destination for cold Story Ad prospecting, the audience least forgiving of a slow first impression. On Snapchat, where the user swiped up from a full-screen vertical video and the page opens inside the in-app browser, a 6.1s load is brutal. Fix this URL first.
  3. Speed is a strong suspect, not a proven sole cause. The reversible one-piece page is slow and weak, but it may also have a creative-to-page mismatch (the Story Ad promised one colourway, the page defaulted to another, a common Dynamic Ads failure mode). 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 a render-blocking AR-preview 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. On Snapchat the upside applies to 100% of your traffic, because there is no desktop slice to dilute it.
Quick reads:
  • Slow mobile LCP + low conversion + cold Story Ad audience = top priority. Cold Snapchat prospecting 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 the offer or the creative-to-page match.

​
Sibling cards merchants should reference together

​
Reconciling against Snapchat Ads Manager

Where to look in Snapchat Ads Manager: Snapchat Ads Manager does not measure Core Web Vitals, it has no native page-speed reporting. The in-platform proxies are partial:
  • In Snapchat Ads Manager at ads.snapchat.com, open an ad and read its swipe-up / attachment URL under the creative details. This shows you which page each ad points to, so you can list your destinations, but not their speed.
  • The swipe-up rate to web-conversion ratio in the campaign reporting hints at a drop-off after the swipe, which a slow page can cause, but it does not isolate speed from other causes. To trust that ratio at all, confirm the Snap Pixel and Conversions API are healthy in Events Manager first.
The authoritative speed signal lives outside Snapchat entirely, in the website-performance (Core Web Vitals) data this card joins in. Snapchat tells you where the traffic goes; the web-vitals source tells you whether the page can hold it. Why our number may legitimately differ from Snapchat: Cross-connector reconciliation:

​
Known limitations / merchant FAQs

Why mobile only and not desktop? Because Snapchat is mobile-only. There are no desktop placements anywhere on the platform, so 100% of your paid traffic lands on a phone inside the Snapchat in-app browser. A desktop or blended web-vitals report is irrelevant here; the only reading that matters is the mobile one this card uses. Does a slow page definitely mean speed is hurting conversion? Not on its own. Speed is one cause of weak conversion among several, including the offer, audience match, and creative-to-page consistency (a frequent Snapchat issue where a Story Ad or Dynamic Ad and the page it lands on do not line up). 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 CrUX field data reflects a range of real mobile users. Second, all Snapchat traffic opens inside the Snapchat in-app browser, which can render slower than a standalone mobile browser such as Chrome or Safari. The card aims to reflect the paid-user experience, not a single test run. Could a low conversion rate just be broken tracking rather than a slow page? Yes, and you should rule that out first. If the Snap Pixel or Conversions API is dropping events, the conversion side of the join will read artificially low and an otherwise fine page can look weak. Check pixel and CAPI health in Snapchat Events Manager, and pair this card with Snap Pixel / Conversions API Tracking Broken before you blame the page. 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. On Snapchat, AR-style preview widgets and autoplay video embedded on the landing page are common culprits, since they echo the swipe-up creative but add weight. 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 (typically Story Ads to fresh audiences) loses the most, because cold Snapchat audiences are among the least patient of any channel. Pair with Landing Page Performance to see which flagged URL carries the most budget. Does this cover Dynamic Ads catalogue pages too? Yes. Dynamic Ads pull from your product catalogue (uploaded to Snapchat or synced from the store feed) and send swipe-ups to the matching product or collection URL, so those destinations are joined to mobile vitals exactly like manually set landing pages. A slow product template will surface here regardless of whether the ad was built by hand or generated from the catalogue. 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 Snapchat 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.