Get a Free Quote
WORDPRESS SPEED OPTIMISATION / PERTH, WA
Performance work for WordPress sites that feel slow on real phones, fail Core Web Vitals, waste paid traffic or make customers wait before they can act. We measure first, isolate the bottleneck, optimise the delivery path and verify the result on mobile and desktop rather than chasing a vanity score.
LCP target <= 2.5s / INP <= 200msCLS target <= 0.10 at the 75th percentilemeasure -> isolate -> optimise -> verifybackup first; test mobile + desktop FASTER IS A USER-EXPERIENCE JOB BEFORE IT IS A SCORE
A slow site is rarely one problem. It can be a slow first server response, an oversized hero image, a page builder loading unused assets, too many third-party scripts, database overhead or a dynamic WooCommerce path that cannot be cached like a normal page. We diagnose the actual request path before changing anything.
PageSpeed Insights can show Lighthouse lab diagnostics and, where enough traffic exists, Chrome UX Report field data. We use both when available instead of treating one synthetic score as the whole user experience.
A service page, product archive, checkout or campaign landing page can create more revenue than the homepage. Priority URLs are chosen around traffic and conversion intent, not just what looks impressive in a report.
Google currently defines good thresholds as LCP within 2.5 seconds, INP under 200 milliseconds and CLS at or below 0.1, assessed at the 75th percentile where field data is available.
We do not promise a universal 100 because third-party tags, hosting, ecommerce functionality and real-user conditions can change the score. The job is to remove avoidable delay and document the measurable before-and-after result.
MEASURE THE BOTTLENECK BEFORE APPLYING THE FIX
The audit separates server delay, front-end rendering, media weight and WordPress overhead so the scope is based on evidence rather than a checklist applied to every site.
We review initial response behaviour, cache status, PHP/runtime constraints and obvious hosting limits before trying to solve server delay with front-end tricks.
We identify the resources blocking first paint, long JavaScript tasks and layout work that delays visible content or makes the interface feel unresponsive.
Hero media, galleries, icons and font files are checked for dimensions, formats, responsive delivery, preload choices and whether the browser is downloading assets it does not need yet.
We look for heavy plugins, excessive autoloaded data, scheduled tasks, duplicate functionality and slow dynamic requests that can keep WordPress busy even after the front end is cleaned up.
OPTIMISE THE METRIC BY FIXING ITS CAUSE
Core Web Vitals are not three switches. Each metric points to a different class of user-experience problem, so the optimisation work is mapped to the cause behind the number.
DELIVERY PATHS NEED TO WORK TOGETHER
Caching is effective only when the browser, CDN, origin and WordPress layer agree about what can be reused and what must stay dynamic. We configure around the actual hosting stack rather than installing several overlapping cache plugins.
Serve reusable pages without rebuilding the same response in PHP on every visit.
Move static assets closer to users and set cache headers so repeated downloads are reduced.
Use sensible expiry and immutable asset strategies for versioned CSS, JavaScript, fonts and images.
Review Redis or equivalent options when database-heavy WordPress workloads justify it and hosting supports it.
Identify slow origin work that a CDN cannot fix, including uncached PHP and expensive database requests.
Keep dynamic WooCommerce and authenticated pages functional while caching the parts that are safe to reuse.
SHIP THE PIXELS PEOPLE SEE, NOT THE FILES THEY DO NOT NEED
Media optimisation is more than bulk compression. The browser should receive the right dimensions, format and priority for the device and position of each asset.
THE FASTEST BYTE IS THE ONE YOU DO NOT SEND
Front-end performance often improves by reducing work rather than adding another optimisation plugin. We trim redundant assets, change loading order and protect layout stability while preserving the features the site actually needs.
Performance projects are delivered remotely across Perth metro. A West Perth consultancy may need fast campaign pages and attribution scripts, an Osborne Park contractor may have large project galleries, a Subiaco clinic may rely on booking widgets, and a Joondalup or Wanneroo service business may receive most enquiries from mobile search.
Remove or conditionally load styles that are not required on every template rather than serving the full design system to every page.
Defer or delay non-critical scripts and reduce long tasks that block interaction on mid-range mobile devices.
Review chat, heatmaps, pixels, embeds and marketing tags because third-party code can dominate the main thread even when WordPress itself is fast.
Prioritise the styles required for the first viewport and prevent lower-priority CSS from blocking meaningful paint where the implementation supports it.
Add dimensions and reserved space for images, embeds and dynamic UI so the page does not jump while assets arrive.
Re-run the agreed priority URLs after deployment so one template does not improve while another becomes slower or visually unstable.
CLEAN WORDPRESS BEFORE BLAMING THE BROWSER
Plugins and database tables are reviewed by what they do on the real request path. We remove obvious waste carefully, preserve required functionality and verify the site after each meaningful change.
Map active plugins, theme dependencies, page-builder modules, integrations and scheduled jobs before anything is disabled.
Output: dependency and risk listIdentify duplicate features, globally loaded assets and plugins that create expensive queries or external requests on pages where they are not needed.
Output: keep / replace / remove recommendationsReview revisions, expired transients, autoloaded options and plugin leftovers before cleaning data that is safe to remove.
Output: documented database cleanupCheck scheduled jobs and recurring processes that can create bursts of server work or duplicate tasks on busy sites.
Output: background-task reviewRe-test functional paths and performance after cleanup so a faster dashboard does not come at the cost of a broken form, search, booking or checkout.
Output: before / after verificationMEASURE BEFORE AND AFTER
Every package starts with an agreed baseline and ends with a repeatable verification pass. Pricing is based on how many priority page types and dynamic paths need engineering work, not on a promise to force every URL to the same synthetic score.
Alpha guide rates keep the Services hub positioning: about 40% below a conservative professional-agency benchmark for comparable one-off performance work. Current Alpha starts at A$300 rather than the A$500 benchmark used on the main Services page.For a brochure site or focused landing-page set with a clear front-end bottleneck and no complex ecommerce path.
Typical delivery: 2–3 business daysFor a standard business site with multiple templates, heavier scripts, a page builder, forms and a wider set of priority URLs.
Typical delivery: 3–5 business daysFor stores that need product, category, cart and checkout performance investigated without breaking dynamic ecommerce behaviour.
Typical delivery: 4–7 business daysGuide prices are in AUD. They assume one WordPress installation and reasonable access to hosting / WordPress. Hosting upgrades, premium CDN plans, paid optimisation plugins, redesign work, third-party tag rewrites and custom application refactoring are excluded unless written into scope. Good Core Web Vitals are a target, not a universal guarantee: real-user results depend on hosting, code, third-party services, device mix and traffic.
Additional approved performance engineering: A$90/hrDYNAMIC STORES NEED A DIFFERENT PERFORMANCE PLAN
A store cannot be optimised like a static brochure site. Product discovery can be cached heavily, while cart, checkout, account and session-dependent requests must stay accurate and personalised.
Explore WooCommerce Development →Reduce image weight, query cost and front-end assets on the templates shoppers use to browse and compare products.
Review recurring dynamic requests that can run on every page and create unnecessary server work when the store configuration does not require them.
Keep transaction pages out of full-page caches and verify that optimisation rules do not serve another shopper's state.
Measure third-party checkout scripts because a fast theme can still feel slow when payment, fraud, shipping and analytics code dominates the main thread.
SPEED QUESTIONS BEFORE YOU BUY ANOTHER PLUGIN
These answers focus on what can actually be measured, what changes the scope and why speed work should be verified instead of sold as a magic score.
Common causes include slow hosting, no effective page cache, oversized media, too many global plugin assets, third-party scripts, heavy page builders, database overhead and dynamic WooCommerce requests. The audit identifies which of those are actually affecting your priority URLs.
Google's current good thresholds are LCP within 2.5 seconds, INP under 200 milliseconds and CLS at or below 0.1, assessed at the 75th percentile where real-user field data is available.
We do not sell a universal score guarantee. Lighthouse is a useful lab diagnostic, but the final score can be affected by hosting, third-party tags, ecommerce functionality and test conditions. We agree the priority URLs, record the baseline and document the measurable improvements.
Our current guide packages are A$300 for a focused speed pass, A$540 for a broader business-site optimisation and A$840 for WooCommerce performance work. The final scope depends on templates, hosting, plugin stack and dynamic functionality.
The normal goal is to preserve the approved design. If a visual feature is inherently expensive, such as an oversized autoplay background video or a heavy third-party widget, we explain the trade-off before changing it.
Not automatically. We measure the current origin first. If server response remains the dominant bottleneck after reasonable configuration, we can recommend a hosting change with evidence rather than moving hosts by default.
Usually yes, although page builders can load more CSS and JavaScript than a lean custom theme. We optimise the current stack first and only recommend structural rebuilding if the builder itself prevents a sensible result.
We record the agreed priority URLs using mobile and desktop Lighthouse / PageSpeed diagnostics, review field data when available, implement the work, then rerun the same test set and functional smoke checks after deployment.
Yes, but the cache and script rules must respect dynamic cart, checkout and account behaviour. The WooCommerce package includes store-path exclusions and functional checkout verification.
Yes. We work remotely with businesses across Perth CBD, West Perth, Subiaco, Osborne Park, Joondalup, Fremantle, Cannington, Midland, Wanneroo and Rockingham, as well as businesses elsewhere in Australia.
START WITH THE URL THAT FEELS SLOW
Send us the pages your customers actually use.
Share the website URL, the pages that matter most, any recent PageSpeed or Search Console data and whether the problem is worse on mobile, desktop or checkout. We will scope the bottleneck before recommending a package.