Want to know how much website downtime costs, and the impact it can have on your business?
Find out everything you need to know in our new uptime monitoring whitepaper 2021
You will have favourite websites that you return to repeatedly. They have earned loyalty by efficiently providing high-quality goods and services that meet your needs. Your website should do the same – providing a consistent and relevant user experience (UX) to your visitors and customers is vital. Here are a few suggestions to help you avoid UX errors and to create an engaging site.
Tailor content to your users
Okay, you’re thinking it’s obvious you should tailor your website’s content to meet your user’s needs but unfortunately many companies still focus more on SEO issues, such as keyword placement and page optimisation, when creating content. SEO is important but it is only effective if your content resonates with people who visit your site. In its Webmaster Guidelines, Google’s first principle tells you to design your web pages primarily for your users, not for search engines.
Clearly define what your business does
One of the first things visitors should see when accessing your site is a clear statement of what your company does. People come to your site with a purpose in mind, and if they can’t quickly determine if your site meets their needs, they will leave and look elsewhere, possibly never to return. Sometimes you only get one chance to gain a customer, so don’t frustrate potential customers by making them search through multiple pages to figure out what you do.
Provide an aesthetically pleasing site
You want your visitors to have a memorable experience but you want it to be memorable for the right reasons.
Use layouts with a mix of text and eye-catching graphics and photos. A site with many pages that only contain text will not keep a visitor’s attention for very long. Check your color scheme to ensure the colors are compatible with each other and don’t detract from text readability and image visibility.
Don’t use stock photos – they’re easy to spot, and you will give your visitors a poor impression of your business. Be sure that any photos you do use are high quality and appear up-to-date.
Don’t overwhelm your visitors with call-to-action (CTA) buttons – use them strategically by placing them at logical decision points on your site.
Reduce page load times
Visitors will not stick around if your site loads slowly, so you should monitor page load times to be sure your site loads quickly and provides a high-quality UX. If you find that it’s taking more than three seconds for your site to load, there are several steps you can try to improve load times short of doing a complete website redesign.
Image files can cause pages to load slowly, so consider using an image optimisation tool to compress the size of your image files before you add them to your site. The size of pages with high-quality content can exceed 100kb, so consider compressing them to reduce bandwidth and improve your page load times.
Plugins also can cause slow page load times. If you have numerous plugins on your site, experiment with disabling some of them to see if they are the cause of your slow load times.
Sometimes we are so concerned about SEO that we don’t spend enough time optimising our website’s UX. We need to remember how valuable a positive UX is in today’s competitive online marketplace.
StatusCake Team
Share this
More from StatusCake
Designing Alerts for Action
3 min read In the first two posts of this series, we explored how alert noise emerges from design decisions, and why notification lists fail to create accountability when responsibility is unclear. There’s a deeper issue underneath both of those problems. Many alerting systems are designed without being clear about the outcome they’re meant to produce. When teams
James Barnes
February 18, 2026
A Notification List Is Not a Team
3 min read In the previous post, we looked at how alert noise is rarely accidental. It’s usually the result of sensible decisions layered over time, until responsibility becomes diffuse and response slows. One of the most persistent assumptions behind this pattern is simple. If enough people are notified, someone will take responsibility. After more than fourteen years
James Barnes
February 11, 2026
Alert Noise Isn’t an Accident — It’s a Design Decision
3 min read In a previous post, The Incident Checklist: Reducing Cognitive Load When It Matters Most, we explored how incidents stop being purely technical problems and become human ones. These are moments where decision-making under pressure and cognitive load matter more than perfect root cause analysis. When systems don’t support people clearly in those moments, teams compensate.
James Barnes
February 4, 2026
The Incident Checklist: Reducing Cognitive Load When It Matters Most
4 min read In the previous post, we looked at what happens after detection; when incidents stop being purely technical problems and become human ones, with cognitive load as the real constraint. This post assumes that context. The question here is simpler and more practical. What actually helps teams think clearly and act well once things are already
James Barnes
January 28, 2026
When Things Go Wrong, Systems Should Help Humans — Not Fight Them
3 min read In the previous post, we explored how AI accelerates delivery and compresses the time between change and user impact. As velocity increases, knowing that something has gone wrong before users do becomes a critical capability. But detection is only the beginning. Once alerts fire and dashboards light up, humans still have to interpret what’s happening,
James Barnes
January 21, 2026
When AI Speeds Up Change, Knowing First Becomes the Constraint
5 min read In a recent post, I argued that AI doesn’t fix weak engineering processes; rather it amplifies them. Strong review practices, clear ownership, and solid fundamentals still matter just as much when code is AI-assisted as when it’s not. That post sparked a follow-up question in the comments that’s worth sitting with: With AI speeding things
James Barnes
January 14, 2026