Short answer
We check hosting and PHP version, set up page and object caching where the host supports it, measure what each plugin and the theme add to key templates, optimize images and clean the database. Changes are made on a staging copy and released in small steps.
Where WordPress speed problems come from
WordPress's own advanced administration handbook lists the main levers plainly: the hosting setup, caching, plugins, images, PHP version, the database and a CDN [1]. On plugins it says "the number of plugins and their performance will also have a huge impact" on speed [1]. In practice the order of importance varies from site to site, which is why this service starts with measurement rather than a fixed checklist.
Hosting and PHP
The handbook notes that "the optimization techniques available to you will depend on your hosting setup" [1]. Shared hosting, managed WordPress hosting and a virtual server each allow different changes. We check what your plan allows, how quickly the server responds before any caching, and which PHP version runs the site. The handbook also observes that newer PHP versions "will usually include better performance optimization" [1]. Upgrading PHP needs care because older plugins and themes can break, so we test on staging first.
Caching
Page caching is often the quickest win on a mostly static WordPress site, because caching plugins can store finished pages as static files [2]. Where the host offers it, an object cache helps sites with many logged-in users, stores or heavy queries. We configure one caching layer properly rather than stacking several plugins that fight each other, and we keep personal pages out of the cache.
Plugins and theme
We measure what each plugin adds on your key templates: extra files, database queries and main-thread time. Some plugins load their scripts and styles on every page even when only one page uses them. The fix may be loading them conditionally, replacing a heavy plugin with a lighter one, or removing one that is no longer used. Themes and page builders get the same treatment: we look at how much of their code each page actually needs.
We never deactivate a plugin on the live site without testing. Plugins often support forms, tracking, SEO settings or redirects that nobody remembers until they stop working.
Images and media
The handbook's advice is short: "Make sure all image files are optimized" [1]. We check that WordPress is generating sensible image sizes, that themes use srcset rather than full-size originals, that the LCP image is not lazy-loaded, and that new uploads are converted to modern formats automatically where possible.
Database
Over time the database collects revisions, expired transients, spam comments and leftovers from removed plugins. The handbook notes that optimization tools "can help you reduce extra clutter in your database" [1]. We back up first, clean what is safe to clean, and check for autoloaded options that load on every request without needing to.
What you receive
- Before and after measurements for key templates, field data where available and lab tests with dates.
- A plugin table with the cost of each plugin and what was changed.
- The caching setup written down, including what is excluded and how to clear it.
- A short guide for adding plugins in future without undoing the work.
Updates and maintenance
Speed work does not replace normal maintenance. Plugin, theme and core updates still matter for security and compatibility. If you want ongoing checks after the project, the monitoring service covers speed, and we can recommend how to fit updates around it.
A typical WordPress project, step by step
- Measure key templates with and without the page cache, so we can see both the cached visitor's experience and the server's real cost per page.
- Check hosting, PHP version and whether an object cache is available [1].
- Profile plugins on key templates to find the few that cost the most, using query and asset profiling as WooCommerce's documentation suggests [3].
- Fix the biggest causes first: usually caching, image delivery, and plugins or theme components loading where they are not needed.
- Clean the database after a backup, and check autoloaded options.
- Retest every template under the same settings and record the results.
Each step happens on a staging copy where the host allows one, and changes reach the live site in small groups.
Page builders and block themes
Page builders make editing easier and often make pages heavier, because they load styles and scripts for components site wide. Block themes built on the WordPress editor tend to be lighter, but they are not automatically fast. In both cases we measure what each template actually uses and trim what it does not. If a page builder is the main limit, we explain the trade-off between keeping it and moving key templates to a lighter approach, with measurements, before anything is decided.
What we need from you
An administrator account created for the project (never shared passwords), hosting access for caching and PHP settings, and a list of plugins whose features must keep working. If you have a staging site, we will use it; if not, we can help set one up so changes never have to be tried on the live site first.
Questions about WordPress speed work
Is a caching plugin enough?
It often helps a lot on simple sites, but it does nothing for slow plugins on uncached pages, heavy scripts that hurt responsiveness, or oversized images. Those need separate work.
How many plugins is too many?
There is no safe number. One heavy plugin can cost more than ten light ones. We measure the cost of each plugin rather than counting them.
Do you work on WooCommerce sites?
Yes. Stores have extra concerns such as carts and checkouts that must stay uncached, so they are covered by our e-commerce speed service as well.
Sources
Opened and checked on November 3, 2026.
- Optimization, Advanced Administration Handbook, Developer.WordPress.org. Primary documentation, checked November 3, 2026.
- Cache, Advanced Administration Handbook, Developer.WordPress.org. Primary documentation, checked November 3, 2026.
- How to optimize performance for WooCommerce stores, WooCommerce developer docs. Primary platform documentation, checked November 3, 2026.