How to check and improve Webflow website speed

Find the slow element before changing your design. Test images, scripts and interactions on the published site.

Updated September 8, 2026 · Layzr

To check Webflow website speed, run the published URL through Layzr's built-in website audit and identify the element or interaction behind the slow metric. Then use Webflow's asset and publishing controls to test one specific improvement. Test a real page on your custom domain; the Designer preview does not reproduce the visitor's entire loading experience.

Start with three pages: the homepage, a page that receives enquiries or sales, and one CMS template page with substantial content. Record the URL and device for each. This catches problems hidden by a fast homepage, such as a large CMS image, an embedded video or a form integration that appears on only one template.

1. Record a baseline you can compare

Open the published page while signed out. Copy the final URL after redirects and note the most recent publication.
Open Layzr, sign in and paste the published URL. Choose General audit, select Mobile and click Run audit. Read the performance metrics and technical findings in Scores. Run Desktop separately when needed; each run uses audit credits.
Record the metrics that Layzr actually returns for the selected device. If the technical scan is unavailable, keep that result separate from a measured poor score and retry later.
Repeat the lab test under comparable conditions. Record the metric that stays slow, the affected element and the proposed change. A single overall score can vary without a meaningful change to the page.

Use a simple measurement row: URL → device → LCP → CLS → slow interaction or long task → suspected component → change → retest. Leave any unavailable value blank. For interaction responsiveness, reproduce an actual menu, form or filter interaction; a page-load score does not tell you whether that action feels fast.

2. Match the symptom to the component

The hero takes a long time to appear: inspect the LCP element. Determine whether it waits for its image request, a font, a script or an entrance animation before becoming visible.
The page arrives quickly but freezes: record a Performance trace while using the slow control. Find the script or task occupying the main thread.
Content jumps as it loads: watch the affected area. A video, image or embed may occupy no space until it finishes loading.
Only CMS pages are slow: compare one slow item with a faster item using the same template. Check asset sizes and embedded content before changing the entire site.
Every page is unusually slow today: compare another network and check Webflow's status page before assuming your latest design change caused it.

Webflow's site health scan can help identify common setup issues. Use its recommendations as investigation leads. A finding still needs to match the page and metric you are trying to improve.

3. Fix the image that delays the first screen

In the browser's Network panel, find the image identified in the LCP diagnostic. Compare its transferred size and dimensions with the space it occupies on mobile. A small-looking image can still download a large original. Inspect the delivered file, not just the Designer's display dimensions.

Keep a copy of the original asset. Webflow's conversion replaces the existing file, so make a backup before converting.
In the Assets panel, expand the panel, select the relevant JPEG or PNG asset, choose WebP or AVIF and click Compress. Republish when conversion finishes.
For CMS images, review the Collections panel's Compress assets option separately. Check the affected CMS template after republishing.
Inspect a mobile page again and confirm which file the browser actually downloaded. Check that the image is still clear at the displayed size.

Webflow creates responsive variants for inline images, but background images need their own sizing review. Consider whether a large decorative background needs to be that large on a phone. Do not lazy-load the important above-the-fold LCP image: delaying its request can delay the main content. Lazy loading is more appropriate for images the visitor has not reached yet.

4. Test optional scripts and publishing settings

List the scripts used on this page: chat, analytics, consent, scheduling, video, animations and custom embeds. Note which are global and which support a specific task. In a staging or duplicate version, test removing one optional integration and repeat the same measurement. Keep forms, payments and required consent behavior working.

Webflow supports per-page JavaScript. Its asynchronous JavaScript option can help loading, but custom code that assumes a particular execution order can break. Check the current publishing options and Webflow documentation before enabling it. After a change, test navigation, tabs, sliders, forms and custom embeds on the published version.

Minification reduces code size, but it will not remove an unnecessary integration or fix a huge hero asset. Prioritize the component the trace identifies. If disabling a script does not produce a repeatable improvement, restore it and test the next hypothesis.

5. Review motion and layout without stripping the design

Keep the headline and main action visible while the page loads. Avoid making essential content wait for a long entrance sequence.
Reserve the final aspect ratio or dimensions of images, videos and embeds so nearby text does not move after they arrive.
Reduce an expensive animation only after testing its effect. Verify the same interaction on a slower phone and with reduced motion enabled.
Check the font swap and line wrapping in the first screen. A font change can alter the headline height even when images are well sized.

6. Retest the metric and the enquiry flow

Publish the isolated change, rerun the same URLs and compare the metric you recorded. Save the new report next to the baseline. Then complete a safe form test and check the confirmation, keyboard navigation and mobile layout. A faster page with a broken enquiry form is not a successful release.

Once loading is understood, use the landing page audit checklist to review the offer, proof and conversion journey. If the page loads well but gets impressions without clicks, investigate its rankings and search intent using the Search Console guide.

Documentation used in this guide

FAQ

Why is my Webflow mobile score lower than desktop?

The lab tests model different device and network conditions. Mobile can expose expensive images, scripts and rendering work that is less visible on a faster desktop. Compare the diagnostics and the same device over time instead of treating the two overall scores as interchangeable.

Will a faster Webflow page automatically get more Google clicks?

No. A page also needs to match a searcher's task, be indexable and rank where people will see it. Performance work should address a measured problem; it does not replace useful content or establish that a ranking increase will follow.

Review the rest of your Webflow landing page

Use Layzr for built-in performance checks and AI feedback on copy, design, UX and SEO. Retest the same URL and device after applying a fix. One free audit is included for new accounts; further runs use your plan credits.

Audit your Webflow page in Layzr