Page speed
measured from every region.
Every HTTP check records DNS, connect, TLS, TTFB and transfer timings from every active region. Compare fastest and slowest locations side by side, track p50 and p95 trends, and read Chrome UX Report Core Web Vitals when Google publishes them for the origin.
- On every plan
- DNS, connect, TLS, TTFB and transfer
- CrUX Core Web Vitals alongside
How it works
No separate check to set up: every page check already records its phases from each region.
Measured on every check
Each HTTP check records DNS lookup, TCP connect, TLS handshake, TTFB and body transfer timings separately from every enabled region.
Percentiles per region
Median (p50), 95th-percentile (p95) and average load times are computed over successful checks within your plan’s history window, showing the fastest and slowest region and the gap between them.
Field speed beside check timings
When Google’s Chrome UX Report holds 28-day field data for the site, LCP, INP and CLS appear alongside the regional network timings; when a site has too few visits, the page says so plainly.
What you get
Five network phases
See whether time went into DNS resolution, TCP connection, TLS negotiation, server processing (TTFB) or response transfer.
Fastest vs slowest region
Compare median and 95th-percentile latency across regions to see where visitors wait longest and whether a CDN edge or origin is responsible.
Portfolio speed overview
Rank every monitored site by 95th-percentile latency across your organisation or filter to a single client’s sites.
In the app and in the API
Read organisation and per-site page speed summaries in the web app, in the client portal and over
GET /api/v1/page-speed.
Which plans include it
Page speed views are included on every plan, Free included, bounded by the plan’s check cadence and history retention.
- FreeIncluded
- SoloIncluded
- TeamIncluded
- AgencyIncluded
- Agency PlusIncluded
Questions about page speed
Is this a Lighthouse or headless browser audit?
No. Beamfar measures HTTP request phases (DNS, connect, TLS, TTFB and transfer) from its regional probes without running page scripts, and pairs them with real-visitor Core Web Vitals from Google’s Chrome UX Report when available.
How often are timings recorded?
On every scheduled HTTP check: every 5 minutes on Free, every minute from Solo, every 30 seconds from Team when you choose it.
Are failed checks mixed into the speed percentiles?
No. Only checks with outcome up are included in p50, p95 and phase averages, so a fast connection reset never makes a broken site look fast.
Can a client portal contact view page speed?
Yes. A read-only client contact can open the page speed view and sees only the sites belonging to that client.
See how fast your sites answer from every region.
Add your sites: regional timing history starts with the initial check.
No card for the Free plan.