www.opentext.com/products/threat-intelligence speed test — 20 Oct 2026

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

https://www.opentext.com/products/threat-intelligence

20 October 2026 at 13:36 UTC · Free test · report pt_ee43bb9abbf6

Re-test this page Test your own site

Grade

78/100

Performance72/100

Structure86/100

13 audit(s) passed, 3 need work

First byte (TTFB)114 msmeasured from this server

Fully loaded2.17 sfirst byte + slowest asset

Requests25document + assets

Page weight4.59 MBcompressed transfer

HTML document39.1 KBbr

ProtocolHTTP/3server not sent

Third-party188.6 KBother hosts

Where the first byte went

DNS lookup 58 ms 51%
TCP connect 2 ms 2%
Server wait 54 ms 47%

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

Page weightheavier than 93% of 4,999 pages tested here4.59 MB against a median of 650.3 KB

Fully loadedslower than 63% of 4,999 pages tested here2.17 s against a median of 1.84 s

Requestssends fewer requests than 74% of 4,999 pages tested here25 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 114 ms, which is fast: almost all of the wait is the page itself, not the host.
The page transfers 4.59 MB over 25 request(s). Html files are 94% of it, so that one type is worth a look on its own.
The HTML itself arrives br-compressed.
It runs over HTTP/3, so the assets share a connection instead of opening one each.
The largest element painted at 752 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 102 ms in total, which is not enough to feel.

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.

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.opentext.com — **Mobile** 390 × 844 · 84.2 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 paint752 msgood is under 2.5 s

Cumulative layout shift0.001under 0.1 is stable

Total blocking time102 mslong tasks during load

First contentful paint592 msfirst content on screen

Browser page weight1.33 MB45 request(s), scripts included

Failed requests2blocked or unreachable

Largest contentful paint752 ms

Goodgood under 2.5 s, poor over 4 s

Cumulative layout shift0.001

Goodgood under 0.1, poor over 0.25

Total blocking time102 ms

Goodgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Html 13 requests

4.33 MB 94%

Javascript 4 requests

118.0 KB 3%

Css 1 request

70.6 KB 2%

Images 6 requests

41.9 KB 1%

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

Top issues

Render-blocking resources

high impact

3 render-blocking resource(s) in the document head (1 script(s), 2 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 4.59 MB across 25 request(s), with the document itself at 39.1 KB.

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

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.