tinder.com speed test — 20 Oct 2026

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

https://tinder.com/

20 October 2026 at 12:26 UTC · Free test · report pt_027b13f80548
Grade
A
92/100
Performance98/100
Structure83/100

11 audit(s) passed, 5 need work

First byte (TTFB)244 msmeasured from this server
Fully loaded951 msfirst byte + slowest asset
Requests17document + assets
Page weight949.3 KBcompressed transfer
HTML document110.4 KBgzip
ProtocolHTTP/3nginx

Where the first byte went

  • DNS lookup 59 ms 24%
  • TCP connect 26 ms 11%
  • Server wait 159 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 85% of 4,999 pages tested here244 ms against a median of 449 ms
Page weightheavier than 61% of 4,999 pages tested here949.3 KB against a median of 650.3 KB
Fully loadedfaster than 93% of 4,999 pages tested here951 ms against a median of 1.84 s
Requestssends fewer requests than 82% of 4,999 pages tested here17 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 244 ms. That is workable, and the cheapest win left is caching or a warmer connection.
  • The page transfers 949.3 KB over 17 request(s). Javascript files are 77% 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.
  • The largest element painted at 1.77 s, inside the 2.5 s Google calls good.
  • Layout stayed still (CLS 0.002), so nothing jumps under the reader's cursor.
  • The main thread was blocked for 492 ms, so taps and scrolling wait while scripts run.

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 tinder.com
Mobile 390 × 844 · 35.9 KB · page is 845 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.77 sgood is under 2.5 s
Cumulative layout shift0.002under 0.1 is stable
Total blocking time492 mslong tasks during load
First contentful paint580 msfirst content on screen
Browser page weight3.74 MB71 request(s), scripts included
Largest contentful paint1.77 s
Goodgood under 2.5 s, poor over 4 s
Cumulative layout shift0.002
Goodgood under 0.1, poor over 0.25
Total blocking time492 ms
Needs improvementgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Javascript 5 requests
733.0 KB 77%
Fonts 3 requests
57.5 KB 6%
Css 3 requests
38.4 KB 4%
Images 4 requests
8.3 KB 1%
Other 1 request
1.8 KB 0%

Transfer size, compressed as sent. 17 request(s) in total, 949.3 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.

Total page weight

medium impact

The page transfers 949.3 KB across 17 request(s), with the document itself at 110.4 KB.

Fix: Work through the heaviest assets first: images, then fonts, then third-party scripts.

HTML document size

medium impact

The document transfers 110.4 KB. A bloated document delays every other request, because nothing else can start until it is parsed.

Fix: Paginate long listings, move repeated markup into a template, and stop inlining large data URIs into the HTML.

JavaScript weight

medium impact

1 JavaScript file(s) over 200 KB: main-2d68dd6374a0c27913b1.js (258.2 KB)

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

Avoid extra redirects

medium impact

2 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

OTHERtinder.com/manifest-en.json
707 ms
FONTStinder.com/static/build/fonts/4c112e110a336202365…
657 ms
IMAGEStinder.com/favicon-16x16.png
639 ms
IMAGEStinder.com/favicon-32x32.png
636 ms
JAVASCRIPTtinder.com/static/build/l/pc-webpack-runtime-8e78…
634 ms
FONTStinder.com/static/build/fonts/f9527cb231fbb96f8b8…
634 ms
CSStinder.com/static/build/l/atomic.bdf7c41f7c5289fd…
628 ms
JAVASCRIPTtinder.com/static/build/l/main-2d68dd6374a0c27913…
625 ms
JAVASCRIPTtinder.com/static/build/l/tinderapp-a48c43d687089…
625 ms
JAVASCRIPTtinder.com/static/build/l/vendor-114d4cccc82272ab…
624 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://tinder.com/manifest-en.jsonother200707 ms1.8 KB
https://tinder.com/static/build/fonts/4c112e110a336202365ba00324390d27.woff2fonts200657 ms21.3 KB
https://tinder.com/favicon-16x16.pngimages200639 ms738 B
https://tinder.com/favicon-32x32.pngimages200636 ms1.0 KB
https://tinder.com/static/build/l/pc-webpack-runtime-8e781518e4b3cd4a335a.jsjavascript200634 ms91.1 KB
https://tinder.com/static/build/fonts/f9527cb231fbb96f8b847c6bb2577e73.woff2fonts200634 ms21.8 KB
https://tinder.com/static/build/l/atomic.bdf7c41f7c5289fd6fcf.csscss200628 ms25.4 KB
https://tinder.com/static/build/l/main-2d68dd6374a0c27913b1.jsjavascript200625 ms258.2 KB
https://tinder.com/static/build/l/tinderapp-a48c43d687089e8d6751.jsjavascript200625 ms110.2 KB
https://tinder.com/static/build/l/vendor-114d4cccc82272abccec.jsjavascript200624 ms159.1 KB
https://tinder.com/static/build/fonts/0d4ec08dc6b105c09ea2f98b104ee5be.woff2fonts200624 ms14.4 KB
https://tinder.com/static/build/93c4c638595d3834c44a84ef30cc4a34.svgimages200624 ms532 B
https://tinder.com/static/build/l/76603-b4a2663bd9599bde52b9.jsjavascript200618 ms114.4 KB
https://tinder.com/static/apple-touch-icon.pngimages200616 ms6.0 KB
https://tinder.com/static/build/l/tinderapp.c9752704c7051f69ea63.csscss200608 ms3.5 KB
https://tinder.com/static/build/l/main.2a6423d337d50f4c0e5f.csscss200605 ms9.4 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.