← All case studies
Case study

Rebuilding a church network directory

Japanese Church Planting Network · jcpnetwork.com

A stock WordPress theme with a brick-wall stock photo became a fast bilingual site with a real church directory — and English pages search engines can finally read.

The problem

JCPN ran on a stock WordPress theme. Every page opened with a full-width stock photograph of a brick wall before any content appeared, the member church directory was a list of plain text links, and the English version of the site existed only as a client-side toggle that search engines never indexed. A visitor looking for a Japanese-speaking church near them had no map and no obvious place to start.

What we did

We rebuilt the site as fully prerendered static pages, put the member churches on an interactive map, and made Japanese and English separate crawlable routes rather than a toggle. Fonts were subsetted and self-hosted so nothing blocks the first paint, images moved to a responsive pipeline, and the performance characteristics are locked behind tests so they cannot quietly regress.

Result

The site is live and ships almost no JavaScript. Its English pages are indexable for the first time, and the directory is now a map a visitor can actually use rather than a wall of links. Accessibility went backwards by five points on a handful of low-contrast text colours — a real regression, listed below and being fixed.

Before and after

Home page

The previous jcpnetwork.com home page: a stock WordPress theme where a full-width photograph of a brick wall fills the screen above the site title.
Before — a brick-wall stock photo above the fold
The rebuilt jcpnetwork.com home page: a clear bilingual title, a photograph from the annual conference, and links into the church directory.
After — the site says what it is straight away

Church directory

The previous member churches page: churches listed as plain underlined text links grouped under state headings, below the brick-wall header.
Before — a text list grouped by state
The rebuilt member churches page: an interactive map of North America with a pin for each member church, above the church listings.
After — an interactive map with every member church

About page

The previous About page: the vision, mission and strategy run together as one unbroken block of small Japanese text below the brick-wall header, with nothing to separate them.
Before — vision, mission and strategy run together
The rebuilt About page: ビジョン, ミッション and 戦略 as separate labelled sections — the vision set off in a quoted block, the two mission points numbered in their own cards, and the five strategy points laid out in a grid.
After — each one labelled and set apart

What changed for the people using it

Rebuilding a church network directory
AspectBeforeAfterChange
English pagesA client-side toggle, never indexed8 prerendered routes under /en/Now crawlable
Church directoryPlain text links grouped by stateInteractive map with every member churchRebuilt
Web fontsRender-blocking Google Fonts CSSSelf-hosted subset, nothing blockingSelf-hosted
Client-side JavaScriptWhole page rendered in the browserA ~1 KB nav script, plus the mapNear-eliminated
Old WordPress linksWould have broken on rebuildPublished slugs 301 to their new homesPreserved
SitemapHand-maintained, drifted from realityGenerated from the route definitionsCannot drift

What changed, measured

Rebuilding a church network directory
MeasureBeforeAfterChange
Performance score7798+21 pts
Accessibility score10095−5 pts
SEO score83100+17 pts
First Contentful Paint2.9 s1.7 s−41%
Largest Contentful Paint4.8 s2.1 s−56%
Page weight668 KiB483 KiB−28%
Date measured
5 August 2026
Methodology
Mobile Lighthouse with simulated throttling, home page. Performance figures are the median of 3 runs; accessibility and SEO are single runs, because those audits are deterministic.
Caveats
The “before” is a local reconstruction of the original WordPress site, rebuilt from JCPN’s own backup (Twenty Seventeen theme and uploads) with markup from an archived capture. It is served from disk, so its server response time is far better than the real hosting was — the original scored no higher than this, and most likely lower.