Web performance optimisation:
faster pages for every visitor.

Our developers make your site measurably faster. They fix Core Web Vitals in your page templates, make pages lighter and speed up your server. We measure your site's real speed before we promise anything.

Get a Proposal Get a Free Website Review

Free website 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 size limits checked at every release. Our developers first measure how fast your site really is. Then they fix the causes in code and templates. We report the measured change, whatever it is. We work direct for brands and white-label for agencies.

A starting measurement you can hold us toReal-visitor data and tests on mid-range phones, measured before any fix, so every result is a measured change.
Core Web Vitals, fixed at the causeLoading, responsiveness and stability fixed in the page templates, delivered as reviewed code in your own code store.
Size limits for images and JavaScriptA written size limit for images and JavaScript on each page type, with the cost of every outside tag listed.

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
Speed limits agreed in writing
Proposals itemised and priced
Fixes made in your code, not left in a report
4,500+ projects delivered since 2004
Clear IP & Ownership Terms
White-label performance work for agencies
Baseline measured before anything is promised
Speed limits agreed in writing
Proposals itemised and priced
Fixes made in your code, not left in a report
4,500+ projects delivered since 2004
Clear IP & Ownership Terms
White-label performance work for agencies

How it starts

From first measurement
to measured results.

Start

Brief and access

We sign an NDA and you give us access. We review your real-visitor data and test the site on everyday phones and connections.

Once the brief is complete

Audit and itemised proposal

We confirm the date your proposal arrives. It explains your current speed in plain English and which page types hurt and why. Each fix is priced and ordered by how much it helps.

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

We write down the size limits for each page type and make the fixes that help most first. Each one is reviewed code in your code store, with automatic checks.

On the date in your proposal

First results, measured

We measure the first fixes against the starting point and report the change, whatever it says. The next fixes follow, most helpful first.

Inside Prism

Your engagement, week to week,
in one workspace.

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

Some engagements include Prism, our client workspace, and your proposal says whether yours does. Where it does, your build runs in a 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 our speed work
includes.

A starting measurement you can hold us to

Before we suggest any fix, we measure how your site really performs. We use data from your real visitors, and tests on mid-range phones and slow connections, not a fast office computer. The report shows where you are, which page types hurt most and why. We set every target from that evidence, and measure every later result against it.

First

Core Web Vitals, fixed at the cause

Core Web Vitals are Google's three measures of loading, responsiveness and visual stability. A poor score is a symptom. The causes sit in templates, scripts and layout, and we fix those. We load key images first, cut script work so pages respond faster and reserve space so layouts don't jump. No quick tricks that wear off. Fixes arrive as reviewed code in your own code store, not as advice in a PDF.

Per template

Size limits for images and JavaScript

Images and scripts are the two heaviest things on most sites, so each page type gets a written size limit for both. We resize and compress images and use modern formats. We split and delay JavaScript, and remove scripts that aren't worth their weight, which helps most. Outside tracking tags get the same check, with a plain list of what each one costs you.

In writing

Faster servers and hosting

Front-end work can't fix a server that is slow to respond. So we test the server side too: slow database queries, missing indexes, caches that don't work, and CDN and hosting settings. Then we fix what the evidence points to. Front-end-only audits skip this half, yet it is often where the biggest and cheapest gains are.

Profiled

Checks that keep your site fast after we leave

Speed is easily lost to the next new feature, so we build the size limits into your release process. A release that breaks a page type's limit is stopped before it goes live. Monitoring then watches real-visitor data. What you get is not one fast day. It is a setup that keeps the site fast long after we finish, documented and owned by you.

Every release

Our work

See what we've built
and the results it brought.

Real projects for real clients, with results we can show.

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

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

Services that often go
with speed work.

Sometimes the fix is a template. Sometimes it is the platform, the release process or the testing around it. You can buy each service here on its own.

01All DevelopmentOur development home page: web, commerce and the technical services around them, from one senior team.02Web DevelopmentCustom builds made to speed limits from the first sprint, so you never start behind.03MigrationsWhen the platform itself holds you back: moves with zero data loss and redirects mapped first.04DevOpsAutomated releases and monitoring: where speed limits are checked and slowdowns are caught.05QA & TestingRepeat tests and release checks that keep fast pages fast, release after release.

Want better rankings rather than faster pages?

Core Web Vitals also matter in search, as one ranking signal among many. That work belongs to our technical SEO service. This page is about speed for sales and a better visit, wherever your visitors come from. If slow pages are really a conversion problem, our CRO service can help.

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

Who is accountable

The people responsible
for your work.

Leadership and how we’re built →

Parvessh Agarwal

Founder & CEO

An entrepreneur at heart. He links business analysis, strategy, clear goals and ROI to practical technology.

LinkedIn →

Saundaraya Gupta

Technical Manager

Brings technical work, client updates and project management together, so work moves smoothly from brief to launch.

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 results

What the first measurement shows,
and what we change.

We fix whatever the tests point to, most helpful first. These are the problems we see most and the change each one gets. In two cases, we tell you the answer sits outside the code.

What the tests show	What we change	Why
Pages slow to show their main content	Key images load first, resized, compressed and saved in modern formats	Images are one of the two heaviest things on most sites, so each page type gets a written size limit.
Pages slow to respond to a tap or click	JavaScript split, delayed or removed where it is not worth its weight	Scripts decide how fast a page responds, and removing one helps most.
Layout that jumps while the page loads	Space reserved in the templates	We fix the cause, not the score, with no quick tricks that wear off.
A server that is slow to respond	Server tests: slow queries, missing indexes, caches that do not work, CDN and hosting settings	Front-end work cannot fix it, and it is often where the biggest and cheapest gains are.
Outside 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 score down, we say so, and what it would take to change it.
A platform that is slow by design	A priced view of what a migration would gain	We tell you the platform is the limit rather than polish something that can't get faster.

Every fix is reviewed code in your own code store. We report every result as a measured change from the starting point, 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 measure your real pages, devices and traffic, and plan which fixes should matter and why. After each release we report the measured change, 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 outside scripts in a tag manager. They also depend on your visitors' real devices and networks. We commit to the process. We fix causes in the templates, agree size limits in writing and check them at every release. We report the real-visitor data plainly, including what's outside our control.

Technical SEO is search work. Core Web Vitals are one ranking signal there, alongside crawling, indexing, structured data and rendering. Our page speed optimisation services are for when slow pages cost you sales, wherever the visitor came from. If search is the goal, start with technical SEO. If speed itself is the problem, start here.

We change whatever the tests show, most helpful first. Usually we resize and compress images, and split, delay or remove JavaScript. We trim fonts and rework templates. Then we look at the server: slow queries, missing indexes, caching, CDN and hosting. If the platform itself holds you back, we say so and price what a migration would gain.

It can be either, and most clients have a short burst of fixes followed by ongoing checks. The burst measures where you start, makes the fixes and reports the changes. The checks enforce size limits at every release, watch real-visitor data and confirm each month that the gains hold. It's all documented in your code store, so your own team can run the checks instead.

Yes. Your brand goes on the reports and our developers make the fixes. 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 is reviewed code in the client's own code store, with IP and ownership terms agreed in writing first.

The range

What it costs,
at the direct rate.

A baseline audit if you want the diagnosis first, and a fixed-quote sprint that ships the fixes. Then a monthly guard, so new features do not undo them. No number is promised before we measure.

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 we measure the page, its speed on a phone included, and a person reviews the report. 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 Proposal Get a Free Website Review

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

Last updated 26 October 2026

Web performance optimisation:faster pages for every visitor.

From first measurementto measured results.

Brief and access

Audit and itemised proposal

You sign off

The work starts

First results, measured

Your engagement, week to week,in one workspace.

Requests and approvals

Owned tasks

Weekly review

What our speed workincludes.

A starting measurement you can hold us to

Core Web Vitals, fixed at the cause

Size limits for images and JavaScript

Faster servers and hosting

Checks that keep your site fast after we leave

See what we've builtand the results it brought.

The performance budget,and the trace behind each number.

Keeping a store running smoothly,fix after fix.

Services that often gowith speed work.

Want better rankings rather than faster pages?

The people responsiblefor your 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 first measurement shows,and what we change.

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:
faster pages for every visitor.

From first measurement
to measured results.

Your engagement, week to week,
in one workspace.

What our speed work
includes.

See what we've built
and the results it brought.

The performance budget,
and the trace behind each number.

Keeping a store running smoothly,
fix after fix.

Services that often go
with speed work.

The people responsible
for your work.

What the first measurement shows,
and what we change.

Frequently
asked.

What it costs,
at the direct rate.

Practitioner notes
on this work.

Get your baseline,
then decide.