Website speed optimization

Website speed optimization services, measured on a phone before and after

We measure each template the way your visitors load it, find the largest cause of delay on each one, fix it on a staging copy you approve and measure again, so the change is a number in a document.

Request a speed review
Trusted by the world's fastest-growing brands

Portfolio · selected work

The work, not the deck.

Every site below is live and owned by the client. Each window is a capture of the real page, not a drawn mockup.

Categories we work across
HospitalityFinancial servicesManufacturing and exportConsulting and researchRecruitmentD2C
urjalifes.inUrjalife's Pravaah resort website: rooms, activities and dining across a photographic homepage.
UrjalifeHospitality
adventswealth.comAdvents Wealth website: a financial planning homepage covering wealth building, tax and retirement.
Advents WealthFinancial services
syounaa.inSyounaa website: a wellness apparel storefront built around smart-textile product ranges.
SyounaaWellness apparel
infokool.comInfokool website: a precision cooling manufacturer, with an outdoor cabinet product grid and capability sections.
InfokoolManufacturing
howardjohnsonhinton.caHoward Johnson Hinton website: a mountain-lodge hero over a room-booking bar, followed by renovated room types.
Howard Johnson HintonHotel
sycamoreconsultant.comSycamore Consultancy website: a recruitment agency, with separate paths for employers and candidates.
Sycamore ConsultancyRecruitment
stutiexports.comStuti Exports website: a technical fibers and specialty yarns exporter, with core markets and capability sections.
Stuti ExportsTechnical textiles
duhomespg.inDuhomes website: student housing, with walking distances to nearby colleges and a room rate table.
DuhomesStudent housing
vaspro-global.comVasPro Global website: a technical advisory and project consulting firm, with expertise and mission sections.
VasPro GlobalConsulting
pretor.aePretor website: a marketing research and promotion consultancy, opening on research, strategy and growth planning.
PretorMarketing research

What the work covers

Three numbers that tell you why a page is slow

Website speed optimization services find what delays a page on a visitor’s phone and remove it. A single score cannot do that, because a page can be slow for four unrelated reasons. We keep three numbers for each template, and each one answers a question the score leaves open.

Sample Keystone Garage DoorsHome pageField · phones4.1 s75th percentileLab · one test4.6 sThrottled phoneCause list · lab 4.6 s, in four parts30%20%35%15%First byte1.4 sLoad delay0.9 sLoad duration1.6 sRender delay0.7 s

The field number

Field data is collected from real visits, on the phones and connections your visitors have. We read it for each template where Google reports it. Where a template has too few visits for Google to report, the review says so and leans on the lab figure instead. It is the number that matches what people experienced, and it is the one we want to move.

The lab number

A lab test loads the page on one device and one network, the same way each time. That repeatability lets us see the effect of one change at a time on a staging copy.

The cause list

We split the load time into the wait for the first byte, the delay before the main image is requested, the time it takes to download and the time to paint it. The largest part gets fixed first, so effort goes where the time is.

How it’s done

Two ways to speed up the same website

Both can shorten a load time. They differ in how much you know about why the site was slow, and in what stays fast after the next plugin or campaign tag is added.

Site-wide settingsOne layer over everythingTemplate by templateCause found, then fixed
Starting pointA single score for the home page, run from a desktop or a testing siteField and lab results for the home page, a service page, a listing and a form page, each on its own
The fixAn optimization plugin or a host setting applied across the whole siteChanges to the page that is slow: the hero image, the scripts it waits for, the server’s response
Risk to the siteSwitched on live, with problems found by visitors or staffTested on a staging copy, with forms, menus and tracking checked before release
What you can read afterwardsA list of the settings that were turned onA change log with the measured effect of each change
The next marketing tagNo record of what a new script adds until the score dropsA script budget that says what each outside script costs in load time
When settings are enough

On a small site with one template and a few images, a plugin may be all it needs, and we will say so in the review. The template-by-template approach earns its time when the site has several page types, a page builder, a store or a stack of marketing scripts.

The facts

Six facts that shape a speed project

What Google’s web.dev, Chrome’s Lighthouse team and Google Search Central say about measuring and improving load time. Sources under each.

  1. Where the time goesweb.dev

    Largest Contentful Paint has four parts, and two of them should be small.

    web.dev splits LCP into time to first byte, resource load delay, resource load duration and element render delay. Its guideline puts about 40% in the first byte and about 40% in load duration, and under 10% in each delay. A page far from that split points to its cause.

  2. The hero imageweb.dev

    Google says never to lazy-load the image that is the LCP element.

    Lazy loading holds the request back until the browser confirms the image is in view, which adds load delay. web.dev advises fetchpriority “high” on the LCP image, and warns that using it on more than one or two images stops it helping.

  3. What a score weighsChrome for Developers

    Three metrics make up 80% of a Lighthouse 10 performance score.

    Lighthouse 10 weights Total Blocking Time at 30%, Largest Contentful Paint at 25% and Cumulative Layout Shift at 25%, with First Contentful Paint and Speed Index at 10% each. A score is therefore a blend, and two sites with the same score can be slow for different reasons.

  4. Lab and field differweb.dev

    A lab test loads the page on a cold cache, and the field does not.

    web.dev lists the reasons lab and field results differ: one device and network in the lab, a cold cache, no back/forward cache, and a page that is not personalized. Visits in the field include returning users, scrolling and varied phones. We read both and say which one a finding comes from.

  5. Responsivenessweb.dev

    A page can have very good Total Blocking Time and still have poor INP.

    web.dev says Total Blocking Time, a lab metric, does not capture every cause of a slow response to a tap, so a page “may have poor INP despite having very good TBT scores.” Interaction delay is therefore checked in the field data, and the lab figure is read as a clue.

  6. SearchGoogle Search Central

    Google says its core ranking systems look at a variety of signals that align with overall page experience.

    Google also says Search always seeks to show the most relevant content, even if the page experience is sub-par. Speed is one signal among several, so it supports a good page and does not replace one.

The scope

What website speed optimization produces

Each part of the work ends in something you can open: a table, a log, a setting or an account. What is covered, and what is quoted separately, is set in the written scope.

Speed baselineSampleTemplatePagesField LCPLab LCPHome14.1 s4.6 sService page123.8 s4.2 sGallery85.2 s6.0 sBlog post243.3 s3.5 sQuote request12.9 s3.1 s5 templates46

Baseline on a phone

We pick the page types that carry your traffic, such as the home page, a service or product page, a listing and the form page. Each is measured in the lab on a throttled phone profile, and read in Google’s field data where the site has enough visits. You receive: a baseline table with one row for each template.

Field dataLab testTemplates
Filmstrip · home pageSampleBefore4.6 sAfter3.4 s1 s2 s3 s4 s5 sImage tag, 150 KB, high prioritySaved 1.2 s

The main image and the first paint

We find the element that counts as the largest paint on each template, then check that it is a real image tag the browser can find early, that it is sized for a phone and that nothing delays it, such as lazy loading or a slider script. Fonts that block text are handled here too. You receive: the list of changes to the main image and fonts, with the time each saved.

LCPHero imageFonts
Script inventory · homeSampleTag managerMarketing · quotesKeepDelayRemoveSlider scriptPage builder · heroKeepDelayRemoveChat widgetOffice · live chatKeepDelayRemoveReview widgetMarketing · reviewsKeepDelayRemoveSlider removed, chat on openSaved 0.3 s

Scripts and third parties

We list each script the page loads, who added it and what it does, then remove the ones with no job, delay the ones that can wait and load a chat or review widget when a visitor asks for it. Tracking is tested again afterward. You receive: a script inventory with the cost of each and a decision beside it.

Tag managerChatWidgets
Response headers · homeCachedGET /keystonegaragedoors.test200BeforeAfterx-page-cacheHITx-cdn-cacheHITcache-controlpublic, max-age=600Before: built for each visit1.4 s first byteLab LCP, home page3.4 s → 2.6 s

Caching and server response

We check how long the server takes to send the first byte, whether pages are cached, whether a CDN sits in front and whether the hosting plan or PHP version is the limit. Hosting changes are proposed with the cost before anything moves. You receive: a server response record, and the cache and CDN settings written down.

Page cacheCDNHosting
Elements that movedSampleHero imageWidth and height set on the imageReview widgetSpace reserved before it loadsOffer bannerMoved into the header, fixed heightAaWeb fontFallback sized to match the font

Layout stability

Layout shift is traced to images and embeds without reserved space, banners that push content down and fonts that swap late. We set dimensions, reserve space and test the phone layout while the page loads. You receive: a list of the elements that moved and the change made to each.

CLSImagesEmbeds
Before and after4 of 5 under 2.5 sSample · labBeforeAfter2.5 sService page4.2 sBlog post3.5 sQuote request3.1 sGallery6.0 sHome4.6 s3.1 s2.2–2.4 s

Re-measure and handover

After release, each template is measured again with the same settings as the baseline, and the field data is read again once enough visits have been collected. We agree on a script budget for future additions. You receive: the before and after table, the change log, and the script budget your team can apply to any new tag.

BeforeAfterScript budget

How it runs

Measure, find the cause, fix on staging, measure again

You approve each stage before the next begins, and the stage hands you a table to keep.

speed-baseline.csv

Speed baseline

Sample · Sample Keystone Garage Doors, Pittsburgh, PA
TemplatePagesField LCP (phone)Lab LCP (throttled)
Home14.1 s4.6 s
Service page123.8 s4.2 s
Gallery85.2 s6.0 s
Blog post243.3 s3.5 s
Quote request12.9 s3.1 s
Five templates cover 46 pages: 1 + 12 + 8 + 24 + 1. Field figures are the 75th percentile for phone visits, as Google reports them.

Our stack

The tools we use to find the delay and prove the fix

Measurement tools and the platforms where fixes are made. Pick one for the detail.

Lighthouse
Why Lighthouse

Lighthouse is Google’s open-source tester for a page’s speed, accessibility and best practices, and it runs in Chrome or from the command line.

How we use it

We run it on a throttled phone profile with the same settings each time, so a before and after compare like with like and a single change shows its own effect.

Perf auditCWVIn CI
LighthouseYes
PageSpeedNo
GTmetrixPaid
WebPageTestYes

Questions

Website speed optimization services, answered

Start here

Request a speed review of your website

Give us your site’s address and the platform behind it. We’ll measure your main templates on a phone, read the field data, list what delays each page and quote the work in a written scope.