The skill
Install once in Claude. It builds your load-time-to-conversion and field-count-to-abandonment curves, prices each second and field in dollars, diagnoses slow pages against Core Web Vitals, and finds the checkout fields that leak.
What's inside
Three files, one job: price and kill the friction tax
Built for performance and growth marketers, not engineers.
Install guide
A short setup walkthrough, plus a no-install option if you cannot add skills.
Plan B prompt
A single prompt you paste into any Claude chat to run the same analysis without installing anything.
How it works
Three steps, from your data to a dollar-ranked fix list.
Step 1Bring your data
Analytics with load time, bounce by load-time bucket and conversion by device for the tax and triage, a Lighthouse or CrUX export for the speed diagnosis, or field-level checkout analytics for the form diagnosis.
Step 2Claude runs the analysis
It builds your own curves and a dollar value per second and per field, classifies each leaking page as friction or offer, reads the slow LCP element and JavaScript weight against the thresholds, or finds the fields causing drop-off, in code.
Step 3Get the verdict and the fix
A dollar figure on the loss, the friction-versus-offer call, the ranked speed fixes, and the checkout fields to cut, make optional, or move to guest checkout.
The skill works from the data you bring, it does not connect to your site or ad platform. It also reads speed on field data, the Chrome User Experience Report, not a lab Lighthouse score, because only field data reflects what real users on real phones endure.
How to stop losing conversions to page speed and form friction
You pay for the click, then a predictable share of those clicks dies before any conversion is possible, waiting for the page to load and grinding through unnecessary form fields. That gap is the cheapest and most ignored lever in performance marketing, because fixing it lifts conversion for all of your traffic at once. Here is what the leak costs and how to close it.
Why delivered clicks die before they convert
Performance teams instrument the numerator of cost efficiency, CPC, CTR and CPM, and almost never the denominator, the share of paid clickers who actually survive load time and friction to convert. That denominator is where the money leaks. A better audience or a new creative lifts conversion for one slice of traffic, but fixing load time or cutting a form field lifts it for paid, organic and email at once, so with the US average cost per click near 5.26 dollars and rising, the clicks lost to a four-second load or an unneeded field are among the most expensive inventory you can waste.
How much page speed actually costs you
The speed curve is steep early and the evidence is causal. Mobile bounce probability rises about 32 percent as load goes from one to three seconds, 90 percent by five, and 123 percent by ten, while e-commerce conversion is about 3.05 percent at a one-second load and falls to about 1.1 percent by five. The strongest proof is within-brand, a single 0.1 second mobile speed gain lifted retail conversion 8.4 percent and lead-gen form submission 21.6 percent. The standard is Core Web Vitals, Largest Contentful Paint at or under 2.5 seconds, Interaction to Next Paint at or under 200 milliseconds, and Cumulative Layout Shift at or under 0.1, each at the 75th percentile of real users, and the skill reads them on field data, not your lab Lighthouse score.
Why checkout dies on form fields, not steps
It is the number of form fields, not the number of steps, that drives abandonment. Documented average cart abandonment is 70.19 percent, and while about 43 percent is unavoidable browsing, the rest is fixable, led by unexpected extra costs and forced account creation. The average checkout runs 11.3 fields when most need only about 8, removing the registration wall lifts completion 15 to 35 percent, and guest checkout with autofill converts about 45 percent higher than guest checkout without it. The skill finds which fields bleed users and which to cut, make optional, or move to guest checkout.
How to tell a friction problem from an offer problem
A friction problem and an offer problem need opposite fixes, so the skill classifies each leaking page before you spend engineering time. A friction problem shows bounce before content even renders, drop-off at a slow step or one form field, mobile far worse than desktop, and bounce that tracks load-time buckets. An offer problem looks different, users reach the page and engage but do not want what is offered, and speed and device do not move the needle. Friction goes to the speed and form playbook, an offer problem goes to messaging and pricing.
What the skill cannot do, and how to stay honest
It is a measurement and diagnosis tool, not a magic fix. Speed has steep diminishing returns, going from eight seconds to three is transformative while one to half a second barely registers, so it will not tell you to shave milliseconds off an already-fast page. Cutting form fields trades lead quality for volume, so test field reduction against downstream lead quality, not just submission count, and some friction is necessary, fraud checks, compliance and lead qualification, and should be kept. AI-generated fixes can break layouts and must be QA'd, and you diagnose on field data, not lab scores. For the full argument and the evidence behind fixing the conversion denominator, read Fix Load Time and Forms, Not Your Audience.