In the second half of February, we polished the blog, added RSS, made discovery visible in the admin, and cleaned up permissions and UX. No single blockbuster—just a solid set of improvements that make the product more usable and the blog more useful.
You've run PageSpeed Insights. The scores are poor. You've optimised images, minified CSS, and still LCP stays red. Or CLS keeps spiking on client sites. Or users complain that clicks feel sluggish even though the page "loads fast". The problem isn't always obvious—some of the worst PageSpeed mistakes look like best practice at first glance.
Every agency managing client websites pays a hidden tax: the time and effort spent on manual performance monitoring. Automated monitoring eliminates this tax entirely.
You need to know whether fixing Core Web Vitals will actually move the needle for rankings — and what to tell clients. Here's what the data shows so you can prioritise with confidence and justify monitoring.
Website load speed is how quickly your pages load and become usable for visitors. It’s the time from when someone opens a link to when the main content is visible and the page responds to taps or clic...
You don't know what "good" looks like for LCP, INP, or CLS — so you can't set budgets or explain them to clients. This template gives you concrete thresholds by site type so you can set, enforce, and report on performance without guesswork.
ChatGPT, Perplexity, Claude, and Google’s AI Overviews don’t magic their answers out of thin air. They rely on systems that fetch, read, and interpret web pages. If your site is slow, times out, or hides content behind heavy client-side rendering, those systems may never get your content in the first place.
The first half of February was dominated by one milestone: we brought the site online. The homepage, landing, and blog are live for testing and early-access signups, and we’ve started to add the structure that will make the blog and content side of Apogee Watcher useful for our users and for search.
Core Web Vitals (LCP, INP, CLS) tend to get treated as "performance metrics". Accessibility tends to get treated as "compliance work". That split is convenient, and it's wrong in practice. A keyboard user doesn't experience your site as a Lighthouse report. They experience it as a sequence of interactions: tab, focus, type, submit, wait, recover, continue. The same bottlenecks that hurt your Web Vitals routinely break assistive-tech UX. The nice part is that the fixes often pull double duty.
A performance budget is a set of limits on metrics that affect user experience. It's a threshold you agree not to exceed. When a metric crosses the budget, it triggers a review, an alert, or a rollback — just like a financial budget triggers action when you overspend.
If you run an agency managing 10, 25, or 50+ client sites, you can't afford ad-hoc performance monitoring. One missed regression can cost you a client. One undetected CLS issue can silently tank a client's rankings for weeks before anyone notices. This checklist gives you a repeatable system.
In the second half of January, we focused on upgrading the admin experience, making the product look and feel like one product, and laying the groundwork for how we’ll handle plans and leads.
