portfolio.adobe.com speed test — 20 Oct 2026

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

https://portfolio.adobe.com/

20 October 2026 at 14:16 UTC · Free test · report pt_3d1306b7f5e8
Grade
A
92/100
Performance96/100
Structure85/100

13 audit(s) passed, 3 need work

First byte (TTFB)364 msmeasured from this server
Fully loaded810 msfirst byte + slowest asset
Requests4document + assets
Page weight388.6 KBcompressed transfer
HTML document20.2 KBno compression
ProtocolHTTP/3adobe
Third-party66.8 KBother hosts

Where the first byte went

  • DNS lookup 75 ms 21%
  • TCP connect 44 ms 12%
  • Server wait 245 ms 67%

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 here364 ms against a median of 449 ms
Page weightlighter than 66% of 4,999 pages tested here388.6 KB against a median of 650.5 KB
Fully loadedfaster than 95% of 4,999 pages tested here810 ms against a median of 1.84 s
Requestssends fewer requests than 94% of 4,999 pages tested here4 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 364 ms. That is workable, and the cheapest win left is caching or a warmer connection.
  • The page transfers 388.6 KB over 4 request(s), which is lean. Images files are 77% 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.92 s, inside the 2.5 s Google calls good.
  • The main thread was blocked for 3 ms in total, which is not enough to feel.

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 portfolio.adobe.com
Mobile 390 × 844 · 99.0 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 paint1.92 sgood is under 2.5 s
Cumulative layout shift0.000under 0.1 is stable
Total blocking time3 mslong tasks during load
First contentful paint1.51 sfirst content on screen
Browser page weight1.06 MB35 request(s), scripts included
Failed requests2blocked or unreachable
Largest contentful paint1.92 s
Goodgood under 2.5 s, poor over 4 s
Cumulative layout shift0.000
Goodgood under 0.1, poor over 0.25
Total blocking time3 ms
Goodgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Images 1 request
297.7 KB 77%
Javascript 2 requests
70.7 KB 18%

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

Top issues

Compress text responses

high impact

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

Image delivery and format

high impact

1 image(s) over 200 KB and 0 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.

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.

Waterfall

Slowest requests

IMAGESportfolio.adobe.com/favicon.ico
446 ms
JAVASCRIPTportfolio.adobe.com/constants.js
411 ms
JAVASCRIPTpro2-ui-assets-s3-fy.myportfolio.com/d709bcd/app.js
327 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://portfolio.adobe.com/favicon.ico?cb=e1252d4f111d4e339e89images200446 ms297.7 KB
https://portfolio.adobe.com/constants.js?cb=e1252d4f111d4e339e89javascript200411 ms3.9 KB
https://pro2-ui-assets-s3-fy.myportfolio.com/d709bcd/app.js?cb=e1252d4f111d4e339e89 3rd partyjavascript200327 ms66.8 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.