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.

Get a Free Website Review See Pricing

Free five-minute video review · Baseline after NDA · Engineer-led fixes

Brands our teams have delivered for

What we do

PixelCrayons' performance service makes websites and web apps measurably faster, and keeps them fast with budgets enforced on every release. Engineers measure your real baseline first, from Core Web Vitals to backend latency, then fix causes at code and template level and report the measured delta, whatever it is. We work direct for brands and white-label for agencies.

A baseline you can hold us toField data and mid-range-phone lab profiles measured before any fix, so every claim is a delta.
Core Web Vitals, fixed at the causeLoading, responsiveness and stability fixed at the template, shipped as reviewed code in your repository.
Image and JavaScript budgetsA written image and JavaScript budget per template, with every third-party tag costed.

Related work · Commerce · Saudi Arabia

Al Majed for Oud: a fragrance house's whole catalogue, online in two languages.

Read the case study

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

How it starts

From unmeasured
to measurably moving.

Start

Brief and access

We sign an NDA, you grant access, and we review your field data and run lab profiles on real-world hardware and connections.

Once the brief is complete

Audit and itemised proposal

We confirm the date your proposal arrives: the baseline in plain English, which templates hurt and why, and each fix priced and sequenced by payoff.

Your decision

You sign off

You confirm the scope, the payment and the access we need. Nothing starts before this.

Typically 2 to 3 business days later

The work starts

Per-template budgets go in writing and the biggest-payoff fixes ship first, each as reviewed code in your repository with CI checks.

On the date in your proposal

First deltas, measured

The first fixes are re-measured against the baseline and the delta reported, whatever it says. The next fixes follow in payoff order.

Inside Prism

Your engagement, week to week,
in one workspace.

Prism is the client workspace where your requests, approvals, tasks and weekly reviews live.

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.

See how Prism runs an engagement

01
Requests and approvals
One queue, beside the repository your team owns.
02
Owned tasks
Every task has one owner and a date.
03
Weekly review
Each decision recorded, with the expectation attached.

In every engagement

What performance engineering
actually includes.

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

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

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

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

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.

Every release

Selected work

Judge the work,
not the adjectives.

Outcomes tied to real engagements, not averages.

All case studies →

2004

Established

500+

Agencies served

4,500+

Projects delivered

340%

Revenue growth · 7 months

eCommerce

+127%

Organic traffic · 5 months

SaaS

85%

Faster delivery · backlog cleared

via agency partner

Checked 15 September 2026

Where the work happens

How we report it, in Prism

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

Related workAl Majed for Oud: a fragrance house's whole catalogue, online in two languages.Commerce · Saudi Arabia · A different discipline, so it is linked here rather than presented as proof of this one.

Al Majed for Oud’s site, Internet Archive copy, 1 April 2026

Related work

Keeping a store running smoothly,
fix after fix.

Select Specs' men's glasses page on desktop, from the Internet Archive's copy: collection buttons from Next Day Express to Semi-Rimless, a man in tortoiseshell glasses, and the Price & Collections and Size filters

Related work · Eyewear · United Kingdom

Select Specs: an eyewear store built for prescriptions, not just products.

eCommerce platform development

Read the case study

PixelCrayons has supported us across both development and ongoing improvements to our e-commerce platform. From product and catalogue functionality to prescription and lens selection, integrations and technical fixes, the team has helped keep the customer experience running smoothly.
David McMillan, CEO, Select SpecsSelect Specs

Around the speed work

Performance rarely
travels alone.

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.

01All DevelopmentThe hub: web, commerce and the engineering disciplines around them, one senior team.02Web DevelopmentCustom builds engineered to performance budgets from sprint one, so the speed work never starts in debt.03MigrationsWhen the platform itself is the ceiling: moves with zero data loss and redirects mapped first.04DevOpsCI/CD and observability: where performance budgets get enforced and regressions get caught.05QA & TestingRegression suites and release gates that keep fast pages fast release after release.

Chasing rankings rather than milliseconds?

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.

Technical SEO: vitals as a ranking signal CRO: conversion rate optimisation Case studies

Who is accountable

The people accountable
for the work.

Leadership and how we’re built →

Parvessh Agarwal

Founder & CEO

An entrepreneur at heart who connects business analysis, strategy, clear objectives and ROI with practical technology solutions.

LinkedIn →

Saundaraya Gupta

Technical Manager

Brings technical delivery, client communication and project management together so work moves from brief to release smoothly.

LinkedIn →

Every engagement

A named coordinator and escalation contact

Know who coordinates your engagement, who owns the work and how to escalate an issue.

All engagements. Roles may be combined and vary with your engagement.

Full terms →

Before you sign

Our commitments

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.

Full terms

30-Day Corrective Maintenance

Applicable development work includes 30 days of corrective maintenance after production launch.

Development engagements, including partner (agency) development engagements and AI implementations; not marketing services or retainers.

Full terms

Clear IP & Ownership Terms

Your materials remain yours. Bespoke deliverable rights, licences and handover are agreed before work starts.

All engagements.

Full terms

Clear Delivery & Escalation Ownership

Know who coordinates your engagement, who owns the work and how to escalate an issue.

All engagements. Roles may be combined and vary with your engagement.

Full terms

How we handle claims, credentials and your data: group credentials, dated ratings, how case figures are signed off, client permissions and data handling.

Reading the profile

What the baseline shows,
and what we change for it.

Fixes follow whatever the profile indicts, in payoff order. These are the findings we see most, the change each one gets, and the two cases where we tell you the answer sits outside the code.

What the profile shows	What we change	Why
Pages slow to show their main content	Image priority, with images sized, compressed and modern-formatted through a media pipeline	Images are one of the two heaviest things most sites ship, so they get a written budget per template.
Pages slow to respond to a tap or click	JavaScript split, deferred or deleted where it is not earning its weight	Script cost drives responsiveness, and deleting a script is the most powerful of the three.
Layout that jumps while the page loads	Space reserved in the templates	Stability is fixed at the cause, not chased with score hacks that decay.
A slow first byte	Server profiling: slow queries, missing indexes, caches that do not cache, CDN and hosting configuration	Front-end polish cannot rescue it, and it is frequently where the largest and cheapest wins are hiding.
Third-party tags, or a widget the business insists on	A plain list of what each one costs you to keep	Those choices stay yours. Where one holds a metric down, we say so, with what it would take to change it.
A platform that is structurally slow	A costed view of what a migration would buy	We say the platform is the ceiling rather than polish something structurally slow.

Every fix ships as reviewed code in your repository, and every result is reported as a measured delta against the baseline, whatever it says.

Questions

Frequently
asked.

It depends on where your site starts, and we won't quote a number before we've measured it. We baseline your real templates, devices and traffic, plan which fixes should matter and why, then report the measured delta after each release, whatever it says. Gains depend on how much of the weight is yours to remove.

No. Results depend partly on choices that stay yours, such as third-party scripts in a tag manager, and partly on your visitors' real devices and networks. We commit to process: causes fixed at template level, budgets agreed in writing and enforced in CI, and plain reporting of the field data, including what's outside our control.

Technical SEO is a search discipline, with Core Web Vitals as one ranking signal among crawling, indexation, structured data and rendering. Our page speed optimisation services are for when slow pages cost revenue, wherever the visitor came from. If search is the goal, start with technical SEO; if speed itself is the problem, start here.

Whatever the profile shows, in payoff order. Typically images go through a media pipeline, JavaScript is split, deferred or deleted, fonts are subset, and templates and render paths are reworked, then the backend: slow queries, missing indexes, caching, CDN and hosting. If the platform is the ceiling, we say so and cost what a migration would buy.

Both exist, and most engagements are a sprint followed by a guard. The sprint measures the baseline, ships the fixes and reports the deltas; the guard enforces budgets in CI, monitors the field data and checks monthly that the gains hold. Everything is documented in your repository, so your own team can run the guard instead.

Yes. Your brand goes on the reports and our engineers do the fixes, and we don't approach your clients for direct business during the work or for twelve months after the last assignment for that client ends. Every fix ships as reviewed code in the client's own repository, with IP and ownership terms agreed in writing first.

The range

What it costs,
at the direct rate.

A baseline audit for buyers who want the diagnosis first, a fixed-quote sprint that ships the fixes, and a monthly guard that stops the next quarter's features undoing them; no number is promised before measurement.

One-offBaseline audit$375–$1,875one-time
ProjectCore Web Vitals sprint$1,250–$7,500fixed quote, one-time
RetainerMonthly performance guard$200–$1,250per month

Indicative: every figure is refined into an itemised proposal.INR figures shown excl. GST.

PricingSee indicative pricing for this serviceDirect and wholesale, in ₹ and $ →

Practitioner notes
on this work.

All articles

14 August 2026 · 5 min read

Core Web Vitals: what actually moves LCP, INP and CLS, and how to read field data

Core Web Vitals move when you fix the broken link in the chain on pages that carry money, measured by real visitors.

22 October 2026 · 8 min read

PHP2Shell: how we patched 375 servers and hundreds of client sites in 12 hours

PHP2Shell (CVE-2026-109618 and CVE-2026-109619) lets one unauthenticated request run code on any PHP install that serves web traffic.

Get your baseline,
then decide.

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.

Get a Free Website Review White-label for agencies

Free website review · Baseline after NDA · Clear IP & Ownership Terms

Last updated 23 October 2026

Web performance optimisation:slow is expensive, fast is engineered.

From unmeasuredto measurably moving.

Brief and access

Audit and itemised proposal

You sign off

The work starts

First deltas, measured

Your engagement, week to week,in one workspace.

Requests and approvals

Owned tasks

Weekly review

What performance engineeringactually includes.

A baseline you can hold us to

Core Web Vitals, fixed at the cause

Image and JavaScript budgets

Backend and infrastructure latency

Regression protection that outlasts us

Judge the work,not the adjectives.

The performance budget,and the trace behind each number.

Keeping a store running smoothly,fix after fix.

Performance rarelytravels alone.

Chasing rankings rather than milliseconds?

The people accountablefor the work.

Parvessh Agarwal

Saundaraya Gupta

A named coordinator and escalation contact

Our commitments

Response and start times

30-Day Corrective Maintenance

Clear IP & Ownership Terms

Clear Delivery & Escalation Ownership

How do we know the work will be good?

Who owns the ad accounts, the data and the work?

What if we want to stop?

How will we know what you are doing?

What the baseline shows,and what we change for it.

Frequentlyasked.

What it costs,at the direct rate.

Practitioner noteson this work.

Core Web Vitals: what actually moves LCP, INP and CLS, and how to read field data

PHP2Shell: how we patched 375 servers and hundreds of client sites in 12 hours

Get your baseline,then decide.

Web performance optimisation:
slow is expensive, fast is engineered.

From unmeasured
to measurably moving.

Your engagement, week to week,
in one workspace.

What performance engineering
actually includes.

Judge the work,
not the adjectives.

The performance budget,
and the trace behind each number.

Keeping a store running smoothly,
fix after fix.

Performance rarely
travels alone.

The people accountable
for the work.

What the baseline shows,
and what we change for it.

Frequently
asked.

What it costs,
at the direct rate.

Practitioner notes
on this work.

Get your baseline,
then decide.