MARKETING

Post a CWV pass/fail status check on every landing-page pull request

On each pull request that touches landing-page code, runs a Core Web Vitals audit on the Vercel preview and writes a GitHub commit status plus a comment so reviewers see LCP…

CategoryMarketing
Enginesim
Difficultyintermediate
Triggerwebhook
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerGitHub PR opened or updatedGitHubGitHub
  • ActionResolve Vercel preview for commitVercelVercel
  • ActionAudit changed routes for LCP/CLSBrowserbase
  • LogicDiff metrics vs base branch baseline
  • OutputWrite commit status + PR commentGitHubGitHub

What it does

Turns Core Web Vitals into a first-class code-review signal. When a PR opens or updates, it audits the matching Vercel preview, computes LCP and CLS deltas against the base branch, and reports them as a GitHub status check and an inline PR comment so reviewers never merge blind.

When to use it

Use it when performance ownership lives with the team writing the page, not a separate perf squad. It gives reviewers the numbers in the place they already work and lets you make the check required for merge on landing-page paths.

How it works

  1. 1A GitHub pull_request webhook fires when a PR is opened or synchronized.
  2. 2The flow resolves the Vercel preview URL for the PR's head commit.
  3. 3It runs a synthetic audit on the changed routes and gets LCP and CLS.
  4. 4A logic step diffs the metrics against the stored baseline for the base branch.
  5. 5It writes a pass/fail GitHub commit status and posts a comment with the per-route table and deltas.

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.