Calculator Inputs
Formula Used
This calculator builds a custom weighted composite score. Each metric is first normalized to a 0 to 100 subscore.
Higher-is-better metrics use:
Subscore = ((Value - Minimum) / (Maximum - Minimum)) × 100
Lower-is-better metrics use:
Subscore = ((Worst - Value) / (Worst - Best)) × 100
The weighted base score is the sum of each subscore multiplied by its weight share. The final result applies context multipliers: Final Score = Base Score × Connection Factor × Device Factor
| Metric | Weight | Benchmark Range |
|---|---|---|
| Download Speed | 16% | 0 to 100 Mbps |
| Upload Speed | 8% | 0 to 50 Mbps |
| Latency | 16% | 20 to 300 ms |
| Jitter | 8% | 0 to 60 ms |
| Packet Loss | 12% | 0% to 5% |
| Time to First Byte | 12% | 100 to 1500 ms |
| Full Page Load | 12% | 1000 to 12000 ms |
| Signal Strength | 6% | -120 to -50 dBm |
| Page Size | 6% | 0.3 to 8 MB |
| Request Count | 4% | 20 to 200 requests |
How to Use This Calculator
- Enter a scenario name so you can compare multiple tests later.
- Select the observed connection type and the target device class.
- Input measured network values like download, upload, latency, jitter, and packet loss.
- Enter page metrics such as TTFB, full load time, total page size, and request count.
- Click the calculate button to show the score above the form.
- Review the weighted table, Plotly radar graph, and top optimization priorities.
- Use the export buttons to save the result as CSV or PDF.
Example Data Table
| Scenario | Connection | Device | Download | Latency | Packet Loss | Page Load | Page Size | Final Score | Grade |
|---|---|---|---|---|---|---|---|---|---|
| Urban 5G | 5G | Flagship | 78.00 Mbps | 32.00 ms | 0.20% | 1,800 ms | 2.20 MB | 89.07 | Excellent |
| Balanced 4G | 4G | Mid-Range | 28.00 Mbps | 74.00 ms | 0.80% | 3,400 ms | 3.60 MB | 59.75 | Fair |
| Congested 3G | 3G | Entry-Level | 6.00 Mbps | 182.00 ms | 2.70% | 6,900 ms | 5.80 MB | 27.41 | Critical |
Frequently Asked Questions
1. What does the mobile speed score represent?
It represents a composite 0 to 100 score built from network quality, page efficiency, and delivery behavior. Higher scores indicate better likely mobile user experience under the entered conditions.
2. Is this the same as an official search engine score?
No. This tool uses a custom weighted model for scenario planning and technical comparison. It helps you analyze mobile performance quickly, but it does not replace official lab or field measurements.
3. Why are latency and packet loss so important?
Even with decent bandwidth, high latency and packet loss can make a page feel slow. They affect request timing, retries, streaming stability, and the speed of user interactions.
4. Why include page size and request count?
Those values capture front-end efficiency. Heavy pages and too many requests raise transfer overhead, connection setup time, and rendering delays, especially on mid-range phones and weak signals.
5. What does the connection factor do?
It slightly adjusts the base score to reflect realistic expectations for 3G, 4G, 5G, or WiFi testing. This makes comparisons more contextual across different mobile environments.
6. Why does device class affect the result?
Device capability influences rendering, decoding, and script execution. A fast network can still feel slower on weaker hardware, so the calculator applies a modest contextual adjustment.
7. Can I use this calculator for app screens too?
Yes. The model works well for app views, mobile web pages, or hybrid screens if you enter realistic transfer, delay, and request values for the specific user journey.
8. How should I interpret a low score?
Start with the weakest subscores shown in the breakdown. Improve those bottlenecks first, then rerun the test. This usually gives the fastest gains in perceived mobile speed.