Personal websites have a habit of becoming collections of earlier decisions. A theme chosen years ago. A plugin installed to solve one problem. A gallery that worked perfectly until the thing responsible for displaying it disappeared.
Eventually, you look around and realise the website still exists, but it no longer feels like somewhere you particularly want to spend time.
That was where I’d got to with infinitelypointless.
The posts were still mine. The interests behind them hadn’t gone away. But the presentation needed attention, and there was plenty behind the scenes that deserved a closer look too.
I wanted to give it a fresh start while keeping its history.
A home for whatever catches my attention
This site has never had a particularly narrow brief. Technology, photography and field archery are recurring subjects, but there have also been renovations, practical projects and occasional complaints about things that probably worked better in the brochure.
I like having somewhere for all of that.
The challenge was making those different interests feel comfortable together. I wanted the site to be easy to explore without forcing everything into the same format or pretending there was a grand editorial strategy behind every post.
“Endless curiosity” felt like a reasonable description of what connects it all. There is usually something to investigate, try, photograph, improve or become mildly irritated by.
The name infinitelypointless still suits that rather well.
Making some room
The visual direction became simpler: a warm, pale background, dark text and a restrained teal accent. Clear typography, fewer competing elements and enough space for the content to breathe.
The homepage now brings together a handful of selected stories, routes into the main topics and a list of recent writing. It gives visitors a few ways in without presenting everything at once.
I’ve also settled on “Notes” for the collection of posts. It feels suitably broad for a mixture of longer articles, practical observations and things I wanted to write down before forgetting them.
Some of the smaller decisions took a surprising amount of attention. A heading can be technically correct and still look far too large. A menu can work on the homepage and pick an entirely different set of links on an error page. A logo that looks fine in the header can become an enormous crop of a few letters when somebody shares the site.
Those details are easy to overlook until you start checking them.
Keeping the history
An important part of the rebuild was preserving the existing posts, their addresses and the discussions attached to them.
Older writing is part of the point of a personal website. Some of it captures a particular moment; some may still help someone trying to solve an obscure problem years later. I didn’t want a visual refresh to become an excuse to throw that away.
There were a few things worth retiring, though.
The old photography galleries depended on NextGEN Gallery. With the plugin removed, the pages were displaying shortcodes instead of photographs. That is a fairly clear sign that something needs a decision.
I chose to remove those obsolete gallery pages. My photography portfolio has a separate home, while photography-related writing still belongs here. The photographs used in existing articles remain in place.
It was a useful reminder that keeping old content and keeping every old feature are separate decisions.
Checking what the browser actually does
The privacy work turned into one of the more revealing parts of the project.
Putting a consent banner on a website is straightforward enough. Establishing whether the site follows the choice made in that banner takes more effort.
I checked the browser’s network requests before accepting optional tracking, after accepting it and after withdrawing consent. During that process, I found an additional analytics service associated with a plugin I no longer needed. It was sending a tracking request before any choice had been made.
The plugin went.
Jetpack statistics then passed the sequence I wanted to see: no statistics request before consent, a request after acceptance and none after rejecting optional tracking and reloading.
The banner also gives acceptance and rejection equal prominence. Visitors can change their choice later, and the language is more direct than the generic wording I started with.
Fonts needed attention as well. Source Sans 3 is now hosted locally. Tracking down the final Google Fonts reference took a little persistence: the main typography settings were correct, but a separate form-field setting was still requesting it.
That experience sums up quite a lot of website maintenance. The setting you changed is correct. There is simply another setting somewhere else.
Less machinery, better results
I also reviewed the plugins and removed several that were no longer needed.
That included the caching plugin. Page caching can be useful, but I wanted to measure the current site and understand its behaviour before adding more configuration.
One clear issue appeared in the performance tests: the server was sending the homepage HTML without text compression.
Apache already had the required module available. After enabling gzip for text-based responses, I confirmed that the server was delivering compressed HTML and ran the tests again.
Across the combined changes, the homepage’s mobile PageSpeed performance score improved from 83 to 93. Its desktop score reached 100.
The sampled article scored 97 on mobile, and the Notes archive scored 98. Both scored 100 on desktop.
Those are Lighthouse lab results from 19 November 2026, rather than a promise about every visit on every device. They also reflect several changes together, so I can’t assign the entire improvement to compression.
They do give me a useful baseline—and a good reason to stop adjusting things for the sake of another point.
The checks beyond the homepage
The rebuild also meant spending time on less glamorous pages and behaviours.
Does the missing-page screen return an actual 404 response? Can its search box find an article? Can you move through the navigation and consent controls using a keyboard? Do the cookie-policy tables fit on a phone?
An accessibility check on an article found a linked signature image without a useful link name, along with a section heading that skipped heading levels. Both were fixable content issues.
The automated checks were useful, but so was simply opening pages, following links and seeing where things felt wrong.
There is no substitute for using the website you’ve just built.
More to come
There is still work to do. The logo needs its final artwork, older content needs an ongoing review, and there are small improvements I’ll return to as I use the site.
For now, infinitelypointless feels like somewhere I can get on with writing again.
The subjects will probably remain as varied as ever. Technology will continue to provide problems to investigate. Photography will continue to get me looking at things more carefully. Archery will continue to offer opportunities to discover that knowing what went wrong and preventing it next time are different skills.
And whatever else catches my attention will probably find its way here too.
Until next time, stay curious.


