Image delivery
Identify oversized, uncompressed, non-responsive, or legacy-format images and verify next/image configuration.
Free Tools / Cost & Savings
Core Web Vitals & Hosting Cost Checker
Find the speed problems hurting real users, map them to practical Next.js fixes, and estimate what avoidable bytes cost at your traffic level.
Field and lab metrics Transfer waste estimate Six-hour report cache
Website workload
Mobile PageSpeed analysis
Reports are cached for six hours to protect Google API quota. Traffic figures are not stored.
Your performance report will appear here
See field Core Web Vitals when available, Lighthouse fallbacks, transferable bytes, and the highest-value fixes.
What the checker turns into action
Fonts and rendering
Surface render-blocking font behaviour and connect it to font-display or next/font improvements.
JavaScript and transfer
Quantify unused JavaScript and compressible payload so optimisation can be prioritised by bytes and time.
Next.js Performance Fix Pack
Copy-paste fixes for the most common Next.js speed and cost problems.
Sent to the work email you verified for tool access. No newsletter, no spam — ever.
Frequently asked questions
Where do the Core Web Vitals numbers come from?+
The checker uses Google PageSpeed Insights. It prefers Chrome User Experience field percentiles for LCP, INP, and CLS, then uses Lighthouse lab measurements where field data is unavailable.
Why might INP be unavailable?+
INP is a real-user interaction metric. New or low-traffic URLs may not have enough Chrome field observations, and Lighthouse does not provide an equivalent lab INP value.
How is hosting waste estimated?+
We multiply PageSpeed’s avoidable-byte opportunities by your monthly page views and apply a transparent $0.09 per GB transfer assumption. It is directional, not a replica of your cloud invoice.
Can this prove a site uses Next.js incorrectly?+
No external audit can inspect every source-level choice. The report maps image, font, JavaScript, and compression findings to common Next.js fixes that an engineer should confirm in the codebase.
Do you store the URL or traffic figure?+
PageSpeed reports are cached by URL for six hours to reduce Google quota usage. The monthly traffic figure is used for the response calculation and is not stored.
Need the fixes implemented, not just listed?
Framz profiles real applications, removes rendering and bundle bottlenecks, and ties performance work to infrastructure cost and conversion outcomes.
Review your application