gelbooru.com speed test — 20 Oct 2026

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

https://gelbooru.com/

20 October 2026 at 14:53 UTC · Free test · report pt_57353ce98315

Re-test this page Test your own site

Grade

91/100

Performance95/100

Structure86/100

13 audit(s) passed, 3 need work

First byte (TTFB)382 msmeasured from this server

Fully loaded1.45 sfirst byte + slowest asset

Requests16document + assets

Page weight174.6 KBcompressed transfer

HTML document3.3 KBidentity

ProtocolHTTP/2nginx/1.26.3

Third-party29.7 KBother hosts

Where the first byte went

DNS lookup 72 ms 19%
TCP connect 64 ms 17%
Server wait 247 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 59% of 4,999 pages tested here382 ms against a median of 449 ms

Page weightlighter than 81% of 4,999 pages tested here174.6 KB against a median of 650.5 KB

Fully loadedfaster than 74% of 4,999 pages tested here1.45 s against a median of 1.84 s

Requestssends fewer requests than 83% of 4,999 pages tested here16 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 382 ms. That is workable, and the cheapest win left is caching or a warmer connection.
The page transfers 174.6 KB over 16 request(s). Javascript files are 75% of it, so defer what is not needed for the first screen, and drop tags nobody uses.
The HTML is sent without compression (identity), so the document is transferred at full size.
It runs over HTTP/2, so the assets share a connection instead of opening one each.
The largest element painted at 588 ms, inside the 2.5 s Google calls good.

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 gelbooru.com — **Mobile** 390 × 844 · 43.3 KB · page is 866 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 paint588 msgood is under 2.5 s

Cumulative layout shift0.000under 0.1 is stable

Total blocking timenone over 50 mslong tasks during load

First contentful paint588 msfirst content on screen

Browser page weight172.1 KB15 request(s), scripts included

Largest contentful paint588 ms

Goodgood under 2.5 s, poor over 4 s

Cumulative layout shift0.000

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

Javascript 5 requests

131.1 KB 75%

Css 3 requests

24.6 KB 14%

Images 7 requests

15.6 KB 9%

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

Top issues

Render-blocking resources

high impact

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

Cache static assets

medium impact

5 asset(s) answer without a Cache-Control max-age, so browsers revalidate them on every visit.

Fix: Version filenames on change and serve them with a long max-age plus immutable. That is what makes a returning visitor fast.

Strict-Transport-Security

low impact

HSTS is not set, so the first visit on a hostile network can still be downgraded to HTTP.

Fix: Send Strict-Transport-Security with a max-age of at least six months. Add includeSubDomains once every subdomain is HTTPS.

Waterfall

Slowest requests

IMAGESgelbooru.com/counter/6.gif

1.07 s

IMAGESgelbooru.com/counter/7.gif

1.06 s

IMAGESgelbooru.com/counter/5.gif

1.05 s

IMAGESgelbooru.com/layout/index_back.png

1.04 s

CSSgelbooru.com/bootstrap.css

1.03 s

CSSgelbooru.com/css/jquery-ui.css

1.02 s

CSSgelbooru.com/responsive.css

1.01 s

IMAGESgelbooru.com/counter/4.gif

1.01 s

JAVASCRIPTgelbooru.com/script/autocomplete3.js

1.00 s

IMAGESgelbooru.com/counter/1.gif

1.00 s

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

Request	Type	Status	Time	Size
https://gelbooru.com/counter/6.gif	images	200	1.07 s	2.1 KB
https://gelbooru.com/counter/7.gif	images	200	1.06 s	2.0 KB
https://gelbooru.com/counter/5.gif	images	200	1.05 s	2.2 KB
https://gelbooru.com/layout/index_back.png	images	200	1.04 s	2.8 KB
https://gelbooru.com/bootstrap.css	css	200	1.03 s	11.4 KB
https://gelbooru.com/css/jquery-ui.css?1	css	200	1.02 s	9.7 KB
https://gelbooru.com/responsive.css?1	css	200	1.01 s	3.5 KB
https://gelbooru.com/counter/4.gif	images	200	1.01 s	1.7 KB
https://gelbooru.com/script/autocomplete3.js?3	javascript	200	1.00 s	4.3 KB
https://gelbooru.com/counter/1.gif	images	200	1.00 s	1.7 KB
https://gelbooru.com/script/application.grid.js	javascript	200	993 ms	92.9 KB
https://gelbooru.com/favicon.png	images	200	980 ms	3.2 KB
https://gelbooru.com/script/jquery-hotkeys.js?1	javascript	200	965 ms	2.0 KB
https://gelbooru.com//script/miscJs.js?1	javascript	200	956 ms	2.1 KB
https://ajax.googleapis.com/ajax/libs/jquery/3.7.1/jquery.min.js 3rd party	javascript	200	945 ms	29.7 KB

Report this page

Run this test on your own site

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

Run a website speed test Have it fixed