www.jnj.com speed test — 20 Oct 2026

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

https://www.jnj.com/

20 October 2026 at 15:00 UTC · Free test · report pt_9e50da50de2f
Grade
A
97/100
Performance100/100
Structure92/100

13 audit(s) passed, 3 need work

First byte (TTFB)198 msmeasured from this server
Fully loaded198 msfirst byte + slowest asset
Requests1document + assets
Page weight557 Bcompressed transfer
HTML document557 Bno compression
ProtocolHTTP/2AkamaiGHost

Where the first byte went

  • DNS lookup 71 ms 36%
  • TCP connect 20 ms 10%
  • Server wait 107 ms 54%

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 93% of 4,999 pages tested here198 ms against a median of 449 ms
Page weightlighter than 98% of 4,999 pages tested here557 B against a median of 650.5 KB
Fully loadedfaster than 100% of 4,999 pages tested here198 ms against a median of 1.84 s
Requestssends fewer requests than 98% of 4,999 pages tested here1 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 server answered in 198 ms, which is fast: almost all of the wait is the page itself, not the host.
  • The page transfers 557 B over 1 request(s), which is lean.
  • It runs over HTTP/2, so the assets share a connection instead of opening one each.
  • The largest element painted at 756 ms, inside the 2.5 s Google calls good.
  • Layout stayed still (CLS 0.001), so nothing jumps under the reader's cursor.
  • The main thread was blocked for 78 ms in total, which is not enough to feel.

Fix first: Avoid extra redirects - 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.

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.jnj.com
Mobile 390 × 844 · 108.7 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 paint756 msgood is under 2.5 s
Cumulative layout shift0.001under 0.1 is stable
Total blocking time78 mslong tasks during load
First contentful paint756 msfirst content on screen
Browser page weight2.36 MB64 request(s), scripts included
Largest contentful paint756 ms
Goodgood under 2.5 s, poor over 4 s
Cumulative layout shift0.001
Goodgood under 0.1, poor over 0.25
Total blocking time78 ms
Goodgood under 200 ms, poor over 600 ms

Top issues

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.

Mobile viewport

medium impact

No viewport meta tag, so a phone renders the desktop layout scaled down.

Fix: Add a viewport meta tag with width=device-width and an initial scale of 1.

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.

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.