www.redgifs.com speed test — 20 Oct 2026

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

https://www.redgifs.com/

20 October 2026 at 15:09 UTC · Free test · report pt_92ba91b44a7a
Grade
A
96/100
Performance100/100
Structure89/100

14 audit(s) passed, 2 need work

First byte (TTFB)135 msmeasured from this server
Fully loaded708 msfirst byte + slowest asset
Requests13document + assets
Page weight32.2 KBcompressed transfer
HTML document2.0 KBgzip
ProtocolHTTP/3cloudflare
Third-party8.6 KBother hosts

Where the first byte went

  • DNS lookup 81 ms 60%
  • TCP connect 2 ms 1%
  • Server wait 52 ms 39%

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 99% of 4,999 pages tested here135 ms against a median of 449 ms
Page weightlighter than 93% of 4,999 pages tested here32.2 KB against a median of 650.5 KB
Fully loadedfaster than 96% of 4,999 pages tested here708 ms against a median of 1.84 s
Requestssends fewer requests than 85% of 4,999 pages tested here13 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 135 ms, which is fast: almost all of the wait is the page itself, not the host.
  • The page transfers 32.2 KB over 13 request(s), which is lean. Css files are 49% of it, so split the stylesheet so the first screen does not download the whole site.
  • The HTML itself arrives gzip-compressed.
  • It runs over HTTP/3, so the assets share a connection instead of opening one each.
  • 27% of the weight comes from other hosts (analytics, fonts, embeds), which also means their slow day becomes your slow day.
  • The largest element painted at 1.67 s, inside the 2.5 s Google calls good.
  • Layout stayed still (CLS 0.058), so nothing jumps under the reader's cursor.
  • The main thread was blocked for 1 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.redgifs.com
Desktop 1366 × 768 · 269.3 KB · page is 768 px tall
Mobile screenshot of www.redgifs.com
Mobile 390 × 844 · 62.9 KB · page is 844 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.67 sgood is under 2.5 s
Cumulative layout shift0.058under 0.1 is stable
Total blocking time1 mslong tasks during load
First contentful paint512 msfirst content on screen
Browser page weight958.72 MB158 request(s), scripts included
Failed requests60blocked or unreachable
Largest contentful paint1.67 s
Goodgood under 2.5 s, poor over 4 s
Cumulative layout shift0.058
Goodgood under 0.1, poor over 0.25
Total blocking time1 ms
Goodgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Css 6 requests
15.8 KB 49%
Javascript 2 requests
8.8 KB 27%
Images 3 requests
5.3 KB 16%
Other 1 request
260 B 1%

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

Top issues

Render-blocking resources

high impact

7 render-blocking resource(s) in the document head (1 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

JAVASCRIPTcdn-cookieyes.com/client_data/e9015ceab2153fb470e7f06a/s…
573 ms
IMAGESwww.redgifs.com/favicon-16x16.png
549 ms
CSSwww.redgifs.com/static/common-Cmd4N-ba.css
516 ms
IMAGESwww.redgifs.com/favicon-32x32.png
507 ms
OTHERwww.redgifs.com/site.webmanifest
492 ms
JAVASCRIPTwww.redgifs.com/static/index-rYe_RXrf.js
485 ms
CSSwww.redgifs.com/static/index-By3riQsK.css
480 ms
CSSwww.redgifs.com/static/components-UI-Stnls9wx.css
467 ms
IMAGESwww.redgifs.com/apple-touch-icon.png
457 ms
CSSwww.redgifs.com/static/components-app-XGnfHP8s.css
454 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://cdn-cookieyes.com/client_data/e9015ceab2153fb470e7f06a/script.js 3rd partyjavascript200573 ms8.6 KB
https://www.redgifs.com/favicon-16x16.pngimages200549 ms332 B
https://www.redgifs.com/static/common-Cmd4N-ba.csscss200516 ms1.0 KB
https://www.redgifs.com/favicon-32x32.pngimages200507 ms680 B
https://www.redgifs.com/site.webmanifestother200492 ms260 B
https://www.redgifs.com/static/index-rYe_RXrf.jsjavascript200485 ms250 B
https://www.redgifs.com/static/index-By3riQsK.csscss200480 ms3.5 KB
https://www.redgifs.com/static/components-UI-Stnls9wx.csscss200467 ms562 B
https://www.redgifs.com/apple-touch-icon.pngimages200457 ms4.3 KB
https://www.redgifs.com/static/components-app-XGnfHP8s.csscss200454 ms5.7 KB
https://www.redgifs.com/static/components-ads-n4NIwupO.csscss200450 ms4.3 KB
https://www.redgifs.com/static/components-alerts-Cmm0_OsV.csscss200450 ms746 B
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.