01What is measured and what changes
A slow site is not fixed by installing a caching plugin. It is measured: what loads, when, and on what device. Then we touch what the measurement points to.
We start from field data (CrUX or Search Console, if they exist) and lab data (Lighthouse or PageSpeed). The goal is a “good” Core Web Vitals result on mobile on the key URLs, but the final figure depends on the hosting, the theme, the plugins, and the content. It is not promised before measuring.
The promise is concrete: measurement before and after, changes explained, and a report with what was touched and what is left. No dressing up a metric or promising a number that has not been measured.
LCP ≤ 2.5 s, INP ≤ 200 ms, and CLS ≤ 0.1 are the Core Web Vitals references. They are the goal, not a contractual guarantee.
02What it covers and what it does not
Includes
- Initial measurement with field CWV, if data exists, and lab measurement.
- Bottleneck diagnosis: cache, images, fonts, CSS/JS, plugins, and hosting.
- Optimization of what was located, within the agreed scope.
- Before/after test with the same methodology and device.
- Report of changes, results, and limits.
- Mobile verification of the key URLs.
Does not include
- Visual redesign or content rewriting.
- New functionality or template changes.
- Hosting migration or CDN change unless separately agreed.
- Licenses for premium plugins, CDN, or third-party services.
- Guarantee of a score or of “good” CWV before measuring.
- Campaigns, content SEO, or linkbuilding.
03How we do it
-
01
Measure
Baseline with field and lab Core Web Vitals, on mobile and desktop, before touching anything.
What is needed The URL, access, and Search Console or analytics data if they exist.
-
02
Locate
We review cache, images, fonts, CSS/JS, plugins, and hosting; priority is set by measured impact, not by trend.
What is needed Access and a window for testing.
-
03
Optimize
Changes are applied in parts, with backup and rollback. Each change is justified by what it improves or what it prevents.
What is needed Confirmation of the scope and a work window.
-
04
Verify
We measure again with the same methodology and compare against the baseline, not against a loose screenshot.
What is needed The environment not changing during the comparison.
-
05
Report
We deliver what was touched, what improved, what did not, and what is still pending. Whatever cannot be improved is stated.
What is needed Someone to validate the final result: content, forms, and sales.
04Price and scope
The optimization is quoted after measuring. There is no fixed figure before seeing what slows the site down: the scope depends on the bottlenecks and the real room for improvement.
What determines the costNumber of URLs and templates: a landing page does not cost the same as a catalog with checkout. · Theme, plugins, and builders: what can be touched without breaking editing. · Images, fonts, and third-party scripts: what can be deferred, compressed, or removed. · Hosting, cache, and CDN: the server's real room for improvement. · Integrations and checkout: where performance affects sales. · Urgency: work outside the agreed hours costs differently.
- Number of URLs and templates: a landing page does not cost the same as a catalog with checkout.
- Theme, plugins, and builders: what can be touched without breaking editing.
- Images, fonts, and third-party scripts: what can be deferred, compressed, or removed.
- Hosting, cache, and CDN: the server's real room for improvement.
- Integrations and checkout: where performance affects sales.
- Urgency: work outside the agreed hours costs differently.
05Timelines and response
The timeline is defined after measuring. No hours are promised before seeing the scope: a landing page and a catalog with checkout are not optimized the same way.
The first response confirms what data we need and whether there is usable prior measurement. It is not a blind quote.
If the access, the hosting, or the data are missing, the timeline starts once they are resolved. Waiting time is not deducted from the work or hidden.
Urgencies are handled according to availability and scope. There is no implicit SLA behind this page: whatever is committed is written in the proposal.
Response policy: First response within 1 business day, Monday to Friday, Colombia and Spain time.
06Compatibility and access
We work on what you already have: WordPress, PHP, MySQL, hosting, theme, plugins, builders, and WooCommerce. The installed stack is part of the case.
To start we need: the URL, WordPress admin access, hosting or SFTP access, cache or CDN access if one exists, Search Console or CrUX data if available, and someone who can validate.
Before changing anything: backup and rollback plan. If an optimization cannot be measured or breaks something, it is reverted.
We do not change the hosting or rebuild the theme if it is not necessary. If the limit is there, it is justified in writing and quoted separately.
07What evidence we deliver
We do not publish client metrics without permission. There are no figures of improvements, times, or published cases: the evidence is the before/after measurement of your site.
- Baseline: field CWV, if available, and lab on mobile and desktop.
- Changes: what was touched and why.
- Comparison: same test, same URL, and same methodology.
- Limits: what did not improve and why.
The report is the deliverable. The lab score is not a field guarantee; if there are cases with permission later, they will appear with source and date.
08What you receive
| Deliverable | When |
|---|---|
| Initial measurement report | Before touching anything |
| Backup and rollback plan | Before changing |
| Applied and verified changes | At the close of the optimization |
| Before/after comparison | With the final report |
| Pending items and next phase | At the close of the optimization |
09What happens next
Optimizing is not maintaining. A fast site starts accumulating plugins, images, and scripts that have to be reviewed.
Optional support starts at €50/month and includes updates, backups, security review, and an alert when something fails.
It is not mandatory. If you prefer to manage it yourself, the report includes what to watch and when to review it.
See support and maintenance10Frequently asked questions
Can you guarantee the site will be fast?
Not before measuring. The goal is “good” CWV on mobile on the key URLs, but it depends on the hosting, the theme, the plugins, and the content. Whatever is committed is written in the proposal.
What are Core Web Vitals?
They are Google's loading and interaction experience metrics: LCP, INP, and CLS. They are measured with field and lab data; the lab score is not the same as the field score.
How much does it cost?
It is quoted after measuring. It depends on the number of URLs, the theme and plugins, the images, the hosting, and the scope. There is no fixed figure before seeing the case.
Do I have to rebuild the site?
Not by default. We optimize what is there; if the theme or the hosting are the real limit, we say so and quote it separately. We do not change the technology to dress up a metric.
Do you touch the design or the content?
We do not redesign or rewrite content; we optimize resources and loading. A visual change or a rewrite is a different engagement and is quoted separately.
How long does it take?
The timeline is defined after measuring. No hours are promised before seeing the scope. If access, hosting, or data are missing, the timeline starts once they are resolved.