Project web-page-quality-pass-one-site-section · revised 11 October 2026
Project
Bring one site section up to a named standard for speed, accessibility and URLs
For up to ten key pages we agree a written standard: up to three speed limits, an accessibility checklist for one flow and clean URLs. We fix what misses it and hand back a results table you accept.
This asks for a proposal by email. Nothing is charged, and nothing starts, until you have agreed the standard, the price and the terms in writing.
The result you are buying
Speed, accessibility and address problems across a section each look small, and each is usually fixed by someone different with a different tool. Nobody agrees the standard in advance, so the work never ends and nobody can say when it is done. A defined section with a written standard and a results table can be finished and accepted.
Who it’s for: An agency, or a site or product owner, who needs one section of a site (a landing set, a shop section, a sign-up path) brought to an agreed standard before a launch, a handover to a client or a tender.
Usually starts when: A relaunch or handover is due, a client or tender asks for evidence on speed, accessibility and address hygiene, or reports list problems across several pages and nobody has turned them into one bounded piece of work.
The result: For up to ten agreed pages, the written standard is met and shown in a results table: up to three agreed page-and-metric speed limits on a fixed lab profile, an agreed accessibility checklist for one flow and clean redirects, canonical tags and sitemap entries. The other pages' speed is measured and reported in the table, with no pass promised. You accept the finished table, or any item is removed from it in writing.
How the work fits together
The project is complete when the speed, accessibility and address items on the agreed standard are each met and shown in the results table, and you have accepted it, or an item has been removed in writing. You accept the finished table, not each internal step.
Bring one Core Web Vitals metric on one slow page into the good range Job Included
One named metric on one named page passes its published good threshold (loading, layout shift) or a stated lab proxy (responsiveness) in agreed lab tests, with the cause written down.
Up to three, one for each page and metric on the agreed list
Each speed item is the same measured job you can buy on its own. More than three are quoted separately.
Fix one page or flow against a named accessibility checklist Job Included
One page or short flow is tested against an agreed list of WCAG 2.2 criteria, the failures are fixed, and each criterion is re-tested by hand and shown as pass or not applicable.
One flow of up to five screens
The accessibility checklist is tested by hand and fixed for one flow.
Make one site's old and new URLs resolve cleanly: redirects, canonicals and sitemap Job Included
Up to 300 agreed URLs on one site each return the right status, one permanent redirect at most, a matching canonical tag and a correct sitemap entry, checked with a repeatable test sheet.
One, for the section's addresses
Redirects, canonical tags and sitemap entries for the agreed pages and any old addresses.
Fix layout that breaks on phones or tablets for one page Job Optional
Up to five named layout defects on one page are gone at four agreed screen widths, with before and after screenshots and an automated screenshot check you can keep.
One per page with a layout defect
Added at its own price where a layout defect would block the other checks.
How an engagement works
The price covers the agreed pages, flow and standard only. Pages you add later are quoted separately, and items that turn out to be bigger jobs are re-scoped with you.
How it starts
You send the section, the ten pages that matter and the reason the work is needed now.
We run the pages, propose the standard and the price, and mark which items are likely to need more than a small fix.
You agree the standard, the list, the price and the terms in writing. Nothing starts before then.
We fix against the standard, sending a pull request and its evidence for each group of fixes.
We run the combined re-test, send the results table and final summary and hand over anything left open.
Who decides what
You agree the standard and accept the results table. Your team merges, applies redirects and deploys on its own gates.
Handover
Each group of fixes arrives as a pull request with evidence. Redirect rules arrive as files for your team to apply. Anything left unfinished is handed back with notes.
Sharing your product safely. Send the page list and any reports, never credentials or customer data. After you agree the project, invite us to a repository or fork you control and set up a staging address.
What is included, and what is not
- A pull request for each group of fixes, with before and after evidence
- The results table: every page, metric, criterion and address rule against the standard
- A final summary: items met, items removed, and anything that turned out to need a bigger job
Included
- One section of one site, up to ten agreed pages, and one flow of up to five screens for the accessibility checklist
- A written standard agreed first: up to three page-and-metric speed limits, the accessibility criteria and the address rules
- Fixes for what misses the standard, using the same jobs you could buy alone (up to three speed fixes, one accessibility pass and one address cleanup; a layout repair is added at its own price where a defect would block the other checks)
- One combined re-test of all ten pages and the flow against the standard, with a results table, and the speed of the other pages measured and shown without a pass promised
- A written final summary showing each item and how it ended
Not included
- Pages outside the agreed ten, or more than one flow, unless you add them in writing
- More than three page-and-metric speed fixes: each further one is quoted at the speed job's own price
- Redesigns, new features, content writing or search-ranking work such as keyword research or link building
- A guaranteed ranking, traffic or conversion outcome, or a legal accessibility statement
- Hosting, DNS and content-network changes and production deployment, which stay with your team
- Fixing third-party components you will not change
- A guarantee that every item on a draft list can be met: items that cannot are named and removed or re-scoped with you
How we know it’s done
Agreed with you before work starts. Each check produces evidence you keep.
Every page-and-metric item on the agreed speed list (up to three) is within its limit on the fixed lab profile, as the median of five runs, in the combined re-test. The other pages are measured in the same re-test and shown in the table without a pass promised.
Evidence: The results table with all raw runs.
Every criterion on the agreed accessibility checklist is recorded as pass or not applicable for every screen of the agreed flow, with the method named.
Evidence: The accessibility rows of the results table.
Every address on the agreed list returns its expected status in at most one permanent redirect, with one self-referencing canonical tag and a correct sitemap entry.
Evidence: The address rows of the results table.
Sign-off. You review the results table, try the section yourself, accept each item or send it back with comments, and then you accept the finished table.
If it fails. An item we cannot meet is named with the reason and what it would take, and is taken off the list with a matching change to the price. Nothing is billed as delivered that you have not accepted.
When it fits, and when we stop
It fits when
- The pages are public or on a staging address with the same scripts and content
- The pages' source and templates can be changed through code you control
- You can agree the standard and sign it off in writing before work starts
- A person on your side can accept changes and deploy
We stop and tell you if
- The section is built in a closed tool whose output you cannot edit
- Most failures sit in third-party components you will not change
- The standard cannot be agreed, or you need a legal compliance statement
What could go wrong
Every group of fixes is a separate pull request that your team merges, so any one can be reverted on its own. Redirect rules are handed over as files that your team can remove. If the project stops, accepted items stay accepted and the rest is handed back with notes.
Scroll the table sideways to read it all.
| Risk | How we handle it |
|---|---|
| The standard is vague, so the project never finishes. | The standard is written first as measurable limits, a named checklist and address rules, and signed off before work starts. |
| A figure is met by hiding or removing content. | Every change shows before and after screenshots and a check that agreed elements remain. |
| A result is read as a legal compliance statement or a ranking promise. | The results table says what it covers and states plainly that it is neither. |
Each change is reviewed separately from the work that produced it, including a check that no content or feature was removed to meet a figure. You accept the results table. No human supervisor is included unless your proposal names one. At launch the work is largely automated, and we say so.
Stays with a person
- You agree the standard and accept the results table
- You merge, apply redirects and deploy on your own gates
Access we would need
- Read access to a repository or fork you control; no production access
- A staging address with test data
Questions
Is this an accessibility certificate or a ranking guarantee?
No. It meets a written standard we agree, for pages and a flow we agree, and shows the result in a table. It is neither a legal statement nor a ranking promise.
What if a third-party widget blocks an item?
We cannot change a component we do not control. The item is named in the table and removed, or re-scoped with you.
Can I buy just one of the three?
Yes. The speed, accessibility and address jobs can each be bought alone; this project is for a section where you want them agreed and finished together.
Why does the project cost more than the three jobs added up?
At their from prices, three speed fixes, the checklist and the address job come to £2,475. The project adds the written standard, one combined re-test of all ten pages and the flow, the results table and the final summary, which the single jobs do not include. It is a test price, and the quote is fixed for the list we agree.
Send an enquiry
Send us
- The section and the ten pages that matter most, and the reason the work is needed now
- Any reports you already hold on speed, accessibility or address problems
- Who accepts changes and who deploys
Later, once you agree
- Source access through an agreed company-controlled route, with a branch or fork for pull requests
- A staging address with test data that holds no customer information
- The signed-off standard, the page list, the price and the terms in writing
Your site, content, domain and accounts stay yours. We work on branches or a fork you control and return pull requests, using test data. Your team applies redirect rules and deploys.
Email fallback: open your mail app
If website submission is unavailable, review and send the fallback email yourself. An email fallback is not a website receipt. Or write to hello@syntheticindustry.ai with “web-page-quality-pass-one-site-section” as the subject.