As the subject of over 100,000 Google searches a month, we know people are still looking to GOV.UK for information on coronavirus. So when we discovered the page was not meeting changing user needs, we made some improvements.
We’re always looking to improve GOV.UK for users, including government publishers. Here is how we identified some of the next improvements to the publishing experience.
We simplified our address finding system using the Ordnance Survey’s Places API. Here’s how we did it and the impact it’s had on GOV.UK and its users.
On September 30th certain users were being prevented from accessing files hosted on GOV.UK. Here is an explanation of what happened and how we resolved the issue.
We strive to make GOV.UK the most user friendly site possible. Here is how we improved subtopic pages to meet user needs better.
Moving across to Google Analytics 4 is a major project. Here’s how we did it and what we’ll be doing to ensure minimal impact to the performance of GOV.UK.
GDS and DLUHC worked together to develop a smart answer to help users find out how much they might have to pay to remove cladding, or make their building safe.
There’s a new and improved campaign template for communicators across government to use on GOV.UK. Read what’s changed and how we’ve tested it.
Moving across to Google Analytics 4 is a major project. Here’s how we’re preparing for the move.
In this blog post, we explain the technical details of removing the jQuery library from GOV.UK’s public facing applications and the performance impact it had for our users.
Removing jQuery from GOV.UK was a huge yet manageable task that led to improved code and performance gains across the site. This is how and why we did this work.
Read the GOV.UK roadmap to find out what the GOV.UK team are working on. It shows what we’ve recently shipped, what we’re working on and what we’re looking into.
Subscribe to Inside GOV.UK to keep up to date with our work