When the website starts getting in the way
Nebraska Music tells stories about music: artists, albums and the world around them. Its author wanted to keep focusing on those articles, but the website was making that harder.
Some pages were slow to open, and working in the WordPress dashboard felt sluggish too. He also had concerns about website security. He contacted us to understand what was happening and see how we could help.
Starting with the delays he was experiencing
We started with what he was experiencing: which pages were slow, what he was doing and when the wait occurred. The homepage, longer articles and WordPress dashboard behaved differently, so we reviewed each situation separately.
We found images with unnecessarily large file sizes and no specified width or height to reserve space as they loaded. We also examined files from external services and the processes involved in using the dashboard. These checks helped us narrow down what needed attention.
Checking what the website revealed to visitors
Alongside the delays, we checked which technical details someone could see without logging in. Some information made it easier to identify how the website was built and did not need to be public.
We assessed what each finding meant and which settings needed attention. Identifying a piece of software does not prove it is vulnerable; we needed to understand the risk for this website and decide what to address first.
Turning the findings into changes
We used the review to prioritise improvements according to the problem they addressed and the work needed to make them. Larger changes remained separate proposals, with time to consider them before deciding.
We made performance and security improvements in small batches. These included reducing technical information the website made public unnecessarily. After each batch, we checked the result before continuing.
Throughout the work, we kept the author’s use of the blog in mind: he needed to keep preparing and publishing articles. The changes had to fit around that work.
Returning to the website to check the difference
After the changes, the pages we reviewed and the WordPress dashboard felt more responsive in use. This was an improvement we noticed while using the website; we do not have timings measured under the same conditions before and after.
We also repeated the external security review and confirmed that the priority problems we had worked on had been corrected. That check covered those specific points, without treating the rest of the website as reviewed.
Is your website making things harder too?
Perhaps a page takes too long to open, working on your website has become frustrating or you have questions about its security. Tell us what is happening and we can work out where to start with you.
To learn more about our work, take a look at what we review in website performance and security.