MARKETING

Fail the PR check when a landing-page preview misses CWV budgets

On every pull request touching landing-page files, it audits the Vercel preview's Core Web Vitals and posts a GitHub commit status that blocks merge until LCP, CLS, and INP pass…

CategoryMarketing
Enginesim
Difficultyintermediate
Triggerevent
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerPR opened on landing-page filesGitHubGitHub
  • ActionResolve Vercel preview for head commitVercelVercel
  • ActionAudit preview Core Web VitalsBrowserbase
  • LogicCheck LCP, CLS, INP vs budget and baseline
  • OutputWrite pass/fail GitHub commit statusGitHubGitHub

What it does

This workflow wires Core Web Vitals into your code review. When a PR changes landing-page code, it waits for the Vercel preview, audits it, and writes a required GitHub status check. A regression in LCP, CLS, or INP turns the check red and blocks merge, so performance is enforced at review time instead of discovered in production.

When to use it

Use it when engineers and marketers co-own landing pages and you want CWV treated like a test: no green check, no merge. Ideal for teams running paid campaigns who cannot afford a perf regression slipping past review.

How it works

  1. 1A GitHub pull_request event fires for a PR touching the landing-page directory.
  2. 2The workflow resolves the matching Vercel preview deployment for the PR's head commit.
  3. 3It audits the preview and reads LCP, CLS, and INP.
  4. 4A logic step checks each metric against budget and the prior baseline.
  5. 5It writes a pass or fail commit status back to GitHub, gating the merge on the result.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect GitHubRepos, issues, pull requests, actions.
  2. 2
    Connect VercelDeploys, runtime logs, analytics.
  3. 3
    Connect BrowserbaseHeadless browsers, sessions, replays.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.