www.gimp.org speed test — 20 Oct 2026

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

https://www.gimp.org/

20 October 2026 at 13:38 UTC · Free test · report pt_7e038d1aa658
Grade
A
98/100
Performance100/100
Structure94/100

14 audit(s) passed, 2 need work

First byte (TTFB)149 msmeasured from this server
Fully loaded1.35 sfirst byte + slowest asset
Requests15document + assets
Page weight114.3 KBcompressed transfer
HTML document4.5 KBgzip
ProtocolHTTP/3Apache/2.4.62 (Red Hat Enterprise Linux) OpenSSL/3.5.8

Where the first byte went

  • DNS lookup 49 ms 33%
  • TCP connect 19 ms 13%
  • Server wait 82 ms 55%

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 98% of 4,999 pages tested here149 ms against a median of 449 ms
Page weightlighter than 86% of 4,999 pages tested here114.3 KB against a median of 650.5 KB
Fully loadedfaster than 80% of 4,999 pages tested here1.35 s against a median of 1.84 s
Requestssends fewer requests than 83% of 4,999 pages tested here15 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 149 ms, which is fast: almost all of the wait is the page itself, not the host.
  • The page transfers 114.3 KB over 15 request(s), which is lean. Images files are 83% of it, so resize and recompress the largest images before anything else.
  • The HTML itself arrives gzip-compressed.
  • It runs over HTTP/3, so the assets share a connection instead of opening one each.
  • The largest element painted at 416 ms, inside the 2.5 s Google calls good.
  • Layout shift is 0.221 (good is under 0.1): something without a reserved size is loading late - an image, an ad, or a font swap.
  • The main thread was blocked for 13 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.

Desktop screenshot of www.gimp.org
Desktop 1366 × 768 · 636.6 KB · page is 4160 px tall
Mobile screenshot of www.gimp.org
Mobile 390 × 844 · 211.6 KB · page is 5875 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 paint416 msgood is under 2.5 s
Cumulative layout shift0.221under 0.1 is stable
Total blocking time13 mslong tasks during load
First contentful paint344 msfirst content on screen
Browser page weight1.16 MB29 request(s), scripts included
Largest contentful paint416 ms
Goodgood under 2.5 s, poor over 4 s
Cumulative layout shift0.221
Needs improvementgood under 0.1, poor over 0.25
Total blocking time13 ms
Goodgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Images 6 requests
94.4 KB 83%
Css 6 requests
13.3 KB 12%
Javascript 2 requests
2.1 KB 2%

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

Top issues

Render-blocking resources

high impact

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

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

IMAGESwww.gimp.org/images/frontpage/Inkscape_Logo.svg.png
1.21 s
CSSwww.gimp.org/theme/css/home.css
1.12 s
JAVASCRIPTwww.gimp.org/js/search-embed.js
966 ms
IMAGESwww.gimp.org/images/frontpage/30banner.svg
950 ms
CSSwww.gimp.org/theme/css/tipuesearch/tipuesearch.css
944 ms
IMAGESwww.gimp.org/images/frontpage/blocks.svg
932 ms
JAVASCRIPTwww.gimp.org/js/push-menu.js
932 ms
IMAGESwww.gimp.org/images/frontpage/200px-Scribus_logo.sv…
929 ms
CSSwww.gimp.org/theme/css/grid.css
924 ms
CSSwww.gimp.org/theme/css/dark.css
923 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://www.gimp.org/images/frontpage/Inkscape_Logo.svg.pngimages2001.21 s37.6 KB
https://www.gimp.org/theme/css/home.csscss2001.12 s2.0 KB
https://www.gimp.org/js/search-embed.jsjavascript200966 ms824 B
https://www.gimp.org/images/frontpage/30banner.svgimages200950 ms10.9 KB
https://www.gimp.org/theme/css/tipuesearch/tipuesearch.csscss200944 ms1.2 KB
https://www.gimp.org/images/frontpage/blocks.svgimages200932 ms2.3 KB
https://www.gimp.org/js/push-menu.jsjavascript200932 ms1.3 KB
https://www.gimp.org/images/frontpage/200px-Scribus_logo.svg.pngimages200929 ms30.8 KB
https://www.gimp.org/theme/css/grid.csscss200924 ms2.1 KB
https://www.gimp.org/theme/css/dark.csscss200923 ms1.5 KB
https://www.gimp.org/theme/css/gimp.csscss200917 ms4.0 KB
https://www.gimp.org/theme/css/normalize.csscss200914 ms2.5 KB
https://www.gimp.org/images/frontpage/wilber-big.pngimages200903 ms11.4 KB
https://www.gimp.org/images/wilber32.pngimages200891 ms1.6 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.