Performance Monitoring

Start your project

Start with speed, then keep it up

Three seconds. According to Google, that’s all the time your site has to load before you lose 40 percent of your viewers. 

Move it or lose it.

The need for speed has never been greater. Bounce rates are measured in milliseconds. Even barely perceptible sluggishness can lower retention. 

This shouldn’t come as a surprise. Online or off, who’d want to wait when they don’t have to? Imagine pulling up to a restaurant and seeing there’s a line out the door. You’re likely to drive to another restaurant down the block. Now imagine there’s a gajillion other restaurants to choose from, and you don’t even need to drive. That’s your competition.

Google PageSpeed Insights and GMetrix for attck.com

In order to keep users happy and keep them coming back, performance monitoring is necessary. Performance monitoring consists of gathering and analyzing large amounts of data to ensure that sites load at consistent rates, display the most important content at the highest possible speeds, and—most importantly—don’t suffer downtimes. 

Good things come to those who wait, but better things come to those who save other people’s time. Delays turn users off and drag revenue down. 

Forget performance anxiety. Meet performance pride.

Measure speed the way Google does

18 web performance resources worth bookmarking

Speed is measured, not guessed. Every project we complete gets a performance audit before launch and monitoring after it. These are the metrics Google uses to judge a page, the tools that test it in the lab and in real visitors’ browsers, and the services that keep watching after launch. Free unless marked otherwise, and none of them pays to be here.

Last reviewed November 2026

The metrics that count
  1. Web Vitals (web.dev)Google’s definition of the three Core Web Vitals (LCP, INP and CLS) and the thresholds for a good score.
  2. Interaction to Next PaintThe responsiveness metric that replaced First Input Delay as a Core Web Vital in March 2024.
  3. Core Web Vitals and Google SearchHow these metrics relate to search ranking, from Google Search Central.
Testing in the lab
  1. PageSpeed InsightsShows real-user field data and a Lighthouse lab test for any URL, side by side.
  2. WebPageTestDetailed waterfalls and filmstrips from real browsers and locations. The tool for finding exactly what is slow.
  3. Chrome DevTools Performance panelRecords what the browser does frame by frame, for diagnosing slow interactions.
  4. Lighthouse CIRuns Lighthouse on every code change so regressions are caught before release.
Real-user data
  1. Chrome UX ReportGoogle’s public dataset of how real Chrome users experience millions of sites. The data behind the field numbers.
  2. CrUX VisCharts a site’s Core Web Vitals history from the Chrome UX Report.
  3. web-vitals libraryA tiny script that measures Core Web Vitals from your own visitors and sends them to your analytics.
Ongoing monitoring
  1. DebugBear (paid)Scheduled lab tests plus real-user monitoring, with clear explanations of what changed.
  2. SpeedCurve (paid)Synthetic and real-user monitoring with performance budgets and competitor benchmarks.
  3. Sentry (free tier)Error and performance monitoring that ties slow pages to the code behind them.
  4. New Relic (free tier)Full-stack monitoring for servers, databases and the browser.
  5. Query MonitorFree WordPress plugin that shows slow database queries, hooks and API calls on every page.
Learning and the business case
  1. Learn Performance (web.dev)Google’s free course on images, fonts, scripts and loading strategy.
  2. Web Almanac: PerformanceHTTP Archive’s yearly look at how fast the web really is, based on millions of sites.
  3. WPO StatsA collection of case studies linking faster pages to conversions, revenue and engagement.
Perform better.
Performance Monitoring Work