WordPress Development, Migration & Performance

Built well. Migrated without regret.

The dev side of WordPress — new builds, careful migrations, performance work, and the unglamorous engineering that keeps a site fast, secure, and indexable for years. We do it ourselves, and we leave the keys with you.

Stack and craft · GeneratePress · GenerateBlocks Pro · Yoast SEO · WPForms · Wordfence · Custom Themes · Plugin Development · Performance Tuning
01 — What’s Included

Six layers of WordPress
work, done in-house.

WordPress is the platform we work with most days of the week. We know its strengths, its quirks, and exactly where things go wrong when the basics are skipped. The sub-disciplines below cover the full life of a WordPress site — from a clean first build, through ongoing optimisation, to a careful migration when the time comes.

This is the development side of Web Design & Development. For the platform-buyer view, see our WordPress technology page.

N° 01

New WordPress builds

Foundational

Every site we build starts with a clean, performance-first architecture. We use GeneratePress as the theme framework paired with GenerateBlocks Pro for layout — a combination that produces sites with minimal DOM complexity, fast load times, and zero dependency on bloated page builders. The result is a site that scores well on Core Web Vitals out of the box, rather than one that needs months of optimisation just to reach acceptable performance. Caching, image handling, structured data, and security baselines are configured during the build, not bolted on afterwards. We hand over a site that is ready to rank, not one that needs another agency to come and fix the foundation.

N° 02

Custom theme development

Design control

We develop custom child themes built on GeneratePress and GenerateBlocks Pro — a lightweight, block-based stack that gives full design control without the overhead of traditional page builders. Your site’s design is expressed in clean, semantic HTML and well-organised CSS rather than layers of shortcodes and nested wrapper divs. Theme work includes custom block patterns for repeating layouts, site-wide design tokens for consistent typography and colour, and responsive behaviour that holds up on every screen. When your content team needs to update a page, they work with intuitive block controls — not fragile builder interfaces that break the next time a plugin updates. Child-theme structure ensures your customisations survive parent-theme updates without manual intervention.

N° 03

Plugin development & audits

Code-level work

Most WordPress performance and security problems trace back to plugins — too many of them, poorly coded ones, or abandoned ones that have not been touched in years. A plugin audit examines every active and inactive plugin against criteria that matter: code quality, update frequency, known vulnerabilities, performance impact, and whether the plugin is actually necessary or whether its function can be handled natively or by a lighter alternative. Where the right answer is a small custom plugin rather than a heavyweight off-the-shelf one, we write it ourselves — a tight, well-scoped piece of PHP that does exactly what your site needs and nothing more, version-controlled and documented so the next developer can read it without reverse-engineering.

N° 04

Performance optimisation

Speed & Vitals

Performance optimisation is not about installing a caching plugin and hoping for the best. It is a systematic process that addresses server-side response time, database query efficiency, asset loading strategy, image delivery, third-party script management, and front-end rendering. We configure proper server-level caching — FastCGI or Redis object caching depending on the hosting environment — clean transients and autoloaded options, lazy-load images and iframes, defer non-critical JavaScript, and eliminate render-blocking CSS. Every optimisation is measured with before-and-after Lighthouse scores and real-user metrics from Core Web Vitals. The goal is not a perfect synthetic score; it is a site that loads quickly for actual visitors on actual devices and network conditions.

N° 05

Migration to WordPress

From Wix · Squarespace · legacy CMS

Moving to WordPress from another platform — Wix, Squarespace, a legacy CMS, or a static HTML site — requires careful planning to preserve search equity and avoid broken links, missing content, and lost rankings. We handle the full process: content extraction and mapping, URL structure planning with proper 301 redirects from every old URL to its new equivalent, media migration with proper file naming, SEO metadata preservation, and post-migration verification. We monitor rankings closely for the first sixty days and address any drops immediately. A well-executed migration should leave search performance intact or better — never a ranking cliff. See also our companion Website & Performance Auditing discipline for pre-migration audits.

N° 06

Security hardening

Layered defence

Security is not a single plugin — it is a layered approach to the most common attack vectors. We start with the fundamentals: keeping core, themes, and plugins updated; enforcing strong authentication with two-factor where possible; removing default admin usernames; restricting file permissions. Beyond the basics, we implement HTTP security headers, disable XML-RPC if it is not needed, restrict REST API exposure, configure CORS policies, set up automated malware scanning, and establish a backup regime that is tested for restore — not just for taking. We also review your hosting environment: server software versions, PHP version, SSL configuration, firewall rules. If your site has already been compromised, we handle malware removal, file-integrity restoration, and post-incident hardening to prevent recurrence.

02 — Our Approach

Clean stack.
Documented work.
No handover mess.

WordPress development tends to attract two failure modes: builds that look fine on launch day but cannot be maintained without the original developer, and migrations that move pixels while quietly losing rankings. We work to avoid both — by writing readable code, by documenting every non-obvious decision, and by leaving infrastructure that any competent next developer can pick up.

i

GeneratePress + GenerateBlocks Pro

Our default stack — chosen for performance and maintainability, not for novelty. Lightweight theme framework, native block-editor layout, semantic HTML, no shortcode lock-in. Sites built on this stack score well on Core Web Vitals from the first deploy, and every layout decision is portable WordPress markup that survives a future theme change.

ii

Staging-first, always

No update, plugin install, or theme change goes near production without running in staging first. We maintain proper development, staging, and production environments for every WordPress engagement and use deploy scripts rather than copy-paste workflows. The sites that “broke after an update” almost always lived without a staging environment — we make sure yours has one and is used.

iii

Documented from day one

Every build comes with a written handover covering hosting, deployment, plugin choices, custom code, backup schedule, and login credentials. Every customisation is committed to version control with meaningful messages. The next developer to look at the site — whether ours, yours, or someone else’s — should not need a phone call to understand what was done and why.

iv

You own the keys

Hosting accounts, domain registrar, repository, plugin licences, third-party services — every credential and ownership detail is in your name. We manage them on your behalf during the engagement, and we hand them back cleanly on the way out. No hostage situations, no plugin licences that expire if you switch agencies, no lock-in by convention.

03 — Who It’s For

Sites that have to
last for years.

WordPress is rarely the right choice for a brochure that will be discarded in twelve months — but for any business that intends to stay online for years, it is one of the most durable choices available. The work looks different depending on where you are starting from.

Our WordPress development clients typically arrive in one of a few shapes — and the engagement looks different in each.

  • i Businesses planning a new buildChoosing a platform for the next five to ten years. We scope the project, recommend hosting, and deliver a clean GeneratePress + GenerateBlocks Pro foundation ready for content, search, and growth.
  • ii Owners of an inherited siteThe previous developer is gone, the theme is unfamiliar, and nothing has been updated in months. We audit, document, harden, and bring the site back to a maintainable baseline before anything else changes.
  • iii Sites trapped in a heavy page builderElementor, Divi, or a stack that produces unreadable markup and slow Core Web Vitals. We rebuild the layouts on GenerateBlocks Pro — same look, fraction of the weight, fully editable in the native block editor afterwards.
  • iv Migrations from another platformWix, Squarespace, a legacy CMS, or static HTML. We map every old URL to its new home, preserve the metadata that drives rankings, and monitor traffic for sixty days post-launch — the unglamorous work that decides whether the move costs you positions.
  • v Sites that have been compromisedMalware, blacklisting, redirect injection, or an admin account quietly added by an attacker. We clean, restore, and harden — then put the maintenance discipline in place that should have been there from the start.

If you are weighing a rebuild against ongoing optimisation, we will tell you honestly which one your site needs. Most sites do not need a rebuild — they need attention. The few that genuinely do are usually obvious within a week of looking under the bonnet, and the free Performance Report below is the fastest way to find out which case you are in.

04 — A complimentary report

Wondering why your site feels slow?

Send us your URL. We’ll send back a Premium Performance Report within 48 hours — page speed, Core Web Vitals, accessibility, and a prioritised fix list ranked by impact on rankings and conversion.

No sales call required.

WordPress is not a launch event. It is a long-haul platform that rewards a careful first build and quiet, disciplined attention every season after.
— The Aureole Practice —
05 — Frequently Asked

Questions we get
about building WordPress.

If a question is missing here, the contact link at the foot of the page goes straight to the person who would answer it. No ticket queues, no funnels.

i Why GeneratePress + GenerateBlocks Pro instead of Elementor or Divi?
Performance and maintainability. Heavy page builders like Elementor and Divi produce complex, deeply nested HTML with large CSS and JavaScript payloads that slow page rendering. They also create vendor lock-in — if you ever want to switch away, your content is trapped in proprietary shortcodes and markup that does not transfer cleanly. GeneratePress is a lightweight theme framework that produces clean, semantic HTML. GenerateBlocks Pro is a block-based layout system that works inside the native WordPress block editor, producing minimal markup without shortcode dependency. The result is a site that loads faster, scores better on Core Web Vitals, is easier to maintain, and keeps your content in standard WordPress blocks that remain portable if you ever change themes. We chose this stack after evaluating the alternatives carefully, and the performance difference is measurable on every project.
ii Can you work on my existing site, or do I need a rebuild?
We work with existing sites regularly. Not every site needs a rebuild — many can be significantly improved through performance optimisation, security hardening, plugin cleanup, and SEO work without touching the underlying theme or layout. We assess the current state during the initial audit and make an honest recommendation. If the foundation is sound but neglected, we optimise it. If the foundation itself is the problem — an overweight theme, a page builder that cannot produce acceptable performance, or an architecture that works against your SEO goals — we will tell you directly and explain why a rebuild would produce a better return on your investment. We never recommend a rebuild when optimisation will achieve the same result.
iii How long does a new WordPress build take?
A typical business website with five to fifteen pages, including content integration, SEO setup, and performance optimisation, takes four to eight weeks from kickoff to launch. More complex builds — those with custom functionality, e-commerce integration, multilingual support, or large content volumes — run eight to twelve weeks, and we will provide a specific timeline after scoping the project. The schedule includes design and layout development, content creation or migration, technical SEO configuration, performance optimisation, security hardening, cross-browser and mobile testing, and a staged launch process. We do not rush builds to meet arbitrary deadlines at the expense of quality, and we do not pad timelines to manufacture the appearance of complexity. The estimate we give you is the one we plan to hit.
iv Can you migrate a site to WordPress without losing rankings?
It is one of our core competencies. A WordPress migration involves pre-migration URL mapping and content auditing, redirect planning (every old URL mapped to its new equivalent), technical configuration of the new site for search, post-launch monitoring to catch ranking drops or crawl issues immediately, and a recovery plan if anything slips. We have managed migrations from Wix, Squarespace, legacy CMS platforms, and bespoke static sites — and within WordPress, we have handled domain changes, HTTPS transitions, and major restructures. The key is planning. Most migration-related ranking losses happen because redirects were incomplete, the robots.txt directive blocked the new site too long, or the technical setup was not validated before launch. We treat every migration as a project with its own dedicated checklist and timeline. See our companion SEO migration discipline for the search-side of the work.
v Do you handle hosting, DNS, and infrastructure too?
Yes. We configure hosting, register or transfer domains, set up DNS records, configure SSL certificates, set up email, and handle the full technical infrastructure — typically as part of the build, or as an ongoing engagement under a maintenance plan. For most business WordPress sites, a well-configured VPS with proper server-level caching gives the best balance of performance, control, and cost; for simpler requirements or smaller budgets, managed WordPress hosting from reputable providers can work well, though you trade some control for convenience. We avoid recommending cheap shared hosting for business sites — the performance ceiling is too low and the shared environment introduces risks outside your control. We will assess your specific situation and recommend the hosting approach that matches your traffic, performance expectations, and budget.
vi Do you offer ongoing maintenance after launch?
Yes. WordPress requires ongoing attention — core updates, plugin updates, theme updates, security monitoring, backup verification, uptime monitoring, and periodic performance review. Our Maintenance & Care Plans cover all of these on a regular schedule, with updates applied through a staging-first workflow so that nothing breaks on the live site without being caught first. Maintenance also includes a monthly allocation of development time for small changes, content updates, and minor feature additions. Most of the WordPress problems we see — security breaches, performance degradation, broken functionality — happen on sites that were not being actively maintained. Regular maintenance is the most cost-effective way to protect your investment in the build.
The Invitation

Ready to build it
properly?

Whether it is a fresh build, a careful migration, a performance overhaul, or a security cleanup — start with a conversation. You’ll hear back from the team that does the work, not a sales department.

Mon–Fri · 9–6 PT support@aureoleintelligence.com Reply within 1 business day