LAPTIME
CI / CD Integration

Gate every deploy on real metrics.

Scan before and after each deploy, get a before/after comparison on the PR, and block the merge when performance, security or SEO regresses. All from GitHub Actions.

Actions / laptime-ci
Baseline scanbefore
Deploydeploy
Post-deploy scanafter
Compare and gategate
globe.li🟢 Improved
Overall84 → 89+5
LCP718 → 558ms−160ms
SEO96 → 99+3
Quick start
01

Add it to your repo

Download the kit and commit three small files. Zero dependencies, no build step, about 11 KB, and each one has a single home.

Download the kit
Then add one secret, LAPTIME_BYPASS_KEY, in your repo settings.
your-repo/
.github/
scripts/
laptime-ci.mjs1
workflows/
laptime-ci.yml3
laptime.config.json2
02

Make it yours

Set up your config in one file: the URL to scan, which scans to run, the quality gate, and optionally any thresholds. Anything you leave out falls back to sensible defaults.

gate: true blocks the merge, "warn" annotates without failing, false just reports.
laptime.config.json
{
  "url":   "https://globe.li",
  "scans": ["performance", "security", "seo"],
  "gate":  true,   // fail the PR on a breach
  "thresholds": {
    "performance": { "maxLcpRegressPct": 15, "maxDrop": 5 },
    "security":    { "min": 80 },
    "seo":         { "maxDrop": 5 }
  }
}
03

Let it rip

Open a pull request and the whole thing runs itself. Build, test and the baseline scan kick off together, the new build ships and gets scanned, and the comparison lands on your PR as a report. If a threshold breaks, the gate blocks the merge.

pull request #128 / checks
build
test
baseline scan
deploy
purge CDN cacheAWS / Cloudflare
post-deploy scanreport.md
gatePASS