WordPress Development in California

In practice it's four things: an oversized theme loading assets no page uses, unoptimised images served at full resolution, a plugin stack where each addition injects its own scripts, and no caching layer so every visit rebuilds the page from database queries. We ship a minimal theme, convert images to WebP at correct display dimensions, keep the plugin count deliberately low, and enable full-page caching plus a CDN. That combination is what gets a typical build under a 1.8-second load.

The count matters less than what each plugin does on the front end. Twenty admin-only plugins can be lighter than three that each enqueue a stylesheet and a script sitewide. Our rule is that a plugin has to earn its place: if the same result can be achieved with a few lines in the theme, we write the code instead. Every plugin is also a maintenance and security surface — it needs updating forever, and abandoned plugins are one of the most common WordPress compromise vectors.

We use a clean post-name permalink structure, keeping URLs short, lowercase, hyphenated, and descriptive of the page's topic rather than its position in a menu. When an existing site changes structure, every old URL gets a 301 redirect to its closest new equivalent. Skipping that step is the single most common reason traffic collapses after a rebuild — the rankings were attached to URLs that now return 404, and a 404 passes no authority to anything.

Nothing changes, because none of it depends on us. The site runs on self-hosted WordPress under your own hosting account and domain, using a theme whose source code sits in your installation. You hold the administrator credentials throughout. Handing the project to another developer means giving them the login — there is no proprietary platform, no licence tied to us, and no export step that loses formatting.

Four things have to line up: an XML sitemap listing every indexable URL and referenced from robots.txt, a robots.txt that doesn't accidentally block resources, a self-referencing canonical tag on each page so near-duplicates consolidate correctly, and internal links pointing at every page you care about — an orphan page with no inbound link is very unlikely to be crawled or indexed even when it appears in the sitemap. We verify all four in Search Console after launch.

They're three measurements Google uses as a ranking signal: Largest Contentful Paint (how long the main content takes to appear, target under 2.5 seconds), Interaction to Next Paint (how quickly the page responds to a tap or click, target under 200 milliseconds), and Cumulative Layout Shift (how much content jumps as the page loads, target under 0.1). We design around them by setting explicit width and height on images so nothing reflows, reserving space for embeds, keeping JavaScript minimal, and preloading the hero image.