Skip to main content

~/proof

Proof

Anyone can write “tested” and “fast” on a portfolio. These are this site's own numbers, written by its pipeline after each change to the main branch. Nothing here is typed by hand.

unit tests
270 / 270
all passing · 45 files · 38 min ago
end-to-end tests
141
browser tests in 22 files, including an accessibility scan of every public page · 38 min ago
ci on main
failure
typecheck, lint, unit and browser tests · run #34 · ba8b0ca · 1 h ago
daily backup
passing
2.9 MB encrypted, database and files · run #2 · 312a7a0 · 13 h ago
database round trip
225 ms
median of 5 from this server · slowest 229 ms · just now
dependencies
16 / 50 current
20 a breaking version behind (@fullcalendar/core, @fullcalendar/react, @tiptap/extension-image, @tiptap/extension-link, @tiptap/extension-placeholder, @tiptap/pm, …) · 38 min ago
shared javascript
87.7 kB
loaded by every page, before page code · 38 min ago

JavaScript per page

First load, as reported by the production build of 20e7e62. Heavier pages are heavier for a reason: the home page carries the query console.

pagepage codefirst load
/0.16 kB141 kB
/for/[role]0.16 kB141 kB
/id0.16 kB141 kB
/match4.63 kB133 kB
/contact0.21 kB131 kB
/id/contact0.21 kB131 kB
/id/projects0.15 kB131 kB
/projects0.15 kB131 kB
/architecture1.51 kB130 kB
/articles/[slug]1.81 kB130 kB
/id/articles/[slug]1.81 kB130 kB
/about0.69 kB129 kB
/articles0.7 kB129 kB
/id/about0.69 kB129 kB
/id/articles0.7 kB129 kB
/id/projects/[slug]0.7 kB129 kB
/offline0.81 kB129 kB
/projects/[slug]0.7 kB129 kB
/cv0.22 kB128 kB
/id/cv0.22 kB128 kB
/login0.2 kB128 kB
/privacy0.22 kB128 kB
/proof0.22 kB128 kB

How to read this

  • Test counts and bundle sizes come from running the test suite and the production build in GitHub Actions on the main branch.
  • The browser tests that need real data run on my machine before a merge; in CI they run against a deliberately unreachable database, which also proves the public pages survive an outage.
  • The backup is a nightly encrypted dump of the database and every uploaded file, restored into a clean server once to check it works.
  • The database round trip is timed by the server that rendered this page, when the page data was last refreshed. To time one yourself, send a request through the site.