We’ve enabled HTTP/2 on GOV.UK to help improve the site’s performance. Here we look at what HTTP/2 is, how it improves performance, and the impact it has had on our users.
GDS’s internal IT infrastructure was built to support flexible working, so here’s how we were able to adapt to a completely remote workforce.
We’ve switched to using Docker ‘containers’ for our local development environment, which has made it simpler to use and less error-prone.
Whether you’re searching for micropigs or income tax, we've upgraded the Elasticsearch database that powers GOV.UK search to make it easier to find information.
The .gov.uk domain name application guidance is the first piece of government technology content to use the new step-by-step pattern. Here’s how we made it happen and the benefits of displaying the content in this way for users.
From new development processes to cultural practices, Chris gives the lowdown on how developing at GDS is different from other organisations.
By making the switch to continuous deployment on one of the government’s busiest services, DWP has reduced downtime on Find a job and released updates faster to provide benefits to users.
The Government Digital Service recently updated guidance on frontend performance. We focus heavily on improving web performance as GOV.UK is accessed from various devices and connectivity. Here’s why you need to focus on it too.
We changed the way fonts load on GOV.UK to speed up loading times on old devices with slow connection speeds.
Service team developers no longer need to test on Internet Explorer 8, 9 and 10 (old versions of IE) when following our ‘designing for different browsers and devices’ guidance.