justgiving.com speed test — 20 Oct 2026

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

https://justgiving.com/

20 October 2026 at 14:33 UTC · Free test · report pt_4e7d3d08f141
Grade
A
93/100
Performance99/100
Structure83/100

13 audit(s) passed, 3 need work

First byte (TTFB)239 msmeasured from this server
Fully loaded1.01 sfirst byte + slowest asset
Requests7document + assets
Page weight590.3 KBcompressed transfer
HTML document2.0 KBgzip
ProtocolHTTP/3AmazonS3
Third-party588.3 KBother hosts

Where the first byte went

  • DNS lookup 49 ms 21%
  • TCP connect 38 ms 16%
  • Server wait 152 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 86% of 4,999 pages tested here239 ms against a median of 449 ms
Page weightlighter than 53% of 4,999 pages tested here590.3 KB against a median of 650.5 KB
Fully loadedfaster than 92% of 4,999 pages tested here1.01 s against a median of 1.84 s
Requestssends fewer requests than 91% of 4,999 pages tested here7 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 239 ms. That is workable, and the cheapest win left is caching or a warmer connection.
  • The page transfers 590.3 KB over 7 request(s), which is lean. Javascript files are 95% of it, so defer what is not needed for the first screen, and drop tags nobody uses.
  • The HTML itself arrives gzip-compressed.
  • It runs over HTTP/3, so the assets share a connection instead of opening one each.
  • 100% 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 680 ms, inside the 2.5 s Google calls good.
  • Layout stayed still (CLS 0.018), so nothing jumps under the reader's cursor.
  • The main thread was blocked for 41 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 justgiving.com
Mobile 390 × 844 · 58.1 KB · page is 5522 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 paint680 msgood is under 2.5 s
Cumulative layout shift0.018under 0.1 is stable
Total blocking time41 mslong tasks during load
First contentful paint568 msfirst content on screen
Browser page weight2.00 MB53 request(s), scripts included
Largest contentful paint680 ms
Goodgood under 2.5 s, poor over 4 s
Cumulative layout shift0.018
Goodgood under 0.1, poor over 0.25
Total blocking time41 ms
Goodgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Javascript 4 requests
559.0 KB 95%
Css 1 request
29.0 KB 5%
Html 1 request
328 B 0%

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

Top issues

Compress text responses

high impact

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

Third-party weight

medium impact

3 third-party host(s) serve 588.3 KB of this page. Each one is another DNS lookup, TLS handshake and point of failure you do not control.

Fix: Self-host the libraries you can, drop the tags you cannot justify, and preconnect the ones you keep.

JavaScript weight

medium impact

2 JavaScript file(s) over 200 KB: polyfill-81c89ab2b57cf78d6318.js (264.2 KB), us-c014fdf79eff1cdb62fd.js (264.1 KB)

Fix: Split routes, remove unused dependencies, and prefer a two-file build (one pinned library, one application bundle) over many small ones.

Waterfall

Slowest requests

JAVASCRIPTwww.jg-cdn.com/assets/jg-homepage/config/config.661d9…
772 ms
CSSwww.jg-cdn.com/assets/jg-homepage/us-c014fdf79eff1cdb…
739 ms
JAVASCRIPTwww.jg-cdn.com/assets/jg-homepage/polyfill-81c89ab2b5…
651 ms
JAVASCRIPTapi.justgiving.com/chrome/client
638 ms
HTMLwww.googletagmanager.com/ns.html
388 ms
JAVASCRIPTwww.jg-cdn.com/assets/jg-homepage/us-c014fdf79eff1cdb…
369 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.jg-cdn.com/assets/jg-homepage/config/config.661d9a9ddc21.js 3rd partyjavascript200772 ms2.5 KB
https://www.jg-cdn.com/assets/jg-homepage/us-c014fdf79eff1cdb62fd.css 3rd partycss200739 ms29.0 KB
https://www.jg-cdn.com/assets/jg-homepage/polyfill-81c89ab2b57cf78d6318.js 3rd partyjavascript200651 ms264.2 KB
https://api.justgiving.com/chrome/client 3rd partyjavascript200638 ms28.2 KB
https://www.googletagmanager.com/ns.html?id=GTM-WL6ZNN 3rd partyhtml200388 ms328 B
https://www.jg-cdn.com/assets/jg-homepage/us-c014fdf79eff1cdb62fd.js 3rd partyjavascript200369 ms264.1 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.