www.familysearch.org/en/united-states speed test — 20 Oct 2026
Measured from the wfix.shop server on 20 October 2026 at 13:46 UTC. Grade B (85/100), with the screenshots, the timings and the fixes that matter.
Where the first byte went
- DNS lookup 73 ms 20%
- TCP connect 29 ms 8%
- Server wait 266 ms 72%
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
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 368 ms. That is workable, and the cheapest win left is caching or a warmer connection.
- The page transfers 946.1 KB over 15 request(s), which is lean. Javascript files are 95% of it, so defer what is not needed for the first screen, and drop tags nobody uses.
- The HTML itself arrives gzip-compressed.
- It runs over HTTP/2, so the assets share a connection instead of opening one each.
- 99% of the weight comes from other hosts (analytics, fonts, embeds), which also means their slow day becomes your slow day.
- The largest element painted at 2.10 s, inside the 2.5 s Google calls good.
- Layout shift is 0.168 (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 490 ms, so taps and scrolling wait while scripts run.
Fix first: Render-blocking resources - 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.
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.
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.
Page weight by type
What the page is made of
Transfer size, compressed as sent. 15 request(s) in total, 946.1 KB across all of them.
Top issues
Render-blocking resources
high impact6 render-blocking resource(s) in the document head (1 script(s), 5 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.
Serve everything over HTTPS
high impact1 asset(s) are still requested over plain HTTP.
Fix: Redirect HTTP to HTTPS at the server, and rewrite the remaining http:// asset references so nothing depends on browser upgrading.
Total page weight
medium impactThe page transfers 946.1 KB across 15 request(s), with the document itself at 6.5 KB.
Fix: Work through the heaviest assets first: images, then fonts, then third-party scripts.
Third-party weight
medium impact4 third-party host(s) serve 939.5 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.
JavaScript weight
medium impact1 JavaScript file(s) over 200 KB: 38392.96f2d3e4175ef284.js (646.4 KB)
Fix: Split routes, remove unused dependencies, and prefer a two-file build (one pinned library, one application bundle) over many small ones.
Waterfall
Slowest requests
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
| Request | Type | Status | Time | Size |
|---|---|---|---|---|
| https://www.familysearch.org/en/united-states/Hemlock-Night-Gosper-this-go-this-Famids-not-of- | other | 302 | 680 ms | 89 B |
| https://js-cdn.dynatrace.com/jstag/15c157a40ab/bf99293tkn/a8e5edd77f861ace_complete.js 3rd party | javascript | 200 | 566 ms | 114.2 KB |
| https://edge.fscdn.org/assets/docs/fs_logo_favicon_sq.png 3rd party | images | 200 | 545 ms | 409 B |
| https://foundry.familysearch.org/Foundry/v1/HeritageBody:Sans:Italic:400@en-Latn/css 3rd party | css | 200 | 532 ms | 972 B |
| https://foundry.familysearch.org/Foundry/v1/HeritageBody:Sans:Normal:400@en-Latn/css 3rd party | css | 200 | 529 ms | 986 B |
| https://edge.fscdn.org/assets/components/hf/assets/img/tree-touch-icon-11024a277f1fda5735de5a9f0f4f75ca.png 3rd party | images | 200 | 525 ms | 900 B |
| https://edge.fscdn.org/assets/static/js/38392.96f2d3e4175ef284.js 3rd party | javascript | 200 | 522 ms | 646.4 KB |
| http://modernizr.com/ 3rd party | other | 301 | 522 ms | 0 B |
| https://edge.fscdn.org/assets/static/js/main.465b5f365be1e7d8.js 3rd party | javascript | 200 | 512 ms | 101.2 KB |
| https://foundry.familysearch.org/Foundry/v1/HeritageBody:Sans:Italic:700@en-Latn/css 3rd party | css | 200 | 511 ms | 970 B |
| https://foundry.familysearch.org/Foundry/v1/HeritageBody:Sans:Normal:700@en-Latn/css 3rd party | css | 200 | 509 ms | 986 B |
| https://foundry.familysearch.org/Foundry/v1/HeritageHeadings:Sans:Normal:500@en-Latn/css 3rd party | css | 200 | 507 ms | 1.0 KB |
| https://edge.fscdn.org/assets/static/js/commonVendor.537473caf5d51d81.js 3rd party | javascript | 200 | 500 ms | 40.6 KB |
| https://edge.fscdn.org/assets/static/css/38392.36ca0c90cb40afcc.css 3rd party | css | 200 | 487 ms | 30.9 KB |
Report this page
Run this test on your own site
The same engine, free, with the screenshots and the fixes. No account needed.