When a Webflow site scores badly on mobile PageSpeed, it's usually not the platform. It's the same few build choices, and most of them take minutes to fix.
Before changing anything, run PageSpeed Insights on mobile and note which element it reports as the LCP. Then go through these:
1) Hero fades in from opacity 0. A page-load interaction with an opacity: 0 initial state keeps the hero heading or image invisible until Webflow's interactions script runs, which pushes back LCP. Keep the LCP element visible on load and animate the supporting elements instead, or move it without hiding it.
2) Hero photo as a background image. Webflow doesn't create responsive versions of background images, and the browser finds them late. Use an Image element with object-fit: cover, set its Load option to Eager, and keep Lazy for images below the fold.
3) Huge source files. A 5 MB PNG export is still heavy, responsive variants or not. Resize to the largest size it's actually shown at (about 2x for retina), then convert it to WebP in the Assets panel.
4) Third-party scripts in the site-wide head. Chat widgets, heatmaps and extra tag managers in Site settings > Custom code > Head code load on every page before the content. Move what you can to the Footer code with defer, put page-only tools in that page's settings, and remove the ones nobody checks.
5) Too many font weights. Every Google Font weight is another file, and Webflow loads Google Fonts through the WebFont loader script. Keep two or three weights, or upload the woff2 files as custom fonts.
6) Collection Lists that show every item with full-size images. Set a limit, turn on pagination, and give cards their own smaller thumbnail field instead of reusing the big hero image.
Which one do you check first when a client says their Webflow site feels slow?