Objective
Keep the website they knew. Make it safe to run.
Inchicore College teaches further education in Dublin 8: art, design, theatre, costume, dance, healthcare, business and more, by day and at night school.
Its website did its job, but it had been built around 2016 and never updated since. Each year, about 500 applications arrive in six to eight weeks, and the site has to hold up for all of them.
The brief was simple to say: keep everything students and staff already know, and make it safe, fast and easy to look after.
Approach
First, a proper check-up.
We started with an audit. The website ran on a version of WordPress released in 2016, on server software that had stopped receiving security updates years before. Nothing had been updated since the day it was built.
That matters more than it sounds. Old software can’t take new security fixes, so every month the gap grows. Here it had grown so wide that current WordPress, current plugins and even the tools that check a site’s health could no longer be installed.
It was a ten-year-old car getting its first NCT.
What the health check found.
-
2016
The WordPress release the site was built on, never updated since
Hidden Depth health check -
19
Plugins with publicly known security holes
Hidden Depth security scan -
12.8s
For the homepage to finish loading
GTmetrix -
1,500
Links typed into the code, so every change to one meant paying a developer
Hidden Depth code review
Solution
Rebuild the engine. Keep the face.
The site was too old to move as it was, so we rebuilt it. Every template was recoded from scratch on Omnia, our own WordPress framework, on current WordPress and PHP. Then we took it over from its previous host and moved it onto our managed WordPress hosting, with every update and the care plan handled for the college.
On screen, nothing changed. Students found the same pages, the same courses and the same Apply Now button in the same place. That was the point.
Underneath, the menu now lives in one place instead of seventeen. Just under 1,500 hard-coded links were rewritten so they can be changed from WordPress, not from code. Every plugin with a known security hole went, replaced by well-maintained plugins or code we wrote ourselves. And the clutter of ten years went: old pages retired, unused files cleared, broken image links mended.
Results
The homepage took 12.8 seconds to load. Now it takes half a second.
Twenty-five times faster. The new code and our hosting, working together, and nothing on screen redesigned to get there.


Two screenshots of the same page. Before: 12.8 seconds to load. Now: 0.5 seconds. The same page, before and after the rebuild.
Safer, faster, and theirs to change.
-
0
Plugins with known security holes, down from 19. The rest are well-maintained or our own code
Hidden Depth security scan -
99
Google performance score, up from 44
Google Lighthouse -
85
Google accessibility score, up from 69, with nothing on screen redesigned
Google Lighthouse -
0
Developers needed to change a link. The college does it in WordPress
Looked after, every day since.
Since the site moved onto its new foundations, the college hasn’t had to think about updates, hosting or security. That’s our job now.
One day
A serious vulnerability is published in PHP, the language most of the web’s servers run on.
That same evening
The college’s site was patched the moment the fix was released.
That is what the rebuild bought: a website that can take the next fix, and someone watching for it.
