“WordPress optimisation included.” Three reassuring words that can cover very different jobs. Adjusting two plugin settings and investigating why checkout stalls while a customer is ready to pay might appear under the same heading. The proposal can sound familiar while buying something else entirely.
For a concrete example of the evidence to request, see our measured WordPress font-delivery before-and-after: six loads per version, the same content and typeface, the full distribution and the limits of the conclusion. It is an intervention on our own website.
A WordPress speed optimisation quote for 2027 should identify the problem, affected pages, proposed work and how the outcome will be checked. The amount becomes useful when you understand the deliverables and dependencies it covers.
This guide includes an enquiry template and an original scope matrix for comparing proposals. You can use them before commissioning work without sending account access or customer data. If you have a specific symptom, request a WordPress performance assessment and quote with the URL and affected action.
What are you buying when you commission optimisation?
An engagement can include diagnosis, implementation and validation, but it does not necessarily include all three. Diagnosis establishes where time is spent. Implementation changes the system. Validation checks results and functions under agreed conditions. Ask for identifiable deliverables for each included stage.
Image-focused work can be appropriate when images are the evidenced problem. A shop with filters, sessions and shipping calculations needs a different scope when the delay occurs in those operations. The number of installed plugins alone does not describe the complexity of the job.
Establish who handles the theme, extensions, server and external services. Where an integration belongs to another supplier, the quote should explain coordination and what happens if that supplier must make changes. That dependency can affect both price and delivery dates.
What should be measured before agreeing a fixed price?
Start with an observable statement: “On this URL, selecting a variation leaves several seconds before the price appears.” Add device, browser, approximate time and session state when known. A homepage screenshot cannot describe that journey or establish its cause.
The provider should review a representative set of templates and actions with recorded conditions. Identify existing evidence and questions requiring preliminary diagnosis. A fixed-price proposal made without that review may rely on assumptions; those assumptions need to be written down with a way to revise the scope.
Use the reproducible WordPress performance testing guide to prepare the technical work. The quote can reference the protocol, owners and URL set rather than reproducing pages of instructions to make the document look more substantial.
A project quote and a performance budget are different documents
The financial quote defines purchased work and its conditions. A performance budget sets measurable product limits, such as resources, timings or another indicator suitable for the journey. Connect the documents while keeping their purposes clear.
The web.dev introduction to performance budgets explains that use of limits. In your proposal, each objective needs measurement conditions and an agreed decision rule rather than adopting a generic number as a universal guarantee.
Reducing an asset’s size might be an implementation task. Checking that navigation responds and content still displays correctly is part of validation. The commercial document should connect the work with its checks and name the person who may accept exceptions.
An enquiry template for comparable quotes
Copy this template and replace the fields you know. Where a measurement is unavailable, write “requires diagnosis”. The provider can then scope the necessary investigation without treating a reported impression as a confirmed technical cause.
WordPress optimisation enquiry | 2027 edition
URL and action where the delay occurs:
Included templates, languages and business journeys:
Devices, browser, network and session states to compare:
Relevant consent state:
Existing reports and capture dates:
Known theme, integrations and recent changes:
Design elements that must be preserved:
Trial environment and publication owner:
Diagnosis / implementation / validation deliverables:
Proposed objectives and measurement method:
Functional regressions to check:
Dependencies, licences and additional costs:
Approval, safe reversal and later follow-up:Name a business owner and technical owner, even if they are the same person. The proposal needs to identify who decides on design, forms, commercial tracking and change windows. “Someone from marketing will look at it” has a habit of turning into a surprisingly long email thread.
Provide descriptions or links to public reports where appropriate. Access, traces containing private information and internal details can be scoped through a managed channel. Defining an intervention does not require distributing passwords across several public enquiry forms.
Six work packages worth comparing
The following matrix is our editorial tool for reviewing proposals. It is not a rate card or hours benchmark. Mark each row included, excluded or unresolved, and keep the provider’s explanation alongside it.
| Work package | Ask for this in writing | Evidence for review |
|---|---|---|
| Diagnosis | URLs, actions and conditions examined | Findings with evidence and limitations |
| Implementation | Included changes and external dependencies | Change record and release identifier |
| Isolated trial | Environment and effects requiring control | Outcome and differences from production |
| Validation | Metrics and functions to check | Comparison under agreed conditions |
| Publication | Approval, change window and safe alternative | Deployment and review record |
| Follow-up | Period, reviews and exclusions | Owner and escalation criteria |
An unanswered row does not automatically make a proposal unsuitable. It may be a deliberate exclusion or work commissioned from another team. The matrix is useful because it exposes that difference before the price is approved and delivery begins.
Compare the same function set. If one proposal covers only the homepage while another includes product, cart and checkout, their totals do not describe the same service. Ask for the missing work packages to be priced or for an explanation of why they are unnecessary for your reported problem.
A fictional example of different scope
Consider two proposals without assigning invented market prices. The first covers one page’s initial load and resource adjustments. The second includes that review plus a product-filter interaction, form checks and validation after the change is published.
The first may suit a specific, limited commission. The second includes more journeys. If the actual complaint concerns filtering, ask both providers how that action will be diagnosed and verified. Selecting only by the final amount before answering that question means comparing different jobs.
Also ask what happens if diagnosis locates the bottleneck in an external API. A proposal might include identifying and documenting it while changes to the third-party service require a separate engagement. Keep that boundary visible and name the person coordinating the next step.
Scope uncertainty without writing a blank cheque
When the cause is still unknown, ask for a phased proposal. The first commission defines an investigation; the next is approved using the findings available. Each phase needs a concrete output so the engagement does not become a succession of hours that are difficult to review.
This organisational example is fictional and does not describe an engagement already commissioned:
- Assessment phase. Agree the templates and actions to examine, their conditions and a findings document. The handover identifies what could be established and what requires another source or supplier.
- Intervention phase. The provider describes included changes, dependencies, environment and verification. Business staff approve the scope before implementation. An additional problem is recorded and priced separately instead of silently becoming part of the commission.
- Review phase. Agree who checks deployment and what follow-up is included. Later reviews of newly introduced functions receive their own classification and commercial decision.
Request an authorised spending limit per phase and a procedure for extending the work. When a dependency changes, ask which finding justifies the extension, what additional deliverable is proposed and how delivery dates are affected. A written cap does not remove the need for investigation; it makes the boundary of each authorisation visible.
The useful commercial question is what information you will receive at the end of each phase and which decision it enables. That lets you compare a bounded assessment with a complete intervention without requiring the same outcome from both or burying their differences in the small print.
What an observed desktop 99/mobile 79 report means for a quote
Our guide to passing PageSpeed reports and slow journeys contains an actual laboratory observation of this website: desktop 99 and emulated mobile 79, with no field data available. Report links and conditions are documented in that guide.
For procurement, the example supports asking for the test profile alongside a score. It does not establish a completed optimisation or commercial result. An objective written only as “improve PageSpeed” leaves the profile, page and conditions open to interpretation.
Preserve the original measurements and comparison criteria. When results vary, the quote should explain how testing will be repeated and interpreted. The guide to variable PageSpeed results covers that question without treating every fluctuation as a new chargeable incident.
Agree which design qualities need to survive
The reference illustrates a decision to make before implementation: what a visual experience contributes to the brand and which alternatives are acceptable. We have not audited this project. Its image supports a design discussion; your implementation’s behaviour and cost require their own checks.
Include essential qualities in the brief: composition, image quality, content, navigation and motion where relevant. If a video or animation change is proposed, ask for a reviewable sample and acceptance criteria. A technical improvement that removes a required function also changes the agreed product.
What changes the complexity of an optimisation quote?
Several templates with different problems require more investigation than one identified resource. Custom code, lack of a trial environment, integrations and coordination with several suppliers introduce work that should be explained explicitly rather than hidden inside a generic package.
The affected condition matters too. Working on a public content page is different from intervening in a cart session or administrator journey. For multilingual sites, establish which templates are shared and which journeys must be checked in each language version.
Ask for these differences to appear as scope and assumptions. Page count does not automatically translate into that many independent jobs: many pages share a template, while others contain their own logic and dependencies. The proposal should explain which distinction applies to your site.
Licences, hosting and recurring work
Identify who pays for and controls required licences, who manages hosting and which recurring costs may be added. Ask what will be handed over if the provider relationship ends and which configurations will remain documented for the next maintainer.
Ongoing work may make sense when frequent changes can introduce regressions. Other projects need an intervention followed by agreed reviews. The guide to ongoing performance maintenance helps make that decision around how the business operates.
Distinguish correcting a defect in the delivered work, adding new functions and reviewing a later third-party change. Agreeing those categories makes support discussions concrete rather than discovering what “follow-up included” meant only after something becomes slow again.
Include validation and publication in the commercial discussion
The quote should identify who tests forms, navigation, consent and affected commercial functions. WooCommerce work may require a controlled test route and coordination with the person managing payments and orders. A performance score should not be assumed to validate those functions.
Ask for a change record, agreed comparison and post-publication review. Define a safe alternative if a regression appears and who can authorise it. The approver needs to distinguish checks completed, checks failed and questions still unresolved at the proposed handover.
For a useful proposal, send the template with the symptom, URLs and available evidence. Assessment allows scope, targets and price to be agreed before intervention. The amount then corresponds to a specific piece of work you can review, approve and verify.
At handover, use the WordPress optimisation report template and acceptance checklist to connect delivered changes, comparable evidence, functional checks and remaining actions.