ESTIMATES / 05 · FREE PERSONAL PLANNING

Page Load Time Estimator

Try a bandwidth and latency scenario using your own assumptions. These numbers are not measured site performance.

No sign-up · No live test · No admin access · Inputs stay in this browser page

01

Your inputs

Use your own estimates. Do not enter credentials or sensitive details.

Planner inputs and actions

Optional. Do not enter a URL expecting it to be tested.

Nothing is submitted. Reloading or leaving this page clears your entries.

02

Your planning result

Make room for a clear next step.

Enter your assumptions, then select Build my plan. Your result will appear here with the method and a portable text copy.

An estimate, not a diagnosis.

OPEN METHOD

Behind the result - No mystery in the method

Transfer seconds = page weight in MB × 8 ÷ bandwidth in Mbps. Network wait seconds = latency in ms × sequential network rounds ÷ 1,000. Model total = server response + transfer + network wait + processing. The cached scenario changes transfer weight only, by your assumed reduction percentage. Request count is an inventory note, not a multiplier: browsers make many requests concurrently. This additive model is deliberately simplified and is not LCP, INP, CLS, a Core Web Vitals assessment or a guaranteed load time.

These tools do not test a live site, access WordPress admin or install anything. They do not fetch, validate or confirm bookings, live prices or exact rates. They do not store data on a server. Blank optional fields are omitted. Text is displayed literally, not interpreted as HTML.

Keep the result in context. This is a starting point for your own checks. Back up first, use staging, and review one reversible change at a time.

A FEW USEFUL ANSWERS

Before you go

Is this a live speed test?

No. It does not request your page or measure a device. Every value is a user-entered assumption.

Why can a measured result differ?

Real requests overlap. Connection setup, protocol behaviour, server variation, rendering, compression, contention and device work are not fully modelled. The result is only a rough scenario.

What does the cached scenario assume?

Only that the transfer weight falls by the percentage you enter. Server response, latency rounds and processing stay unchanged. It does not predict a real cache hit.

Are the results Core Web Vitals?

No. They are model totals, not field or lab measurements of visitor experience.

Can I save my assumptions with the result?

Yes. Print or download includes the input assumptions and model breakdown so someone else can understand the estimate.