Frontend and Backend Optimisation

Frontend and backend optimisation measures both ends of a slow screen: server response time and browser rendering. The two are fixed in the order the numbers justify.

Share your requirements

Splitting the wait in two

The first useful number is how long your server took to answer, measured separately from how long the browser then took to draw the page.

Server answer time

How long before the first byte arrives. No amount of image work will improve it.

Draw time

What happens afterwards, from scripts and styles to images and fonts.

The ratio

Six seconds of server time and one of rendering is a different project from the reverse.

Why order matters

Doing both ends at once makes the result impossible to attribute. The work is sequenced on purpose.

The dominant half first

Whichever side holds the most seconds is fixed first, and it is measured again before the other side is touched, so the result can be attributed to that change.

One change at a time

Two changes released together do not show which of them worked.

Quick wins early

Anything that takes an afternoon and is visible to staff goes out first.

Where the two ends meet

Some problems belong to neither side alone. A specialist working on one end tends to miss them.

Endpoints per screen

A page waiting on nine separate calls, each quick on its own, adds up to a slow screen. Combining the calls fixes it.

Data the page never shows

An endpoint returns a hundred fields for a table that displays six of them.

Work done on the click

A PDF or a message generated inside the request belongs in a background job.

FAQ

Frequently asked questions

Can one team handle frontend and backend optimisation?

Yes. It avoids the stalemate where each specialist points at the other. The code is read on both sides, and your own developers are brought in where they know the history.

What if a different vendor maintains each end?

That is common. Both vendors are kept informed and receive the same measurements. Changes are handed back in a form the responsible vendor can maintain, and nobody is worked around.

How do we know the work helped?

The same journeys are timed on the same test after the changes, and you see both sets of numbers. A change that made no difference shows up too.

Talk to us

Tell us what you need.

Share your requirements and one of our engineers will come back to you within one business day.

No obligation
A reply within one business day
Your details stay private

Start with your requirements

Seven short steps that tell us what you need. An engineer reads them before getting in touch.

Share your requirements