What a cutting-edge website shares with a car, part 1: infrastructure
A fast car and a good website have something in common: what you see is the least of it. Under the paint there is a frame, an engine, brakes and a mechanic who knows them. This is the first of a short series on that comparison, and it starts at the bottom, with the part of a website you never see: its infrastructure.
The frame: where the site lives, and whose name is on it
A car’s frame decides what it can carry and how it behaves at speed. A website’s frame is its hosting: the servers it runs on, the account they sit in, and the domain that points to them.
The first question is not speed. It is ownership. Whose name is on the hosting account and on the domain? On white-label work for agencies, the sites stay in the agency’s own Kinsta account and we work inside it. We think that is right for any owner: the account in your name, and whoever maintains the site invited as a user. A car registered to the mechanic is not your car.
The engine: what turns a request into a page
When someone opens a page, a server has to build it or hand over a stored copy. Managed hosting looks after the engine for you: the server software, the database, the stored copies at the edge of the network that make a page arrive quickly.
Stored copies have a catch. After we changed a setting on our own blog, the home page kept serving the old version for five minutes, because a copy at the edge had not yet been replaced. We only saw it because we checked two addresses, one that skips the stored copy and one that does not.
The brakes: backups and the way back
You do not notice brakes until you need them. A site’s brakes are its backups and a written way back.
Two things matter. The backup has to exist before a change starts, with its time written down. And it has to still exist when you need it: a manual backup on managed hosting can expire. Ours had a date on it, and we made our own copy before it ran out.
The test track: staging
Nobody tests new brakes on the highway. A staging copy of the site is where changes that could take it down are rehearsed first: updates, template changes, anything that touches caching. It does not catch everything. When our staging rehearsal of a security change on our own blog could not settle the question, we reported it «inconclusive», not «pass», and the edge-cache delay above only showed up on the live site.
The mechanic
A frame, an engine and brakes still need someone who checks them on a schedule and writes down what was done. Our routine is in How we maintain WordPress sites on Kinsta, in the order we follow it.
Four questions to ask about yours
- Whose name is on the hosting account and the domain?
- When was the last backup, where is it, and when does it expire?
- Is there a staging copy, and was it used for the last update?
- Who checks the site after a change, and how do they read it as a visitor would?
Next in the series: marketing, the fuel. If you want someone to look under your site’s hood, talk to us.
Gráfica built this survey as a WordPress plugin, and builds plugins like it for clients. Tell us what your site needs