Performance Budget Thresholds Template

The Problem: No Clear Definition of "Good"

Without concrete thresholds, you can't set performance budgets, explain pass/fail to clients, or know when to alert. "LCP should be good" isn't enough — you need numbers. This template gives you those numbers: ready-to-use thresholds by site type (e-commerce, agency client sites, content, SaaS, landing pages) so you can define "good" once and enforce it everywhere.

Benefits: One place for all your budget values, client-ready language, and clear escalation (warning vs critical). What you get: Set budgets per site, get alerted only when it matters, and report to clients with confidence.

Your Ready-to-Use Performance Budget Template

Copy the thresholds below into a Google Sheet, CSV, or your monitoring tool. No theory — just the numbers, organised by site type and strategy.

If you want the "why" behind these numbers, read our Complete Guide to Performance Budgets first.

The Template

Universal Thresholds (Google's "Good" Baselines)

These are the starting points for any site. For an introduction to what is Core Web Vitals, see our practical guide; the numbers below follow Google's documented thresholds. Adjust based on your baseline: If your current scores are far from these targets, use them as stretch goals and set interim budgets at your current values. Tighten as you improve.

Note: For LCP, INP, FCP, TBT, Speed Index — lower is better. "Poor" = exceed the max. For Performance Score and CLS — higher is better (Score) / lower is better (CLS).

Budget Template by Site Type

E-Commerce

Agency Client Sites (Default)

Content / Blog Sites

SaaS / Web Applications

Landing Pages / Marketing Sites

How to Use This Template

Step 1: Choose Your Site Type

Pick the template that matches your site (or start with the "Agency Client Sites" default if you're not sure).

Step 2: Copy Into Your Tool

Google Sheets / CSV:Copy the CSV data above into a spreadsheet. Add columns for:

• Current Mobile Score — Your latest test result

• Current Desktop Score — Your latest test result

• Status — Within Budget / Over Budget / Critical

Monitoring tool (like Apogee Watcher):Enter the Mobile Budget and Desktop Budget values as your performance budget thresholds per site.

Lighthouse CI config:Translate thresholds into your lighthouserc.json:

{
  "ci": {
    "assert": {
      "assertions": {
        "largest-contentful-paint": ["error", {"maxNumericValue": 2500}],
        "cumulative-layout-shift": ["error", {"maxNumericValue": 0.1}],
        "total-blocking-time": ["error", {"maxNumericValue": 200}],
        "first-contentful-paint": ["warn", {"maxNumericValue": 1800}],
        "categories:performance": ["error", {"minScore": 0.9}]
      }
    }
  }
}

Step 3: Baseline Your Sites

Run PageSpeed Insights on your key pages. Fill in the "Current" columns. Anything marked "Over Budget" is an immediate action item.

Step 4: Set Up Alerts

Configure your monitoring tool to alert you when any metric exceeds its budget. Without alerts, this template is just a document. With alerts, it's a safety net.

Multi-Client Tracking Spreadsheet

For agencies managing multiple clients, use this structure:

Color-code the Status column: green for OK, red for OVER. Review weekly.

Budget Escalation Levels

Not all budget violations are equal. Use escalation levels to prioritise response:

Adjusting Budgets Over Time

Budgets aren't permanent. Review quarterly:

Tighten when:

• Your team consistently meets budgets with room to spare

• Competitors are faster and you're losing rankings

• Client expectations increase

Loosen when:

• New required functionality legitimately impacts performance (e.g., adding a complex interactive feature)

• A temporary campaign requires heavier scripts (set an expiration date for the loosened budget)

Never loosen because:

• "We can't fix it right now" — that's a prioritisation issue, not a budget issue

• "The score fluctuates" — that's normal variance, not a reason to move the goalposts

Get this template on GitHub

Copy-ready CSV budgets by site type, a multi-client tracking sheet, and a Lighthouse CI example live in performance-budget-thresholds-template (CC0).

Browse the full set in core-web-vitals-checklists · Apogee on GitHub.

FAQ

Can I customise these thresholds for my specific site?Yes. The template provides baseline values. Adjust based on your current scores, site type, and competitive benchmarks. E-commerce and landing pages often need stricter LCP and CLS budgets; content sites can use the standard thresholds.

What's the difference between the "Agency Client Sites" and "E-Commerce" templates?Agency Client Sites use Google's standard "Good" thresholds as a default. E-Commerce is stricter — lower LCP (2s vs 2.5s), tighter INP (150ms vs 200ms), and stricter CLS (0.05 vs 0.1) because conversion-critical pages need to feel instant.

How do I use this template with a monitoring tool?Copy the budget values into your tool's configuration. Most tools let you set thresholds per metric, per site, and per strategy (mobile/desktop). Once set, the tool will run tests against these budgets and alert you when thresholds are exceeded.

Should I track all metrics or just LCP, INP, and CLS?LCP, INP, and CLS are the Core Web Vitals — track them first. FCP, TBT, and Speed Index add useful context. Performance Score is a useful composite. Start with CWV + Score; add others if you need deeper visibility.

What you can achieve: Every site can have clear pass/fail thresholds, alerts that fire only when metrics cross the line, and reports clients understand. Use this template so performance budgets stop being guesswork and start being something you can set, enforce, and show.

Managing performance budgets across multiple sites is easier with automation. Apogee Watcher lets you set budgets per site, get alerted when thresholds are exceeded, and track trends over time. Join the waitlist for early access.