openssl.org speed test — 20 Oct 2026

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

https://openssl.org/

20 October 2026 at 13:07 UTC · Free test · report pt_33b87a19b09a
Grade
A
90/100
Performance96/100
Structure82/100

13 audit(s) passed, 3 need work

First byte (TTFB)365 msmeasured from this server
Fully loaded1.06 sfirst byte + slowest asset
Requests9document + assets
Page weight400.3 KBcompressed transfer
HTML document6.9 KBno compression
ProtocolHTTP/3UploadServer
Third-party4.2 KBother hosts

Where the first byte went

  • DNS lookup 66 ms 18%
  • TCP connect 66 ms 18%
  • Server wait 233 ms 64%

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 62% of 4,999 pages tested here365 ms against a median of 449 ms
Page weightlighter than 65% of 4,999 pages tested here400.3 KB against a median of 650.5 KB
Fully loadedfaster than 91% of 4,999 pages tested here1.06 s against a median of 1.84 s
Requestssends fewer requests than 89% of 4,999 pages tested here9 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 365 ms. That is workable, and the cheapest win left is caching or a warmer connection.
  • The page transfers 400.3 KB over 9 request(s), which is lean. Images files are 58% of it, so resize and recompress the largest images before anything else.
  • It runs over HTTP/3, so the assets share a connection instead of opening one each.
  • The largest element painted at 1.16 s, inside the 2.5 s Google calls good.
  • Layout stayed still (CLS 0.003), so nothing jumps under the reader's cursor.

Fix first: Compress text responses - 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.

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 openssl.org
Mobile 390 × 844 · 42.6 KB · page is 2695 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.16 sgood is under 2.5 s
Cumulative layout shift0.003under 0.1 is stable
Total blocking timenone over 50 mslong tasks during load
First contentful paint752 msfirst content on screen
Browser page weight898.1 KB14 request(s), scripts included
Largest contentful paint1.16 s
Goodgood under 2.5 s, poor over 4 s
Cumulative layout shift0.003
Goodgood under 0.1, poor over 0.25
Total blocking timenone over 50 ms
Goodgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Images 3 requests
234.1 KB 58%
Css 4 requests
155.2 KB 39%
Javascript 1 request
4.2 KB 1%

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

Top issues

Compress text responses

high impact

3 text response(s) of 10 KB or more are sent uncompressed, and the document itself is not compressed. That is 154.5 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.

Render-blocking resources

high impact

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

Image delivery and format

medium impact

0 image(s) over 200 KB and 1 large image(s) still served as JPEG or PNG.

Fix: Serve WebP or AVIF with a JPEG fallback, size images to the space they occupy, and lazy-load anything below the fold. Images are usually more than half of a slow page.

Waterfall

Slowest requests

JAVASCRIPTapi.transpond.io/tracker
699 ms
CSSopenssl.org/css/main.abe249895d3af7f37653d265973a5…
538 ms
IMAGESopenssl.org/images/openssl_logo_library_393_265.png
494 ms
IMAGESopenssl.org/images/bouncy_castle.png
472 ms
CSSopenssl.org/css/fontawesome.min.80a5cf80e4ba6d1ff1…
458 ms
CSSopenssl.org/css/brands.9c662012d93fb448c96f67697bb…
458 ms
CSSopenssl.org/css/solid.40e9c76835b2f8346bf5a2dda24f…
456 ms
IMAGESopenssl.org/images/cryptlib_logo_393_265.png
448 ms

Each bar is one request's own response time, scaled to the slowest. Assets were fetched in parallel, so the bars overlap in real time rather than stacking. first party third party

RequestTypeStatusTimeSize
https://api.transpond.io/tracker?am=MzgyOTE%253D 3rd partyjavascript200699 ms4.2 KB
https://openssl.org/css/main.abe249895d3af7f37653d265973a575e7fbd4ad64b517d07ffdc2b164fe3f42d.csscss200538 ms44.7 KB
https://openssl.org/images/openssl_logo_library_393_265.pngimages200494 ms12.0 KB
https://openssl.org/images/bouncy_castle.pngimages200472 ms161.2 KB
https://openssl.org/css/fontawesome.min.80a5cf80e4ba6d1ff172b4995ad5ce996071022227860700308ed797fbd150ad.csscss200458 ms85.5 KB
https://openssl.org/css/brands.9c662012d93fb448c96f67697bbee60ae06d6552398ca9487dcc79df4a032eb3.csscss200458 ms24.4 KB
https://openssl.org/css/solid.40e9c76835b2f8346bf5a2dda24f8a0ec0624a4a2232ad15dad086f44a672772.csscss200456 ms633 B
https://openssl.org/images/cryptlib_logo_393_265.pngimages200448 ms60.9 KB
Report this page

The page is removed when the owner agrees. Sending this removes nothing by itself.

Run this test on your own site

The same engine, free, with the screenshots and the fixes. No account needed.