Skip to content
Results
$28M+ Revenue GeneratedFor our clients2,140+ Keywords — Page 1Google rankings$12M+ Ad Spend ManagedAcross channels2.5M+ Signups DrivenUser acquisitions87,200+ Leads GeneratedQualified pipeline
Get proposal

Website Speed Optimization Services

Make your important pages faster without breaking what sells.

We'll reply with a written proposal: the work, what we need from you and an estimated timeline.

The hidden problems

Why a high speed test score isn't a plan for a fast website

Testing a single page, ignoring how real visitors experience the site, scripts from other companies that nobody owns and risky site-wide fixes can make a report look better while real visitors still wait, or key steps like checkout stay slow or break.

  • Speed scores don't match what visitors experience

    A green score in one lab test is treated as proof, while real visitors on different pages, devices and connections, with or without saved files, have a very different experience.

  • The main-content fix targets the wrong delay

    Teams shrink an image, when the real hold-up is how late the browser finds it, its loading priority, a slow server response or the time it takes to draw it on screen. LCP (Largest Contentful Paint) measures when that main item appears.

  • Slow responses are blamed only on code size

    The delay before the page reacts, the time spent handling a tap or click and the time to show the result are never tested on the tasks your visitors actually do. Together these make up INP (Interaction to Next Paint).

  • The page starts jumping after launch

    Fonts, embedded content, ads and parts of the page that change move things around, but only the first load was tested before approval. This movement is measured as CLS (Cumulative Layout Shift).

  • No one owns the cost of outside scripts

    Tracking tags, chat widgets, cookie consent tools, testing tools and media scripts pile up with no limit on how much browser work they use or what they cost the business.

  • Speed gains vanish in later updates

    Nothing protects the improvement: no speed limit for each page type, no dated starting point, no check before updates go live, no watch on real visitors and no one in charge of undoing a bad change.

Exactly what's included

What our website speed optimization service includes

Find out what is making your important pages slow, fix the causes we agree on and put changes live without breaking the path customers take to buy. Softscotch keeps lab tests (controlled tests run by a tool) separate from real-visitor data where it exists, puts work in order by likely benefit and risk, and checks the agreed pages before we hand over.

Eight areas of work cover groups of similar pages, where the evidence comes from, the causes behind Google's three Core Web Vitals (LCP, INP and CLS), outside scripts, fixes in order of priority, backups, making the changes, re-checks, going live and ongoing monitoring.

Starting point for your pages, customer paths and data

We list your most important pages and paths, page types, tasks visitors complete, recent updates, devices, connection types, groups of real-visitor data, lab test settings and gaps in the data we know about.

Why your main content loads slowly (LCP)

For the actual largest item on screen, we trace server response time, how soon the browser finds it, its loading priority, download time, drawing time, image sizes for different screens and any fonts it waits for.

Why the page is slow to respond (INP)

We repeat the most important taps and clicks and split the delay into waiting time, the work done by the page's code, drawing the result, outside scripts and embedded frames from other sites.

Stopping the page from jumping (CLS)

We trace each jump, during or after loading, to missing size settings, content added late, fonts, ads, embeds or parts of the page that change, then test the approved fixes.

Caching, your server and file settings

We review how long saved copies stay fresh, how they are checked, how private pages are handled, whether CDN and server settings match, file compression, image formats, bundled code files and the order key files load in.

Limits for outside scripts and cookie consent

For each outside script, we record its purpose, owner, when it loads, what cookie consent it needs, how much work it adds, what happens if it fails, and whether to keep it, load it later, replace it or remove it.

Stopping slowdowns and real-visitor proof

We set speed limits for each page type, automatic checks, proof needed before going live, sample groups of real visitors, how long we watch, signs that a change must be undone and who maintains it.

Priority list, approved fixes and safe releases

We rank the causes we find by likely benefit, risk and effort, then make the fixes you approve. We keep a backup, re-test the agreed pages and customer paths, and release each change with a clear way to undo it.

Why Softscotch

Know which cause we fixed, where it helped and what could get worse again

Each fix links a measured problem to the pages it affects, the change we made, checks before and after, any trade-offs, the decision to go live and the person who can undo it if needed.

Real-visitor data stays tied to the right group

Every statement about real visitors keeps its web address or whole-site scope, device, location, time period and whether there was enough data to trust it.

Lab tests can be repeated

Each diagnosis records the tool version, test location, device settings, connection speed, whether files were saved, the content shown and any live experiment that was running.

Fixes target the biggest cause

We trace the real chain behind slow main content (LCP), slow responses (INP), page jumps (CLS), network delays and browser workload before choosing what to change.

Business scripts keep named owners

Cookie consent, analytics, chat, testing and sales tracking tags are given limits based on their purpose and what breaks if they fail, instead of being removed blindly.

"Done" means the site still works properly

Speed checks also confirm that visitors can still complete tasks and that accessibility, privacy, security, analytics and content all still work as they should.

Proof of each launch survives handover

Speed limits, monitors, slowdowns found, changes undone and maintenance decisions stay dated and on record long after the first improvement.

Service decisions

The 36 decisions behind safe website speed improvements

The work covers real-visitor and test data, groups of pages, devices, images, fonts, scripts, caching (saving copies of files so they load faster), server limits, fixes, testing, going live and monitoring.

Basics and limits
What's covered and your most important customer pathsBefore you sign off what the audit covers, we write down the limits of the speed work and the customer paths that matter most, including what we need from you, who owns it and its limits.
List of sample page types and devicesBefore you sign off what the audit covers, we confirm a list of sample page types (templates) and devices to test, including where things stand now, what is going wrong and the next step.
Who approves changes and how we undo themBefore you sign off what the audit covers, we agree who can approve changes and how a change is rolled back (undone) if needed, including the agreed rule, what it depends on and how we check it.
Today's real-visitor and lab test resultsBefore you sign off what the audit covers, we record today's results from real visitors and from lab tests as the starting point, including why it matters to your business, how it works and who takes it over.
Business limits and speed targets (budget)Before you sign off what the audit covers, we test your business limits against a speed budget (agreed targets each page should meet), using typical examples as well as ones that go wrong.
Who watches speed and owns each partBefore you sign off what the audit covers, we name who monitors speed and who owns each part, including what would trigger an update, who makes the decision and the proof used.
Information and proof
Keeping real-visitor data and test data apartWhen we choose which pages and data sources to use, we confirm that real-visitor data and lab test data are kept apart, including what we need from you, who owns it and its limits.
Core Web Vitals by group of pages and visitorsWhen we choose which pages and data sources to use, we map Google's Core Web Vitals results by group of pages, devices and visitors, including where things stand now, what is going wrong and the next step.
Setting up real-visitor measurementWhen we choose which pages and data sources to use, we connect a way to measure speed for your real visitors (called real-user monitoring), including the agreed rule, what it depends on and how we check it.
Dated, repeatable test methodWhen we choose which pages and data sources to use, we test a dated method for repeating lab tests the same way each time, including why it matters to your business, how it works and who takes it over.
Structure and definitions
Finding the main item (LCP) and what delays itWhile we work out causes and what they depend on, we define which item counts as the largest on screen and which of its loading steps causes the delay, including what we need from you, who owns it and its limits.
How soon the browser finds the main itemWhile we work out causes and what they depend on, we trace the chain of files the browser must load before it even finds the main image or text, including where things stand now, what is going wrong and the next step.
Server response time and page deliveryWhile we work out causes and what they depend on, we test how quickly your server responds and delivers the page's code, including the agreed rule, what it depends on and how we check it.
Plan for loading the most important files firstWhile we work out causes and what they depend on, we name who owns a plan for loading the most important files first, including why it matters to your business, how it is done and who takes it over.
Making the changes
Right-sized images with set dimensionsWhile we plan fixes on sample pages, we set up images that are sized for each screen and have fixed width and height so nothing jumps, including what we need from you, who owns it and its limits.
Font loading and backup fontsWhile we plan fixes on sample pages, we test how fonts load and how closely the backup font matches so text doesn't shift, including where things stand now, what is going wrong and the next step.
Breaking down slow taps and clicks (INP)While we plan fixes on sample pages, we name who breaks each slow interaction into its parts (waiting, processing and showing the result), including the agreed rule, what it depends on and how we check it.
Finding long tasks that block the browserWhile we plan fixes on sample pages, we record which long pieces of work keep the browser busy and unable to respond, and where they come from, including why it matters to your business, how it is done and who takes it over.
Safety checks
Owner list for outside scriptsBefore changes go live, we test a list showing who owns every script from another company on your site, including what we need from you, who owns it and its limits.
Finding what makes the page jump (CLS)Before changes go live, we name who traces each page jump back to its cause, including where things stand now, what is going wrong and the next step.
Caching rules and freshness checksBefore changes go live, we record the rules for how long browsers and servers keep saved copies and how they check for newer versions, including the agreed rule, what it depends on and how we check it.
CDN and server cache settings that matchBefore changes go live, we confirm that the cache settings on your CDN and on your own server agree with each other, including why it matters to your business, how it is done and who takes it over.
Testing and improving
Fair speed tests between groupsWhen we run speed checks and re-checks, we name who runs fair tests comparing groups of visitors or pages, including what we need from you, who owns it and its limits.
Speed limits for each page typeWhen we run speed checks and re-checks, we record the speed limits each page type must stay within, including where things stand now, what is going wrong and the next step.
How long we watch real-visitor dataWhen we run speed checks and re-checks, we confirm how long we watch real-visitor data before judging a fix, including the agreed rule, what it depends on and how we check it.
Limits on outside scripts and browser workloadWhen we run speed checks and re-checks, we define how much browser work outside scripts and your own code are allowed to use, including why it matters to your business, how it is done and who takes it over.
Advanced work
Checks that block slower releasesWhile changes roll out and are watched live, we record automatic checks that stop an update going live if it makes pages slower, including what we need from you, who owns it and its limits.
Repeat tests for key pages and page typesWhile changes roll out and are watched live, we confirm a set of repeat tests for your key pages and page types, including where things stand now, what is going wrong and the next step.
Working well on slow phones and connectionsWhile changes roll out and are watched live, we define how the site should cope with older phones and slow connections, including the agreed rule, what it depends on and how we check it.
Loading tracking tags only with consentWhile changes roll out and are watched live, we connect tag loading to cookie consent so tracking only loads when visitors allow it, including why it matters to your business, how it is done and who takes it over.
Testing key steps when a script failsWhile changes roll out and are watched live, we test that essential steps like checkout or booking still work when an outside script fails, using typical examples as well as ones that go wrong.
Rules, upkeep and growth
Rules for loading videos, images and embedded contentTo settle remaining risks, owners and handover, we confirm rules for when videos, images and content embedded from other sites load, including what we need from you, who owns it and its limits.
Checks for return visits and moving between pagesTo settle remaining risks, owners and handover, we define speed checks for visitors who come back and for moving from page to page, including where things stand now, what is going wrong and the next step.
Linking speed to completed customer tasksTo settle remaining risks, owners and handover, we connect speed data to whether visitors completed tasks like buying or booking, including the agreed rule, what it depends on and how we check it.
Honest limits on search ranking claimsTo settle remaining risks, owners and handover, we test what the evidence can and can't say about speed's effect on Google rankings, including why it matters to your business, how it's done and who takes it over.
Reviewing slow drift over timeTo settle remaining risks, owners and handover, we name who reviews how speed slowly drifts as the site changes over time, tested on typical examples as well as ones that go wrong.
Platforms and working tools

Website speed tools we use, and what each one can and can't tell you

Before we rely on any tool, we check that your account, plan, country, permissions, connections to other software and the features you need are really available to you.

What we review

Our speed audit: seven checks from starting point to a monitored launch

Each check shows where the evidence came from, the likely cause, which customer path is affected, any test that failed, who fixes it and the decision to go live.

Check 01 · Starting point for pages and customer paths

Starting point for your pages, customer paths and data

We list your most important pages and paths, page types, tasks visitors complete, recent updates, devices, connection types, groups of real-visitor data, lab test settings and gaps in the data we know about.

This check ends with a clear decision on the starting point for your pages, customer paths and data, a list of anything blocking progress, who owns each item and the next approved step.

What we start with proveBefore anything changes, we confirm what speed data and page information we have and which pages and paths the work will affect.
The goal defineWe write down what the starting point must capture, who signs it off and what is not included in the speed work.
How it runs buildWe follow each important page step by step through its content, data, platform and the people who pass work to each other.
What could go wrong riskWe test what happens when page, device or speed data is missing, out of date, wrong, duplicated, unavailable or unclear.
Final check sign-offWe compare the result with what was agreed, using typical customers, phones and computers, real data and the people who own each part.
Decision decideWe record any problems found, the risk that remains, how it will be watched and kept up to date, and who is responsible for the next step.
Check 02 · Slow-loading main content (LCP)

Why your main content loads slowly (LCP)

For the actual largest item on screen, we trace server response time, how soon the browser finds it, its loading priority, download time, drawing time, image sizes for different screens and any fonts it waits for.

This check ends with a clear decision on why your main content loads slowly and what to fix, a list of anything blocking progress, who owns each item and the next approved step.

What we start with proveBefore anything changes, we confirm the main-content loading data we have and which pages and page types it affects.
The goal defineWe write down what fixing slow main content (LCP) must achieve, who signs it off and what is not included in the work.
How it runs buildWe follow the main item step by step from your server, through the browser, to the screen and the people who own each part.
What could go wrong riskWe test what happens when the main image, text or file it depends on is missing, out of date, wrong, duplicated, unavailable or unclear.
Final check sign-offWe compare main-content loading with the agreed result, using typical customers, phones and computers, real data and the people who own each part.
Decision decideWe record any problems found, the risk that remains, how loading speed will be watched and kept up, and who is responsible for the next step.
Check 03 · Slow response to taps and clicks (INP)

Why the page is slow to respond to taps and clicks (INP)

We repeat the most important taps and clicks and split the delay into waiting time, the work done by the page's code, drawing the result, outside scripts and embedded frames from other sites.

This check ends with a clear decision on why the page responds slowly and what to fix, a list of anything blocking progress, who owns each item and the next approved step.

What we start with proveBefore anything changes, we confirm the response-time data we have and which pages, buttons and forms it affects.
The goal defineWe write down what fixing slow responses (INP) must achieve, who signs it off and what is not included in the work.
How it runs buildWe follow each tap or click step by step through the page's code, data, outside scripts and the people who own each part.
What could go wrong riskWe test what happens when data, scripts or page states are missing, out of date, wrong, duplicated, unavailable or unclear.
Final check sign-offWe compare response times with the agreed result, using typical customers, phones and computers, real data and the people who own each part.
Decision decideWe record any problems found, the risk that remains, how response times will be watched and kept up, and who is responsible for the next step.
Check 04 · Page jumping while loading (CLS)

Stopping the page from jumping around (CLS)

We trace each jump, during or after loading, to missing size settings, content added late, fonts, ads, embeds or parts of the page that change, then test the approved fixes.

This check ends with a clear decision on what makes the page jump and how to keep it steady, a list of anything blocking progress, who owns each item and the next approved step.

What we start with proveBefore anything changes, we confirm the page-jump data we have and which pages, ads and embeds it affects.
The goal defineWe write down what fixing page jumps (CLS) must achieve, who signs it off and what is not included in the work.
How it runs buildWe follow each moving element step by step through the content, data, platform and people who add or change it.
What could go wrong riskWe test what happens when sizes, fonts, ads or embeds are missing, out of date, wrong, duplicated, unavailable or unclear.
Final check sign-offWe compare page stability with the agreed result, using typical customers, phones and computers, real data and the people who own each part.
Decision decideWe record any problems found, the risk that remains, how page stability will be watched and kept up, and who is responsible for the next step.
Check 05 · Caching, server and file settings

Caching, your server and file settings

We review how long saved copies stay fresh, how they are checked, how private pages are handled, whether CDN and server settings match, file compression, image formats, bundled code files and the order key files load in.

This check ends with a clear decision on caching, server and file settings, a list of anything blocking progress, who owns each item and the next approved step.

What we start with proveBefore anything changes, we confirm your current caching, server and file settings and which pages and files they affect.
The goal defineWe write down what the caching, server and file settings must achieve, who signs them off and what is not included.
How it runs buildWe follow each file step by step from your server, through the CDN, to the visitor's browser and the people who manage each part.
What could go wrong riskWe test what happens when saved copies are missing, out of date, wrong, duplicated, unavailable or unclear, including private pages that must never be shared.
Final check sign-offWe compare caching and file settings with the agreed result, using typical customers, phones and computers, real data and the people who own each part.
Decision decideWe record any problems found, the risk that remains, how caching will be watched and kept up to date, and who is responsible for the next step.
Check 06 · Outside scripts and cookie consent

Limits for outside scripts and cookie consent

For each outside script, we record its purpose, owner, when it loads, what cookie consent it needs, how much work it adds, what happens if it fails, and whether to keep it, load it later, replace it or remove it.

This check ends with a clear decision on limits for outside scripts and how they follow cookie consent, a list of anything blocking progress, who owns each item and the next approved step.

What we start with proveBefore anything changes, we confirm which outside scripts are on your site today and which pages and business tasks depend on them.
The goal defineWe write down what the limits on outside scripts and consent must achieve, who signs them off and what is not included.
How it runs buildWe follow each script step by step from the cookie banner, through the page and data it uses, to the people who own it.
What could go wrong riskWe test what happens when a script or a visitor's consent choice is missing, out of date, wrong, duplicated, unavailable or unclear.
Final check sign-offWe compare script loading with the agreed result, using typical customers, phones and computers, real data and the people who own each part.
Decision decideWe record any problems found, the risk that remains, how outside scripts will be watched and kept in check, and who is responsible next.
Check 07 · Stopping slowdowns and real-visitor proof

Checks that stop slowdowns, and proof from real visitors

We set speed limits for each page type, automatic checks, proof needed before going live, sample groups of real visitors, how long we watch, signs that a change must be undone and who maintains it.

This check ends with a clear decision on the checks that stop slowdowns and on what real-visitor data shows, a list of anything blocking progress, who owns each item and the next approved step.

What we start with proveBefore anything changes, we confirm the release checks and real-visitor data we have and which pages and updates they affect.
The goal defineWe write down what the slowdown checks and real-visitor proof must achieve, who signs them off and what is not included.
How it runs buildWe follow each update step by step through testing, the live site, real-visitor data and the people who approve releases.
What could go wrong riskWe test what happens when release checks or visitor data are missing, out of date, wrong, duplicated, unavailable or unclear.
Final check sign-offWe compare live results with the agreed result, using typical customers, phones and computers, real data and the people who own each part.
Decision decideWe record any problems found, the risk that remains, how speed will be watched and kept up over time, and who is responsible for the next step.
The change

From measured causes to a careful, controlled launch

Before

First, your most important pages and customer paths get evidence we can repeat, with the likely causes of slowness and a named owner for each.

  • Real-visitor and lab data are kept apartReal-visitor data and lab test data are shown separately, with the proof behind each, the person who owns it and any gap still open for your website speed work.
  • Affected groups of pages are namedThe groups of pages that are affected are named and checked on typical pages, devices and customer paths before approval.
  • Dependencies and trade-offs are visibleWhat each fix depends on and what it might cost you elsewhere is made visible, ending in a clear decision to start, hold, maintain or plan as next work, with limits stated openly.
After the first cycle

Changes on sample pages pass speed checks, checks that everything still works and re-checks that nothing got slower, before going live.

  • Before and after tests can be comparedBefore and after tests are run the same way so they can be fairly compared, with the proof, the owner and any gap still open for your website speed work.
  • Key customer paths still workWe check that key steps like buying, booking and signing up still work on typical pages, devices and customer paths before approval.
  • Steps to undo changes are readyThe steps to undo each change (roll back) are ready, ending in a clear decision to start, hold, maintain or plan as next work, with limits stated openly.
Ongoing control

Approved fixes are live, with monitoring in place, remaining risks written down and the decision on the next rollout recorded.

  • Live behavior is checkedHow the live site behaves is checked and shown with the proof, the owner and any gap still open for your website speed work.
  • Remaining causes have ownersEach remaining cause of slowness has a named owner and is checked on typical pages, devices and customer paths before approval.
  • Wider rollout follows the evidenceRolling fixes out to more pages is based on what we have seen working, ending in a clear decision to start, hold, maintain or plan as next work, with limits stated openly.
Your type of business

The approach changes with your type of business

The agreement adapts to your audience, your risks, the data you have, how often you release changes and how your business makes money, while the service itself stays the same.

Local

Local services

For local services, website speed work has to protect the pages that show your location, the areas you serve, availability, calls, bookings and who responds to customers.

FocusKeeping real-visitor data and test data apart, Core Web Vitals by group of pages and visitors, setting up real-visitor measurement
MeasureReal-visitor and lab starting point, main content loading (LCP) breakdown, response to taps and clicks (INP) log
Ecommerce

Online stores and direct-to-consumer brands

For online stores and direct-to-consumer brands, website speed work has to protect accurate product details, stock levels, promotion terms, the path to checkout, returns and profit margins.

FocusFinding the main item (LCP) and what delays it, how soon the browser finds the main item, server response time and page delivery
MeasureMain content loading (LCP) breakdown, response to taps and clicks (INP) log, page jumping (CLS) report
Software

Software companies (SaaS)

For software companies, website speed work has to protect pages that show real use cases, proof of what the product does, the path to a free trial or demo, connections with other tools and getting new users started.

FocusRight-sized images with set dimensions, font loading and backup fonts, breaking down slow taps and clicks (INP)
MeasureResponse to taps and clicks (INP) log, page jumping (CLS) report, release and re-check record
B2B

Business-to-business (B2B) and professional services

For B2B and professional services, website speed work has to reflect groups of decision makers, expert proof, checking whether a lead is a good fit, handing leads to sales and the long delay before deals close.

FocusOwner list for outside scripts, finding what makes the page jump (CLS), caching rules and freshness checks
MeasurePage jumping (CLS) report, release and re-check record, speed-to-results decision
Health

Healthcare and wellness

For healthcare and wellness, website speed work has to protect accuracy, patient privacy, who can use a service, appointment booking and what is and isn't medical advice.

FocusFair speed tests between groups, speed limits for each page type, how long we watch real-visitor data
MeasureReal-visitor and lab starting point, main content loading (LCP) breakdown, response to taps and clicks (INP) log
Regulated

Finance, insurance and legal

For finance, insurance and legal businesses, website speed work has to respect the rules in each region, required approvals, legal disclaimers, sensitive personal data and terms that change.

FocusChecks that block slower releases, repeat tests for key pages and page types, working well on slow phones and connections
MeasureMain content loading (LCP) breakdown, response to taps and clicks (INP) log, page jumping (CLS) report
Education

Education and training

For education and training, website speed work has to protect accurate program facts, dates, who can apply, enrollment steps, realistic outcomes and accessibility.

FocusRules for loading videos, images and embedded content, checks for return visits and moving between pages, linking speed to completed customer tasks
MeasureResponse to taps and clicks (INP) log, page jumping (CLS) report, release and re-check record
Media

Publishers and media

For publishers and media, website speed work has to reflect who wrote what, usage rights, subscriptions, fast publishing cycles and original reporting or research.

FocusWhat's covered and your most important customer paths, list of sample page types and devices, who approves changes and how we undo them
MeasurePage jumping (CLS) report, release and re-check record, speed-to-results decision
Marketplaces

Marketplaces and directories

For marketplaces and directories, website speed work has to serve both buyers and sellers and protect identity checks, listings available, data quality and the same action being counted twice.

FocusKeeping real-visitor data and test data apart, Core Web Vitals by group of pages and visitors, setting up real-visitor measurement
MeasureReal-visitor and lab starting point, main content loading (LCP) breakdown, response to taps and clicks (INP) log
Travel

Travel and hospitality

For travel and hospitality, website speed work has to reflect busy and quiet seasons, location, availability, booking value, cancellations and changing policies and terms.

FocusFinding the main item (LCP) and what delays it, how soon the browser finds the main item, server response time and page delivery
MeasureMain content loading (LCP) breakdown, response to taps and clicks (INP) log, page jumping (CLS) report
Industrial

Industrial and manufacturing

For industrial and manufacturing businesses, website speed work has to protect technical specs, which parts work together, distributors, long buying decisions and good-quality inquiries.

FocusRight-sized images with set dimensions, font loading and backup fonts, breaking down slow taps and clicks (INP)
MeasureResponse to taps and clicks (INP) log, page jumping (CLS) report, release and re-check record
Membership

Memberships and communities

For memberships and communities, website speed work has to reflect who has access to what, ongoing value for members, moderation, renewals and member support.

FocusOwner list for outside scripts, finding what makes the page jump (CLS), caching rules and freshness checks
MeasurePage jumping (CLS) report, release and re-check record, speed-to-results decision
Clear ownership

Speed work is separate from moving platforms, redesigns and replacing your hosting

Softscotch is responsible for the named diagnosis, fixes and pre-launch checks. You keep your hosting and supplier accounts, decisions on essential scripts, business trade-offs and the final say on going live. Major rebuilds and work by outside suppliers stay separate.

We handle

The website speed optimization work named in your proposal.

  • Starting point for key customer paths and page types
  • Real-visitor and lab data, ranked by how much to trust them
  • Finding the causes behind LCP, INP and CLS
  • Approved speed fixes
  • Re-checks before launch and a plan to undo changes
  • Speed report with honest limits
We coordinate

Agreed handovers with your teams and specialist partners.

  • Hosting and CDN providers
  • Product and design owners
  • Analytics and cookie consent owners
  • Accessibility and security reviewers
  • Content and media owners
  • Sales and support owners
You keep

The facts about your business, your accounts, usage rights, budget and final approval.

  • Access to your live site and the final say on going live
  • Decisions on scripts your business can't do without
  • Privacy and legal decisions
  • Sign-off on accessibility and security
  • Decisions on buying hosting and other infrastructure
  • What counts as a good business result
How it fits together

Nine working records make every speed change easy to explain

Your team can follow each group of pages and its evidence through the cause, the fix, what it depends on, testing, going live, any slowdown that comes back, monitoring and the next priority.

Speed Optimization

01
List of customer paths and page types

Lists your most important web addresses, page types, tasks, devices, connection types, traffic and the business owner of each.

02
Real-visitor data map

Stores whether data covers one page or the whole site, the device, location, time period, whether there was enough data and current LCP, INP and CLS results across visitors.

03
Dated lab test pack

Records the tool, browser, device settings, location, saved-file state, page version, the order files loaded in (the waterfall), browser workload and screenshots.

04
Main content (LCP) breakdown

Links each largest on-screen item to evidence on server response, how soon it was found, loading priority, download time and drawing delay.

05
Tap and click log

Maps typical visitor actions to waiting time, code work, drawing time, long tasks, screen frames and outside scripts.

06
Page jump record

Records the element that moved, what triggered it, when in the visit it happened, its source, the part of the screen affected, the fix and the re-test.

07
Script and caching chart

Sets each item's purpose, loading rule, consent, owner, cost, what happens on failure, how long copies stay fresh, how they are checked and limits for sensitive data.

08
Pre-launch check pack

Captures results for how the site works, accessibility, privacy, analytics, speed, unusual cases and undo steps, for each version.

09
Slowdown and results dashboard

Keeps lab test findings, real-visitor data, completed tasks, quality, business results and anything still uncertain apart.

The connected growth engine

Product

In charge of key customer paths, signed-in and guest states, how features work, experiments and trade-offs when changes go live.

Engineering

In charge of the code, how pages are drawn, network, caching, outside code the site relies on, testing and how changes are undone.

Infrastructure

In charge of your main server, CDN, file compression, caching, uptime and the tools that show what the system is doing.

Data

In charge of real-visitor measurement, consent, what each tracked event means, the quality of visitor groups and matching data between tools.

Experience

In charge of content, design, accessibility, images and video, fonts and signing off that essential tasks still work.

Rules and upkeep

In charge of privacy, security, buying decisions, tags the business can't do without and the final decision to go live.

One connected scope. Speed Optimization is coordinated with the strategy, creative, experience, data and reporting it depends on, so responsibilities and handoffs stay visible in one written plan.

What to expect

From a sample speed audit to the first checked fixes

The audit and putting fixes in order usually take 3 to 5 working days. A first fix on sample pages usually takes 3 to 10 working days once we have access and approval. A wider rollout depends on how many page types there are, what the fixes depend on and when you allow changes to go live.

Website speed optimization: first delivery and decision

Days 1 to 2

Scope and starting point

We confirm your most important pages, page types, customer paths, devices, test and live environments, data sources and who approves changes going live.

KPI Scope
Days 2 to 5

Finding the causes

We compare lab tests with any real-visitor data, then pin down the likely causes of slow main content (LCP), slow responses (INP), page jumps (CLS) and slow delivery.

KPI Diagnose
Days 3 to 7

Fix plan for sample pages

We choose clearly limited fixes and set out what they depend on, backups, trade-offs, the checks that prove they work and the steps to undo them.

KPI Plan
Days 5 to 10

Making changes and re-checking

We make the approved changes and test the affected page types, devices, taps and clicks, and key steps like checkout or booking.

KPI Fix
After approval

Careful launch

We put changes live in the agreed time window, check how the live site behaves and watch for errors and speed data.

KPI Go live
After a watching period

Decide on a wider rollout

We expand, change or stop the work based on checked results, causes still left, risk and what matters most to your business.

KPI Decide

Our full growth plan (all services together), month by month

Month 1

Setup and first launch

Agree priorities, fix the biggest problems and launch the first approved work once we have access, content, budget and your sign-off.

KPI First work live
Month 2

Build and improve

Use the first report to improve the live work and build the next agreed materials, campaigns, pages or follow-up steps.

KPI Improvements live
Month 3

Do more of what works

Do more of the messages, audiences, pages or channels that the results show are working, while keeping budgets and quality checks within the limits we agreed.

KPI What works, expanded
Month 4

Strengthen results

Fix weak handovers between teams, gaps in tracking and anything slowing delivery, then test the next priorities against measures that matter to your business, such as lead quality and sales.

KPI Blockers removed
Month 5

Turn more visitors into customers

Improve the offer, message, page and follow-up steps wherever the results show people getting stuck or leads that aren't a good fit.

KPI Improvements to win more customers live
Month 6

Plan the next round

Review what changed, what the results really show, what should stop and which work deserves budget and attention in the next period.

KPI Next round agreed
How we compare

Measured page fixes, not chasing one speed score

The difference is agreed customer paths and devices, real-visitor and test data side by side, fixes aimed at real causes, protection against things getting slower again, a named owner for each launch and honest limits on what speed can do for rankings and revenue.

The risk of using a different agency for everything
  • Starts with one Lighthouse score (Google's lab testing tool)
  • Mixes up real-visitor and lab numbers
  • Speeds up every page the same way
  • Shrinks images before finding what really delays the main content
  • Blames slow responses only on code size
  • Checks page jumps only during the first load
  • Removes tags without asking who in the business needs them
  • Caches more without checking for private data
  • Reports guesses about rankings or revenue
  • Stops after one passing re-test
vs
Softscotch
  • Starts with your key customer paths and visitor groups
  • Labels real-visitor and lab data separately
  • Maps pages, page types and the visitors who use them
  • Traces every step that delays the main content
  • Breaks typical taps and clicks into their parts
  • Tests for jumps during and after loading
  • Sets limits for outside scripts by owner and purpose
  • Checks caching rules and keeps private pages safe
  • Keeps speed separate from search rankings and business results
  • Hands over automatic slowdown checks and named owners
The numbers

Results from Softscotch client work.

These totals come from work for Softscotch clients across search, paid ads, websites and lead generation, as published on softscotch.com. Past results don't guarantee future results.

$12M+Ad spend managed for clients
87,200+Leads generated for clients
2,140+Search terms ranked on Google's first page
$28M+Revenue generated for clients
Client case studies

All six Softscotch client stories.

Every Quick Story currently published on Softscotch.com, covering education, ecommerce, healthcare and SaaS. Stock photography represents each client industry; the figures are reported historical results and do not guarantee future performance.

Education consultant speaking with a prospective student Education Ads + local SEO
+183%leads

183% more leads for an education consultancy

WordPressQuora adsLocal SEO
The challenge

An education consulting business in India needed to build its digital presence and lead flow from scratch.

What changed
  • Built a new WordPress website
  • Used Quora ads to grow daily lead volume
  • Added Local SEO and community engagement
+183% leads25+ leads/day-38% bounce rate+273% new users
Bright modern home interior representing the home-solutions client Home solutions Shopify + SEO
+82%Shopify sales

Home-solutions ecommerce growth

ShopifyOrganic searchAmazon ads
The challenge

A home-solutions business was dependent on business-to-business (B2B) marketplaces, losing sales and recovering from a Google penalty.

What changed
  • Resolved the Google penalty
  • Revamped the website and online store
  • Improved organic visibility and Amazon campaign performance
+82% Shopify sales+147% organic+23% Amazon ROAS
Mother and baby representing the lactation-consultant client Health consultant $20/day
5/daybooked calls

Five booked calls a day for a health consultant

Facebook adsGoogle AdsLocal SEO
The challenge

A Houston lactation consultant needed to recover a malware-damaged website and rebuild local patient acquisition.

What changed
  • Rebuilt the hacked site and migrated it to secure hosting
  • Ran targeted Facebook and Google campaigns
  • Reached top-three local Google positions
5 calls/day$20 daily spend+87% local traffic+34% new users
Ecommerce owner preparing customer orders beside a laptop Ecommerce 10 months
+315%organic traffic

315% organic growth for an ecommerce site

Content strategyOn-page SEO
The result

Softscotch reports a 315% increase in ecommerce organic traffic over 10 months through focused on-page SEO.

What changed
  • Optimized product and collection pages
  • Improved the links between pages and the page addresses (URLs)
  • Made the site easier for Google to explore and better matched to what people search for
+315% organic10 monthsProductsCollections
SaaS team reviewing campaign data around a laptop SaaS platform Cold outreach
16%reply rate

9% close rate for a transcription SaaS

ProspectingSMTP
The challenge

A transcription platform needed a qualified prospect list and a reliable email-sending setup for outreach we managed.

What changed
  • Built a comprehensive prospecting list
  • Managed the cold outreach campaigns
  • Set up reliable email-sending servers (SMTP)
9% close rate16% reply rateSaaSManaged outreach
Healthcare professional consulting with a patient Healthcare 6 months
+182%organic traffic

182% organic growth for a healthcare clinic

HealthcareOn-page SEOOff-page SEO
The challenge

A clinic in a competitive location needed to build organic search visibility from the ground up.

What changed
  • Built the clinic's foundation for unpaid (organic) Google search
  • Combined on-page and off-page SEO
  • Reached top-five positions in Google Search
+182% organic6 monthsTop 5 Google
01 / 06
In their words

Teams that stopped leaving clicks on the table.

★★★★★

"The Softscotch team has been a solid partner as our business evolved over the last five years. Unlike most agencies, they have never charged us for work that falls outside the agreement. That is what sets them apart."

IM
Imtiyaz MominHairareus
★★★★★

"Without their knowledge, we would be in a very different place than we are now. Whenever they find something that can be improved, they implement it quickly. I could not be happier with their performance and response time."

AP
Aaron PaulsonBaby Pavilion
★★★★★

"Softscotch goes above and beyond the scope. The time, effort and dedication they put in is like having your own in-house marketing team. They are not just another marketing company."

TM
Tabassum MithaniTRS Care
★★★★★

"We are extremely happy with Softscotch, such an attentive team. No project is too small, and they give their 100%. We are extremely satisfied with their work."

SH
Safiya HafiziSimply Lactation
★★★★★

"Softscotch is a great team to work with: transparent, reliable and genuinely invested in the growth of your company. They are good partners to have by your side."

MJ
Malvika JainCyclop
★★★★★

"The Softscotch team has been a solid partner as our business evolved over the last five years. Unlike most agencies, they have never charged us for work that falls outside the agreement. That is what sets them apart."

IM
Imtiyaz MominHairareus
★★★★★

"Without their knowledge, we would be in a very different place than we are now. Whenever they find something that can be improved, they implement it quickly. I could not be happier with their performance and response time."

AP
Aaron PaulsonBaby Pavilion
★★★★★

"Softscotch goes above and beyond the scope. The time, effort and dedication they put in is like having your own in-house marketing team. They are not just another marketing company."

TM
Tabassum MithaniTRS Care
★★★★★

"We are extremely happy with Softscotch, such an attentive team. No project is too small, and they give their 100%. We are extremely satisfied with their work."

SH
Safiya HafiziSimply Lactation
No black box

You'll always know exactly what we changed.

Plenty of agencies go quiet after the audit and you never quite know what you're paying for. We do the opposite. You get a live view of every change and what it moved, in plain language you can act on.

Your delivery, at a glanceSample
Changes shipped12
Pages reviewed28
StartMidpointNow
Delivery activity✓ Up to date
HTML mockupExplore mockup ↗

Live client dashboard

Every change, score and ranking in one place you can open any time, not a monthly PDF you wait around for.

This week, explainedSample
✓Titles updated
Ready for your review
SSSoftscotch weekly update
0:00
2:00
HTML mockupExplore mockup ↗

Weekly video summary

A short screen-recorded video (Loom) each week walking you through exactly what shipped and what it moved, so nothing is a mystery.

The change is clearSample

Before

Titles30 / 100
Structure42 / 100
Content28 / 100

After

Titles84 / 100
Structure79 / 100
Content90 / 100
Same page. Reviewed changes.
HTML mockupExplore mockup ↗

Before/after score per page

See the exact lift on every page we touch, not a vague "it's improving" you have to take on faith.

Your weekly reportSample
01
What shipped

Approved page updates are live.

02
What we learned

Product details need a review.

03
What happens next

Confirm the next priority pages.

HTML mockupExplore mockup ↗

Plain-English reporting

Clicks, rankings and revenue, explained in words you can act on, instead of a wall of charts about how often you were seen (impression charts.

Your data. Your view.Sample
Organic search
StartMidpointNow
Sample report preview↗
HTML mockupExplore mockup ↗

Reports on demand

Ask for any cut of the data whenever you need it and get it, no waiting for the end of the month.

Every step, visibleSample
  1. ✓
    Proposed

    Softscotch prepares the change.

  2. ✓
    Approved

    Your team gives the go-ahead.

  3. ✓
    Published

    Checked live and recorded.

HTML mockupExplore mockup ↗

Ethical, transparent, always on

One accountable team, strictly white-hat (only methods search engines and platforms allow), no shortcuts and no surprises. Support whenever you need it.

One plan, full-stack access

One Softscotch plan gives you access to the full service stack, coordinated around your priorities.

You do not need a separate agency or retainer for every channel. Your plan can draw from search, paid media, web, ecommerce, outreach, automation, lead generation, messaging, content, creative and operations. The agreed scope sets what is active, in what order and at what capacity.

Pricing approach

One price for everything, not a stack of separate retainers.

You get one price for your whole marketing, not a separate retainer for every service. SEO, paid ads, your website, automations, cold email and newsletters, we run all of it as a single scope, so you get the most result for what you pay. Agencies sell each of these on its own, so the invoice climbs whether or not that line drives a single lead.

Bought separately, service by service

A different agency or retainer for each service. The bill stacks up fast, and keeps climbing whether or not each one moves a single lead.

SEO (technical, on-page, content)$2,000–3,500/mo
Local SEO+$750–1,500/mo
Programmatic SEO+$1,000–2,500/mo
CRO & landing pages+$2,000–3,500/mo
Paid ads (Google & Meta)+$2,500–4,000/mo
Marketing automations+$1,500–3,000/mo
Cold email outreach+$1,500–2,500/mo
Email marketing & newsletters+$750–1,500/mo
Website management & care+$750–1,500/mo
WordPress build & setup+$2,500–6,000 once
10 separate services$12,750–23,500/mo

Plus the one-off build, and a fresh contract, kickoff and onboarding delay for every new service you add.

All of it, one scope

We run your whole marketing as one engagement, so you get the most result for what you pay, not a pile of disconnected invoices.

  • SEO: technical, on-page, content, local and AI search
  • Template-built pages (programmatic SEO), links from other websites (backlinks) and authority
  • CRO and landing pages
  • Paid ads across Google and Meta
  • Automations, cold email and newsletters
  • WordPress build, setup and ongoing care
  • One team, one roadmap and one point of contact
  • Reporting tied to qualified leads and revenue
Everything above. One flat monthly fee.A fraction of the cost of the stack on the left
Plus free access to our own platforms
Post InstantlyVerified WidgetsTrending FunnelsBrands for CreatorsDarnItSEOGoHighLevel

Priced to your site after the audit. No sticker price, and no per-service creep.

What shapes your quote
Site sizePage count, templates and how much of the site actually needs work.
Market competitionHow hard the terms you want to win are, and who you are up against.
Content needsHow much new writing, rewriting and production the plan calls for.
Build complexityYour website platform (CMS, the system you edit your site in), your other tools and how involved the changes are to make.
Final pricing comes after the audit, once we have seen the four things above on your actual site. You get a written scope and a fixed quote before any work begins: no lock-in, no surprise line items, and no upfront number that ignores your market.
Request a custom scope
Questions, answered

Website speed optimization questions to ask before we start

These answers explain which pages are covered, the evidence we use, fixes, access, what we depend on, going live, costs, timing, Core Web Vitals and the limits on results.

Filter
What is included in your website speed optimization service?

The agreed work can include a starting point for your pages, customer paths and data; finding why your main content loads slowly (LCP); finding why the page is slow to respond (INP); stopping the page from jumping (CLS); caching, server and file settings; limits for outside scripts and cookie consent; making the approved fixes in order of priority and releasing them safely; and checks that stop slowdowns, backed by real-visitor proof. Your proposal names what we need from you, who owns each part, what you get, how we check it and what is not included.

When is website speed optimization the right service for you?

It is a good fit when your important pages or tasks are measurably slow or jumpy, real-visitor and lab reports disagree, an update made things slower, or your team needs agreed causes and lasting checks that keep future updates from undoing the gains.

What access and information do you need from us?

We need sample web addresses and tasks, evidence from your test and live sites, a history of recent updates, access to real-visitor and analytics data where the law allows, background on your code and hosting, a list of tracking tags, named owners and clear, limited permission to make changes.

What do you look at to find the causes?

We look at real-visitor data from CrUX (the Chrome User Experience Report, Google's public data from real Chrome users), PageSpeed Insights and Google Search Console reports, dated Lighthouse and Chrome DevTools test recordings, charts of how files load, the web-vitals measuring library, server and CDN evidence, your code, update logs and whether visitors completed their tasks.

How do you work out the starting point?

We map your key customer paths and page types, label which data comes from real visitors and which from lab tests, record tool versions and which visitors the data covers, repeat the most important LCP, INP and CLS problems ourselves, and get sign-off on the current features and business limits we must protect.

How do you tell an observation apart from a proven result?

An observation keeps a note of which visitors it covers, the test setup, the tool version and how sure we are. A proven result needs an approved change, a fair re-test on sample pages and, if your site gets enough visitors to appear in Google's real-visitor data, a long enough watching period, without hiding anything that got worse.

Can you run fair tests?

Yes, when you have enough traffic, stable versions of the page, the right consent and agreed rules for deciding. Many speed problems are better handled by re-checking before each update goes live than by an A/B test (showing two versions to different visitors).

Do the numbers inside a platform prove speed caused extra sales?

No. Attribution (how a platform or analytics tool gives credit for a sale) follows that tool's own rules. Proving faster pages caused extra sales that would not have happened anyway needs a fair comparison group, enough data, control over overlapping changes and an honest statement of how certain the result is.

Do automatic suggestions decide what we fix next?

No. Automatic test reports and platform suggestions are treated as dated inputs, not orders. A named person checks whether the problem can be repeated, the limits, rights, risk and how relevant it is to your business before anything is approved.

Do you change our live site while you're reviewing it?

No, not by default. While we review, we only record a dated starting point. Changes to live code, caching, the CDN, tracking tags or hosting need your clear permission, step-by-step checks and a way to undo them.

Can you guarantee Google or another platform will accept, show or rank our pages?

No. Google and other platforms control access, reviews, where pages appear, how they are delivered, which pages get indexed (added to search results) and how rules are enforced, and they can change any of this without notice. We check what each platform supports at the time we do the work.

Who makes legal, privacy, rights and claim decisions?

You do. Your business keeps the final say on legal, privacy, consent, usage rights, claims, disclosures and going live. Softscotch writes down how these decisions fit into the work and only carries out instructions you have approved.

What does the report keep separate?

It keeps apart real-visitor data, lab test findings, changes made, re-check results, whether visitors completed their tasks, good-quality business results and anything we are still unsure about.

What can the results not prove?

A clean test or a better score doesn't prove that every visitor got a faster site, that Google will rank a page higher, or that a change in sales, sign-ups or revenue was caused by speed alone.

What work is not part of this service?

Moving to a new hosting platform, a full redesign of the user experience, CRO testing (conversion rate optimization: changing pages so more visitors take action), rebuilding analytics, penetration testing (security testing by simulated attack) and wider accessibility fixes stay with their own specialists unless they are added to your scope separately.

Can you guarantee results from website speed optimization?

No. Softscotch is responsible for the agreed research, the work itself, the checks and the report. Results also depend on platforms, your data, customer demand, how your business runs, the kinds of visitors you get and market conditions, which we don't control.

How long does the first round of work take?

The twelve-step plan above is an example, not a fixed schedule. Real timing depends on how quickly we get access, the quality of the evidence, how much needs to change, platform reviews, your approvals and how long we need to watch results before making a sound decision.

How is website speed optimization priced?

The price depends on the page types, customer paths, accounts, files, page versions, the changes needed, quality checks, reporting and handover we confirm. Your proposal states our assumptions and what is and isn't included before work begins.