www.maricopa.gov speed test — 20 Oct 2026

Measured from the wfix.shop server on 20 October 2026 at 12:32 UTC. Grade C (73/100), with the screenshots, the timings and the fixes that matter.

https://www.maricopa.gov/

20 October 2026 at 12:32 UTC · Free test · report pt_2d2d8ba0edbb

Re-test this page Test your own site

Grade

73/100

Performance72/100

Structure74/100

10 audit(s) passed, 6 need work

First byte (TTFB)302 msmeasured from this server

Fully loaded1.42 sfirst byte + slowest asset

Requests26document + assets

Page weight5.89 MBcompressed transfer

HTML document81.8 KBgzip

ProtocolHTTP/3cloudflare

Third-party193.7 KBother hosts

Where the first byte went

DNS lookup 54 ms 18%
TCP connect 46 ms 15%
Server wait 202 ms 67%

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 bytefaster than 74% of 4,999 pages tested here302 ms against a median of 449 ms

Page weightheavier than 94% of 4,999 pages tested here5.89 MB against a median of 650.3 KB

Fully loadedfaster than 76% of 4,999 pages tested here1.42 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 arrived in 302 ms. That is workable, and the cheapest win left is caching or a warmer connection.
The page transfers 5.89 MB over 26 request(s). Images files are 93% of it, so resize and recompress the largest images before anything else.
The HTML itself arrives gzip-compressed.
It runs over HTTP/3, so the assets share a connection instead of opening one each.
The largest element took 4.68 s to paint, past the 2.5 s threshold: usually a hero image that is too big or a render-blocking script in front of it.
Layout shift is 0.199 (good is under 0.1): something without a reserved size is loading late - an image, an ad, or a font swap.
The main thread was blocked for 719 ms, so taps and scrolling wait while scripts run.

Fix first: Image delivery and format - Serve WebP or AVIF with a JPEG fallback, size images to the space they occupy, and lazy-load anything below the fold. Images are usually more than half of a slow page.

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.maricopa.gov — **Mobile** 390 × 844 · 41.0 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 paint4.68 sgood is under 2.5 s

Cumulative layout shift0.199under 0.1 is stable

Total blocking time719 mslong tasks during load

First contentful paint696 msfirst content on screen

Browser page weight11.78 MB179 request(s), scripts included

Failed requests3blocked or unreachable

Largest contentful paint4.68 s

Poorgood under 2.5 s, poor over 4 s

Cumulative layout shift0.199

Needs improvementgood under 0.1, poor over 0.25

Total blocking time719 ms

Poorgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Images 14 requests

5.46 MB 93%

Javascript 11 requests

354.6 KB 6%

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

Top issues

Image delivery and format

high impact

2 image(s) over 200 KB and 0 large image(s) still served as JPEG or PNG.

Fix: Serve WebP or AVIF with a JPEG fallback, size images to the space they occupy, and lazy-load anything below the fold. Images are usually more than half of a slow page.

Total page weight

high impact

The page transfers 5.89 MB across 26 request(s), with the document itself at 81.8 KB.

Fix: Work through the heaviest assets first: images, then fonts, then third-party scripts.

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.

Third-party weight

low impact

5 third-party host(s) serve 193.7 KB of this page. Each one is another DNS lookup, TLS handshake and point of failure you do not control.

Fix: Self-host the libraries you can, drop the tags you cannot justify, and preconnect the ones you keep.