Portfolio · the entry product · 15 audit-shaped openings · 2016 to today
Know which fixes matter before you spend a dollar on them.
Most of this portfolio shows outcomes. This page sells the thing that comes first: the audit. It is the smallest engagement here and the one our audit-led engagements grew out of.
the path
field data on your key templates; if the problem is small, you are told it is small
six analysis sections plus the roadmap, issue-to-solution rows, written findings
quick wins separated from involved changes, effort-priced
retainers, migrations, year-long engagements; some audits just end
15 audit-shaped openings since 2016; 7 engagements on this site are tagged audit-driven. Some audits end at the report, and that is a fine ending.
01 · inside the report
This is the table of contents of the audit deliverable: six analysis sections and the prioritized roadmap that closes it. Each of the six carries a sample finding below it: a real line in the voice the report writes in, from a real engagement, paraphrased from project records. Yours will name your plugins, your templates, your numbers.
CrUX · Google Search Console
What real visitors actually experienced over the last 28 days, per page group, at the 75th percentile: the numbers Google ranks by, split by template so a healthy average cannot hide a failing page.
sample finding“CrUX says this origin is fine on average. The homepage is not: the reservation form loads last and pushes everything down.”Hotel Okura Amsterdam, 2025
DebugBear RUM · live traffic
What the numbers look like the moment monitoring switches on. Lab tools stop measuring at the page-load event; RUM keeps watching past it: per-visitor Core Web Vitals at the interaction level, TTFB by the hour under real ad traffic, and the per-template p75s a 28-day CrUX average smooths over. Monitoring is left running at handoff, so the numbers keep flowing after the report.
sample finding“The lab cannot tell you which interaction fails. RUM can: the INP is JavaScript from ads, video ads named per interaction, plus one page element driving the CLS.”gfcnieuws.com, 2024
Chrome DevTools coverage · waterfall
Every stylesheet and script weighed and attributed: which plugin or theme file owns it, how much of it executes before first paint, and what can be deferred, delayed, or deleted outright.
sample finding“Theme and plugin CSS and JS ship as one merged, minified bundle. Nothing can be attributed to a plugin until a coverage profile splits it back apart.”Aerotime, 2024
TTFB sampling · cache HIT/MISS analysis
How often pages are actually served from cache versus rebuilt in PHP, where the misses are (ads traffic, geolocation, query strings), and whether the host is helping or quietly fighting the cache plugin.
sample finding“Same page, same minute: 3 s TTFB on a cache miss, under 1 s on a hit. A host-side rewrite module is racing the cache plugin.”thefelthub.com, 2025
LCP element trace · format audit
Which element is the LCP on each template, whether it is preloaded, fetched with priority, served in a modern format, and the honest size budget of the hero the lab will measure you on.
sample finding“The image you are measured on is being lazy-loaded. The hero arrives last by configuration, not by accident of network.”tech4gamers.com, 2024
autoload audit · page-build profiling
What each plugin costs on every request, what the database loads on boot for pages that no longer exist, and the cron jobs that were supposed to be keeping the cache warm.
sample finding“Cache preload is warming 1,300+ zero-value tag URLs while real pages expire; an unused-CSS job has been silently dead for months.”thefelthub.com and the Macaw roster, 2025
02 · how it runs
The written report typically follows in one to two weeks. The one variable that has ever stretched delivery is access, never analysis: one hotel audit waited weeks on a Search Console permission chain, and the field data it unlocked was worth every day of the chase.
One site, every template that matters: home, article or product, category, landing. Field data first. Frontend always; server configuration wherever host access is granted.
WordPress admin (or Shopify collaborator access on shop builds), Search Console read-only, host panel or file access when possible. Read-only where the client prefers it; the audit adapts to what can be shared.
Lab and field together: CrUX and Search Console p75s per template, real-user monitoring where INP is the mystery, DevTools coverage for per-plugin attribution, cache HIT/MISS sampling for TTFB.
A findings document structured as issue-to-solution rows ready for developer tickets, quick wins separated from involved changes, an effort indicator per item, and monitoring left running so the numbers keep flowing after handoff.
03 · the hero narrative
In December 2025 a craft-education publisher bought an audit titled as a performance audit and strategic roadmap. The diagnostic milestone installed real-user monitoring and named the root causes of volatile TTFB within days: a host-side module racing the cache plugin, an opcode cache running full, and a preload queue warming over a thousand zero-value URLs. The client kept hiring.
Monitoring installed, field data read, root causes named and priced against effort. TTFB volatility explained down to the cache HIT-versus-MISS level; average TTFB about 0.3 s better within 24 hours of the first host-side fix.
LCP render-delay work on the ad-laden article template, under Mediavine scripts, without touching a single revenue tag.
Full hosting and domain migration: content, media, and membership data, redirects, Cloudflare, and the Search Console change of address, plus a custom membership-to-mailing-list plugin replacing a paid automation workflow.
04 · what an audit turns into
Not a pitch tactic: the pattern the contract archive actually shows. 15 audit-shaped openings since 2016,9 of them with the word "audit" in the contract title outright, and 7 engagements on this site tagged audit-driven. The cadence is not slowing:
| Year | Client | Opened as | Turned into |
|---|---|---|---|
| 2016 | Byrne Ventures | Site speed analysis, fixes and recommendations | returned two months later for a second pass |
| 2017 | SureShot Books | maintenance audit | the archive's first audit-titled contract |
| 2023 | Alexander Orth | two PageSpeed analysis contracts | CLS-scoped analysis, then a WP Rocket follow-through |
| 2024 | Dalton Luka | Core Web Vitals Audit & Fixes, twice | one-day site audit; working relationship still open in 2026 |
| 2024 | tech4gamers (Banoori) | opened with an audit request | the 3.7s TTFB rescue, then a second publisher site |
| 2024 | Aerotime | speed audit for a news site | issue-to-solution document, then four months of implementation support |
| 2024 | boogzelclothing.com | WordPress performance audit needed | same-day first read, then a year of hourly work |
| 2025 | Macaw Digital Marketing | PageSpeed analysis and optimization | an audit the agency presented to its client; the Elementor roster retainer; a repeat audit request nine months later |
| 2025 | Hotel Okura Amsterdam (Hotelchamp) | hotel website speed audit | recommendations-only report; the CrUX average vs page-level split finding |
| 2025 | Sandy M (thefelthub.com) | performance audit & strategic roadmap | three projects in four months |
| 2025 | Don Carom | audit traffic drop | fourth contract with a returning WooCommerce client |
| 2026 | Odds and Ends Supply | remediation, audit supplied by the client | Shopify Liquid work, Feb to Aug 2026 |
| 2026 | Creative Escapes | Lighthouse LCP diagnosis | client supplied their own audit; closed in a week with 5.0 public feedback |
Counts read from the normalized contract archive (529 contracts, 2014 to 2026). Two of the 2026 openings are remediations where the client supplied the audit document themselves; they count as audit-shaped, not as audits sold. Opening titles are paraphrased contract subjects; thread contents are never quoted.
05 · what it costs
the standing offer
That is the offer everywhere on this site, and it is the same offer here: a free first read of your field data, honest findings, no obligation. If the free read shows your problem is small, you will be told it is small.
Get a free auditbeyond the free read
The full report (six analysis sections plus the roadmap), deeper diagnostics, agency deliverables, multi-site rosters: quoted per scope, not off a rate card. The written report typically follows in one to two weeks. Numbers come after the scope is understood, in writing, before any work starts.
Verbatim from public Upwork feedback, unedited.
"Milan was very attentive, knowledgeable and eager to help. His input was very important for us to be able to decide what to do and what not to do. Extremely worthwhile consultation!"
"Milan is highly skilled and knowledgeable -- I will absolutely work with Milan again when I have questions about page speed issues, WordPress plug-in recommendations, and Divi's impact on page speed."
"It was pleasure working with Milan, he provided us the necessary support and consultation in a timely manner, adhering to high quality standards. We are looking forward to working with Milan again!"
Free audit, honest findings, no obligation. Every audit-led engagement in this portfolio started exactly here.
Get a free audit