Webflow sync, pageviews & more.
NEW

How can I improve the mobile score above 90 on Google audits for webflow, particularly addressing the issue of First Contentful Paint 3G timing?

TL;DR
  • Compress and lazy load images, avoid large above-the-fold hero images.
  • Limit fonts to essential styles, use font-display: swap, or system fonts.
  • Defer non-critical and third-party scripts, and move them to the footer.
  • Delay or exclude heavy Lottie animations above the fold.
  • Simplify DOM structure, reduce nesting and unnecessary layers.
  • Enable Webflow’s HTML/CSS/JS minification and clean up unused styles.
  • Preload key assets and preconnect to common CDNs.
  • Use Lighthouse in Mobile + Slow 3G mode to locate and address FCP bottlenecks.

To improve the mobile score above 90 on Google Lighthouse audits in Webflow, specifically tackling First Contentful Paint (FCP) under 3G, you need to optimize what loads first and how quickly it appears. Below are key actions to improve FCP performance on mobile devices.

1. Optimize Image Delivery

  • Reduce image sizes using WebP format and compressed JPEGs where possible.
  • Set all large images to lazy load by enabling loading="lazy" in Webflow image settings.
  • Avoid using large hero background images above the fold; instead, use compressed inline images.

2. Limit Font Loads and Delays

  • Use only essential font weights and styles. Limit fonts to 1–2 families and max 2 weights (e.g. 400, 700).
  • Enable font-display: swap through custom code to avoid render-blocking.
  • Consider using system fonts where practical to eliminate load time.

3. Clean and Defer Scripts

  • Minimize or defer third-party scripts like chat widgets, analytics, or tracking tags. Add them after DOMContentLoaded event.
  • In Page Settings > Custom Code, move non-critical scripts to the footer section.
  • Disable Webflow’s built-in integrations (like Google Maps or interactions) if unused.

4. Remove or Delay Large Lottie Animations

  • Lottie or GIF animations above the fold dramatically slow down FCP, especially on 3G.
  • If necessary, hide with interactions, set to trigger only once the page has loaded, or open on scroll.

5. Reduce DOM Complexity

  • Simplify your structure above the fold; nesting multiple divs and animations causes rendering delays.
  • Avoid unnecessary absolute-positioned layers or multiple stacking contexts right at page load.

6. Enable Webflow Minification and Clean Unused Styles

  • In Project Settings > Hosting, turn on Minify HTML, CSS, and JS.
  • Use Webflow’s Audit panel in the Designer to remove unused styles and interactions.

7. Set Proper Preload and Preconnect Options

  • Add preload for key fonts or hero image using the <link> element in Custom Code head (Example: <link rel="preload" href="font-url.woff2" as="font" type="font/woff2" crossorigin>).
  • Add preconnect for commonly-used CDNs: Webflow assets, Google Fonts, etc.

8. Test with Lighthouse Throttling

  • Use Lighthouse in Chrome DevTools simulating “Mobile + Slow 3G” mode to identify specific FCP bottlenecks.
  • Test pages individually. Focus especially on the home page and any high-traffic landing pages.

Summary

To improve your FCP on 3G and hit 90+ on Lighthouse mobile scores, ensure above-the-fold content is minimal, lightweight, and fast-loading. Compress images, defer scripts, reduce font and animation loads, and leverage lazy loading and minification in Webflow’s settings.

Rate this answer

Other Webflow Questions