Common suggestion types

1. Optimize large images using WebP format

This appears when one or more images are served as JPEG or PNG and could be 30 to 70% smaller as WebP. WebP is supported by every modern browser. Fix in Framer: open the image in your design, replace it with a WebP version exported from Figma or any image tool. Re-analyze speed to confirm LCP improvement.

2. Minify CSS and JavaScript files

Lighthouse flags this when CSS or JS files contain whitespace and comments that bloat their size. Framer minifies its own output by default, so this suggestion usually points to custom code components or third-party scripts you embedded. Audit your custom code overrides and embedded scripts. Remove or replace anything you do not actively use.

3. Use a CDN for static assets

Suggestion appears when server response time is high (e.g. above 600ms). Framer already serves through a global CDN, so this suggestion typically reflects a slow third-party API call or a custom fetch in your code components. Reduce blocking external requests during page load.

4. Reduce server response time

The first byte of HTML takes longer than 600ms to arrive. On Framer this can be caused by complex CMS queries with many filters or by custom code making blocking requests before render. Simplify your CMS bindings and defer non-essential fetches.

5. Properly size images

You are loading an image larger than the size it actually displays. A 4000px image rendered at 800px wastes bandwidth and slows LCP. Fix in Framer: re-export the image at the actual rendered size, or use Framer's responsive image options.

6. Eliminate render-blocking resources

Scripts or stylesheets in the document head are blocking the first paint. Check custom code components that include external scripts. Move them to load asynchronously where possible.

How to verify a fix worked

Make the change in Framer, publish the site, click Re-analyze Speed in RankFrame, then compare the gauge and Core Web Vitals to the previous values. If your fix targeted LCP, watch the LCP metric specifically. If you addressed JavaScript size, watch TBT (Total Blocking Time) move.