www.ehow.com speed test — 20 Oct 2026

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

https://www.ehow.com/

20 October 2026 at 15:46 UTC · Free test · report pt_7012de8a4fad
Grade
C
73/100
Performance76/100
Structure68/100

10 audit(s) passed, 6 need work

First byte (TTFB)379 msmeasured from this server
Fully loaded1.88 sfirst byte + slowest asset
Requests26document + assets
Page weight3.05 MBcompressed transfer
HTML document62.7 KBbr
ProtocolHTTP/3cloudflare
Third-party2.99 MBother hosts

Where the first byte went

  • DNS lookup 90 ms 24%
  • TCP connect 70 ms 18%
  • Server wait 219 ms 58%

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 60% of 4,999 pages tested here379 ms against a median of 449 ms
Page weightheavier than 88% of 4,999 pages tested here3.05 MB against a median of 650.3 KB
Fully loadedslower than 52% of 4,999 pages tested here1.88 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 379 ms. That is workable, and the cheapest win left is caching or a warmer connection.
  • The page transfers 3.05 MB over 26 request(s). Images files are 98% 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.
  • 98% 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 772 ms, inside the 2.5 s Google calls good.
  • Layout stayed still (CLS 0.032), so nothing jumps under the reader's cursor.
  • The main thread was blocked for 581 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.

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 paint772 msgood is under 2.5 s
Cumulative layout shift0.032under 0.1 is stable
Total blocking time581 mslong tasks during load
First contentful paint772 msfirst content on screen
Browser page weight7.99 MB1231 request(s), scripts included
Failed requests25blocked or unreachable
Largest contentful paint772 ms
Goodgood under 2.5 s, poor over 4 s
Cumulative layout shift0.032
Goodgood under 0.1, poor over 0.25
Total blocking time581 ms
Needs improvementgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Images 25 requests
2.99 MB 98%

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

Top issues

Image delivery and format

high impact

1 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 3.05 MB across 26 request(s), with the document itself at 62.7 KB.

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

Cache static assets

medium impact

19 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.

Third-party weight

medium impact

2 third-party host(s) serve 2.99 MB 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 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.

Waterfall

Slowest requests

IMAGESassets.ehow.com/375/ehowta/1/7/5a7e13d6b49e46f0a99b289…
1.50 s
IMAGESassets.ehow.com/375/ehowta/2/15/5c6569b4ea5043dba5955c…
1.47 s
IMAGEScdn.technologyadvice.io/articles/16365/cover.webp
1.33 s
IMAGEScdn.technologyadvice.io/articles/16619/cover.webp
1.33 s
IMAGEScdn.technologyadvice.io/articles/15558/cover.webp
1.33 s
IMAGEScdn.technologyadvice.io/articles/16544/cover.webp
1.32 s
IMAGEScdn.technologyadvice.io/articles/15443/cover.webp
1.32 s
IMAGEScdn.technologyadvice.io/articles/16099/cover.webp
1.32 s
IMAGEScdn.technologyadvice.io/articles/15889/cover.webp
1.32 s
IMAGEScdn.technologyadvice.io/articles/16693/cover.webp
1.31 s

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://assets.ehow.com/375/ehowta/1/7/5a7e13d6b49e46f0a99b2899be1ccb18.jpg 3rd partyimages2001.50 s40.1 KB
https://assets.ehow.com/375/ehowta/2/15/5c6569b4ea5043dba5955cf212e83a0c.jpg 3rd partyimages2001.47 s31.9 KB
https://cdn.technologyadvice.io/articles/16365/cover.webp 3rd partyimages2001.33 s119.1 KB
https://cdn.technologyadvice.io/articles/16619/cover.webp 3rd partyimages2001.33 s154.7 KB
https://cdn.technologyadvice.io/articles/15558/cover.webp 3rd partyimages2001.33 s174.2 KB
https://cdn.technologyadvice.io/articles/16544/cover.webp 3rd partyimages2001.32 s89.4 KB
https://cdn.technologyadvice.io/articles/15443/cover.webp 3rd partyimages2001.32 s198.0 KB
https://cdn.technologyadvice.io/articles/16099/cover.webp 3rd partyimages2001.32 s191.2 KB
https://cdn.technologyadvice.io/articles/15889/cover.webp 3rd partyimages2001.32 s150.5 KB
https://cdn.technologyadvice.io/articles/16693/cover.webp 3rd partyimages2001.31 s123.4 KB
https://cdn.technologyadvice.io/articles/16631/cover.webp 3rd partyimages2001.30 s152.7 KB
https://cdn.technologyadvice.io/articles/15932/cover.webp 3rd partyimages2001.28 s166.5 KB
https://cdn.technologyadvice.io/articles/16125/cover.webp 3rd partyimages2001.28 s110.2 KB
https://cdn.technologyadvice.io/articles/15409/cover.webp 3rd partyimages2001.28 s133.1 KB
https://cdn.technologyadvice.io/articles/15956/cover.webp 3rd partyimages2001.28 s100.9 KB
https://cdn.technologyadvice.io/articles/15454/cover.webp 3rd partyimages2001.28 s194.4 KB
https://cdn.technologyadvice.io/articles/15374/cover.webp 3rd partyimages2001.27 s112.8 KB
https://cdn.technologyadvice.io/articles/16113/cover.webp 3rd partyimages2001.26 s82.6 KB
https://cdn.technologyadvice.io/articles/16217/cover.webp 3rd partyimages2001.24 s194.9 KB
https://cdn.technologyadvice.io/articles/16224/cover.webp 3rd partyimages2001.23 s172.3 KB
https://assets.ehow.com/375/ehowta/2/26/53374eec78d04ed4b4358281e3f69bbf.jpg 3rd partyimages2001.23 s14.8 KB
https://cdn.technologyadvice.io/articles/16226/cover.webp 3rd partyimages2001.22 s110.8 KB
https://assets.ehow.com/375/ehowta/3/7/13b5b23562754ae1850842ab7cebac6d.jpg 3rd partyimages2001.19 s34.0 KB
https://assets.ehow.com/867x648/ehowta/3/2/c70001eb15c84a6f97f40eefdbd36e08.png 3rd partyimages2001.14 s56.9 KB
https://assets.ehow.com/1440/ehowta/heroes/6a7eb88a-f162-451e-aba1-7a304dfe6888-5fae2ed04bd647a1ba04c304823dcc3f.jpg.webp 3rd partyimages2001.13 s153.4 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.