www.globenewswire.com speed test — 20 Oct 2026

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

https://www.globenewswire.com:443/

20 October 2026 at 13:02 UTC · Free test · report pt_7fccba1d81eb

Re-test this page Test your own site

Grade

72/100

Performance70/100

Structure74/100

11 audit(s) passed, 5 need work

First byte (TTFB)372 msmeasured from this server

Fully loaded1.70 sfirst byte + slowest asset

Requests26document + assets

Page weight52.96 MBcompressed transfer

HTML document15.3 KBgzip

ProtocolHTTP/3server not sent

Third-party52.49 MBother hosts

Where the first byte went

DNS lookup 79 ms 21%
TCP connect 51 ms 14%
Server wait 242 ms 65%

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

Page weightheavier than 100% of 4,999 pages tested here52.96 MB against a median of 650.3 KB

Fully loadedfaster than 58% of 4,999 pages tested here1.70 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 372 ms. That is workable, and the cheapest win left is caching or a warmer connection.
The page transfers 52.96 MB over 26 request(s). Media files are 99% of it, so let video load on demand instead of on first paint.
The HTML itself arrives gzip-compressed.
It runs over HTTP/3, so the assets share a connection instead of opening one each.
99% of the weight comes from other hosts (analytics, fonts, embeds), which also means their slow day becomes your slow day.

Fix first: Render-blocking resources - 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.

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.

No screenshot for this report.

The headless browser did not capture this page when the test ran, so only the server measurements are shown.

Page weight by type

What the page is made of

Media 1 request

52.32 MB 99%

Javascript 5 requests

422.4 KB 1%

Images 14 requests

162.6 KB 0%

Css 3 requests

47.3 KB 0%

Html 2 requests

184 B 0%

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

Top issues

Render-blocking resources

high impact

7 render-blocking resource(s) in the document head (2 script(s), 5 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.

Total page weight

high impact

The page transfers 52.96 MB across 26 request(s), with the document itself at 15.3 KB.

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

Third-party weight

medium impact

4 third-party host(s) serve 52.49 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.

JavaScript weight

medium impact

1 JavaScript file(s) over 200 KB: react-scripts (367.9 KB)

Fix: Split routes, remove unused dependencies, and prefer a two-file build (one pinned library, one application bundle) over many small ones.

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.