Blue Penguin Digital Blue Penguin Digital
Case Study · Digital Transformation

19 years of trust.
A website that looked stuck in 2013.

How we rebuilt Accudo's digital front door to match the quality of their recruitment work.

19+ years in business
2006 founded
0 plugin dependencies
The Problem

Great recruiters, outdated first impression

Meet Adam. He founded Accudo in 2006 and built a reputation on relationships, integrity, and getting placements right.

The problem was simple and painful. The old WordPress setup no longer reflected the quality of the business behind it. On paper, Accudo was experienced and trusted. Online, the first impression felt dated.

For a recruitment company, that gap matters. Senior candidates judge quickly. Hiring managers do too. If the website feels old, people assume the service is old as well.

What was holding them back

  • Legacy WordPress and ageing PHP support concerns
  • Ongoing maintenance overhead for a brochure-site
  • Slower, heavier delivery than necessary
  • Brand presentation didn't match real-world credibility
  • Avoidable CMS exposure with no business upside
The Strategy

The Human Signal: "Professional, Ethical, Personal"

"People still buy from people." That was the centre of this one.

The look

Accudo's brand is warm and professional, not corporate theatre. We leaned into clean space, confident typography, and one strong visual anchor instead of stuffing the page with effects.

The voice

Adam and Charlie already had a clear tone — straight-talking, ethical, and personal. We kept that voice intact and let structure do the heavy lifting.

The goal

Make the website feel like a proper extension of how they work with clients and candidates in Bristol — not a generic recruitment template.

The Solution

The Rebuild Engine: Static, Secure, and Easy to Trust

The WordPress Trap

The Jargon: "Dynamic CMS rendering with plugin dependency chain."

The Reality: Every time a visitor loaded a page, the server rebuilt it from scratch using a CMS admin layer and a chain of third-party plugins nobody wanted to update.

Slower delivery, avoidable CMS exposure, ongoing maintenance drag.

The Static Advantage

The Jargon: "Static-first delivery with no CMS runtime."

The Reality: We rebuilt the site as static HTML with Tailwind CSS and vanilla JavaScript, served through Apache. Pages pre-built and ready instantly. No CMS admin layer. No plugin chain. No database connected to the public web.

A fraction of the load time. Dramatically reduced attack surface.

Winston

Developer Insight // Winston

"The best performance win here wasn't a trick. It was removing unnecessary moving parts. Static pages, local assets, and sane cache headers beat plugin roulette every time."

The Shield

Reducing the runtime surface while tightening what remains.

Server-Level Controls

Canonical HTTPS host redirects at Apache level. CSP controls. Clickjacking protection via X-Frame-Options. MIME sniffing protection via nosniff. Strict referrer policy across all pages.

Page-Level Metadata

Canonical URLs on key pages. Open Graph and Twitter card fields. EmploymentAgency structured data on the homepage. Robots.txt and sitemap.xml retained for crawl clarity.

The Engineering

0kb Video.
100% CSS3.

This was the design stress test. Could we make the hero feel polished without shipping a heavy animation stack?

Yes. We built a layered, animated Orb in pure CSS and HTML, then kept interactions in vanilla JavaScript. That gave Accudo a distinctive visual identity while protecting first-load weight and keeping long-term maintenance simple.

A typical 10-second background video can weigh 2MB+. This entire orb — radial gradients, pseudo-element sheen, layered inner spheres, three independent keyframe animations — is pure CSS rendered by the browser's compositor. No video. No JavaScript. No CDN dependency.

RENDER: CSS3
The Outcome

The Upgrade in Numbers

Legacy Architecture vs Blue Penguin Build

01

Architecture

Before: WordPress with dynamic runtime

After: Static HTML with Tailwind build pipeline

02

Security

Before: CMS exposure, ageing PHP concerns

After: Reduced runtime surface, tighter headers, HTTPS enforcement

03

Maintenance

Before: Ongoing CMS/plugin updates

After: Lower maintenance for a brochure site

Back to recruitment, not website firefighting

Adam and Charlie can focus on people, placements, and client relationships instead of worrying about whether a plugin update will break something.

The new site does one job clearly. It presents Accudo as the experienced, ethical recruitment partner they already are.

Under the Bonnet

The Tech Specs

Custom-built for speed. No bloat. No shortcuts.

tech-specs.yaml
project: Accudo Solutions Website Rebuild
build_type: Static multi-page marketing site
business_context: IT recruitment & HR consultancy in Bristol

stack:
  frontend: HTML5
  styling: Tailwind CSS (CLI build)
  scripting: Vanilla JavaScript
  server: Apache with .htaccess rules
  icons: Lucide (self-hosted)

delivery_model:
  cms: none
  runtime_database: none
  plugin_dependency_chain: none

security_controls:
  canonical_https_redirect: enabled
  csp: enabled (self + map allowance)
  x_frame_options: SAMEORIGIN
  x_content_type_options: nosniff
  referrer_policy: strict-origin-when-cross-origin

seo_foundations:
  canonical_tags: present
  open_graph: present
  twitter_cards: present
  schema: EmploymentAgency JSON-LD
  robots_txt: present
  sitemap_xml: present
Behind the Build

Engine Room: How We Built It

01

The Stack

Static, multi-page HTML served via Apache. Styling via Tailwind CLI pipeline. Interaction in vanilla JavaScript. Lucide icons served locally — not from a third-party CDN.

Static delivery removes unnecessary server-side processing and gives tighter control over payload, caching, and uptime.

02

The Hardest Hurdle

Replacing a legacy CMS-era setup without losing crawl clarity or trust signals, while tightening delivery controls. Coordinated updates across redirects, canonical tags, robots directives, sitemap entries, and page-level metadata.

03

The Performance Flex

  • No CMS runtime or plugins in production
  • Minified CSS via production build script
  • Scoped Tailwind content scanning
  • Browser cache policy for static assets
04

The How (NLP/SEO)

Static-first request path with canonical host enforcement at Apache level. Indexable metadata in server-rendered HTML: canonicals, OG/Twitter cards, and EmploymentAgency structured data. Crawl essentials retained through robots and sitemap files.

Ready to close your credibility gap?

If your business has outgrown its old site, let's build a cleaner engine behind your brand.