www.answers.com speed test — 20 Oct 2026
Measured from the wfix.shop server on 20 October 2026 at 14:05 UTC. Grade C (72/100), with the screenshots, the timings and the fixes that matter.
Where the first byte went
- DNS lookup 76 ms 5%
- TCP connect 32 ms 2%
- Server wait 1.30 s 92%
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 took 1.41 s. Everything else waits for that number, so the server is where to start: caching, a slow query, or an overloaded host.
- The page transfers 659.3 KB over 26 request(s). Images files are 50% 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.
- 48% 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 1.65 s, inside the 2.5 s Google calls good.
- The main thread was blocked for 44 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.
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. 26 request(s) in total, 659.3 KB across all of them.
Top issues
Server response time (TTFB)
high impactThe first byte arrived after 1406 ms. Of that, 1298 ms was the server thinking and 108 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.
Third-party weight
medium impact2 third-party host(s) serve 315.8 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.
Avoid extra redirects
medium impact1 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.
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://imgservice.answers.com/bots/5/answer-bot.jpg?1933198428&filter=icon 3rd party | images | 200 | 1.26 s | 5.4 KB |
| https://imgservice.answers.com/bots/10/taiga-anime-protagonist.png?1933198428&filter=icon 3rd party | images | 200 | 1.19 s | 51.2 KB |
| https://imgservice.answers.com/bots/13/devin-bartender.png?1933198428&filter=icon 3rd party | images | 200 | 1.04 s | 45.8 KB |
| https://www.answers.com/js/359.1fe0b3f2320dbd293097.js | javascript | 200 | 1.04 s | 10.4 KB |
| https://www.answers.com/images/logos/answers-logo-white-updated.svg | images | 200 | 1.02 s | 5.1 KB |
| https://www.answers.com/js/vendor.2e75eb812a056581b83b.js | javascript | 200 | 1.01 s | 170.8 KB |
| https://imgservice.answers.com/bots/16/rene-devils-advocate.png?1933198428&filter=icon 3rd party | images | 200 | 1.00 s | 47.2 KB |
| https://imgservice.answers.com/bots/8/fran-grandma.png?1933198428&filter=icon 3rd party | images | 200 | 997 ms | 51.3 KB |
| https://imgservice.answers.com/bots/17/dio-wildcard.png?1933198428&filter=icon 3rd party | images | 200 | 993 ms | 51.5 KB |
| https://imgservice.answers.com/bots/2/dude-bot.jpg?1933198428&filter=icon 3rd party | images | 200 | 986 ms | 4.9 KB |
| https://www.answers.com/js/react.cec56ed0399ca770acfc.js | javascript | 200 | 985 ms | 41.4 KB |
| https://www.answers.com/js/manifest.ae22b25275b488fc5c4f.js | javascript | 200 | 982 ms | 2.9 KB |
| https://st.answers.com/logos/logo-answers-white.png 3rd party | images | 200 | 981 ms | 2.1 KB |
| https://www.answers.com/js/ads.js | javascript | 200 | 981 ms | 146 B |
| https://www.answers.com/images/avatars/default.png | images | 200 | 980 ms | 4.9 KB |
| https://www.answers.com/js/8380.7923fe6a5526f0bf30f9.js | javascript | 200 | 980 ms | 3.2 KB |
| https://imgservice.answers.com/bots/4/betty-bot.jpg?1933198428&filter=icon 3rd party | images | 200 | 974 ms | 4.6 KB |
| https://www.answers.com/icons/coinIcon.svg | images | 200 | 968 ms | 2.1 KB |
| https://www.answers.com/icons/notificationBellIcon.svg | images | 200 | 967 ms | 204 B |
| https://www.answers.com/icons/hamburgerMenuIcon.svg | images | 200 | 963 ms | 181 B |
| https://www.answers.com/js/1916.d982dae4543fa934fef0.js | javascript | 200 | 956 ms | 3.0 KB |
| https://imgservice.answers.com/bots/12/ezra-religious-leader.png?1933198428&filter=icon 3rd party | images | 200 | 950 ms | 51.9 KB |
| https://www.answers.com/icons/searchGlassWhiteIcon.svg | images | 200 | 924 ms | 240 B |
| https://www.answers.com/js/979.5ade9879183777988091.js | javascript | 200 | 919 ms | 4.5 KB |
| https://www.answers.com/js/571.41b134ccff41cd42ad5e.js | javascript | 200 | 917 ms | 21.0 KB |
Report this page
Run this test on your own site
The same engine, free, with the screenshots and the fixes. No account needed.