Webflow Core Web Vitals: What You Can and Can't Control

TL;DR: Webflow Core Web Vitals are decided by three layers, and only one of them belongs to Webflow. Webflow controls the hosting and CDN that set server response time, the jQuery and webflow.js runtime it loads on published pages, and the responsive image variants it generates. The developer controls how the hero image loads, the interactions, the custom code and the fonts. The people editing content control what gets uploaded and embedded after launch. In HTTP Archive's October 2026 field data, 72.1% of Webflow sites passed all three Core Web Vitals on mobile. LCP failed most often, and INP is where Webflow trailed Wix, Squarespace and WordPress the most (figures calculated from HTTP Archive's published counts).
- Layer 1, Webflow: hosting, CDN, server response time, the jQuery and webflow.js runtime, image variants for Image elements.
- Layer 2, the developer: hero image loading, interactions, third-party scripts, custom code, fonts.
- Layer 3, content editors: image uploads, rich text images, embeds, tags added after launch.
How do Webflow sites actually score on Core Web Vitals?
In October 2026, 72.1% of Webflow origins passed all three Core Web Vitals on mobile; LCP was their most-failed metric at 79.6% good, and INP, at 87.7% good, was the only metric where Webflow trailed Wix, Squarespace and WordPress. The 72.1% pass rate is close to Squarespace at 71.0%, behind Wix at 80.9% and well ahead of WordPress at 49.0%. Those percentages are my calculation from the good and eligible origin counts in the HTTP Archive Core Web Vitals Technology Report, which draws on Chrome's real-user data; for Webflow that is 40,700 good origins out of 56,474. A page passes when Largest Contentful Paint (LCP), Interaction to Next Paint (INP) and Cumulative Layout Shift (CLS) are all good at the 75th percentile, using the thresholds in Google's web.dev guide; the Webflow QA checklist covers holding a build to them before launch.
Webflow's field data shows two different weak spots. LCP is the metric Webflow sites fail most often: 79.6% of origins were good, so 20.4% were not (my subtraction). LCP is also the lowest metric on every platform in the table, and Webflow's LCP beats Squarespace and WordPress, so that weakness is shared, not Webflow-specific. INP is where Webflow trails its peers: 87.7% good, against 92.6% for Wix, 97.1% for Squarespace and 90.0% for WordPress. CLS, at 93.8% good, is rarely the problem. In the Webflow sites I review, the failing metric is almost always LCP or INP, which matches the table.
Which parts of Core Web Vitals does Webflow control, and which do you?
Webflow controls the server, the CDN and the runtime scripts it adds to every published page; the developer controls what the build loads and runs; content editors control what gets uploaded and embedded after launch. Webflow says its hosting is "powered by AWS and Cloudflare" with "Global CDN delivery" on its hosting page. Published Webflow pages also load jQuery 3.5.1 and webflow.js runtime files, which I confirmed today in the page source of webflow.com itself, and a builder cannot remove them on Webflow hosting. The rule I apply on client projects is to name the owner of a failing metric before anyone touches it. The matrix below is the one I use; whether Webflow hosting is a good choice overall is covered in is Webflow good for SEO.
| Cause | Metric it moves | Who controls it | What can change |
|---|---|---|---|
| Server response time and CDN delivery | LCP (through TTFB) | Webflow | Little on standard hosting beyond avoiding redirect chains, which count toward TTFB |
| jQuery 3.5.1 and webflow.js runtime on published pages | INP and LCP | Webflow | Not removable on Webflow hosting |
| Responsive variants and srcset for Image elements | LCP | Webflow generates them; the developer chooses the element | Webflow does not create variants for background images |
| Lazy loading of new images (Webflow's default) | LCP | Developer | Loading setting per image |
| Interactions, GSAP and custom JavaScript | INP | Developer | Script work on the main thread |
| Third-party tags (chat, analytics, ads, heatmaps) | INP and LCP | Developer and whoever adds tags after launch | Tag review at handoff and every quarter |
| Web fonts and font swapping | CLS and LCP | Developer | Number of font files, fallback sizing |
| Oversized uploads and rich text images | LCP | Content editors | Upload rules in the handoff guide |
| Embeds without reserved space (video, forms, widgets) | CLS | Content editors and developer | Fixed-ratio wrappers built into components |
The step-by-step fixes for each developer-owned row, including hero image loading and background images, are in my guide to speeding up a slow Webflow site, so this post does not repeat them.
Which layer is behind a failing LCP on a Webflow site?
A failing LCP on a Webflow site can come from any of the three layers, which is why LCP is the most-failed Core Web Vital on Webflow and on every other platform in HTTP Archive's table. Google's TTFB guide says "most sites should strive to have a TTFB of 0.8 seconds or less," notes that TTFB "isn't a Core Web Vitals metric," and lists redirect time as part of TTFB; because TTFB is the first slice of LCP, it is the check that separates the server layer from the page. Across platforms, good TTFB on mobile in October 2026 was 74.8% for Webflow, 74.8% for Squarespace, 78.5% for Wix and 23.6% for WordPress (calculated from the technology report counts). When I audit a Webflow page with poor LCP, I work through the layers in this order.
- Server layer: check your own TTFB; if it is above 0.8 seconds, look for redirect chains first.
- Build layer: check how the hero element and its loading setting were built (fixes in the speed-up guide).
- Content layer: check the size of the file an editor uploaded for the largest element.
What could explain Webflow's lower INP pass rate?
Webflow's lower INP pass rate has no measured cause in HTTP Archive's data, but in my reading two Webflow-specific factors are the likeliest candidates: the jQuery and webflow.js runtime that every published Webflow page loads, and builds that lean on scroll-triggered interactions and GSAP animations. INP measures how fast a page responds to input, and Google's INP optimisation guide notes that script evaluation "can introduce long tasks on the main thread." Marketing tags pasted into custom code fields add to that on any platform. The decision rule I use: the runtime is fixed, so if INP fails while TTFB passes, the fix is removing the script work the build and its tags add. Google splits every interaction into three parts:
- Input delay: the time before the click handler can start, usually spent waiting on other scripts.
- Processing duration: the time the handler itself takes to run.
- Presentation delay: the time until the browser paints the result.
Why does Search Console show no Core Web Vitals data for my Webflow site?
Search Console shows no Core Web Vitals data for a Webflow site when the site does not get enough real Chrome visits to enter the Chrome UX Report (CrUX), which is where the report's data comes from. Google's Core Web Vitals report help says "The data for the Core Web Vitals report comes from the CrUX report" and that "No data available" can mean "there is not enough data available." Chrome's CrUX methodology adds that "Pages and origins that don't meet the popularity threshold are not included in the CrUX dataset." Most small business Webflow sites I see sit below that line for many of their pages. If there is no field data, judge the site with lab tools like Lighthouse and treat any score as an estimate, not a pass. Whether Core Web Vitals move rankings at all is covered in is Webflow good for SEO.
- Field data (CrUX, Search Console) is what real Chrome visitors experienced.
- Lab data (Lighthouse, a single PageSpeed Insights run) is a simulation on one device profile.
- Search Console validates a fix over a 28-day monitoring period after you click Start Tracking, per the same help page.
Where do Webflow Core Web Vitals projects go wrong?
Webflow Core Web Vitals projects go wrong in five predictable ways, and each one spends budget on the wrong layer or reads the wrong data. What I see agencies get wrong most often is treating a Lighthouse score as the goal when the real goal is field data at the 75th percentile defined in Google's Core Web Vitals guide. If a fix is not tied to a named failing metric and a named owner, park it.
- Chasing a lab score of 100. Consequence: Lighthouse turns green while CrUX field data, the data Search Console reports, does not move.
- Trusting a Lighthouse pass on a site with no CrUX data. Consequence: the client is told the site passes Core Web Vitals when no real-user measurement exists.
- Blaming Webflow hosting for poor INP. Consequence: the team plans a migration when the delay comes from scripts on the page.
- Adding tags after handoff without a review. Consequence: INP regresses months after launch and nobody connects it to the new chat widget.
- Expecting next-day proof. Consequence: a correct fix gets reverted because Search Console validation runs for 28 days.
Want to know which layer is failing on your Webflow site?
If your Webflow site fails Core Web Vitals and you are not sure whether the cause is Webflow, the build or what was added after launch, book a 15-minute call. You get a read of your field data, the failing metric named with its owner from the matrix above, and the first two changes I would make, before any quote.
FAQ
What share of Webflow sites pass Core Web Vitals?
Webflow sites passed all three Core Web Vitals on mobile at 72.1% of eligible origins in October 2026, calculated from the HTTP Archive Core Web Vitals Technology Report counts of 40,700 good out of 56,474 origins. By metric, Webflow origins were 79.6% good on LCP, 87.7% on INP and 93.8% on CLS, so LCP is the metric Webflow sites miss most often, while INP is where Webflow trails Wix, Squarespace and WordPress.
Can you change Webflow's server response time?
Webflow's server response time can barely be changed on standard Webflow hosting, because Webflow runs the servers and CDN itself on AWS and Cloudflare. The one lever a builder keeps is avoiding redirect chains, since Google counts redirect time inside Time to First Byte. Google suggests a TTFB of 0.8 seconds or less and notes TTFB is not itself a Core Web Vital.
Why does a Webflow page pass Lighthouse but fail Core Web Vitals in Search Console?
A Webflow page can pass Lighthouse and fail in Search Console because Lighthouse is a lab simulation on one device profile, while Search Console reports field data from real Chrome users in the Chrome UX Report. Real visitors on slower phones, with third-party tags firing and real interactions, produce worse INP and LCP than a single lab run. Search Console is the number to trust.
Why is there no Core Web Vitals data for my Webflow site in Search Console?
Search Console shows no Core Web Vitals data for a Webflow site when the site lacks enough real Chrome visits to enter the Chrome UX Report, the report's only data source. Chrome states that pages and origins below its popularity threshold are not included. Low-traffic Webflow sites should rely on lab tools such as Lighthouse and treat those scores as estimates.
How long does a Core Web Vitals fix take to show in Search Console?
A Core Web Vitals fix on a Webflow site takes up to 28 days to confirm in Search Console. Clicking Start Tracking in the Core Web Vitals report begins a 28-day monitoring period, and the issue is marked fixed only if it does not appear on any URL in that window. Reverting a correct fix after a few days usually means reading the data too early.
Do content editors affect a Webflow site's Core Web Vitals?
Content editors affect a Webflow site's Core Web Vitals through what they add after launch: oversized image uploads and rich text images slow LCP, embeds without reserved space cause layout shift, and new third-party tags can worsen INP. The developer controls the build, but the handoff guide needs upload and embed rules, or the scores drift after launch.
Agency with more Webflow work than developers?
I build white-label Webflow sites for agencies with an AI-accelerated, senior-reviewed workflow. Book a 15-minute fit call for a straight answer on scope, timeline and cost.
Need a Webflow site that your team can actually run?
I build, migrate and optimize Webflow sites for companies: fast, ready for Google and AI search, and easy to update. Book a 15-minute call for a straight answer on scope, timeline and budget.



