Web performance optimisation: slow is expensive, fast is engineered.
Engineers who own the fix make your site measurably faster: Core Web Vitals repaired in the templates, page weight cut to budget, server latency profiled to the query. Your real baseline is measured before anything is promised.
Free five-minute video review · Baseline after NDA · Engineer-led fixes
In one answer
PixelCrayons' performance service makes websites and web apps measurably faster, and keeps them fast with budgets enforced on every release. Engineers profile your real baseline first: Core Web Vitals, image and JavaScript weight, backend latency, then fix causes at code and template level and report the measured delta, whatever it is. No before/after scores are invented or promised ahead of measurement. Once we have a complete brief, we confirm the date you will receive your priced plan; the measured baseline follows the NDA. Direct for brands, white-label for agencies.
Baseline measured before anything is promised✦
Performance budgets agreed in writing✦
Proposals itemised and priced✦
Fixes shipped at template level, not PDF'd✦
4,500+ projects delivered since 2004✦
Clear IP & Ownership Terms✦
White-label performance work for agencies✦
Baseline measured before anything is promised✦
Performance budgets agreed in writing✦
Proposals itemised and priced✦
Fixes shipped at template level, not PDF'd✦
4,500+ projects delivered since 2004✦
Clear IP & Ownership Terms✦
White-label performance work for agencies✦
04
How it starts
From unmeasured to measurably moving.
01
Days 1 to 2
NDA signed, baseline instrumented
Access granted, field data reviewed, lab profiles run on real-world hardware and connections. Measurement starts before opinions do.
02
Complete brief
Findings and a priced plan
The baseline in plain English: which templates hurt, why, and what each fix costs, itemised and sequenced by expected payoff.
03
Week 1
Budgets agreed, first fixes shipped
Per-template budgets in writing, the fixes with the biggest payoff first, each landing as reviewed code in your repository with CI checks alongside.
04
Start
First deltas, measured
The first fixes re-measured against the baseline and the delta reported, whatever it says: evidence of movement, not a slide about intent.
Inside Prism
Your engagement, week to week, in one workspace.
Where the engagement includes it, your build runs in a Prism workspace you log into: requests, approvals, the task list and the weekly review, beside the repository your team already owns.
Each decision recorded, with the expectation attached.
In every engagement
What performance engineering actually includes.
01
A baseline you can hold us to
Before any fix is proposed, we measure how the site actually performs. Field data from your real visitors, and lab profiles on mid-range phones and slow connections, not a dev machine on office wifi. The baseline report states where you are, which templates hurt most and why. Every target is set from that evidence, and every later claim is a delta against it.
First
02
Core Web Vitals, fixed at the cause
Core Web Vitals (Google's three measures of loading, responsiveness and visual stability) are symptoms. The causes live in templates, render paths, scripts and layout. We fix the causes: image priority for loading, script cost for responsiveness, reserved space for stability. No chasing a score with hacks that decay. Fixes ship as reviewed code in your repository, not as recommendations in a PDF.
Per template
03
Image and JavaScript budgets
The two heaviest things most sites ship are pictures and scripts, so both get a written budget per template. Images sized, compressed and modern-formatted through a proper media pipeline; JavaScript split, deferred and, most powerfully, deleted where it isn't earning its weight. Third-party tags get the same audit, with a plain list of what each one costs you to keep.
In writing
04
Backend and infrastructure latency
Front-end polish cannot rescue a slow first byte. We profile the server side: slow queries, missing indexes, cache layers that don't cache, CDN and hosting configuration. Then we fix what the evidence indicts. This is the half of performance work that front-end-only audits skip, and it is frequently where the largest and cheapest wins are hiding.
Profiled
05
Regression protection that outlasts us
Speed regained is easily lost to the next feature, so the budgets are wired into your CI. Releases that blow a template's budget fail loudly before they ship, and monitoring watches the field data after. The deliverable is not a fast Tuesday. It is a system that keeps the site fast when we're no longer looking, documented and owned by you.
The performance budget, and the trace behind each number.
What you receive in month one
Performance work is reported from field data and lab traces you can re-run. In the first month you receive the baseline of real-user metrics by template, the trace review naming the scripts, images and requests that cost the most, and the budget setting a ceiling per page type. Each fix is logged with its before and after measurement, so nothing is claimed from memory.
01Field baseline: real-user metrics by template, from your own analytics
02Trace review: the heaviest scripts, images and requests, ranked
03Performance budget: a ceiling per page type, checked on every deploy
04Fix log: each change with its before and after measurement
05Regression alert: what fires when a deploy breaks the budget
Sometimes the fix is a template; sometimes it's the platform, the pipeline or the tests around it. Each neighbour here is a service you can buy on its own.
Core Web Vitals also appear inside search work: as one ranking signal among many in an SEO programme. That lane is our technical SEO service. This page is the engineering service: speed bought for revenue and experience, whoever sends the traffic, and if the speed problem is really a conversion problem, CRO is the neighbour to call.
Each one says where it applies and links to its full terms.
Response and start times
We typically respond within four business hours. Eligible engagements can typically start within two to three business days after scope, payment and required access are confirmed.
Business hours are Monday to Friday, 9:00 am to 6:00 pm IST, excluding published company holidays. Typical expectations, not guaranteed service levels.
Every delivery is reviewed before release by QA, your Project or Account Manager and a senior delivery lead, and you then review it against the acceptance criteria agreed at the start. Our specialists use AI to support delivery, with people responsible for reviewing the work. Applicable development work includes 30 days of corrective maintenance after production launch.
Who owns the ad accounts, the data and the work?
Your materials, data and accounts remain yours, and we prefer to work in advertising and analytics accounts you own, with access delegated to our team. Agreed ownership rights in bespoke deliverables transfer under the engagement terms and applicable payment; third-party software and assets keep their licences. We do not withhold customer-owned data or accounts over a payment dispute.
What if we want to stop?
Cancellation, notice and any renewal terms are written into your proposal or statement of work before you accept it. If an engagement ends early, we hand over completed, paid-for work and list any unfinished work separately. For an eligible specialist trial, you can stop within the trial window and pay nothing for eligible trial hours.
How will we know what you are doing?
Before work starts we agree how often you get updates, what the reports cover and who sends them. You know who coordinates your engagement, who owns the work and how to escalate an issue. For hourly and retainer work, time is recorded in Workstatus, so you can see the time records behind your invoice.
We won't quote a number before we've measured your site, and we'd treat anyone who does with suspicion. The honest sequence is: baseline first, on your real templates, devices and traffic; then a plan stating which fixes we expect to matter and why; then the measured delta reported after each release, whatever it says. Gains depend on where your site starts, how much of the weight is yours to remove and what constraints stay fixed. That's exactly why the baseline, not a sales page, is where the promises come from.
No, and a guarantee sold before measurement isn't one worth having. The result of any Core Web Vitals optimization depends partly on choices that remain yours (a tag manager full of third-party scripts, an embedded widget the business insists on) and partly on your traffic's real devices and networks. What we do commit to is process: causes fixed at template level rather than score-chasing hacks, budgets agreed in writing and enforced in CI, and plain reporting of the field data. Where something outside our control is holding a metric down, we say so, with what it would take to change it.
Same engineering muscles, different job. Technical SEO is a search discipline: crawling, indexation, structured data and rendering, with Core Web Vitals as one ranking signal inside a broader programme. You buy it to win search visibility. This page covers our page speed optimization services: you buy them because slow pages cost revenue and patience, whether the visitor came from Google, an ad or a bookmark. If search is the goal, start with technical SEO; if speed itself is the problem, start here. On engagements that need both, the two teams work from one plan instead of billing you twice for overlap.
Whatever the profile indicts, in payoff order. Typically: images resized, compressed and modern-formatted through a real media pipeline; JavaScript split, deferred or deleted, with third-party tags audited for what they cost; fonts subset and loaded sanely; templates and render paths reworked for the three vitals; then the backend: slow queries, missing indexes, caching, CDN and hosting configuration. Occasionally the finding is that the platform is the ceiling, and we say so, with a costed view of what a migration would buy, rather than polishing something structurally slow.
Both exist, and most website speed optimization engagements are a sprint followed by a guard. The sprint measures the baseline, ships the fixes and reports the deltas; the guard is what stops the next quarter's features undoing it: budgets enforced in CI, monitoring on the field data, and a monthly check that the graphs still hold. The guard is a choice, not a hostage situation: everything we build is documented in your repository, so your own team can run it. Either way, the plan is itemised and priced.
Yes on both counts. Performance retainers are one of the easiest services to add to an agency offer: your brand on the reports, our engineers on the fixes, NDA-backed. We do not approach the clients you introduce to us for direct business. That protection runs through the work and for twelve months after the last assignment for that client ends, and it is written into the agreement. And every fix ships as reviewed code in the client's own repository, with IP and ownership terms agreed in writing before work starts.
Send us the URL and what feels slow. Pick the free website review and a senior strategist records five minutes on what's costing you. Pick the proposal and the engineering comes back itemised and priced. The instrumented baseline (field data, lab profiles on real devices) starts the day the NDA is signed, and the numbers are yours whoever does the fixes.
