The OLXR website has been through a substantial update over the past six weeks. The changes span new content, new features, a full performance and accessibility pass, and a number of smaller improvements that collectively make the site a more accurate and useful reflection of what OLXR does.
The site has always been bespoke - built on our own stack, hosted on AWS, and maintained directly rather than through a third-party platform. This update builds on that foundation with considerably more depth in the service and resource content, a clearer picture of how engagements are priced, and measurable improvements to how the site loads and performs.
More Service Coverage
The most significant addition is 36 new service sub-pages. Previously, the services section described OLXR's capabilities at a fairly high level. A prospective client looking for a Fractional CTO engagement, a technical due diligence review, or a CI/CD pipeline setup would land on a general consultancy page and have to make inferences about whether the work was within scope.
Each service now has its own dedicated page covering what the work involves, when it typically makes sense, and what a client can expect from an engagement. The new pages cover web application development, custom software, API integrations, database services, mobile applications, AI services, and the full range of consultancy offerings - including Architecture Planning, Code Reviews, Technology Strategy, Team Augmentation, DevOps and CI/CD, and Technical Due Diligence.
The intent is straightforward: a business with a specific need should be able to find a page that speaks directly to that need, rather than having to extrapolate from a general description of what we build.
Resources and Pricing Detail
Three new resource guides have been published to help prospective clients approach a software project with more confidence. The guides address questions that come up consistently in early conversations: what bespoke software costs and how to think about value, how to choose a software company, and how to write a useful software brief before approaching a developer. These are not sales documents - they are intended to be genuinely useful regardless of whether a reader ends up working with OLXR or not.
The resources section will expand over time. Longer-form reference content - the kind that does not fit naturally into a blog post - has a home here, and more guides are planned as the section develops.
The pricing section has been expanded with three new pages covering the different ways clients can work with OLXR - bespoke projects, time-based retainers, and partnerships.
The decision to include pricing at all was not straightforward. Publishing rates risks deterring clients before a conversation has started, and bespoke software is genuinely difficult to price without understanding the scope. At the same time, a website that gives no indication of cost forces prospective clients to invest time in a conversation before they can establish whether a project is even within budget - which is not a good use of anyone's time.
We settled on displaying ranges rather than fixed figures. The intent is to set realistic expectations without being prescriptive - giving prospective clients enough information to self-qualify, while making clear that every engagement is scoped individually. Transparency about how we work has always been part of the OLXR approach, and pricing is part of that.
New Sections
Several new sections have been added to the site. The Team page gives more context on Owen's background before founding OLXR - including experience leading a team of twelve developers, delivering high-volume enterprise platforms and payments systems, and migrating legacy systems for a major UK financial institution. For clients who want to understand the engineering experience behind the consultancy before making contact, it is worth a read.
A dedicated Isle of Man page has been added to address the practical questions that UK and European clients sometimes have about working with an Isle of Man-based consultancy - covering time zones, GBP invoicing, legal framework, and how in-person meetings work when needed. The short answer is that working with OLXR is no different in practice to working with a UK-based consultancy, and the page sets that out clearly.
The portfolio has been reframed around case studies rather than a simple project list. The current entries focus on KEEP.FIT, RepeatPosts, and DomainDasher - three products designed, built, and developed in-house by OLXR - with each write-up covering the problem being solved, the technical approach, and the current status of the product. The intention is to give prospective clients a more substantive view of how OLXR thinks through and delivers a build, rather than a list of project names. Client work will be added to the portfolio in due course, subject to client approval.
An Incubator section has also been added, where visitors can submit and vote on product ideas. It is an experiment in open idea generation and will evolve depending on how it is used.
Performance and Accessibility
The site went through a full performance and accessibility pass. Desktop Lighthouse sits at 98, with Accessibility, Best Practices, and SEO all scoring 100.
Several specific changes drove the improvement. The background video on the homepage hero - a particle explosion effect that had been in place since launch - was removed. It was visually interesting and entirely responsible for a significant chunk of the mobile load time. Homepage image cards were also addressed: blog and news thumbnails were previously loading at close to 1 MB each and are now auto-generated at a smaller size, bringing each card down to around 50 KB. The Lottie animation on the homepage now loads on desktop only, saving approximately 450 KB on mobile. The reCAPTCHA script was removed from pages without forms, where it was loading around 80 KB without serving any purpose.
On the compliance side, third-party analytics scripts - including Google Analytics and Meta Pixel - now only load after a visitor explicitly accepts cookies, bringing the site into full GDPR and PECR compliance. The cookie banner was rebuilt to meet WCAG AA contrast requirements. Heading structure was corrected across all pages, and social links were given proper aria-labels for screen readers.
A custom 404 and error page were also added - a small detail, but one that matters when a visitor ends up somewhere unexpected.
What Is Next
The mobile performance score has room to improve further and that work is ongoing. Additional blog and resource content is being published on a regular basis and will carry future announcements for anyone who wants to follow along.
If you have a project in mind or want to understand more about how OLXR works, the updated site should give you a clearer starting point. The first step is always a conversation.
Get in touch at olxr.co.uk/contact.
