Diagnosis, then a plan
WordPress Performance Consulting: Find the Real Bottleneck Before You Pay for Another Fix
By now you may have three opinions on why the site is slow. The host blames the plugins, the plugin developer blames the theme, and the last agency sold you a caching plugin. A consultation replaces opinions with measurements and a written plan you can hand to anyone.
October 6, 2026 · 8 min read
The short answer
WordPress performance consulting is a diagnosis-and-roadmap engagement. We measure real-visitor field data alongside lab tests, isolate what the theme, plugins, hosting and third-party scripts each cost, and deliver a written, prioritized plan. It ends with an honest recommendation: keep tuning WordPress, change the theme, or rebuild. You decide who does the work.
On this page
You need a diagnosis before another remedy
Most WordPress speed work starts with a fix and hopes the diagnosis was right. A new host. A caching plugin. An image optimizer. Each helps a little or not at all, and nobody can say why, because nobody measured which layer was responsible in the first place. Meanwhile the money goes out one plausible remedy at a time, and the PageSpeed score bounces around like a stock ticker.
This engagement is the measuring. We don't change your live site, sell you hosting or tuck a tune-up into the price. You get a document that says where the time goes and what to do about it, in order. If you want hands-on work instead, the WordPress speed and optimization service and our repair-side speed work do the fixing. Consulting is for owners who want to understand the problem before they spend on it.
Field data is the score that counts
Two kinds of numbers get confused. Field data comes from real Chrome users visiting your site, collected in the Chrome UX Report over a rolling 28 days. Google's Core Web Vitals assessment uses it and judges the 75th-percentile visit: Largest Contentful Paint at 2.5 seconds or less, Interaction to Next Paint at 200 milliseconds or less, and Cumulative Layout Shift at 0.1 or less.
Lab data is a single test run, such as the Lighthouse report inside PageSpeed Insights, on a simulated phone over a throttled connection. It is repeatable and excellent for finding causes, and it is not what your visitors experience. Say a site scores 60 in the lab and passes in the field; that is a very different problem from a site scoring 90 in the lab while failing INP for real users. Our guide to reading PageSpeed Insights and the wider performance section go deeper.
Smaller sites often have no field data at all, because Chrome needs enough visits before it reports anything. Then we test each template repeatedly instead of trusting one run, and where it is worth it we add lightweight real-user measurement for a few weeks, so the plan rests on something sturdier than a single screenshot. The Core Web Vitals guide explains the three metrics in plain terms.
Theme, plugins, hosting, scripts: costed separately
Theme and builder
Dynamic CSS printed inline, fonts fetched from Google, a builder writing deep wrappers. We find the theme's floor by testing key templates on staging with its heaviest features off, then on a lean theme. Theme-by-theme detail lives in our theme reviews.
Plugins
Each plugin's server time, measured with a profiler such as Query Monitor, plus every stylesheet and script it adds to pages that never use it. The result is a cost table, plugin by plugin.
Hosting
Time to first byte on cached and uncached pages, PHP version, object caching, and the pages a page cache cannot help: cart, checkout, account and anything a logged-in user sees.
Third-party scripts
Tag managers, chat widgets, review badges, booking embeds, heatmaps and ad pixels. Each one listed with who added it, what it costs on a phone, and whether anyone still reads its data.
The finding is rarely one villain. It is usually a ranking: this layer costs the most, that one is cheap to fix, the third isn't worth touching. That ranking is the whole value of the exercise, because it tells you where the next dollar does the most good. Our explainer on why WordPress gets slow describes how the layers pile up over the years.
Third-party scripts deserve special attention because nobody owns them. Marketing added the pixel, sales added the chat, a former agency added the heatmap and nobody removed it. They load from other companies' servers, change without notice and compete for the same main thread your visitors need for taps and scrolls. The inventory gives each one an owner and a reason to exist, or a removal date.
The roadmap you receive, item by item
- A written report in plain English, with the technical detail in an appendix for your developer.
- Field and lab results for each template type: home, service or product, article, and checkout where there is one.
- Annotated waterfalls showing what blocks the first render and what delays interaction.
- A plugin cost table and a third-party script inventory, with a keep, replace or remove call on each item.
- A prioritized action list ranked by expected effect and effort, so the cheap, large wins come first.
- A stay-or-rebuild recommendation with the reasoning written out.
- A walkthrough call to go through it all, with your developer on the line if you like.
The report is written to be acted on by anyone competent, not only by us. Each fix names the setting, the plugin or the file involved, what to change, and how to confirm it worked. If your developer disagrees with a recommendation, the evidence is in the appendix for both of you to argue over.
The third option
Athena CMS, with AI agents on staff.
Not a theme and not a blank Next.js repo. The content system we put behind every custom site: plain fields, a real preview, every version kept, and AI agents that handle the chores a plugin only nags you about.
- PicassoImages
- ApolloSite analysis
- AresCompetitor watch
- PrometheusContent holes
- AtlasPage depth and structure
- DelphiAI search visibility
and 12 more agents. Two come with Athena; the rest are monthly add-ons.
What happens after you say yes
- 1
Intake call
What the site has to do for the business, what has already been tried, and which pages matter most. We ask for read-only access where possible.
- 2
Baseline
Field data from the Chrome UX Report and Search Console's Core Web Vitals report, plus repeated lab runs on each template.
- 3
Isolate on a copy
On a staging copy we switch off plugin groups, strip third-party scripts and swap the theme to measure what each layer actually costs.
- 4
Write the plan
Findings ranked, and fixes described precisely enough for any capable developer to carry out.
- 5
Walk through it
We go through the report together and answer questions until the plan makes sense to the person paying for it.
- 6
Choose who executes
Your developer, your in-house team, or us. The plan works the same way in any of those hands.
Most of the engagement is quiet. You hear from us at the intake call, if a measurement needs access we don't have, and at the walkthrough. Nothing on the live site changes, no plugins are installed there, and your team keeps publishing throughout. The only trace is a staging copy used for the isolation tests, which is removed when the work is done unless you want to keep it.
Keep WordPress or rebuild: the written verdict
Every report ends with the recommendation owners want and rarely get: is this site worth tuning, or has it hit its limits? We make that call on evidence. If the theme's floor and the plugins you truly need still leave room to pass Core Web Vitals, the answer is to stay and tune, and we will say so in writing even though we build Next.js sites for a living.
- Stay and tune when the fixes are mostly settings, plugin trimming and hosting, and the site does what the business needs. Theme speed optimization or a general tune-up follows.
- Change the theme when a builder theme sets the floor but your team is happy in WordPress. That is a theme migration.
- Rebuild when the floor is too high, the features you need fight WordPress, or the plugin stack's cost keeps compounding. Then rebuilding in Next.js or a straight WordPress to Next.js migration is the honest answer.
If you are already leaning one way, read should I leave WordPress and the five-year cost of a WordPress site before the walkthrough call. If the verdict is to move, replacing WordPress covers what life looks like afterward.
Who should skip the consultation
Some sites don't need a roadmap. If the site is down or throwing errors, you need theme repair today, not a report next week. If it is a five-page brochure site with no complaints and a mediocre score, run the free website health check first. If you have already decided to leave WordPress, skip ahead to a free mockup of the new site; performance gets measured as part of that project anyway.
For everyone else, the consultation is quoted at a fixed price after a free site audit. The price depends on the number of distinct templates, WooCommerce or membership features, multisite setups, and how much field data already exists. Financing for WordPress work is available. Call (210) 346-0848 if you would rather talk it through first.
Questions people ask before they call
Field data is collected from real Chrome visitors over 28 days and is what Google uses to judge Core Web Vitals. Lab data is one simulated test, like the Lighthouse run in PageSpeed Insights, useful for finding causes but not a measure of real experience. A plan built on lab scores alone often fixes the wrong thing, which is why we start with the field.
Not for most of it. Field data needs nothing from you, and Search Console access helps. For isolation tests we work on a staging copy, never the live site, so nothing you rely on changes during the engagement. Where we do need the dashboard, read-only or a limited account is usually enough.
If you want us to. The plan is written so any capable developer can carry it out, and many clients hand it to their own. If we do the work, it is quoted separately at a fixed price and the consultation becomes its first phase, so nothing is measured twice.
You should; it is free. It tells you what is slow on one page in one test. It doesn't tell you which plugin added the script, whether the host or the theme causes slow server response, or whether a fix is worth the money. The consultation answers those questions and ranks the answers.
No, and you are right to ask, since we build in Next.js. The recommendation follows the measurements and your business. Plenty of WordPress sites only need tuning, and the report says so when that is the case. When we do recommend a rebuild, the report shows the numbers that led there, and the WordPress vs Next.js comparison lays out the trade-offs.
Get a plan you can hand to anyone
Tell us what the site does for your business and what you have already tried. We will scope the consultation after a free audit and quote it at a fixed price.
Which of these sounds like you? (pick any)
Rather talk now? Call (210) 346-0848.