www.expediapartnercentral.com/Account/Logon?returnUrl=https%3A%2F%2Fwww.expediapartnercentral.com%2F speed test — 20 Oct 2026

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

https://www.expediapartnercentral.com/Account/Logon?returnUrl=https%3A%2F%2Fwww.expediapartnercentral.com%2F

20 October 2026 at 15:04 UTC · Free test · report pt_648b3bef003c

Re-test this page Test your own site

Grade

88/100

Performance94/100

Structure80/100

12 audit(s) passed, 4 need work

First byte (TTFB)424 msmeasured from this server

Fully loaded1.09 sfirst byte + slowest asset

Requests12document + assets

Page weight333.1 KBcompressed transfer

HTML document13.7 KBgzip

ProtocolHTTP/3istio-envoy

Third-party237.4 KBother hosts

Where the first byte went

DNS lookup 80 ms 19%
TCP connect 27 ms 6%
Server wait 317 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 53% of 4,999 pages tested here424 ms against a median of 449 ms

Page weightlighter than 70% of 4,999 pages tested here333.1 KB against a median of 650.5 KB

Fully loadedfaster than 90% of 4,999 pages tested here1.09 s against a median of 1.84 s

Requestssends fewer requests than 86% of 4,999 pages tested here12 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 424 ms. That is workable, and the cheapest win left is caching or a warmer connection.
The page transfers 333.1 KB over 12 request(s), which is lean. Javascript files are 71% 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/3, so the assets share a connection instead of opening one each.
71% 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 576 ms, inside the 2.5 s Google calls good.
The main thread was blocked for 446 ms, so taps and scrolling wait while scripts run.

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.

Mobile screenshot of www.expediapartnercentral.com — **Mobile** 390 × 844 · 52.2 KB · page is 1820 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 paint576 msgood is under 2.5 s

Cumulative layout shift0.000under 0.1 is stable

Total blocking time446 mslong tasks during load

First contentful paint576 msfirst content on screen

Browser page weight1.04 MB47 request(s), scripts included

Failed requests4blocked or unreachable

Largest contentful paint576 ms

Goodgood under 2.5 s, poor over 4 s

Cumulative layout shift0.000

Goodgood under 0.1, poor over 0.25

Total blocking time446 ms

Needs improvementgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Javascript 5 requests

237.4 KB 71%

Html 6 requests

82.0 KB 25%

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

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 424 ms. Of that, 317 ms was the server thinking and 107 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.

Compress text responses

high impact

6 text response(s) of 10 KB or more are sent uncompressed, and the document itself is not compressed. That is 82.0 KB of compressible text.

Fix: Turn on brotli (preferred) or gzip for text/css, javascript and text/html in the web server. This is the cheapest win available on almost any site.

Cache static assets

medium impact

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

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.