Calculator Inputs
Enter measured mobile page values and adjust weights when a metric matters more for your workflow. The calculator handles weight normalization automatically.
Example Data Table
Use these sample ranges to compare common mobile page types and expected scoring outcomes.
| Page Type | LCP | INP | CLS | Page Size | Requests | Estimated Score |
|---|---|---|---|---|---|---|
| Lean blog article | 1.9 s | 160 ms | 0.03 | 540 KB | 31 | 94.3 |
| Balanced landing page | 2.7 s | 240 ms | 0.06 | 980 KB | 58 | 82.9 |
| Heavy ecommerce category page | 4.8 s | 390 ms | 0.18 | 2,650 KB | 118 | 54.1 |
Formula Used
This calculator converts each metric into a normalized 0 to 100 score, then applies your custom weight mix. Lower-is-better metrics and higher-is-better metrics use different linear formulas.
Lower-better score = max(0, min(100, ((worst - value) / (worst - best)) × 100)) Higher-better score = max(0, min(100, ((value - worst) / (best - worst)) × 100)) Normalized weight = metric weight / total entered weights Overall mobile performance score = Σ(metric score × normalized weight)
Lower-is-better thresholds used: LCP 2.5 to 6.0 seconds, INP 200 to 800 ms, CLS 0.10 to 0.35, TTFB 800 to 3000 ms, page size 700 to 5000 KB, requests 35 to 220, JavaScript 200 to 2200 KB, image weight 250 to 3000 KB.
Higher-is-better thresholds used: compression 40% to 100%, cache 30% to 100%, usability 50% to 100%, and SEO essentials 40% to 100%.
How to Use This Calculator
- Collect current mobile measurements from your testing tools or reports.
- Enter the page metrics in the calculator fields above.
- Adjust weights to reflect what matters most for your page type.
- Submit the form to see the overall score and metric breakdown.
- Review the top improvement opportunities with the largest impact gaps.
- Export the report as CSV or PDF for audits, planning, or client sharing.
FAQs
1) What does this score measure?
It blends loading speed, responsiveness, layout stability, payload efficiency, caching, usability, and search readiness into one weighted mobile performance score.
2) Is this the same as a Lighthouse score?
No. It is a custom weighted model built for planning and comparison. It helps prioritize improvements using your chosen importance mix.
3) Why are custom weights useful?
Different pages need different priorities. Ecommerce, blogs, and web apps can emphasize speed, interaction, or usability differently.
4) Should higher scores always be the goal?
Usually yes, but context matters. A realistic score with strong business outcomes can be better than chasing perfection with expensive changes.
5) Why are some metrics lower-is-better?
Timing, payload, and request metrics represent delays or weight. Smaller values usually mean faster delivery and smoother mobile experiences.
6) Can I compare two pages with this tool?
Yes. Run each page with the same weight profile, then compare overall scores, contribution patterns, and top loss areas.
7) Does this replace real user data?
No. It is a planning calculator. You should still validate decisions with field data, conversion behavior, and real-device testing.
8) What is the fastest way to raise the score?
Focus first on metrics with the biggest impact gap. Those areas usually offer the largest score gain for the least effort.