Make your website fast enough that visitors stay

I find what slows your pages, fix images, scripts, caching and the server, and prove it with before and after measurements. For WordPress, WooCommerce, Magento and custom sites. From €490.

from€490excl. VAT 25.5%. Fixed price, before and after report.
example-site.fi / WordPress / mobile, 4Gexample model
2.5 4 4.5 s Poor LCPLargest Contentful Paint good ≤ 2.5 s, poor > 4 s
200 500 340 ms Needs improvement INPInteraction to Next Paint good ≤ 200 ms, poor > 500 ms
0.1 0.25 0.22 Needs improvement CLSCumulative Layout Shift good ≤ 0.1, poor > 0.25
site
device

Cache and server work move LCP; they do not touch INP or CLS. That is why I measure before choosing fixes.

Fixes

0 of 3 vitals pass. Biggest remaining lever in this model: compress images.

Get a speed check for your slowest page

Thresholds are Google's: a page passes when LCP is 2.5 s or less, INP 200 ms or less and CLS 0.1 or less, measured at the 75th percentile of real visits. The site and its numbers above are an example model, not a client.

Where the seconds go: the request waterfall

Every speed job starts with a chart like this one. The switches are shared with the gauges above: tick a fix and the long amber bars shrink into a short green stack, with the dashed outlines keeping the before state in view.

Fixes applied
LCP, lab4.5 s
First-load weight3.5 MB
Render-blocking3
Requests on load10

Before: 4.5 s LCP, 3.5 MB. All values are an example model for a WordPress page on mobile.

example-site.fi, first load, mobileexample model
beforeslow or render-blockingfastdeferred, not blockingLCP

What I fix, layer by layer

I run servers as well as write PHP and front-end code, so the fix happens at the layer that is actually slow, not wherever a plugin happens to reach.

Images

AVIF or WebP at the size each slot shows, width and height set so nothing jumps, fetchpriority="high" on the LCP image, lazy loading below the fold.

Scripts

defer on theme scripts, unused jQuery plugins removed, long tasks over 50 ms split so taps and clicks answer quickly.

Third parties

Chat widgets, heatmaps and tag sprawl loaded on interaction or after consent, each one kept only with a written reason.

Caching

Full-page cache for guests, a CDN for static files, and rules that leave cart, checkout and account pages uncached.

Server

Current PHP with OPcache, HTTP/2 or HTTP/3, Brotli, enough PHP workers and a slow-query log that gets read. Target: time to first byte under 0.8 s.

Fonts and layout

Self-hosted WOFF2 subsets, font-display: swap with matched fallback metrics, reserved space for banners and embeds.

Speed packages

Fixed prices in euros, excluding VAT 25.5%. Every package ends with the same before and after measurements, taken under the same conditions.

Speed check and quick fixes

€490from, one site proposed
  • Field data from Search Console and the Chrome UX Report
  • Lighthouse lab runs on your five busiest templates
  • Image, script and cache fixes
  • Before and after report in plain language
Get a speed check
Recommended

Full speed fix

€890from, one site owner to confirm
  • Everything in the speed check
  • Server tuning: PHP, OPcache, HTTP/3, Brotli
  • Theme and plugin clean-up, third parties trimmed
  • Up to 15 templates checked
  • Field data re-checked after 28 days
Ask about the full fix

Store speed

€1,490from, WooCommerce or Magento owner to confirm
  • Cart, checkout and search profiled separately
  • Redis object cache, Varnish where it fits
  • Magento indexers and JavaScript bundling
  • All changes tested on staging first
Ask about store speed

If the measured before and after shows no improvement on the pages we agreed, I keep working on it at no charge or refund the fix phase. owner to confirm

Know your slowest page? Send the URL and get a fixed price within one working day.

Get a speed check

How a speed job runs

Measure first, change one layer at a time, prove every step. You keep admin access to your site, server and accounts throughout.

  1. 1

    Measure

    Field data from real visitors, then lab runs on the templates that carry your traffic and sales.

  2. 2

    Find

    Waterfalls, performance traces and server logs show which layer costs the seconds.

  3. 3

    Fix

    Changes go to a staging copy first, then live in a quiet hour with a backup ready.

  4. 4

    Prove

    The same tests, same pages, same conditions. You see before and after side by side.

  5. 5

    Guard

    A short performance budget so new plugins and tags do not undo the work. A care plan can watch it monthly.

When I would not sell you a speed fix

Speed work pays when speed is the bottleneck. Sometimes it is not.

  • 01Your pages already pass all three Core Web Vitals in the field and visitors still leave. The problem is the offer or the page, so conversion work will earn more.
  • 02The site is due for a redesign within six months anyway. Build the new one fast from the start instead of tuning the old one.
  • 03The hosting plan caps PHP workers or memory and moving is not an option. I will tell you what the ceiling is before you pay for anything.

Questions about site speed

What are Core Web Vitals?

They are three Google metrics for real-user experience: Largest Contentful Paint for loading, good at 2.5 seconds or less; Interaction to Next Paint for responsiveness, good at 200 milliseconds or less; and Cumulative Layout Shift for visual stability, good at 0.1 or less. Google judges them at the 75th percentile of real visits.

Will a faster site help my SEO?

Somewhat, and it helps sales more. Core Web Vitals are part of Google's page experience signals, but relevance and content still decide most rankings. Speed pays off most clearly in visitors who stay, fewer abandoned carts and better landing page experience in Google Ads, which feeds into Quality Score and click costs.

Can you speed up a Magento or WooCommerce store?

Yes. On WooCommerce I work on object caching, PHP workers, plugin weight and cart fragments. On Magento it is full-page cache with Varnish, Redis, indexers, JavaScript bundling and, where it pays, a lighter front-end theme. Cart and checkout cannot be page-cached, so server tuning matters most there.

Get a speed check

Send one URL and tell me what worries you. You get a written fixed price within one working day, and the price does not change once agreed.

Prefer email? Write to [email protected]

Pikselipolku is an independent studio and is not affiliated with Google, WordPress, WooCommerce or Magento.

Audit requestReply within one working day

Optional: slow pages, lost rankings, a deadline, a law you need to meet.

About 2 minutes. Helps me send a firmer price.

Reply within one working day

Or email me: [email protected]

Made in Tampere. The path ends here.61.4978° N, 23.7610° E

Tell me what you need. I reply within one working day.

About these landmarks
  • Näsinneula tower, Tampere, 1971. Opened in 1971, with an observation deck and a revolving restaurant at the top.
  • Finlayson mill, Tampere, 1820. Cotton mill founded in 1820 by James Finlayson; the red-brick mill and chimney still stand by the Tammerkoski rapids.
  • Tampere Cathedral, 1907. National Romantic granite church by Lars Sonck, with frescoes by Hugo Simberg.
  • Helsinki Cathedral, 1852. White neoclassical church with green domes above the Senate Square steps, designed by Carl Ludvig Engel.
  • Parliament House, Helsinki, 1931. Eduskuntatalo, built of red granite behind a front row of tall columns.
  • Temppeliaukio Church, Helsinki, 1969. The Rock Church: cut into solid bedrock and roofed with a copper dome.
  • Suomenlinna sea fortress, Helsinki, 1748. Island fortress begun in 1748 at the entrance to Helsinki harbour; a UNESCO World Heritage Site.
  • Olavinlinna castle, Savonlinna, 1475. Medieval castle with three round towers, built on a rock island between two lakes.
  • Sauna by a frozen lake, UNESCO 2020. Finnish sauna culture is on UNESCO’s list of the intangible cultural heritage of humanity.
  • Lapland: spruce, reindeer and a fell, North. The northern end of the journey: spruce forest, a reindeer and a snow-capped fell.
© 2026 Pikselipolku, Tampere, FinlandBusiness ID [Y-tunnus]Built to WCAG 2.2 AABack to top