Recorded on 2026-09-01 with the JWT sessions of that day. The session paths and the token wording below describe that day, not the current design. For today's design read the Rails authentication pages and the JodApp Web authentication pages.

Web latency baseline — prod, measured from a laptop

This page holds one benchmark run. It measures how long the Jod web server and the Jod Rails API take to answer.

It exists to answer one question. Should a page fetch its data in a React Router loader() or in a clientLoader()?

• A loader() runs on the web server. The web server calls the Rails API over a private name inside the VPC. Then it sends finished HTML to the browser. The user waits once.
• A clientLoader() runs in the browser. The page shell arrives first. Then the browser calls the Rails API itself over the public internet, through Cloudflare. The user waits twice, and the second wait leaves the page half empty.

The two shapes pay different network costs. This run measures both costs so the choice rests on numbers, not on a guess.

This run is a baseline, not the final answer

A new session middleware is coming to the web server. On every navigation that carries a session cookie, it will call GET /identities/sessions/current on the Rails API. That middleware does not exist yet. It did not run during this benchmark.

So treat these numbers as the "before" picture. Run the same script again after the middleware ships, with the same flags. Then put the two reports side by side.

What was measured, and from where

Item	Value
Environment	prod
Mode	client (from a laptop over the public internet)
Started (UTC)	2026-09-01T09:56:19Z
Finished (UTC)	2026-09-01T09:57:41Z
Run time	81 seconds
Machine host name	Nerdherd-M2-Max.local
Machine kernel	Darwin 25.5.0 arm64
curl	curl 8.7.1 (x86_64-apple-darwin25.0) libcurl/8.7.1 (SecureTransport) LibreSSL/3.3.6 zlib/1.2.12 nghttp2/1.68.1
Network the run came from	home fibre, jakarta, indihome
Public web host	jodapp.com
Public API host	api.jodapp.com
Private API host	api.internal.jodapp.com
Measured requests per measurement	20
Warm-up requests per measurement	3
Total requests sent	253
User-Agent sent	jod-latency-benchmark/1.0
Session cookie	supplied. Its value is not in this report.

The two API endpoints, and why there are two

This report measures the Rails API twice, with two different endpoints. They answer different questions.

Endpoint	What it does	What its number means
/up	The Rails health route. It touches no database.	The network floor. The smallest cost the path can have. No page ever calls it, so it is not the cost of a data fetch.
GET /identities/sessions/current	Verifies the JWT from the session cookie, then asks two services whether the user may enter the talent area and the employer area.	One real signed-in fetch. This is what a page actually pays, and it is the endpoint the coming middleware calls.

The gap between the two is the Rails work. That split matters. Only one half of it changes when you move a fetch from the server to the browser.

• The network half changes a lot. The private path stays inside the VPC. The public path crosses the internet and Cloudflare.
• The Rails half does not change at all. The same query runs either way.

So read the two numbers together. Reading /up on its own leads to the wrong conclusion, in a way that is easy to miss.

• The gap in milliseconds between the two paths is the same either way. The Rails work is added to both sides, so it cancels out.
• What changes is how large that gap looks next to the whole wait.
• On /up alone, the gap is almost the entire number. Next to a real fetch it is one part of a larger total.

That share is what the decision turns on. A gap of 30 ms matters a lot when the whole fetch takes 35 ms. It matters much less when the whole fetch takes 300 ms.

Does this environment serve the session endpoint?

Environments do not always run the same build. So the script checks before it starts, instead of assuming. It sends one request with no cookie and reads the status code.

Answer	What it means	What the script does
401	The route is there. The cookie is simply missing on a check request.	Measures the real fetch.
404	This Rails API does not serve the path.	Skips the measurement, rather than recording 404 timings as a result.

On this run, /identities/sessions/current answered on prod. So the numbers below include one real signed-in fetch.

Why the GET, and not the session refresh

The path /identities/sessions/current answers four verbs. Only one of them belongs in a benchmark.

Verb	Can this benchmark use it?
GET	Yes. It changes nothing. It verifies the JWT, then asks two services whether the user may enter the talent area and the employer area.
PATCH	No. It rotates the JWT and sets new cookies. That is a write. It would also end the session being used to run the benchmark, because each call replaces the cookie the last one used.
POST	No. It signs a user in. It is a write, and it needs a password.
DELETE	No. It signs the user out. It is a write.

This script only ever sends GET requests. It never touches the other three.

The GET is the right one for a second reason. The coming middleware calls this exact endpoint on every request that carries a session cookie. So its cost is the cost the middleware will add.

A heavier endpoint to compare against

The session endpoint is deliberately small. It answers who is signed in and where they may go, and it carries no page data.

For a heavier read, run the script again with --session-endpoint /identities/users/current. That one loads the user with about ten associated tables and serialises the lot. It shows what a fatter fetch costs on the same two paths.

How to read the numbers

Every number in this report is milliseconds.

Term	What it means
TTFB (time_starttransfer)	The wait until the first byte of the response arrives. This is the wait the user feels.
Whole response (time_total)	The wait until the last byte arrives. For a big HTML page this is larger than TTFB.
DNS (time_namelookup)	Time spent turning the host name into an IP address.
TCP connect (time_connect)	Time spent opening the TCP connection.
TLS handshake (time_appconnect)	Time spent on the TLS handshake. It is 0 on plain HTTP.
Ready to send (time_pretransfer)	Everything above, finished. The request has not left yet.

Two connection shapes appear below.

Shape	How it was produced	What it stands for
New connection each time	One curl process per request. A new process cannot reuse a connection.	The first call after a cold start. It pays DNS, TCP and TLS.
Connection reused	One curl process, many URLs. curl keeps the connection open.	Real life. Node's built-in fetch keeps connections alive by default, and so does a browser. Use this number when you reason about loader() and clientLoader().

In a reused-connection measurement the DNS, TCP and TLS rows read close to 0. That is correct. The connection was already open, so no time was spent opening it.

The p95 uses the nearest-rank method. Sort the samples, then take the sample at position ceil(0.95 times n). With 20 samples that is the 19th.

Warm-up requests are listed under each table. They are never mixed into min, median, mean, p95 or max.

Every page request carries a cb query parameter. Its value is different every time. So no cache can answer the request.

Every measured request sends Accept-Encoding for gzip, the way a browser and Node's fetch both do.

Warnings from this run

None. Every request answered 200, no response came from a cache, and every connection behaved as expected.

Results

Network floor, browser to Rails API, public internet, new connection each time

The smallest cost the public path can have. /up touches no database, so this is network, Cloudflare and TLS, and nothing else.

• URL: https://api.jodapp.com/up
• Connection shape: new connection each time
• Requests: 3 warm-up, 20 measured
• Connections opened: 23
• Status codes: 200 x23
• HTTP version: HTTP/2 x23
• cf-cache-status: DYNAMIC x23

Measure	min	median	mean	p95	max
TTFB (time_starttransfer)	85.21	96.57	180.88	397.99	450.14
Whole response (time_total)	85.52	96.86	181.80	398.52	451.50
DNS (time_namelookup)	1.84	2.12	2.16	2.69	3.02
TCP connect (time_connect)	21.71	24.23	41.52	94.28	115.06
TLS handshake (time_appconnect)	47.56	53.89	90.80	192.99	197.03
Ready to send (time_pretransfer)	47.62	53.95	90.91	193.22	197.30

All values are milliseconds.

Warm-up requests. They are shown here and left out of the table above.

Request	TTFB	Whole response	Status
1	97.51	97.74	200
2	306.54	307.77	200
3	103.16	103.55	200

Network floor, browser to Rails API, public internet, connection reused

The same network floor with the connection already open. No page ever calls /up, so this is not the cost of a data fetch.

• URL: https://api.jodapp.com/up
• Connection shape: connection reused
• Requests: 3 warm-up, 20 measured
• Connections opened: 1
• Status codes: 200 x23
• HTTP version: HTTP/2 x23
• cf-cache-status: DYNAMIC x23

Measure	min	median	mean	p95	max
TTFB (time_starttransfer)	105.48	111.56	125.10	192.72	193.50
Whole response (time_total)	106.08	112.50	126.12	193.75	194.31
DNS (time_namelookup)	0.01	0.03	0.03	0.04	0.07
TCP connect (time_connect)	0.00	0.00	0.00	0.00	0.00
TLS handshake (time_appconnect)	not used	not used	not used	not used	not used
Ready to send (time_pretransfer)	0.06	0.17	0.16	0.23	0.28

All values are milliseconds.

The TLS row says "not used" because no TLS handshake happened. Either the request went over plain HTTP, or the connection was already open.

Warm-up requests. They are shown here and left out of the table above.

Request	TTFB	Whole response	Status
1	240.02	241.27	200
2	335.90	336.97	200
3	165.26	166.26	200

In this measurement request 1 also opened the connection. That is why it is slower than the rest.

One real signed-in fetch, public internet, new connection each time

What the first real clientLoader() API call costs. It pays DNS, TCP and TLS on top of the Rails work.

• URL: https://api.jodapp.com/identities/sessions/current
• Connection shape: new connection each time
• Requests: 3 warm-up, 20 measured
• Connections opened: 23
• Status codes: 200 x23
• HTTP version: HTTP/2 x23
• cf-cache-status: DYNAMIC x23
• Sent a session cookie. Its value is not in this report.

Measure	min	median	mean	p95	max
TTFB (time_starttransfer)	94.05	142.49	198.40	457.64	561.01
Whole response (time_total)	94.41	143.38	199.16	458.94	562.39
DNS (time_namelookup)	1.90	2.32	2.49	3.20	3.25
TCP connect (time_connect)	22.03	23.54	47.99	137.09	165.39
TLS handshake (time_appconnect)	48.48	52.79	96.23	216.16	279.64
Ready to send (time_pretransfer)	48.55	52.87	96.36	216.35	279.85

All values are milliseconds.

Warm-up requests. They are shown here and left out of the table above.

Request	TTFB	Whole response	Status
1	116.97	117.34	200
2	243.09	244.36	200
3	317.09	318.34	200

One real signed-in fetch, public internet, connection reused

What every later real clientLoader() API call costs. This is the number the decision rests on.

• URL: https://api.jodapp.com/identities/sessions/current
• Connection shape: connection reused
• Requests: 3 warm-up, 20 measured
• Connections opened: 1
• Status codes: 200 x23
• HTTP version: HTTP/2 x23
• cf-cache-status: DYNAMIC x23
• Sent a session cookie. Its value is not in this report.

Measure	min	median	mean	p95	max
TTFB (time_starttransfer)	106.81	113.25	129.77	189.67	192.03
Whole response (time_total)	107.35	113.85	130.47	190.64	192.67
DNS (time_namelookup)	0.01	0.03	0.03	0.04	0.06
TCP connect (time_connect)	0.00	0.00	0.00	0.00	0.00
TLS handshake (time_appconnect)	not used	not used	not used	not used	not used
Ready to send (time_pretransfer)	0.06	0.18	0.18	0.29	0.32

All values are milliseconds.

The TLS row says "not used" because no TLS handshake happened. Either the request went over plain HTTP, or the connection was already open.

Warm-up requests. They are shown here and left out of the table above.

Request	TTFB	Whole response	Status
1	296.38	297.80	200
2	109.82	110.87	200
3	118.94	119.82	200

In this measurement request 1 also opened the connection. That is why it is slower than the rest.

Public page /up, the control, new connection each time

The smallest cost any page request can have from this network. It runs no loader and no session code.

• URL: https://jodapp.com/up
• Connection shape: new connection each time
• Requests: 3 warm-up, 20 measured
• Connections opened: 23
• Status codes: 200 x23
• HTTP version: HTTP/2 x23
• cf-cache-status: DYNAMIC x23

Measure	min	median	mean	p95	max
TTFB (time_starttransfer)	95.94	171.91	187.79	309.27	463.14
Whole response (time_total)	96.15	172.24	188.59	310.78	464.50
DNS (time_namelookup)	1.75	2.16	2.36	3.40	3.74
TCP connect (time_connect)	21.37	23.27	43.60	103.57	105.49
TLS handshake (time_appconnect)	46.40	88.89	98.82	148.83	294.77
Ready to send (time_pretransfer)	46.46	89.01	98.92	148.93	295.03

All values are milliseconds.

Warm-up requests. They are shown here and left out of the table above.

Request	TTFB	Whole response	Status
1	246.76	247.03	200
2	100.56	100.92	200
3	109.76	110.16	200

Public page /up, the control, connection reused

The same control without DNS, TCP and TLS.

• URL: https://jodapp.com/up
• Connection shape: connection reused
• Requests: 3 warm-up, 20 measured
• Connections opened: 1
• Status codes: 200 x23
• HTTP version: HTTP/2 x23
• cf-cache-status: DYNAMIC x23

Measure	min	median	mean	p95	max
TTFB (time_starttransfer)	38.14	40.73	48.29	109.88	128.22
Whole response (time_total)	38.45	41.44	49.13	113.15	128.47
DNS (time_namelookup)	0.01	0.01	0.01	0.02	0.02
TCP connect (time_connect)	0.00	0.00	0.00	0.00	0.00
TLS handshake (time_appconnect)	not used	not used	not used	not used	not used
Ready to send (time_pretransfer)	0.05	0.07	0.07	0.10	0.11

All values are milliseconds.

The TLS row says "not used" because no TLS handshake happened. Either the request went over plain HTTP, or the connection was already open.

Warm-up requests. They are shown here and left out of the table above.

Request	TTFB	Whole response	Status
1	146.20	146.59	200
2	39.81	40.19	200
3	43.27	43.61	200

In this measurement request 1 also opened the connection. That is why it is slower than the rest.

Public page /privacy, new connection each time

What a first-time visitor waits for a light page.

• URL: https://jodapp.com/privacy
• Connection shape: new connection each time
• Requests: 3 warm-up, 20 measured
• Connections opened: 23
• Status codes: 200 x23
• HTTP version: HTTP/2 x23
• cf-cache-status: DYNAMIC x23

Measure	min	median	mean	p95	max
TTFB (time_starttransfer)	445.61	498.26	569.70	773.50	990.81
Whole response (time_total)	446.57	500.23	571.51	777.83	992.79
DNS (time_namelookup)	1.73	2.14	2.43	3.33	3.37
TCP connect (time_connect)	21.31	23.25	43.22	101.91	131.82
TLS handshake (time_appconnect)	47.25	56.61	98.25	213.91	297.37
Ready to send (time_pretransfer)	47.32	56.69	98.36	214.11	297.59

All values are milliseconds.

Warm-up requests. They are shown here and left out of the table above.

Request	TTFB	Whole response	Status
1	442.60	444.95	200
2	901.06	902.34	200
3	488.51	490.55	200

Public page /privacy, connection reused

What a returning visitor waits for a light page.

• URL: https://jodapp.com/privacy
• Connection shape: connection reused
• Requests: 3 warm-up, 20 measured
• Connections opened: 1
• Status codes: 200 x23
• HTTP version: HTTP/2 x23
• cf-cache-status: DYNAMIC x23

Measure	min	median	mean	p95	max
TTFB (time_starttransfer)	502.39	515.80	524.87	561.72	621.68
Whole response (time_total)	508.98	522.17	531.19	570.39	622.88
DNS (time_namelookup)	0.02	0.05	0.04	0.06	0.10
TCP connect (time_connect)	0.00	0.00	0.00	0.00	0.00
TLS handshake (time_appconnect)	not used	not used	not used	not used	not used
Ready to send (time_pretransfer)	0.09	0.21	0.20	0.26	0.27

All values are milliseconds.

The TLS row says "not used" because no TLS handshake happened. Either the request went over plain HTTP, or the connection was already open.

Warm-up requests. They are shown here and left out of the table above.

Request	TTFB	Whole response	Status
1	874.70	876.26	200
2	521.07	524.04	200
3	523.51	525.29	200

In this measurement request 1 also opened the connection. That is why it is slower than the rest.

Public page /jobs, new connection each time

A public list page with real loader() work, measured from outside.

• URL: https://jodapp.com/jobs
• Connection shape: new connection each time
• Requests: 3 warm-up, 20 measured
• Connections opened: 23
• Status codes: 200 x23
• HTTP version: HTTP/2 x23
• cf-cache-status: DYNAMIC x23

Measure	min	median	mean	p95	max
TTFB (time_starttransfer)	532.96	652.95	713.89	1032.18	1371.90
Whole response (time_total)	534.97	654.59	716.19	1036.15	1377.09
DNS (time_namelookup)	1.74	2.65	2.58	3.13	3.41
TCP connect (time_connect)	21.74	23.97	46.53	104.31	108.26
TLS handshake (time_appconnect)	48.15	52.33	91.27	206.39	217.58
Ready to send (time_pretransfer)	48.24	52.42	91.39	206.60	217.82

All values are milliseconds.

Warm-up requests. They are shown here and left out of the table above.

Request	TTFB	Whole response	Status
1	548.45	549.35	200
2	550.86	551.36	200
3	533.66	537.15	200

Public page /jobs, connection reused

The same page without DNS, TCP and TLS.

• URL: https://jodapp.com/jobs
• Connection shape: connection reused
• Requests: 3 warm-up, 20 measured
• Connections opened: 1
• Status codes: 200 x23
• HTTP version: HTTP/2 x23
• cf-cache-status: DYNAMIC x23

Measure	min	median	mean	p95	max
TTFB (time_starttransfer)	475.09	520.27	536.72	569.54	982.29
Whole response (time_total)	476.40	523.17	538.80	571.03	983.91
DNS (time_namelookup)	0.01	0.05	0.05	0.07	0.16
TCP connect (time_connect)	0.00	0.00	0.00	0.00	0.00
TLS handshake (time_appconnect)	not used	not used	not used	not used	not used
Ready to send (time_pretransfer)	0.05	0.22	0.21	0.31	0.35

All values are milliseconds.

The TLS row says "not used" because no TLS handshake happened. Either the request went over plain HTTP, or the connection was already open.

Warm-up requests. They are shown here and left out of the table above.

Request	TTFB	Whole response	Status
1	525.72	526.36	200
2	498.70	499.14	200
3	473.03	474.46	200

In this measurement request 1 also opened the connection. That is why it is slower than the rest.

Public page /employers/dashboard, signed in, connection reused

The real employer journey, measured from outside.

• URL: https://jodapp.com/employers/dashboard
• Connection shape: connection reused
• Requests: 3 warm-up, 20 measured
• Connections opened: 1
• Status codes: 200 x23
• HTTP version: HTTP/2 x23
• cf-cache-status: DYNAMIC x23
• Sent a session cookie. Its value is not in this report.

Measure	min	median	mean	p95	max
TTFB (time_starttransfer)	80.51	86.48	96.34	168.30	180.90
Whole response (time_total)	81.71	87.31	97.58	171.97	183.31
DNS (time_namelookup)	0.01	0.04	0.04	0.12	0.18
TCP connect (time_connect)	0.00	0.00	0.00	0.00	0.00
TLS handshake (time_appconnect)	not used	not used	not used	not used	not used
Ready to send (time_pretransfer)	0.05	0.21	0.19	0.30	0.39

All values are milliseconds.

The TLS row says "not used" because no TLS handshake happened. Either the request went over plain HTTP, or the connection was already open.

Warm-up requests. They are shown here and left out of the table above.

Request	TTFB	Whole response	Status
1	142.36	142.91	200
2	84.85	86.12	200
3	90.67	91.89	200

In this measurement request 1 also opened the connection. That is why it is slower than the rest.

What these numbers mean for loader() and clientLoader()

Question	Answer from this run
What does one real API call from a clientLoader() cost?	113.25 ms, median, on a connection that is already open
How much of that is network, Cloudflare and TLS?	111.56 ms, median, the /up floor
How much of that is Rails work?	1.69 ms
What does that real call cost when the connection is new?	142.49 ms, median, including DNS, TCP and TLS
What does opening the connection add?	29.24 ms
How much of the network floor is DNS?	2.12 ms, median
How much of it is TCP?	24.23 ms, median
How much of it is TLS?	53.89 ms, median
What does the page shell cost on its own?	41.44 ms, median, for /up
What does a light public page cost?	522.17 ms, median, for /privacy
What does a public list page cost?	523.17 ms, median, for /jobs
What does the signed-in employer dashboard cost?	87.31 ms, median

Read it like this.

• One real API call from the browser costs about 113.25 ms once the connection is open. A clientLoader() pays this on top of the page shell, and the user sees an empty area while it runs.
• About 1.69 ms of that is Rails work. The rest is network, Cloudflare and TLS.
• The network on its own costs about 111.56 ms. That is /up, which touches no database. No page ever calls it. It is the smallest cost this path can have, not a result.
• The very first call to the API host costs about 29.24 ms more, because it pays DNS, TCP and TLS. A clientLoader() on a fresh visit pays this. A loader() never does, because the web server holds its connection open.
• A clientLoader() page has two waits. The shell arrives after about 41.44 ms. The data arrives about 113.25 ms after that. Total: about 154.69 ms before the page is complete.
• A loader() page has one wait. /jobs takes about 523.17 ms, and it arrives complete.
• On a first visit, /jobs costs about 131.42 ms more, because the browser has to open a connection to the web host first.

The honest comparison needs both reports

This run measured the public path only. It cannot tell you what the web server pays to reach the Rails API, because that path lives inside the VPC.

Run the server-side mode on the web instance, then read the two reports together: --mode server --env prod

Compare the same endpoint on both paths. Not /up against /up.

Shape	What the user waits for	Which number to use
loader()	One wait. The page shell plus one private API call.	The real signed-in fetch, private name, connection reused. It is in the server-side report.
clientLoader()	Two waits. The page shell first, then one public API call.	The real signed-in fetch, public internet, connection reused. It is in the table above.

Both rows name the same endpoint. The only difference is the path it travels. That is the comparison the decision needs.

One more point that no benchmark can measure. A loader() sends finished HTML. A clientLoader() sends a shell, so search engines and link previews see an empty page unless something else fills it in.

The exact commands this run used

Each line below sends one request. The script sent the same request many times.

For a reused-connection measurement, the script passed every URL to one curl call. curl then kept the connection open between them.

Network floor, browser to Rails API, public internet, new connection each time

curl -sS -o /dev/null -D - --compressed --max-time 20 -A 'jod-latency-benchmark/1.0' -w 'TIMING %{time_namelookup} %{time_connect} %{time_appconnect} %{time_pretransfer} %{time_starttransfer} %{time_total} %{http_code} %{size_download} %{num_connects} %{http_version}' 'https://api.jodapp.com/up'

Network floor, browser to Rails API, public internet, connection reused

curl -sS -o /dev/null -D - --compressed --max-time 20 -A 'jod-latency-benchmark/1.0' -w 'TIMING %{time_namelookup} %{time_connect} %{time_appconnect} %{time_pretransfer} %{time_starttransfer} %{time_total} %{http_code} %{size_download} %{num_connects} %{http_version}' 'https://api.jodapp.com/up'

One real signed-in fetch, public internet, new connection each time

curl -sS -o /dev/null -D - --compressed --max-time 20 -A 'jod-latency-benchmark/1.0' -K cookie.conf -w 'TIMING %{time_namelookup} %{time_connect} %{time_appconnect} %{time_pretransfer} %{time_starttransfer} %{time_total} %{http_code} %{size_download} %{num_connects} %{http_version}' 'https://api.jodapp.com/identities/sessions/current'

About cookie.conf:

• It holds one line: header = "Cookie: ...".
• The quotes are required. In a curl config file an unquoted value stops at the first space, and a cookie header always has spaces in it.
• The script writes it into a private temporary folder, with file mode 600.
• The script deletes it when it exits.
• curl reads the cookie from that file, never from the command line. So the cookie never shows up in ps output.

One real signed-in fetch, public internet, connection reused

curl -sS -o /dev/null -D - --compressed --max-time 20 -A 'jod-latency-benchmark/1.0' -K cookie.conf -w 'TIMING %{time_namelookup} %{time_connect} %{time_appconnect} %{time_pretransfer} %{time_starttransfer} %{time_total} %{http_code} %{size_download} %{num_connects} %{http_version}' 'https://api.jodapp.com/identities/sessions/current'

About cookie.conf:

• It holds one line: header = "Cookie: ...".
• The quotes are required. In a curl config file an unquoted value stops at the first space, and a cookie header always has spaces in it.
• The script writes it into a private temporary folder, with file mode 600.
• The script deletes it when it exits.
• curl reads the cookie from that file, never from the command line. So the cookie never shows up in ps output.

Public page /up, the control, new connection each time

curl -sS -o /dev/null -D - --compressed --max-time 20 -A 'jod-latency-benchmark/1.0' -H 'Accept: text/html,application/xhtml+xml' -w 'TIMING %{time_namelookup} %{time_connect} %{time_appconnect} %{time_pretransfer} %{time_starttransfer} %{time_total} %{http_code} %{size_download} %{num_connects} %{http_version}' 'https://jodapp.com/up'

Public page /up, the control, connection reused

curl -sS -o /dev/null -D - --compressed --max-time 20 -A 'jod-latency-benchmark/1.0' -H 'Accept: text/html,application/xhtml+xml' -w 'TIMING %{time_namelookup} %{time_connect} %{time_appconnect} %{time_pretransfer} %{time_starttransfer} %{time_total} %{http_code} %{size_download} %{num_connects} %{http_version}' 'https://jodapp.com/up'

Public page /privacy, new connection each time

curl -sS -o /dev/null -D - --compressed --max-time 20 -A 'jod-latency-benchmark/1.0' -H 'Accept: text/html,application/xhtml+xml' -w 'TIMING %{time_namelookup} %{time_connect} %{time_appconnect} %{time_pretransfer} %{time_starttransfer} %{time_total} %{http_code} %{size_download} %{num_connects} %{http_version}' 'https://jodapp.com/privacy'

Public page /privacy, connection reused

curl -sS -o /dev/null -D - --compressed --max-time 20 -A 'jod-latency-benchmark/1.0' -H 'Accept: text/html,application/xhtml+xml' -w 'TIMING %{time_namelookup} %{time_connect} %{time_appconnect} %{time_pretransfer} %{time_starttransfer} %{time_total} %{http_code} %{size_download} %{num_connects} %{http_version}' 'https://jodapp.com/privacy'

Public page /jobs, new connection each time

curl -sS -o /dev/null -D - --compressed --max-time 20 -A 'jod-latency-benchmark/1.0' -H 'Accept: text/html,application/xhtml+xml' -w 'TIMING %{time_namelookup} %{time_connect} %{time_appconnect} %{time_pretransfer} %{time_starttransfer} %{time_total} %{http_code} %{size_download} %{num_connects} %{http_version}' 'https://jodapp.com/jobs'

Public page /jobs, connection reused

curl -sS -o /dev/null -D - --compressed --max-time 20 -A 'jod-latency-benchmark/1.0' -H 'Accept: text/html,application/xhtml+xml' -w 'TIMING %{time_namelookup} %{time_connect} %{time_appconnect} %{time_pretransfer} %{time_starttransfer} %{time_total} %{http_code} %{size_download} %{num_connects} %{http_version}' 'https://jodapp.com/jobs'

Public page /employers/dashboard, signed in, connection reused

curl -sS -o /dev/null -D - --compressed --max-time 20 -A 'jod-latency-benchmark/1.0' -H 'Accept: text/html,application/xhtml+xml' -K cookie.conf -w 'TIMING %{time_namelookup} %{time_connect} %{time_appconnect} %{time_pretransfer} %{time_starttransfer} %{time_total} %{http_code} %{size_download} %{num_connects} %{http_version}' 'https://jodapp.com/employers/dashboard'

About cookie.conf:

• It holds one line: header = "Cookie: ...".
• The quotes are required. In a curl config file an unquoted value stops at the first space, and a cookie header always has spaces in it.
• The script writes it into a private temporary folder, with file mode 600.
• The script deletes it when it exits.
• curl reads the cookie from that file, never from the command line. So the cookie never shows up in ps output.

How to reproduce this run

./jod-latency-benchmark.sh --mode client --env prod --samples 20 --warmup 3 --network "home fibre, jakarta, indihome"

Raw samples

Every request this run made, in the order it made them. Times are milliseconds.

Open the raw samples

Network floor, browser to Rails API, public internet, new connection each time

Request	Kind	DNS	TCP	TLS	Ready to send	TTFB	Whole response	Status	Bytes	Connections	HTTP
1	warmup	2.00	27.10	55.32	55.38	97.51	97.74	200	82	1	2
2	warmup	1.92	59.68	133.05	133.14	306.54	307.77	200	82	1	2
3	warmup	2.87	23.30	51.93	52.03	103.16	103.55	200	82	1	2
4	sample	2.11	94.28	197.03	197.30	378.11	379.42	200	82	1	2
5	sample	2.14	92.27	192.99	193.22	450.15	451.50	200	82	1	2
6	sample	2.12	22.86	49.04	49.11	89.88	90.22	200	82	1	2
7	sample	2.06	24.56	51.61	51.68	93.88	94.15	200	82	1	2
8	sample	1.97	24.38	55.91	55.98	99.25	99.57	200	82	1	2
9	sample	2.23	115.06	191.90	192.24	317.55	318.79	200	82	1	2
10	sample	2.17	57.32	119.16	119.25	397.99	398.52	200	82	1	2
11	sample	2.12	56.58	117.76	117.88	220.73	222.06	200	82	1	2
12	sample	3.02	24.08	143.28	143.47	180.31	181.44	200	82	1	2
13	sample	2.23	22.27	47.98	48.05	86.90	87.32	200	82	1	2
14	sample	2.00	22.44	51.09	51.15	91.46	91.72	200	82	1	2
15	sample	1.98	29.39	58.15	58.21	186.82	188.17	200	82	1	2
16	sample	2.17	21.72	48.05	48.12	85.21	85.52	200	82	1	2
17	sample	2.01	21.94	48.39	48.45	90.61	90.93	200	82	1	2
18	sample	1.87	56.91	121.83	121.93	250.00	251.09	200	82	1	2
19	sample	2.33	23.66	49.76	49.83	88.62	94.00	200	82	1	2
20	sample	2.10	22.46	48.81	48.87	86.88	87.20	200	82	1	2
21	sample	2.03	52.62	123.82	123.93	249.07	249.60	200	82	1	2
22	sample	2.69	23.66	51.87	51.93	88.89	89.17	200	82	1	2
23	sample	1.84	22.01	47.56	47.62	85.36	85.61	200	82	1	2

Network floor, browser to Rails API, public internet, connection reused

Request	Kind	DNS	TCP	TLS	Ready to send	TTFB	Whole response	Status	Bytes	Connections	HTTP
1	warmup	2.55	59.24	125.26	125.36	240.02	241.27	200	82	1	2
2	warmup	0.04	0.00	0.00	0.18	335.90	336.97	200	82	0	2
3	warmup	0.04	0.00	0.00	0.21	165.26	166.26	200	82	0	2
4	sample	0.07	0.00	0.00	0.28	111.45	112.31	200	82	0	2
5	sample	0.04	0.00	0.00	0.20	108.89	109.73	200	82	0	2
6	sample	0.03	0.00	0.00	0.23	111.75	117.55	200	82	0	2
7	sample	0.04	0.00	0.00	0.19	181.70	183.47	200	82	0	2
8	sample	0.04	0.00	0.00	0.17	107.36	108.34	200	82	0	2
9	sample	0.03	0.00	0.00	0.21	112.28	112.69	200	82	0	2
10	sample	0.02	0.00	0.00	0.16	109.05	110.13	200	82	0	2
11	sample	0.04	0.00	0.00	0.18	192.72	193.75	200	82	0	2
12	sample	0.04	0.00	0.00	0.19	111.68	112.74	200	82	0	2
13	sample	0.03	0.00	0.00	0.19	105.58	106.08	200	82	0	2
14	sample	0.02	0.00	0.00	0.09	106.72	107.72	200	82	0	2
15	sample	0.03	0.00	0.00	0.22	193.50	194.31	200	82	0	2
16	sample	0.02	0.00	0.00	0.14	123.01	123.30	200	82	0	2
17	sample	0.01	0.00	0.00	0.08	124.26	124.52	200	82	0	2
18	sample	0.01	0.00	0.00	0.06	124.24	124.80	200	82	0	2
19	sample	0.02	0.00	0.00	0.09	149.86	150.49	200	82	0	2
20	sample	0.02	0.00	0.00	0.12	108.53	108.88	200	82	0	2
21	sample	0.01	0.00	0.00	0.06	107.83	108.18	200	82	0	2
22	sample	0.02	0.00	0.00	0.08	106.14	107.00	200	82	0	2
23	sample	0.04	0.00	0.00	0.18	105.48	106.51	200	82	0	2

One real signed-in fetch, public internet, new connection each time

Request	Kind	DNS	TCP	TLS	Ready to send	TTFB	Whole response	Status	Bytes	Connections	HTTP
1	warmup	2.13	40.25	68.47	68.58	116.97	117.34	200	182	1	2
2	warmup	2.22	59.51	125.00	125.11	243.09	244.36	200	182	1	2
3	warmup	4.05	118.03	190.97	191.22	317.09	318.34	200	182	1	2
4	sample	3.14	56.15	117.34	117.50	283.78	285.50	200	182	1	2
5	sample	3.13	23.95	49.56	49.67	97.29	97.81	200	182	1	2
6	sample	2.27	56.56	119.44	119.58	241.49	242.74	200	182	1	2
7	sample	2.57	89.06	116.31	116.45	158.79	160.18	200	182	1	2
8	sample	3.20	23.92	49.60	49.72	94.05	94.41	200	182	1	2
9	sample	1.90	56.95	120.23	120.34	561.01	562.39	200	182	1	2
10	sample	3.20	23.17	48.59	48.71	98.11	98.48	200	182	1	2
11	sample	2.02	165.39	279.64	279.85	457.65	458.94	200	182	1	2
12	sample	3.25	137.09	201.48	201.64	314.62	315.19	200	182	1	2
13	sample	1.98	22.64	52.64	52.73	126.20	126.58	200	182	1	2
14	sample	2.36	22.80	135.93	136.23	179.42	180.62	200	182	1	2
15	sample	3.07	24.16	63.39	63.52	114.17	114.55	200	182	1	2
16	sample	2.67	22.64	52.93	53.02	101.03	101.41	200	182	1	2
17	sample	1.97	22.38	48.48	48.55	180.47	180.84	200	182	1	2
18	sample	2.05	22.19	49.95	50.03	97.57	97.86	200	182	1	2
19	sample	1.94	101.39	216.16	216.35	377.86	378.87	200	182	1	2
20	sample	2.17	22.30	50.66	50.75	100.75	101.10	200	182	1	2
21	sample	1.95	22.03	51.48	51.57	105.35	105.69	200	182	1	2
22	sample	1.97	22.05	49.73	49.80	168.71	170.02	200	182	1	2
23	sample	2.98	23.05	51.02	51.13	109.71	110.08	200	182	1	2

One real signed-in fetch, public internet, connection reused

Request	Kind	DNS	TCP	TLS	Ready to send	TTFB	Whole response	Status	Bytes	Connections	HTTP
1	warmup	2.13	54.10	113.03	113.12	296.38	297.80	200	182	1	2
2	warmup	0.03	0.00	0.00	0.29	109.82	110.87	200	182	0	2
3	warmup	0.04	0.00	0.00	0.25	118.94	119.82	200	182	0	2
4	sample	0.03	0.00	0.00	0.27	109.41	110.73	200	182	0	2
5	sample	0.03	0.00	0.00	0.21	181.34	182.14	200	182	0	2
6	sample	0.04	0.00	0.00	0.25	108.47	109.29	200	182	0	2
7	sample	0.04	0.00	0.00	0.29	113.91	114.85	200	182	0	2
8	sample	0.04	0.00	0.00	0.26	112.40	113.38	200	182	0	2
9	sample	0.03	0.00	0.00	0.21	184.46	185.21	200	182	0	2
10	sample	0.03	0.00	0.00	0.18	112.72	113.23	200	182	0	2
11	sample	0.02	0.00	0.00	0.13	106.81	107.35	200	182	0	2
12	sample	0.02	0.00	0.00	0.13	114.34	114.74	200	182	0	2
13	sample	0.01	0.00	0.00	0.09	189.67	190.64	200	182	0	2
14	sample	0.06	0.00	0.00	0.27	107.33	107.82	200	182	0	2
15	sample	0.02	0.00	0.00	0.12	112.82	113.57	200	182	0	2
16	sample	0.03	0.00	0.00	0.17	107.02	107.87	200	182	0	2
17	sample	0.03	0.00	0.00	0.19	192.03	192.67	200	182	0	2
18	sample	0.02	0.00	0.00	0.15	109.99	110.52	200	182	0	2
19	sample	0.02	0.00	0.00	0.13	117.74	118.88	200	182	0	2
20	sample	0.04	0.00	0.00	0.32	116.36	116.64	200	182	0	2
21	sample	0.01	0.00	0.00	0.07	176.32	176.59	200	182	0	2
22	sample	0.01	0.00	0.00	0.06	113.67	114.13	200	182	0	2
23	sample	0.02	0.00	0.00	0.09	108.67	109.12	200	182	0	2

Public page /up, the control, new connection each time

Request	Kind	DNS	TCP	TLS	Ready to send	TTFB	Whole response	Status	Bytes	Connections	HTTP
1	warmup	2.39	56.75	122.10	122.18	246.76	247.03	200	4240	1	2
2	warmup	1.89	23.84	53.50	53.58	100.56	100.92	200	4240	1	2
3	warmup	1.99	22.63	50.56	50.63	109.76	110.16	200	4240	1	2
4	sample	2.28	21.89	51.23	51.30	129.32	129.64	200	4240	1	2
5	sample	2.01	103.57	129.77	129.85	180.86	182.13	200	4240	1	2
6	sample	1.83	60.45	126.94	127.04	286.71	288.69	200	4240	1	2
7	sample	2.25	96.27	123.81	123.90	172.41	172.74	200	4240	1	2
8	sample	1.86	21.55	51.07	51.14	95.94	96.15	200	4240	1	2
9	sample	1.83	21.42	50.74	50.79	116.25	116.70	200	4240	1	2
10	sample	2.56	23.30	148.83	148.93	233.36	233.86	200	4240	1	2
11	sample	2.62	22.96	49.76	49.85	104.99	105.47	200	4239	1	2
12	sample	2.67	21.37	47.64	47.72	100.56	102.34	200	4239	1	2
13	sample	3.74	23.25	146.49	146.64	193.99	195.28	200	4240	1	2
14	sample	2.98	22.70	50.53	50.59	100.22	100.69	200	4239	1	2
15	sample	2.07	22.48	54.13	54.21	104.46	104.88	200	4239	1	2
16	sample	1.90	22.24	48.49	48.56	171.40	171.73	200	4240	1	2
17	sample	1.80	64.57	129.47	129.56	255.14	255.88	200	4240	1	2
18	sample	1.75	52.36	123.66	123.80	288.71	289.88	200	4240	1	2
19	sample	2.69	24.54	50.12	50.20	99.91	100.37	200	4240	1	2
20	sample	2.01	105.49	294.77	295.03	463.14	464.50	200	4240	1	2
21	sample	3.40	62.77	128.55	128.65	309.27	310.78	200	4240	1	2
22	sample	2.86	57.22	124.05	124.19	246.75	247.42	200	4240	1	2
23	sample	2.03	21.69	46.40	46.46	102.36	102.66	200	4240	1	2

Public page /up, the control, connection reused

Request	Kind	DNS	TCP	TLS	Ready to send	TTFB	Whole response	Status	Bytes	Connections	HTTP
1	warmup	2.02	53.65	82.18	82.25	146.20	146.59	200	4240	1	2
2	warmup	0.01	0.00	0.00	0.06	39.81	40.19	200	4240	0	2
3	warmup	0.01	0.00	0.00	0.09	43.27	43.61	200	4240	0	2
4	sample	0.02	0.00	0.00	0.08	40.98	41.35	200	4240	0	2
5	sample	0.01	0.00	0.00	0.07	38.27	38.67	200	4240	0	2
6	sample	0.01	0.00	0.00	0.08	43.23	43.74	200	4240	0	2
7	sample	0.01	0.00	0.00	0.10	41.36	43.43	200	4240	0	2
8	sample	0.01	0.00	0.00	0.09	38.47	38.84	200	4240	0	2
9	sample	0.02	0.00	0.00	0.08	128.22	128.47	200	4240	0	2
10	sample	0.01	0.00	0.00	0.05	39.86	40.12	200	4240	0	2
11	sample	0.01	0.00	0.00	0.05	42.63	42.87	200	4240	0	2
12	sample	0.01	0.00	0.00	0.05	39.86	40.23	200	4240	0	2
13	sample	0.01	0.00	0.00	0.07	39.33	40.56	200	4240	0	2
14	sample	0.01	0.00	0.00	0.07	41.06	41.54	200	4240	0	2
15	sample	0.01	0.00	0.00	0.09	39.84	43.40	200	4240	0	2
16	sample	0.01	0.00	0.00	0.07	38.51	39.18	200	4240	0	2
17	sample	0.01	0.00	0.00	0.06	38.14	38.45	200	4240	0	2
18	sample	0.01	0.00	0.00	0.07	40.83	41.96	200	4240	0	2
19	sample	0.01	0.00	0.00	0.06	40.62	40.89	200	4240	0	2
20	sample	0.01	0.00	0.00	0.05	109.88	113.15	200	4240	0	2
21	sample	0.02	0.00	0.00	0.11	42.72	43.05	200	4240	0	2
22	sample	0.01	0.00	0.00	0.07	38.59	38.94	200	4240	0	2
23	sample	0.02	0.00	0.00	0.07	43.39	43.72	200	4240	0	2

Public page /privacy, new connection each time

Request	Kind	DNS	TCP	TLS	Ready to send	TTFB	Whole response	Status	Bytes	Connections	HTTP
1	warmup	1.91	21.73	47.53	47.62	442.60	444.95	200	14333	1	2
2	warmup	3.00	104.54	215.91	216.15	901.06	902.34	200	14334	1	2
3	warmup	3.20	25.12	65.03	65.14	488.51	490.55	200	14334	1	2
4	sample	3.08	59.16	122.84	122.94	604.49	604.89	200	14331	1	2
5	sample	1.73	22.75	49.88	49.94	447.93	449.90	200	14329	1	2
6	sample	2.70	66.00	126.15	126.26	615.85	616.88	200	14334	1	2
7	sample	2.08	22.38	48.66	48.74	458.62	459.78	200	14332	1	2
8	sample	2.05	22.34	48.66	48.74	445.61	446.57	200	14331	1	2
9	sample	1.96	21.86	47.25	47.32	448.13	448.70	200	14330	1	2
10	sample	2.21	23.20	47.98	48.04	456.18	458.11	200	14332	1	2
11	sample	3.19	93.41	204.57	204.70	990.81	992.79	200	14330	1	2
12	sample	3.33	23.47	50.77	50.86	474.11	474.60	200	14328	1	2
13	sample	2.07	131.82	297.37	297.59	701.88	703.39	200	14335	1	2
14	sample	1.96	22.44	60.29	60.38	520.83	522.76	200	14329	1	2
15	sample	2.15	21.80	56.77	56.87	498.02	500.00	200	14331	1	2
16	sample	2.17	101.91	213.91	214.11	773.50	777.83	200	14330	1	2
17	sample	2.13	21.31	47.89	47.95	498.49	500.46	200	14333	1	2
18	sample	3.10	23.30	49.37	49.47	471.30	472.82	200	14333	1	2
19	sample	2.01	22.22	48.02	48.11	447.51	449.39	200	14334	1	2
20	sample	3.37	57.26	118.49	118.63	615.25	618.85	200	14334	1	2
21	sample	2.08	60.68	131.34	131.46	695.93	698.76	200	14332	1	2
22	sample	3.11	24.40	138.42	138.56	745.36	747.56	200	14335	1	2
23	sample	2.12	22.65	56.44	56.51	484.26	486.21	200	14333	1	2

Public page /privacy, connection reused

Request	Kind	DNS	TCP	TLS	Ready to send	TTFB	Whole response	Status	Bytes	Connections	HTTP
1	warmup	2.33	101.98	212.27	212.51	874.70	876.26	200	14332	1	2
2	warmup	0.03	0.00	0.00	0.15	521.07	524.04	200	14333	0	2
3	warmup	0.05	0.00	0.00	0.22	523.51	525.29	200	14331	0	2
4	sample	0.10	0.00	0.00	0.27	521.26	522.51	200	14333	0	2
5	sample	0.04	0.00	0.00	0.16	621.68	622.88	200	14335	0	2
6	sample	0.05	0.00	0.00	0.26	513.79	518.12	200	14336	0	2
7	sample	0.04	0.00	0.00	0.19	509.64	516.04	200	14333	0	2
8	sample	0.05	0.00	0.00	0.21	507.29	514.21	200	14335	0	2
9	sample	0.05	0.00	0.00	0.22	505.98	511.39	200	14331	0	2
10	sample	0.05	0.00	0.00	0.19	517.91	523.58	200	14334	0	2
11	sample	0.06	0.00	0.00	0.21	516.32	524.00	200	14336	0	2
12	sample	0.02	0.00	0.00	0.10	515.28	518.85	200	14331	0	2
13	sample	0.04	0.00	0.00	0.17	512.73	519.73	200	14333	0	2
14	sample	0.03	0.00	0.00	0.13	537.88	544.94	200	14333	0	2
15	sample	0.04	0.00	0.00	0.16	529.80	538.98	200	14330	0	2
16	sample	0.05	0.00	0.00	0.23	510.17	521.83	200	14332	0	2
17	sample	0.05	0.00	0.00	0.24	552.01	559.32	200	14332	0	2
18	sample	0.03	0.00	0.00	0.22	510.35	518.25	200	14335	0	2
19	sample	0.05	0.00	0.00	0.21	502.39	508.98	200	14331	0	2
20	sample	0.05	0.00	0.00	0.19	519.48	527.39	200	14330	0	2
21	sample	0.05	0.00	0.00	0.21	511.51	518.96	200	14333	0	2
22	sample	0.05	0.00	0.00	0.21	520.17	523.54	200	14332	0	2
23	sample	0.02	0.00	0.00	0.09	561.72	570.39	200	14334	0	2

Public page /jobs, new connection each time

Request	Kind	DNS	TCP	TLS	Ready to send	TTFB	Whole response	Status	Bytes	Connections	HTTP
1	warmup	2.58	22.58	48.28	48.37	548.45	549.35	200	14991	1	2
2	warmup	2.31	22.64	49.56	49.64	550.86	551.36	200	14991	1	2
3	warmup	2.18	24.16	57.32	57.39	533.66	537.15	200	14991	1	2
4	sample	2.95	24.13	144.28	144.51	661.43	663.47	200	14991	1	2
5	sample	2.65	23.13	58.22	58.29	598.00	599.14	200	14991	1	2
6	sample	2.65	22.57	49.98	50.05	540.91	542.88	200	14993	1	2
7	sample	2.06	97.75	206.39	206.60	1032.18	1036.15	200	14991	1	2
8	sample	2.14	24.31	52.79	52.88	535.83	536.83	200	14992	1	2
9	sample	2.83	23.81	48.37	48.43	541.00	541.75	200	14991	1	2
10	sample	1.74	21.74	50.48	50.54	532.96	534.97	200	14993	1	2
11	sample	3.01	23.37	49.64	49.73	536.28	538.70	200	14992	1	2
12	sample	3.13	97.97	126.40	126.53	732.08	734.40	200	14992	1	2
13	sample	2.85	23.08	51.13	51.22	899.27	901.35	200	14990	1	2
14	sample	2.25	22.21	48.67	48.74	543.00	547.65	200	14992	1	2
15	sample	3.06	25.20	51.87	51.97	625.49	627.66	200	14992	1	2
16	sample	2.17	22.22	51.54	51.63	834.84	836.78	200	14990	1	2
17	sample	2.15	108.26	217.58	217.82	825.97	831.27	200	14991	1	2
18	sample	2.19	101.99	131.38	131.50	644.48	645.70	200	14991	1	2
19	sample	3.41	56.69	118.12	118.30	741.75	742.84	200	14993	1	2
20	sample	2.41	21.88	48.15	48.25	591.53	592.66	200	14991	1	2
21	sample	2.92	104.31	142.40	142.53	1371.90	1377.09	200	14990	1	2
22	sample	2.21	22.36	48.87	48.97	788.51	790.61	200	14991	1	2
23	sample	2.74	63.54	129.16	129.29	700.37	701.84	200	14991	1	2

Public page /jobs, connection reused

Request	Kind	DNS	TCP	TLS	Ready to send	TTFB	Whole response	Status	Bytes	Connections	HTTP
1	warmup	1.85	21.30	47.46	47.53	525.72	526.36	200	14991	1	2
2	warmup	0.01	0.00	0.00	0.06	498.70	499.14	200	14994	0	2
3	warmup	0.01	0.00	0.00	0.06	473.03	474.46	200	14991	0	2
4	sample	0.07	0.00	0.00	0.26	484.21	486.10	200	14990	0	2
5	sample	0.05	0.00	0.00	0.26	482.88	484.61	200	14991	0	2
6	sample	0.05	0.00	0.00	0.27	475.09	476.40	200	14990	0	2
7	sample	0.04	0.00	0.00	0.17	480.00	481.44	200	14990	0	2
8	sample	0.05	0.00	0.00	0.22	569.54	571.03	200	14991	0	2
9	sample	0.05	0.00	0.00	0.29	479.86	481.46	200	14991	0	2
10	sample	0.04	0.00	0.00	0.21	982.29	983.91	200	14993	0	2
11	sample	0.06	0.00	0.00	0.25	514.80	518.29	200	14990	0	2
12	sample	0.01	0.00	0.00	0.05	526.22	528.48	200	14991	0	2
13	sample	0.02	0.00	0.00	0.11	523.91	525.33	200	14991	0	2
14	sample	0.16	0.00	0.00	0.35	519.81	523.77	200	14992	0	2
15	sample	0.05	0.00	0.00	0.21	524.07	526.07	200	14991	0	2
16	sample	0.05	0.00	0.00	0.24	517.63	520.35	200	14992	0	2
17	sample	0.05	0.00	0.00	0.31	566.21	570.12	200	14991	0	2
18	sample	0.04	0.00	0.00	0.20	535.64	538.27	200	14992	0	2
19	sample	0.05	0.00	0.00	0.22	481.94	482.93	200	14991	0	2
20	sample	0.03	0.00	0.00	0.15	503.28	506.30	200	14990	0	2
21	sample	0.03	0.00	0.00	0.14	522.71	523.56	200	14990	0	2
22	sample	0.03	0.00	0.00	0.15	523.51	524.85	200	14991	0	2
23	sample	0.05	0.00	0.00	0.23	520.72	522.78	200	14990	0	2

Public page /employers/dashboard, signed in, connection reused

Request	Kind	DNS	TCP	TLS	Ready to send	TTFB	Whole response	Status	Bytes	Connections	HTTP
1	warmup	2.10	22.50	49.64	49.73	142.36	142.91	200	6990	1	2
2	warmup	0.02	0.00	0.00	0.09	84.85	86.12	200	6989	0	2
3	warmup	0.04	0.00	0.00	0.30	90.67	91.89	200	6989	0	2
4	sample	0.04	0.00	0.00	0.25	121.01	122.14	200	6989	0	2
5	sample	0.03	0.00	0.00	0.21	86.86	87.47	200	6990	0	2
6	sample	0.02	0.00	0.00	0.11	84.63	85.26	200	6988	0	2
7	sample	0.03	0.00	0.00	0.13	95.69	96.60	200	6989	0	2
8	sample	0.02	0.00	0.00	0.19	81.59	82.82	200	6989	0	2
9	sample	0.05	0.00	0.00	0.30	168.30	171.97	200	6989	0	2
10	sample	0.01	0.00	0.00	0.05	81.50	81.71	200	6990	0	2
11	sample	0.01	0.00	0.00	0.05	83.93	84.97	200	6988	0	2
12	sample	0.02	0.00	0.00	0.12	85.29	85.86	200	6988	0	2
13	sample	0.02	0.00	0.00	0.11	86.58	87.25	200	6988	0	2
14	sample	0.03	0.00	0.00	0.14	180.90	183.31	200	6990	0	2
15	sample	0.18	0.00	0.00	0.39	83.17	85.94	200	6988	0	2
16	sample	0.04	0.00	0.00	0.21	89.47	90.59	200	6990	0	2
17	sample	0.03	0.00	0.00	0.25	80.51	81.82	200	6988	0	2
18	sample	0.04	0.00	0.00	0.24	81.70	83.11	200	6989	0	2
19	sample	0.12	0.00	0.00	0.28	86.45	87.37	200	6990	0	2
20	sample	0.03	0.00	0.00	0.22	92.40	93.48	200	6990	0	2
21	sample	0.04	0.00	0.00	0.23	87.33	88.31	200	6989	0	2
22	sample	0.04	0.00	0.00	0.21	82.96	84.03	200	6989	0	2
23	sample	0.03	0.00	0.00	0.22	86.52	87.60	200	6990	0	2