← ClaudeAtlas

framer-lighthouse-100listed

Audit and fix a Framer website so it scores 100 in Lighthouse / PageSpeed Insights (Performance, Accessibility, Best Practices, SEO) on mobile and desktop. Measures with the PageSpeed API and in the owner's own browser, reads console and network logs, audits every image, video, font, ticker, color and meta tag on every page, fixes what is safe, asks before anything visible, keeps asking until every item is decided, and delivers a detailed report in the chat plus a downloadable PDF.
studiohans-agency/framer-lighthouse-100 · ★ 1 · Data & Documents · score 77
Install: claude install-skill studiohans-agency/framer-lighthouse-100
# Framer Lighthouse 100 You are getting a website built in Framer to 100 in all four PageSpeed categories on mobile and desktop. Work in five passes: **measure, fix, ask, verify, report**. Fix everything that is invisible to visitors straight away. Ask before anything that changes how the site looks, reads or behaves, and keep asking until every open item has a yes or a no. Never publish unless the owner tells you to. PageSpeed is the referee, but it is not the whole audit. It only sees what loads in the first viewport of one page, it skips hidden states, and it trusts whatever color the browser happens to paint at that moment. This skill exists because the real problems are often the ones PageSpeed does not flag. Measure the whole site, not only the score. ## What you need 1. **The live URL** (the custom domain, or the `framer.website` address). If it is missing, ask for it before doing anything else. 2. **Access to the Framer project.** Use whichever Framer connection the session has (the Framer MCP server with `exec`, or the Framer plugin tools). Without it you can still measure and report, and give step by step instructions instead of fixing. 3. **A browser tool on the owner's computer** (Claude in Chrome, or the built in browser). Use it to run PageSpeed the way the owner sees it, to load the live site, and to read console and network logs. If none is available, say so and use the API and a headless browser instead. 4. **A shell** with `ffmpeg`, `cwebp` (or Node `sha