01 · website speed optimization

Website speed-upmeasured before and after

We find what slows your site down and fix it: images, scripts, caching, server, database, third-party widgets. We compare by Core Web Vitals and real-visitor data, not by eye

Timeline
from 3 days

Different causes, different fixes

A landing page and a CMS-based store have different bottlenecks. First we look at what the site runs on and how it is built, then decide what to fix

  • 01

    WordPress sites

    A do-everything theme, a page builder and thirty plugins, each loading its own styles and scripts on every page

    • Plugin review: what to drop, what to replace
    • Page caching and object caching
    • Plugin scripts only where they are needed
    • Database cleanup of revisions and junk
  • 02

    Sites on a legacy PHP CMS

    Heavy components, caching switched off and an ERP sync that loads the server during business hours

    • Full-page and component caching
    • Profiling slow queries
    • Combining and minifying CSS and JS
    • Background jobs and syncs moved to cron
  • 03

    Online stores

    A catalog of thousands of products, filters and a cart: here a slow page means an abandoned purchase

    • Fast filters and catalog search
    • Indexes for frequent database queries
    • Lightweight product pages on mobile
    • Cache for guests, live data in the cart
  • 04

    Ad landing pages

    The click is already paid for. If the first screen takes five seconds, people close the tab before they see the offer

    • A light first screen without a slider
    • Trackers and pixels that don’t block
    • Video and animation after load
    • Testing on slow mobile connections
  • 05

    Content-heavy sites

    News, blogs, article libraries: hundreds of images and embedded videos, ads and social widgets

    • WebP and AVIF images at the right size
    • Lazy loading below the first screen
    • Video previews instead of a player up front
    • CDN for static files and media
  • 06

    React and Next.js sites

    A modern stack doesn’t guarantee speed: a huge bundle, data loaded in the browser, a page that jumps around

    • Bundle and library audit
    • Server rendering and static pages where possible
    • Code splitting by page
    • Fixing layout shifts

How we speed it up, step by step

Six steps from the first measurement to the next. Every change can be verified with numbers, not taken on faith

  1. 01Baseline

    We measure

    We look at the home page, catalog, product page and the pages your ads point to. We record LCP, INP and CLS on mobile and desktop so there is something to compare against later

  2. 02Load breakdown

    We find the cause

    We break the load down request by request: what loads first, what blocks rendering, how long the server takes to respond. The result is a list of causes ranked by impact

  3. 03Images and fonts

    We lighten images

    We convert images to WebP and AVIF, serve the right size for each screen and defer everything below the first screen. Fonts are loaded so the text shows up right away

  4. 04Code and widgets

    We sort out scripts

    We remove the excess, defer chats, trackers and widgets until the first interaction, and combine and minify styles. Anything that affects inquiries and analytics gets checked separately

  5. 05Cache, database, hosting

    We tune the server

    We turn on page caching and compression, add indexes for slow queries and connect a CDN if needed. If hosting is the bottleneck, we say so and offer options

  6. 06Before-and-after report

    We measure again

    We compare the same pages with the same tools. A month later we look at real-visitor data: it shows how the site performs for people, not in a test

What the speed-up includes

  1. 01Baseline measurement of key pages
  2. 02A list of causes ranked by impact
  3. 03WebP and AVIF images at the right size
  4. 04Deferred loading of widgets and trackers
  5. 05Minified and combined styles and scripts
  6. 06Page caching and server compression
  7. 07Fonts without invisible text or flicker
  8. 08A first screen without layout shifts
  9. 09Work on a copy, deployment with no downtime
  10. 10A before-and-after report with the same metrics

We measure like search engines do

A lab test shows what to fix, and visitor data shows how the site performs for people on their own phones. We look at both

Tools and technologies: PageSpeed Insights, Core Web Vitals, Analytics, Search Console, CDN, Caching, WebP and AVIF, Compression

Real-visitor data takes about a month to build up, and not every site has it: with low traffic we rely on lab tests and the page load report in your analytics. We compare identical measurements before and after

What most often slows a site down

Six causes we find in almost every audit. There are usually several at once, and the order you fix them in matters more than how many there are

  • Heavy images

    A 5 MB camera photo, only scaled down in the layout. The phone downloads the whole file to show a palm-sized thumbnail

  • A dozen third-party scripts

    Chat, live support, a quiz, pixels, maps, a reviews widget. Each pulls in its own files and ties up the browser while the visitor tries to tap a button

  • No caching

    The server rebuilds the same page from scratch for every visitor. When ad traffic surges, the site starts taking seconds to respond

  • Slow hosting

    A budget plan, an old PHP version, a server far from visitors. No code optimization helps if the server takes more than a second to respond

  • Database queries without indexes

    The catalog filter scans the entire product table. With a hundred products nobody notices; with ten thousand the page thinks for several seconds

  • Fonts and sliders up top

    Five font weights and a slider of huge photos on the first screen. The text appears last, and blocks jump around while everything finishes loading

Speed optimization: packages

The cost depends on scope. We send a detailed estimate after the first measurement and don't change it after kickoff unless the scope changes

  • Quick fixes

    Custom quote

    from 3 days

    • Measurement of up to 5 key pages
    • Images in WebP and AVIF
    • Deferred widget loading
    • Server caching and compression
    Get an estimate
  • Turnkey speed-up

    Custom quote

    1–2 weeks

    • Theme, plugin and code review
    • Fonts, first screen and layout shifts
    • Slow database queries
    • Before-and-after report for all pages
    Get an estimate
  • Complex project

    Custom quote

    from 3 weeks

    • A store or portal with a large database
    • Rebuilding heavy templates
    • CDN and server setup
    • A month of speed monitoring
    Get an estimate

What drives the cost

  • A catalog of tens of thousands of products with slow filters
  • A theme or site builder that is easier to rewrite than to fix
  • Moving to a different host or server
  • A sync with your ERP or external services that slows pages down
  • No staging copy of the site — we set one up ourselves

How the work runs

  1. 01

    Access and measurement

    1–2 days

    We get access to the site and hosting, measure the key pages and send an estimate with a plan the next day

  2. 02

    Plan by impact

    1 day

    First, whatever gives the most for the least effort. You see what we change and why

  3. 03

    Work on a copy

    per estimate

    We make every change on a staging copy and check forms, cart and trackers. The live site stays untouched

  4. 04

    Deploy and measure

    30 days

    We move the changes to the live site, deliver a before-and-after report, and a month later review real-visitor data

Common questions

Open 01 of 07

Didn’t find your question? Ask it on Telegram and we’ll reply during business hours

Ask on Telegram
  1. We don’t promise a number before the audit

    The score depends on the theme, third-party scripts and hosting. After measuring, we tell you what is realistic and what has to change to get there. Load time for real people matters more than the score, and that is what we treat as the main result

  2. It depends on scope; the estimate comes after measurement

    A typical WordPress or CMS site usually takes one to two weeks. Stores and portals with a large database take from three weeks. We send an exact estimate after measuring, and it doesn’t change unless the scope changes

  3. We work on a copy and check what matters

    Every change is made on a staging copy. Before deploying we check inquiry forms, the cart, payments and analytics goals. We deploy at a quiet time and keep a backup so we can roll back in minutes

  4. Sometimes, but it is usually half the solution

    A WordPress caching plugin is useful, and we configure it. But it won’t shrink a 5 MB photo, remove an unnecessary widget or speed up a database query. And bad settings in such a plugin often break layouts and forms

  5. Three speed metrics from the visitor’s point of view

    LCP is how fast the main block appears, INP is how fast the site responds to a tap, CLS is whether blocks jump around while loading. Google collects them from real Chrome users, and your analytics shows how long your pages take to load

  6. Only if it is the bottleneck

    First we check the server response time and whether resources are sufficient. If the problem is the plan or an old PHP version, we show it in numbers and offer options. We handle the move ourselves, with no downtime

  7. Yes, speed work is done fully remotely

    Speed optimization only needs access to the site and hosting, so location doesn’t matter. We hold calls during business hours and send reports in writing

Let's speed up your site

Send us your site's address and tell us what it runs on. We reply within two hours during business hours and send a plan and an estimate after measuring

Your site

By clicking the button, you agree to the processing of your personal data