www.whitepages.com speed test — 20 Oct 2026

Measured from the wfix.shop server on 20 October 2026 at 14:18 UTC. Grade B (85/100), with the screenshots, the timings and the fixes that matter.

https://www.whitepages.com/

20 October 2026 at 14:18 UTC · Free test · report pt_42e34deab634
Grade
B
85/100
Performance87/100
Structure83/100

11 audit(s) passed, 5 need work

First byte (TTFB)663 msmeasured from this server
Fully loaded1.56 sfirst byte + slowest asset
Requests26document + assets
Page weight215.8 KBcompressed transfer
HTML document77.2 KBbr
ProtocolHTTP/3cloudflare
Third-party259 Bother hosts

Where the first byte went

  • DNS lookup 54 ms 8%
  • TCP connect 5 ms 1%
  • Server wait 604 ms 91%

Measured on the connection that fetched the HTML. Every other request on the page waits for the end of this bar before it can start.

How this page compares

First byteslower than 67% of 4,999 pages tested here663 ms against a median of 448 ms
Page weightlighter than 78% of 4,999 pages tested here215.8 KB against a median of 650.5 KB
Fully loadedfaster than 66% of 4,999 pages tested here1.56 s against a median of 1.84 s
Requestssends more requests than 100% of 4,999 pages tested here26 against a median of 26

Every report published here is in this comparison, so it is a reference population of pages tested from one server - not a benchmark of the whole web.

What these numbers mean

  • The first byte took 663 ms. Everything else waits for that number, so the server is where to start: caching, a slow query, or an overloaded host.
  • The page transfers 215.8 KB over 26 request(s). Images files are 54% of it, so resize and recompress the largest images before anything else.
  • The HTML itself arrives br-compressed.
  • It runs over HTTP/3, so the assets share a connection instead of opening one each.
  • The largest element painted at 292 ms, inside the 2.5 s Google calls good.
  • The main thread was blocked for 117 ms in total, which is not enough to feel.

Fix first: Server response time (TTFB) - Cut server think time: page cache, query indexes, fewer synchronous calls to third parties inside the request. Connection setup is distance, so a nearer region or a CDN edge helps instead.

Read on one shared server, not a visitor's phone: use it to compare pages against each other, not as a promise about every connection. We fix what these tests find.

Screenshot

What the page looks like

Loaded in headless Chromium on this server. Click an image to open it full size.

Mobile screenshot of www.whitepages.com
Mobile 390 × 844 · 113.9 KB · page is 6000 px tall

Browser render

The same URL loaded in a real browser, so these are the readings curl cannot produce. The grade above is still built from the server measurements.

Largest contentful paint292 msgood is under 2.5 s
Cumulative layout shift0.000under 0.1 is stable
Total blocking time117 mslong tasks during load
First contentful paint292 msfirst content on screen
Browser page weight1.53 MB93 request(s), scripts included
Failed requests13blocked or unreachable
Largest contentful paint292 ms
Goodgood under 2.5 s, poor over 4 s
Cumulative layout shift0.000
Goodgood under 0.1, poor over 0.25
Total blocking time117 ms
Goodgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Images 18 requests
116.8 KB 54%
Javascript 2 requests
18.1 KB 8%
Css 2 requests
3.7 KB 2%

Transfer size, compressed as sent. 26 request(s) in total, 215.8 KB across all of them.

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 663 ms. Of that, 604 ms was the server thinking and 59 ms was connection setup. A first byte under 400 ms is what a visitor feels as instant.

Fix: Cut server think time: page cache, query indexes, fewer synchronous calls to third parties inside the request. Connection setup is distance, so a nearer region or a CDN edge helps instead.

Render-blocking resources

high impact

3 render-blocking resource(s) in the document head (1 script(s), 2 stylesheet(s)). The page cannot paint until each one arrives.

Fix: Add defer or async to scripts that do not change the first paint, inline the critical CSS, and load the rest with media="print" plus an onload swap.

Cache static assets

medium impact

1 asset(s) answer without a Cache-Control max-age, so browsers revalidate them on every visit.

Fix: Version filenames on change and serve them with a long max-age plus immutable. That is what makes a returning visitor fast.

Avoid extra redirects

medium impact

1 redirect hop(s) before the page load started, each one a full round trip before the first byte.

Fix: Link to the canonical URL (and make sure http, the apex domain and www all point at it) so no visitor pays a redirect first.

Strict-Transport-Security

low impact

HSTS is not set, so the first visit on a hostile network can still be downgraded to HTTP.

Fix: Send Strict-Transport-Security with a max-age of at least six months. Add includeSubDomains once every subdomain is HTTPS.

Waterfall

Slowest requests

HTMLwww.whitepages.com/e,t={}
900 ms
CSSwww.whitepages.com/static/dist/styles/shared.css
879 ms
CSSwww.whitepages.com/static/dist/styles/global.css
874 ms
HTMLwww.whitepages.com/h,u,r
868 ms
IMAGESwww.whitepages.com/favicon.ico
867 ms
IMAGESwww.whitepages.com/static/images/png/usa-today.png
862 ms
IMAGESwww.whitepages.com/static/images/png/wall-street.png
858 ms
IMAGESwww.whitepages.com/static/images/webp/whitepages-app-illu…
855 ms
IMAGESwww.whitepages.com/static/images/png/nbc.png
852 ms
IMAGEScdn.whitepages.com/static/images/check-icon-blue.svg
851 ms

Each bar is one request's own response time, scaled to the slowest. Assets were fetched in parallel, so the bars overlap in real time rather than stacking. first party third party

RequestTypeStatusTimeSize
https://www.whitepages.com/e,t={}html403900 ms0 B
https://www.whitepages.com/static/dist/styles/shared.css?v=420a56259cf0css200879 ms3.7 KB
https://www.whitepages.com/static/dist/styles/global.css?v=420a56259cf0css200874 ms0 B
https://www.whitepages.com/h,u,rhtml403868 ms0 B
https://www.whitepages.com/favicon.icoimages200867 ms1.4 KB
https://www.whitepages.com/static/images/png/usa-today.pngimages200862 ms3.1 KB
https://www.whitepages.com/static/images/png/wall-street.pngimages200858 ms8.5 KB
https://www.whitepages.com/static/images/webp/whitepages-app-illustration.webpimages200855 ms6.1 KB
https://www.whitepages.com/static/images/png/nbc.pngimages200852 ms5.1 KB
https://cdn.whitepages.com/static/images/check-icon-blue.svg 3rd partyimages200851 ms259 B
https://www.whitepages.com/static/images/png/ny-times.pngimages200847 ms3.8 KB
https://www.whitepages.com/static/dist/addressAutocomplete.js?v=420a56259cf0javascript200845 ms2.2 KB
https://www.whitepages.com/static/images/png/app-phone-mockup.pngimages200843 ms63.1 KB
https://www.whitepages.com/static/images/svg/google-play-store.svgimages200843 ms8.3 KB
https://www.whitepages.com/static/images/svg/apple-store.svgimages200843 ms6.3 KB
https://www.whitepages.com/static/images/png/forbes.pngimages200843 ms5.6 KB
https://www.whitepages.com/static/images/png/cbs.pngimages200843 ms2.0 KB
https://www.whitepages.com/static/images/png/abc.pngimages200843 ms1.8 KB
https://www.whitepages.com/static/images/svg/linkedin-icon.svgimages200843 ms354 B
https://www.whitepages.com/static/images/svg/loading-arrow.svgimages200843 ms293 B
https://www.whitepages.com/static/images/svg/youtube-icon.svgimages200843 ms287 B
https://www.whitepages.com/static/images/svg/facebook-icon.svgimages200843 ms277 B
https://www.whitepages.com/static/images/png/app-qr-code.pngimages200843 ms246 B
https://www.whitepages.com/apple-touch-icon-precomposed.pnghtml403843 ms0 B
https://www.whitepages.com/static/dist/htmx-1.9.11.min.jsjavascript200842 ms16.0 KB
Report this page

The page is removed when the owner agrees. Sending this removes nothing by itself.

Run this test on your own site

The same engine, free, with the screenshots and the fixes. No account needed.