I’m running a Webflow site (microagility.webflow.io/) and struggling to eliminate a render‑blocking main stylesheet that Lighthouse flags as ~11 s of FCP/LCP delay. I’ve tried various client‑side hacks, but they all run too late for PageSpeed Insights. I need an expert who can:

Propose and implement a bullet‑proof solution (via HTML export & head reordering, Cloudflare Worker HTML rewrite, or another server‑side approach) that removes or defers Webflow’s autogenerated microagility.shared…min.css link before the browser parse‑time

Inline critical “above‑the‑fold” CSS for header/hero

Load the full stylesheet asynchronously (e.g. preload + onload switch or equivalent)

Maintain full Webflow functionality (no visual regressions)

Demonstrate at least 10 s of render‑blocking savings in Lighthouse/Piglighthouse reports

Responsibilities:

Audit current Webflow head output and PageSpeed report

Implement a robust solution that rewrites/edits the HTML before parse (e.g. export & manual edit, Cloudflare Worker, Netlify Edge Function, or similar)

Inline minimal critical CSS and defer the main CSS file

Test across mobile and desktop to ensure no layout shifts or FOUC

Provide before/after Lighthouse screenshots and verification

Requirements:

Proven experience optimizing Webflow sites for Core Web Vitals (FCP, LCP, TBT)

Deep understanding of critical‑CSS generation, render‑blocking resource removal, and asynchronous CSS loading patterns

Familiarity with Cloudflare Workers, Netlify Edge Functions, or other CDN/edge‑rewrite tools is a plus

Strong HTML/CSS/JavaScript skills and comfort exporting & rebuilding Webflow code if needed

Clear communication and demonstration of past performance wins

Deliverables & Timeline:

Audit report with current bottlenecks and proposed approach

Implemented solution on a staging copy of the site

Lighthouse score improvement proof (FCP/LCP render‑blocking eliminated)

• Proven experience optimizing Webflow sites for Core Web Vitals (FCP, LCP, TBT)
• Deep understanding of critical‑CSS generation, render‑blocking resource removal, and asynchronous CSS loading patterns
• Strong HTML/CSS/JavaScript skills and comfort exporting & rebuilding Webflow code if needed
• Clear communication and demonstration of past performance wins

• I’m running a Webflow site (microagility.webflow.io/) and struggling to eliminate a render‑blocking main stylesheet that Lighthouse flags as ~11 s of FCP/LCP delay
• Propose and implement a bullet‑proof solution (via HTML export & head reordering, Cloudflare Worker HTML rewrite, or another server‑side approach) that removes or defers Webflow’s autogenerated microagility.shared…min.css link before the browser parse‑time
• Inline critical “above‑the‑fold” CSS for header/hero
• Load the full stylesheet asynchronously (e.g. preload + onload switch or equivalent)
• Maintain full Webflow functionality (no visual regressions)
• Demonstrate at least 10 s of render‑blocking savings in Lighthouse/Piglighthouse reports
• Audit current Webflow head output and PageSpeed report
• Implement a robust solution that rewrites/edits the HTML before parse (e.g. export & manual edit, Cloudflare Worker, Netlify Edge Function, or similar)
• Inline minimal critical CSS and defer the main CSS file
• Test across mobile and desktop to ensure no layout shifts or FOUC
• Provide before/after Lighthouse screenshots and verification
• Audit report with current bottlenecks and proposed approach
• Implemented solution on a staging copy of the site