www.philips-hue.com/en-us speed test — 20 Oct 2026

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

https://www.philips-hue.com/en-us

20 October 2026 at 12:39 UTC · Free test · report pt_4a34a5066803

Re-test this page Test your own site

Grade

93/100

Performance90/100

Structure97/100

15 audit(s) passed, 1 need work

First byte (TTFB)356 msmeasured from this server

Fully loaded2.89 sfirst byte + slowest asset

Requests26document + assets

Page weight46.0 KBcompressed transfer

HTML document43.7 KBgzip

ProtocolHTTP/3Apache

Where the first byte went

DNS lookup 71 ms 20%
TCP connect 19 ms 5%
Server wait 266 ms 75%

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 64% of 4,999 pages tested here356 ms against a median of 449 ms

Page weightlighter than 91% of 4,999 pages tested here46.0 KB against a median of 650.5 KB

Fully loadedslower than 81% of 4,999 pages tested here2.89 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 356 ms. That is workable, and the cheapest win left is caching or a warmer connection.
The page transfers 46.0 KB over 26 request(s).
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 painted at 624 ms, inside the 2.5 s Google calls good.
Layout stayed still (CLS 0.016), so nothing jumps under the reader's cursor.
The main thread was blocked for 151 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.philips-hue.com — **Mobile** 390 × 844 · 48.3 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 paint624 msgood is under 2.5 s

Cumulative layout shift0.016under 0.1 is stable

Total blocking time151 mslong tasks during load

First contentful paint316 msfirst content on screen

Browser page weight2.72 MB123 request(s), scripts included

Largest contentful paint624 ms

Goodgood under 2.5 s, poor over 4 s

Cumulative layout shift0.016

Goodgood under 0.1, poor over 0.25

Total blocking time151 ms

Goodgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Images 1 request

2.3 KB 5%

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

Top issues

Avoid extra redirects

medium impact

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