Why website speed is not a minor issue for the public sector
When a municipality, school or library website loads slowly, people do not call it a technical problem. They simply say: “it does not work”. And most of the time they close the window. Residents do not care whether the server is stuck or the image on the home page is too large. They need to quickly find reception hours, an application form or the events calendar.
Website speed optimisation here is directly linked to service accessibility. If parents cannot quickly open the school timetable on a phone, if a patient waits for registration information to load, if a museum visitor cannot see the opening hours before leaving — the problem is no longer only technical.
Another important layer is search. Google increasingly values real user experience, not just keywords. That is why a slow website often loses not because it lacks content, but because it is inconvenient for visitors to use. This is where Core Web Vitals come in — metrics that help show whether a page really works smoothly.
What actually slows down an organisation’s website
The most common reason is very down to earth: oversized images. An arts centre uploads a 6 MB poster file, a school adds a photo taken straight from a phone to a news item, and a municipality department puts a huge hall image on the home page. It is displayed small on screen, but the browser still has to download the whole file.
Another common problem is too much that moves, spins or loads from elsewhere. Social media plugins, maps, external fonts, videos in the hero area. Each of these elements adds extra requests. Separately, they seem harmless. Together, they already slow the whole page down.
The choice of hosting is no less important. If the website is on a weak server, speed will fluctuate even when the content itself is in order. This is felt especially during a registration peak, an admissions period or after an important announcement. Suddenly more visitors arrive at once, and the website starts to struggle.
Poor website maintenance also contributes to slowness. Modules not updated for a long time, unnecessary features, unused plugins, old scripts left behind. Over time the website gets weighed down like an office where document folders have been carried in for years, but nothing is ever thrown out.
Core Web Vitals: what is worth understanding if you are not a developer
These metrics are often discussed as if only technical people could understand them. In fact, the logic is simple. The first question is when the visitor sees the main content. The second is whether the page responds quickly to a click. The third is whether the layout shifts while loading.
If on a school website a person opens a page and first sees a blank space for several seconds, the problem is clear. If nothing happens after clicking the menu button, that is also clear. If they are about to click “Menu”, but then a promotional block or panel loads at the top and all the content shifts down — that is another example of a poor experience.
Core Web Vitals are not just numbers in a report. They describe everyday situations very precisely. That is why it is worth checking at least once a month how the website looks to a real visitor, especially on a phone. Most public-sector websites are read there today — on the bus, in a corridor, outside a doctor’s office or during a break.
What an organisation can do itself without a developer
1. Prepare images before uploading them
This is where the quickest win lies. If staff reduce the image dimensions and file size before uploading, the website becomes lighter straight away. A news item usually does not need a photo several thousand pixels wide. Often a much smaller file is enough, and it looks the same on screen.
A simple rule: if an image will be displayed at 1200 pixels wide, there is no need to upload the 4000-pixel original. It is also worth using modern formats if the system supports them. This one step often brings more benefit than long technical discussions about speed.
- Before uploading a photo, reduce its dimensions.
- Choose a file that looks good, but is not excessive.
- Do not upload posters or scanned documents as huge images if a PDF or a clearer summary can be provided.
2. Review what really needs to be on the home page
The home page often becomes a storage area for everything. Five panels, three news blocks, events, a gallery, a video, a map, a social media feed. Each section wants to be visible, and that is understandable. But the visitor rarely benefits from it.
If you are a library, a person needs opening hours, contacts, events and a link to the catalogue more than an animated background. If you are a school, parents first need admissions information, the timetable, the menu and contacts. Everything else can live on internal pages.
3. Remove unnecessary plugins and external elements
Some functions seem useful only until you measure their cost in terms of speed. For example, a live social media feed on the home page often slows loading more than it brings real benefit. The same applies to excessive animated blocks.
If an element does not help the visitor complete a clear action, it is worth asking whether it is really necessary. Website optimisation often starts not with code, but with the courage to remove what gets in the way.
4. Check the speed regularly
Even without technical knowledge, it is possible to use public testing tools. They show which pages are slow, what is delaying loading and where the problem is most obvious on a phone. It is important not just to take a screenshot once, but to monitor the change: after a new design, after a major content update, after a registration module is installed.
It is useful to check more than just the home page. Often the slowest pages are contacts with a map, news pages with galleries, or document sections with many attached files.
When it is worth calling in a specialist
Cache settings
Cache is talked about a lot, but in simple terms it is a way not to build the same page again for every visitor. If the settings are good, part of the content is delivered faster, the server is less loaded and the user waits less.
Here it is worth having someone who understands what they are doing. Poorly configured cache can show outdated content, mix up forms or interfere with certain functions. For example, if you update an urgent notice on the municipality website, you do not want a visitor to still see the old version an hour later.
Using a CDN
A CDN is useful when a website has a lot of static content — images, files, styles, scripts — and you want them to reach the visitor faster. This is especially useful when people from different locations visit the website, or when traffic is higher at the same time.
It is not necessary from day one for every small organisation. However, if the website has many photo galleries, document archives or public campaign pages, a CDN can make a noticeable difference. Properly chosen and connected to the hosting, it helps withstand the load more steadily.
Hosting review
If the website is slow even after the content has been tidied up, there is a strong chance the problem lies deeper. Weak or poorly chosen hosting often becomes an invisible brake. From the outside it looks like everything is “more or less fine”, but pages load slowly, the admin area lags and the situation gets worse at peak times.
A specialist can assess whether server resources are sufficient, whether the database is working properly and whether there are excessive requests. Sometimes changing the plan is enough. Sometimes a more serious migration is needed. The important thing is not to choose the cheapest option, but the one that matches the website’s real use.
Review of code and templates
If over the years the website has accumulated various fixes, extra blocks and temporary solutions, content clean-up alone will no longer be enough. Then it is necessary to review what loads on each page, which files are duplicated and where unnecessary requests are being made.
Such a review is especially relevant for older organisation websites that have been expanded several times but not properly reviewed as a whole. At first glance they work. Internally — they have long since been asking for a full tidy-up.
Speed and website security go together
Sometimes it seems that speed and website security are separate topics. In practice they are closely linked. An neglected, unmaintained website is more likely to slow down, more likely to fail and at the same time more vulnerable. Old components not only burden the system, but also open the door to problems that a public body really does not want to be dealing with on a Friday evening.
Security measures also need to be chosen wisely. Excessive checks or badly configured protections can slow a website down, but that does not mean they are unnecessary. They simply need to be matched to real use. A well-maintained website is usually both faster and calmer in day-to-day operation.
A simple action plan for an organisation
If you want to start without chaos, it is worth beginning not with the most complex thing, but with what gives a quick result. Usually a few clear steps are enough for the situation to improve noticeably.
- Check the 3–5 most important pages on a phone.
- Review what images are uploaded there and how much they weigh.
- Remove unnecessary blocks from the home page.
- Update the system and review what is no longer used in it.
- If the website is still slow, ask for help with cache, hosting and a deeper technical analysis.
The most important thing is not to try to solve everything at once. First sort out what can be done by the staff uploading content. Then you will see how many technical problems remain and whether broader work is really needed.
In conclusion
Website speed optimisation is not a one-off project that you do once and forget. It is more about everyday order: how images are uploaded, how much content is placed on the home page, whether website maintenance is carried out on time, and whether hosting and technical settings are reviewed regularly.
For public-sector organisations this is especially important, because the website is often the first and sometimes the only contact with a person. If it is fast, clear and stable, the visitor simply finds what they came for. And that is exactly what everyone expects from an organisation’s website — not tricks, not effects, but smooth operation.