What this website is made of
The site you are reading went live on papush.ro today. A look inside: what it is built from, how a change reaches the live site, and what launch day measured.
Plain files, nothing else
The site is plain HTML and CSS with a little vanilla JavaScript. No frameworks, no libraries, no third-party scripts. No jQuery, no cookies, no fonts from someone else's server.
The CSS and JavaScript live inside the HTML file. A page is one file, plus fonts, plus a photo.
It is hosted on Cloudflare Workers as static assets. Cloudflare runs more than 300 data centres, and the page comes from the one closest to you. The fonts are self-hosted: Pangea by Fontwerk. Images are WebP.
Visits are counted on Cloudflare's servers, not in your browser. No analytics script, no cookie, nothing to consent to — and no banner asking you to.
No server code at all
An earlier version of this note described one small worker that turned links into pre-written WhatsApp messages. The worker is gone, and the buttons with it. Nothing executes on a server when you open a page: the files are copied to your browser, and that is the whole transaction.
Contact is e-mail now: mihai@papush.ro. Cloudflare Email Routing receives it and forwards it on — MX records and a forwarding rule, no code.
The address sits in the page as HTML character entities. Browsers decode them; most address-harvesting bots do not. A long-running honeypot experiment puts the cut at roughly 96–99% of harvesters. The build does the encoding, so the source files stay readable.
A build that can say no
There is still no bundler. No webpack, no Vite, no node_modules. The code I write is the code your browser gets — almost. The production build strips developer comments, encodes the e-mail address, turns working file names into clean addresses and fills in page metadata. It rewrites plumbing, not content.
Notes like this one live as HTML fragments with a small JSON file each. A Node script with zero dependencies, about 190 lines, stamps them into finished pages.
The production build is a PowerShell script with guards: trial fonts, forgotten draft links, WhatsApp leftovers, stray to-do marks. Any guard that trips stops the build, and a stopped build cannot deploy.
It also writes a headers file for Cloudflare. The part that tells browsers to keep fonts and images for a year:
/fonts/*
Cache-Control: public, max-age=31536000, immutable
/img/*
Cache-Control: public, max-age=31536000, immutable
The price of immutable: a replaced image gets a new file name.
Deploying is one command, wrangler deploy. The build runs by itself first; saved file to live site takes about twenty seconds. A typical text change — a price, opening hours, a paragraph — is 2–5 minutes of work, including a check on the live site. That's from daily practice, dozens of deploys.
The staging copy on workers.dev sends a noindex header, so search engines ignore it. The header is keyed to workers.dev hosts only; papush.ro never sends it.
What launch day measured
The home page after the production build: 18.4 KB of HTML, with all styles and scripts inside.
A first visit costs about 129 KB in 5 requests on a phone, and about 161 KB in 6 requests on a desktop: the HTML, the fonts, a 48.8 KB photo, the favicon. The footer on the home page says "This page: 6 requests · 161 KB". The build counted that — a measurement, not a forecast.
Timing of the first-ever visit to the live domain, measured from a desktop browser in Oradea — phones on mobile networks will see higher numbers:
- Server response (TTFB): 138 ms.
- Load event: 283 ms.
- First paint: 360 ms.
Paint comes after the load event here, and that is expected: the fonts load with font-display: block, so the browser holds the first paint until they arrive instead of flashing a fallback.
For comparison, the median web page weighs about 2,500 KB, according to the HTTP Archive.
The fonts were the heavy part
The September version of this note ran on Pangea's trial files: 705 KB of fonts, most of the roughly 800 KB a first visit cost back then. It made a forecast: 80–110 KB of fonts and 170–190 KB for a first visit, once the licence was bought and the fonts were subset.
The licence was bought on 30 September. A small Python script now cuts each weight down to what the pages actually use — Latin, Romanian diacritics, a few arrows — and lands at 29–33 KB per file. A phone loads Regular and Bold: 62 KB. A desktop adds Medium: 94 KB. SemiBold is licensed too, but unused; everything bold on the site is Bold.
So the forecast held, with room to spare: 62–94 KB of fonts against the predicted 80–110, and 129–161 KB for a first visit against 170–190.
One more font decision: the 404 page loads no web fonts. A mistyped address gets system fonts; it isn't worth 62 KB.
The 4.5-second problem, in the past tense
In September, PageSpeed Insights reported a mobile LCP of 4.5 seconds on staging. Two causes, both since removed: the 705 KB of trial fonts on the critical path, and a photo preload that went out with low priority, behind the fonts. One attribute fixed the photo:
<link rel="preload" href="img/mihai.webp" as="image" fetchpriority="high">
That alone took the LCP in PageSpeed from 4.5 to 3.0 seconds. The font subset removed the rest of the weight: 62–94 KB where 705 used to be.
On launch day, PageSpeed ran against the live domain: a mobile performance score of 100, LCP at 0.4 seconds. From 4.5 to 0.4 — that was the fonts, almost entirely.
Why this matters if you own a business
- Nothing to break. No plugins that go out of date, no platform to update, no server code to fail.
- Any developer can continue. Whoever comes after me opens the code and keeps working.
- Light on a phone. The code of the whole page is smaller than one photo in a chat.
Don't take my word for the numbers. Open your browser's developer tools and look at the Network tab. The weight and the requests are right there.