Web performance & Core Web Vitals

Your website is slow for a reason, usually three or four of them. I find them, from database queries to JavaScript bundles, remove them on purpose, and prove the result with real-user data. Audits and hands-on fixes for Laravel, Vue, Nuxt and WordPress sites, from Milano to anywhere.

  • 10+ years in production
  • Full-stack, not just frontend
  • Verified on real users
70%
better overall performance on a large booking platform
25%
faster page loads after deferring and code splitting
40%
higher SEO ranking with structured data
20+
slow operations moved off the request onto a job queue

Measured on client work at Santandrea Top Properties and Tanguear, Shine Software.

01 / Why it matters

Speed is the first thing visitors judge

Nobody reads your copy on a page that hasn’t loaded. Slow is a business problem wearing a technical costume.

Visitors don’t open DevTools. They feel a blank screen, a button that ignores them, a layout that jumps right as they tap. Then they leave, and most never tell you why.

Search engines feel it too. Core Web Vitals are part of Google’s page experience signals, and a slow page gets crawled less, rendered later and trusted less. AI answer engines favour pages they can fetch and parse quickly.

Your costs feel it. Heavy pages burn bandwidth, slow queries burn server time, and every workaround stacked on a slow foundation makes the next feature more expensive.

Performance isn’t a plugin you install once. It’s an engineering habit across every layer, and that is exactly the work I do.

02 / Signs

You probably need this if…

06 symptoms
  • Search Console flags “Poor URLs”

    The Core Web Vitals report shows pages failing on mobile, and the list isn’t getting shorter.

  • Lighthouse looks fine, users don’t agree

    Green scores in the lab, complaints in the field. Real phones on real networks tell a different story.

  • Mobile visitors bounce

    Analytics shows a much higher bounce rate on mobile than desktop for the same pages.

  • The admin is painfully slow

    Dashboards and listings take seconds to load. Often an N+1 query or a missing index hides behind it.

  • Every redesign got heavier

    New sliders, trackers and fonts arrived. Nothing ever left. The bundle doubled and nobody noticed.

  • Traffic spikes hurt

    Campaigns or seasonal peaks slow the whole site down, or take it offline right when it matters most.

03 / What I optimise

Every layer, not just the front

06 layers

Most performance services stop at the browser. Many of the slowest pages I’ve fixed were slow because of the server and the database. I work across the whole stack, so the fix lands where the problem actually is.

  • 01LCP

    Loading and rendering

    Get the main content on screen first, and everything else out of its way.

    • Critical rendering path and resource priority
    • Preload, preconnect and fetch priority
    • Server-side rendering and static generation
    • Render-blocking CSS and scripts removed
  • 02INP

    JavaScript and interactivity

    Less code on the main thread, so taps and clicks answer instantly.

    • Bundle analysis and code splitting
    • Lazy hydration and on-demand features
    • Long tasks broken up
    • Third-party scripts audited and deferred
  • 03CLS

    Images, media and fonts

    The heaviest bytes on most pages, and the usual cause of jumping layouts.

    • AVIF and WebP with responsive sizes
    • Low-quality placeholders (LQIP)
    • Reserved space for media and embeds
    • Font subsetting and swap strategy
  • 04TTFB

    Backend and database

    The server has to answer before the browser can do anything.

    • N+1 queries and missing indexes
    • Query and Eloquent optimisation
    • Slow work moved onto job queues
    • Application and query caching
  • 05TTFB

    Server and delivery

    Bytes travel shorter, compressed and cached wherever they can be.

    • Cloudflare and CDN caching rules
    • HTTP/2 and HTTP/3, Brotli compression
    • Cache headers that actually work
    • Linux, Apache and WHM tuning
  • 06All

    Guardrails

    A fast site stays fast only if regressions get caught before they ship.

    • Performance budgets in CI
    • Automated Lighthouse checks on pull requests
    • Real-user monitoring
    • A short playbook for your team

04 / Process

Measure, fix, prove

01 — 04
  1. 01

    Measure what users feel

    Field data from Search Console and the Chrome UX Report first, then lab profiling in DevTools and Lighthouse to find the cause behind each number.

    You get A baseline, page by page.

  2. 02

    Find the real bottlenecks

    Every issue ranked by impact against effort. The few fixes that move most of the needle go first, the long tail waits.

    You get A prioritised fix list.

  3. 03

    Fix, layer by layer

    Changes in small, reviewable pull requests on staging, so nothing surprises your team or your visitors on launch day.

    You get Working code, not a PDF.

  4. 04

    Verify and guard

    Before and after compared on real-user data, then budgets and checks added to CI so the gains don’t quietly erode.

    You get A report and guardrails.

05 / Case study

A slow booking platform, made fast

Santandrea Top Properties homepage, the booking platform optimised in this case studyPlatform

Santandrea Top Properties · Vue, Nuxt · 2022 to 2023

Visitors waited for parts of the page they hadn’t reached yet

A large property booking platform loaded images and scripts for the whole page before showing anything useful. I profiled the real bottlenecks first, then deferred off-screen images and components until visitors reach them, split the bundle so JavaScript loads only when a feature is used, and added low-quality placeholders so something meaningful paints immediately.

70%
better overall performance
25%
faster page loads
20%
more user engagement

06 / Ways to work together

Pick the depth you need

Performance audit

For teams who want a clear diagnosis and will fix it in-house.

A full review of your site’s speed across every layer, delivered as a plan your developers can act on the next morning.

  • Field and lab baseline for key templates
  • Root cause for every failing metric
  • Fixes ranked by impact and effort
  • A walkthrough call with your team

Ongoing care

For growing sites that ship features every month.

Regular hours to watch the numbers, catch regressions early and keep the site fast as it grows.

  • Monthly Core Web Vitals review
  • Regression fixes before they hurt rankings
  • Performance review of new features
  • Priority response on incidents

07 / Toolkit

What I measure with, and work on

Measurement

  • Search Console
  • Chrome UX Report
  • PageSpeed Insights
  • Lighthouse
  • Chrome DevTools
  • WebPageTest

Stacks

  • Laravel
  • Vue 3
  • Nuxt
  • Astro
  • Inertia
  • WordPress
  • Express.js
  • MySQL

Infrastructure

  • Cloudflare
  • Linux
  • Apache
  • WHM / cPanel
  • GitHub Actions
  • Job queues

08 / FAQ

Questions clients ask first

What are Core Web Vitals?

Three metrics Google uses to describe real user experience. Largest Contentful Paint measures how fast the main content appears (good is 2.5 seconds or less). Interaction to Next Paint measures how fast the page responds to input (200 milliseconds or less). Cumulative Layout Shift measures how much the layout jumps (0.1 or less).

They’re measured on your real visitors, and a page passes when 75% of visits meet the target.

My Lighthouse score is high. Why does Search Console still flag my pages?

Lighthouse is a lab test on one simulated device. Search Console reports field data from real Chrome users on real phones and networks. The two often disagree, and the field data is what counts. I start from field data and use lab tools to find the cause.

Will speeding up my site change how it looks?

Almost never. Most gains come from how things load, not what loads: deferring off-screen content, splitting JavaScript, modern image formats, faster queries and better caching. If a design choice is the bottleneck, I show you what it costs and you decide.

Which platforms do you work with?

Mostly Laravel, Vue, Nuxt and Astro, plus WordPress and custom PHP or Node.js sites. The method is the same on any stack: measure, find the real bottleneck, fix it, verify with real-user data.

Do you need access to my server?

Not for the audit. A public URL and read access to Google Search Console are enough to start. For backend and server fixes I need repository access and, where relevant, hosting or Cloudflare access, ideally on a staging environment first.

Do you work remotely?

Yes. I’m based in Milano and work with teams in Italy and abroad, fully remotely, in English.

10 / Next step

Fast is a choice.
Make it on purpose.

Send me your URL and a line about what feels slow. I’ll reply within two working days with a first read on where the time is going.

Or write directly: masih@masihtak.dev