StreamzAI
WordPress engineering with performance work
WordPress for a Singapore AI sales-readiness platform
WordPress performance optimization measured on the real page: Core Web Vitals, caching, queries, and the plugin pile — not a lab URL that never runs your stack.
Speed work here is production work. The usual suspects are uncached database work, oversized images, render-blocking scripts, and a CDN that was never wired to the HTML cache. Hosting matters: a VPS and an enterprise platform fail in different ways.
Who this is for
Teams whose WordPress site is slow in production, not only in a lab report
WooCommerce catalogues where product and checkout templates are the bottleneck
Sites on a VPS or CDN that was never fully wired to page cache
In-house developers who need a senior pass through plugins, queries, and PHP
This is not a Core Web Vitals tutorial, a plugin download, or a promise of a specific Lighthouse score.
Services included
01
LCP, INP, and CLS on the templates people actually hit — including the ones with hero images and third-party scripts.
02
Page cache, object cache, and a CDN that serves the HTML you think it serves.
03
Uncached queries, slow admin-ajax, and the PHP that is on the critical path.
04
Uploads that survive the editor, and the CSS/JS the theme and plugins actually print.
05
What the theme and plugins load on every request, what is cache-unfriendly, and what can leave.
Relevant work
Titles, notes, and links are from the existing work section. No invented metrics.
WordPress engineering with performance work
WordPress for a Singapore AI sales-readiness platform
WooCommerce catalogue performance
A faster storefront for an Indian ethnic-wear catalogue
WordPress delivery with performance overlap
WordPress for a US banking product for global citizens
More delivery notes sit in the case studies.
Stack
Process
01
Field or lab data on the real templates, with the plugin stack turned on.
02
Queries, images, scripts, cache headers — whichever is actually on the critical path.
03
Change those things. I do not sell a score; I sell the work that moves the page you named.
04
Check the same templates after cache warms. No guaranteed numeric outcome.
Why this practice
FAQ
No. Hosting, third-party scripts, and editor uploads can undo a lab win. I work the bottlenecks on the real page and re-measure.
Yes. Product, cart, and checkout queries are a common intake. There is a WooCommerce-specific checklist on the blog if you want the notes first.
Often not. A CDN that never caches HTML, or an origin that still runs uncached queries, will look “fine” in the dashboard and slow in the browser.
Only the ones that are on the critical path and replaceable. I do not run a generic “delete your plugins” script.
Yes. PHP, TLS, and cache on a droplet fail differently than on managed WordPress. Say the host when you write.
No. The scan is a public tool. Consulting is the work on your templates, cache, and plugins afterwards.
Related
Start
Send the URL, the template that hurts (home, product, article), and any hosting notes. I will say what a first pass would cover — without promising a score.
Prefer a calendar? Use the consultation scheduler on the contact page.