Is hand-coded WordPress harder for marketers to update?

Not if it's built with structured ACF fields and proper Gutenberg blocks. Marketers learn the patterns once and stop thinking about them. The trade-off is less ad-hoc layout freedom, which most maritime marketing teams don't actually want once they've spent a year fighting a builder.

How long does a hand-coded build take versus a builder build?

Eight to sixteen weeks for a serious corporate site, against four to eight for a builder equivalent. The extra time goes into custom blocks, content modelling and performance work. Total cost of ownership over five years is materially lower because the maintenance burden is smaller.

Can we move from a builder to hand-coded without rebuilding everything?

Page by page, yes. We've migrated 200-page sites off Elementor or Divi across three to four months while keeping the live site running. The content extracts cleanly; the layouts have to be rebuilt, but you get to cull dead pages and improve structure as you go.

The case for hand-coded WordPress over page builders in maritime

A page builder website is fast to ship and expensive to own. A hand-coded WordPress site is slower to ship and cheap to own. Maritime corporate sites are decade-long assets, and the maths on that decade favours hand-coded by a wide margin.

This isn’t a religious argument about WordPress versus the alternatives. It’s about what kind of WordPress build you commission when you’ve decided WordPress is right (which, as we’ve covered elsewhere, is the right answer for most ship managers, operators, ports and marine equipment manufacturers). The choice within WordPress is between a page builder (Elementor, Divi, WPBakery, Beaver Builder) and a hand-coded theme.

What page builders give you

A non-technical marketing manager can build pages quickly. Templates ship with hundreds of elements. Drag, drop, publish. For a 10-page brochure site for a small marine surveyor or crewing agency, a page builder may be the right choice. The build is cheap and the maintenance is light because nobody touches it after launch.

Beyond that scale, page builders start charging rent.

The hidden costs

Performance. Page builders ship a lot of CSS and JavaScript regardless of what your page actually uses. A typical Elementor page weighs 2 to 4MB before you’ve added an image. Lighthouse scores on builder sites we audit average around 35 to 55 on mobile. A hand-coded equivalent regularly hits 95+. On a satellite connection at sea, that’s the difference between usable and unusable.

Lock-in. A page built in Elementor is not a page in pure HTML and CSS; it’s a page in Elementor’s nested shortcode structure. Migrating off Elementor to anything else (a redesign, a different builder, a headless rebuild) means rebuilding every page. We’ve seen 200-page maritime sites where the rebuild estimate is double the original build cost just because of the lock-in.

Plugin sprawl. Page builders pull in companion plugins for forms, sliders, animations, mega-menus, theme builders. Each is another attack surface, another update cadence, another performance hit. WordPress sites with 40+ active plugins are the norm on builder-based stacks; under 15 is normal on hand-coded.

Editor experience that gets worse over time. Marketing teams love builders for the first 90 days. By month 18 the builder editor has become a dance of “find the right widget, hope the styling propagates, undo when it doesn’t, ask the agency to fix it”. Hand-coded sites with structured ACF fields are less flashy but more predictable. Editors learn them once and stop thinking about them.

What hand-coded WordPress looks like

A custom theme built on the underscores starter or a clean Tailwind-based foundation. Block editor (Gutenberg) for content, with custom blocks for the marketing-specific patterns that appear on the site (hero, fleet card grid, case study, FAQ, CTA). ACF Pro for structured fields where blocks aren’t the right fit. A short, deliberate plugin list (security, caching, forms, SEO, multilingual, integration). Hosting on Kinsta, WP Engine or Rocket.net with object cache, full-page cache and a CDN.

The build takes longer up front, typically 8 to 16 weeks for a serious corporate site. The total cost of ownership across five years is materially lower because:

Pages render fast on cheap hosting.
Updates are quick because the plugin surface is small.
Editors can publish without breaking the design.
The next agency (in five years, when you re-evaluate) can read the code.
Performance compounds as Google Core Web Vitals weight rises.

The honest counter-argument

If you have a marketing team of one, a 20-page brochure site, no integrations, no fleet data, no multilingual requirement and a very tight budget, a page builder is fine. We’ve built a few. The use case is real but narrow.

The mistake is the middle case: a 100-page site for a serious operator commissioned on a builder because it shaved 10K off the build cost. Three years in, the marketing director is paying weekly retainer hours to fix layout drift, the site is too slow for buyers at sea and the next refresh is going to cost more than the original because every page needs rebuilding.

A test before you commission

Ask any agency pitching a builder-based site three questions:

What’s your homepage TBT and LCP target on mobile, and what’s your contractual recourse if you miss? A serious agency hits sub 200ms TBT and sub 2.5s LCP. A builder agency will hedge.
How many active plugins does your typical site ship with? Over 30 is a smell. Over 40 is a problem.
What’s the migration story if we want to move off this stack in five years? A hand-coded site exports clean HTML and content. A builder site exports a tangle.

If the answers are weak, the long-term cost is in those answers, regardless of what’s quoted on the build itself.