Website speed is not just a technical metric. For public-sector organisations, it is a direct measure of how effectively they serve residents in the digital space. When a citizen tries to find information about social services, book an appointment or submit an application, every extra second of loading time increases the likelihood that they will leave the website without finding the information they need. In this article, we will look in detail at why website speed is critically important, how to measure it, and what practical steps can be taken to make a public-sector website fast and reliable.
How website speed affects user experience
Research consistently confirms the same trend: users expect a website to load within 2–3 seconds. According to Google, if a website takes longer than 3 seconds to load, 53 % of mobile users leave it. In a public-sector context, this means that more than half of residents trying to access important information may simply not wait for the page to load.
This is especially relevant for older people and residents in more remote regions, where internet connections may be slower. If a municipality website is heavy and slow, it discriminates against precisely those residents who need digital services most. In addition, a slow website creates a negative image of the organisation — it is associated with inefficiency and technological backwardness.
A fast website, by contrast, builds trust. When a resident clicks a link and immediately receives the information they need, they feel they have been served professionally. This reduces the number of calls to the reception desk, reduces queues and allows staff to focus on more complex questions.
Website speed and SEO: why Google rankings depend on speed
Since 2021, Google has officially included Core Web Vitals — the key web vitality metrics — in its ranking algorithm. This means that a slow website will rank lower in search results, even if its content is high quality and relevant.
The three main Core Web Vitals metrics are:
- LCP (Largest Contentful Paint) — the loading time of the largest content element. It should be less than 2.5 seconds.
- INP (Interaction to Next Paint) — the interactivity metric, measuring how quickly the website responds to user actions. It should be less than 200 milliseconds.
- CLS (Cumulative Layout Shift) — the visual stability metric. The lower, the better — elements should not jump during loading.
For public-sector organisations, SEO is especially important because residents usually search for information via Google. If a municipality website does not appear on the first page of search results, a resident may end up on an unreliable source or simply not find the information they need. Professional website maintenance includes regular speed monitoring and optimisation, ensuring that these metrics always meet Google standards.
Realistic speed standards for public-sector websites
What specific metrics should a public-sector website aim for? Here are the recommended standards:
- Full page load: up to 3 seconds on 4G, up to 5 seconds on 3G
- First Contentful Paint (FCP): up to 1.8 seconds
- Page size: up to 3 MB (ideally up to 1.5 MB)
- Number of requests: up to 50 HTTP requests per page
- TTFB (Time to First Byte): up to 600 milliseconds
Unfortunately, the metrics of many public-sector websites in the EU are well above these standards. It is not uncommon to encounter websites that take 8–15 seconds to load, weigh 10+ MB and have hundreds of unoptimised requests. This is not just a technical shortcoming — it is a direct barrier to residents accessing public services.
Main reasons for a slow website
Before optimising a website, it is important to understand what is slowing it down. The most common speed problems in public-sector websites are as follows:
Unoptimised images
This is the most common problem. A single photo can be 5–10 MB, when an optimised version would take only 100–200 KB. Organisations often upload photos directly from a camera or phone, without reducing them or converting them to a modern format (WebP or AVIF). A single page may contain 10–20 such photos, and the website becomes unbearably slow.
Outdated technology infrastructure
An old server, an unoptimised database, an outdated PHP version — all of this drastically reduces website speed. If a website runs on a server that was installed 5–7 years ago and has never been updated, speed problems are inevitable.
Too many plugins and unoptimised code
Every WordPress plugin adds additional CSS and JavaScript files. When a website runs 30–40 plugins, each page has to load dozens of extra files, which are often not even used on that particular page.
Lack of caching mechanisms
Without proper caching, the server has to generate the page from scratch every time — execute PHP code, query the database, and assemble all the content. Caching allows the already generated page to be saved and delivered quickly to repeat visitors.
Practical steps to optimise website speed
Speed optimisation is not a one-off action — it is an ongoing process. However, there are concrete steps that can deliver significant results:
1. Image optimisation
Convert all images to WebP format. Use the right size — if an image is displayed at 800 pixels wide, there is no point uploading the 4000-pixel original. Implement lazy loading — images that are not visible on the screen are loaded only when the user scrolls to them. This step alone can reduce page size by 60–80 %.
2. Server and infrastructure optimisation
Update PHP to the latest stable version (currently PHP 8.2+). Use SSD drives and ensure sufficient RAM. If the website is visited by many users at the same time, consider server scaling or using a CDN (content delivery network).
3. CDN (content delivery network)
A CDN distributes website content across a network of servers worldwide. When a resident from Vilnius accesses the website, the content is served from the nearest server rather than the main server, which may be in another country. This is especially relevant for websites with a lot of static content — images, documents and video files.
4. Code minification and optimisation
CSS and JavaScript files should be minified (unnecessary spaces and comments removed) and compressed. Unused styles and scripts should be removed. Critical CSS (required for the first screen view) should be included directly in the HTML document.
5. Caching strategy
Implement multi-level caching: browser caching (so a repeat visitor does not load the same files again), server caching (so the server does not have to generate the page every time) and object caching (Redis or Memcached). Properly configured caching can speed up a website by 5–10 times.
6. Database optimisation
Regularly clean the database — remove old post revisions, trash content and temporary data. Optimise tables and indexes. A WordPress database expands over time, and this directly affects speed metrics.
How to measure website speed
There are several reliable and free tools you can use to measure website speed:
- Google PageSpeed Insights (pagespeed.web.dev) — Google’s official tool, showing Core Web Vitals and providing specific recommendations.
- GTmetrix (gtmetrix.com) — a detailed speed test with a waterfall chart showing the load time of each element.
- WebPageTest (webpagetest.org) — a professional tool that allows testing from different locations and devices.
- Chrome DevTools — a built-in browser tool that allows you to analyse speed problems in real time.
We recommend testing the website at least once a month and after every significant change. That way, you can spot a speed regression at an early stage and fix it before it causes damage.
The impact of speed optimisation in numbers
In concrete terms, website speed optimisation can deliver the following results:
- Bounce rate decreases by 20–35 %, as users no longer leave the website before it loads.
- Page views increase by 15–25 %, as a fast website encourages browsing more pages.
- Conversion rate increases by 10–20 % — more residents complete forms and register for services.
- SEO positions improve by an average of 5–15 places in search results.
- Server load decreases by 40–60 %, as caching and optimisation reduce resource usage.
How Tobalt can help
Website speed optimisation requires technical knowledge and experience. Public-sector IT specialists often have many other responsibilities and cannot devote enough time to speed issues. It is therefore worth considering a professional website maintenance service, which includes regular speed monitoring, optimisation and technical maintenance.
If you are planning a new website or an update to an existing website, speed should be one of the main criteria from the very beginning. Check how much a modern, fast website would cost using our pricing page, or contact us directly and we will discuss your organisation’s needs.
Conclusions
Website speed in the public sector is not a luxury — it is a necessity. A fast website means better services for residents, higher positions in Google search, lower server load and a more professional image of the organisation. Investment in speed optimisation pays off quickly and provides long-term benefits both for the organisation and for the residents it serves.
Start with measuring speed — run a test with Google PageSpeed Insights and see where the biggest gaps are. Then, step by step, address the problems in order of priority. And remember — website speed is not a one-off project, but an ongoing process that requires regular attention and maintenance.