iam.iponweb.net/auth/realms/iponweb/protocol/openid-connect/auth?approval_prompt=force&client_id=jira.iponweb.net&redirect_uri=https%3A%2F%2Fjira.iponweb.net%2Foauth2%2Fcallback&response_type=code&scope=openid+email+profile&state=cdFVROP45hr49DfZOqgvsw4bWeRgkuLchqF9Fd1-JaE%3A%2F speed test — 20 Oct 2026

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

https://iam.iponweb.net/auth/realms/iponweb/protocol/openid-connect/auth?approval_prompt=force&client_id=jira.iponweb.net&redirect_uri=https%3A%2F%2Fjira.iponweb.net%2Foauth2%2Fcallback&response_type=code&scope=openid+email+profile&state=cdFVROP45hr49DfZOqgvsw4bWeRgkuLchqF9Fd1-JaE%3A%2F

20 October 2026 at 13:04 UTC · Free test · report pt_edf11820b6a8

Re-test this page Test your own site

Grade

87/100

Performance91/100

Structure80/100

12 audit(s) passed, 4 need work

First byte (TTFB)533 msmeasured from this server

Fully loaded1.54 sfirst byte + slowest asset

Requests18document + assets

Page weight79.2 KBcompressed transfer

HTML document4.4 KBno compression

ProtocolHTTP/3server not sent

Where the first byte went

DNS lookup 126 ms 24%
TCP connect 31 ms 6%
Server wait 376 ms 71%

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 byteslower than 58% of 4,999 pages tested here533 ms against a median of 448 ms

Page weightlighter than 89% of 4,999 pages tested here79.2 KB against a median of 650.5 KB

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

Requestssends fewer requests than 81% of 4,999 pages tested here18 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 took 533 ms. Everything else waits for that number, so the server is where to start: caching, a slow query, or an overloaded host.
The page transfers 79.2 KB over 18 request(s). Html files are 94% of it, so that one type is worth a look on its own.
It runs over HTTP/3, so the assets share a connection instead of opening one each.
The largest element painted at 1.51 s, inside the 2.5 s Google calls good.
The main thread was blocked for 5 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.

Mobile screenshot of iam.iponweb.net — **Mobile** 390 × 844 · 9.9 KB · page is 888 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 paint1.51 sgood is under 2.5 s

Cumulative layout shift0.000under 0.1 is stable

Total blocking time5 mslong tasks during load

First contentful paint1.51 sfirst content on screen

Browser page weight275.7 KB21 request(s), scripts included

Failed requests2blocked or unreachable

Largest contentful paint1.51 s

Goodgood under 2.5 s, poor over 4 s

Cumulative layout shift0.000

Goodgood under 0.1, poor over 0.25

Total blocking time5 ms

Goodgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Html 17 requests

74.8 KB 94%

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

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 533 ms. Of that, 376 ms was the server thinking and 157 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.

Render-blocking resources

high impact

15 render-blocking resource(s) in the document head (1 script(s), 14 stylesheet(s)). The page cannot paint until each one arrives.

Fix: Add defer or async to scripts that do not change the first paint, inline the critical CSS, and load the rest with media="print" plus an onload swap.

TLS certificate validity

high impact

The certificate for iam.iponweb.net has 1 day(s) left.

Fix: Renew automatically (certbot with a working renewal timer) and alert on the certificate, not on the renew command, so a silent failure is caught weeks before a browser warning.

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.