Skip to content

test: add homepage performance guardrails - #1355

Draft
jderochervlk wants to merge 8 commits into
masterfrom
test/homepage-performance-guardrails
Draft

jderochervlk wants to merge 8 commits into
masterfrom
test/homepage-performance-guardrails

Conversation

@jderochervlk

@jderochervlk jderochervlk commented Sep 18, 2026

Copy link
Copy Markdown
Collaborator

Context

Establish regression coverage before the homepage performance stack changes component boundaries, images, route payloads, CSS, effects, and compiler behavior.

Changes

  • add production-build Playwright coverage for prerendering, hydration, navigation, clipboard behavior, and image loading
  • extend Vitest coverage for critical homepage sections and copy feedback
  • add deterministic JavaScript, CSS, DOM, and media baselines with focused report tests
  • run the build, performance budget, and browser suite in CI
  • run Lighthouse three times against the completed Cloudflare Pages deployment without enforcing score thresholds while optimization work is ongoing
  • retain one current Lighthouse artifact per branch and compare each PR with its target branch baseline, reporting N/A when no target baseline exists

Relates to #1354.


Stack created with GitHub Stacks CLI

@cloudflare-workers-and-pages

cloudflare-workers-and-pages Bot commented Sep 18, 2026

Copy link
Copy Markdown

Deploying with  Cloudflare Workers  Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status Name Latest Commit Preview URL Updated (UTC)
✅ Deployment successful!
View logs
guide c2468ab Commit Preview URL

Branch Preview URL
Sep 18 2026, 02:20 PM

@jderochervlk

Copy link
Copy Markdown
Collaborator Author

@codex

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Sep 18, 2026

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review Completed 2026-09-18T12:43:54.603934Z 282b282 Manual request
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. Can't wait for the next one!

Reviewed commit: 282b282781

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

@github-actions

github-actions Bot commented Sep 18, 2026

Copy link
Copy Markdown
Contributor

Lighthouse baseline

No Lighthouse baseline is available for target branch master. Scores are the median of 3 runs against the deployed Cloudflare preview.

Category Target Current Change
Performance N/A 83 N/A
Accessibility N/A 74 N/A
Best practices N/A 100 N/A
SEO N/A 50 N/A

Download the full Lighthouse reports and baseline

Commit 8883d79 · Cloudflare preview

@github-actions

Copy link
Copy Markdown
Contributor

Guide Cloudflare deployment

⛅️ wrangler 4.130.0
────────────────────
🌀 Building list of assets...
✨ Read 17 files from the assets directory /home/runner/work/rescript-lang.org/rescript-lang.org/apps/guide/build/client
🌀 Starting asset upload...
No updated asset files to upload. Proceeding with deployment...
Total Upload: 0.31 KiB / gzip: 0.22 KiB
Worker Startup Time: 0 ms
Uploaded guide (1.54 sec)
Worker Version ID: 523fb20a-2978-496d-b7f9-63ed8e888483
Version Preview URL: https://523fb20a-guide.rescript.workers.dev
Version Preview Alias URL: https://test-homepage-performance-gu-guide.rescript.workers.dev

To deploy this version to production traffic use the command wrangler versions deploy

Changes to non-versioned settings (config properties 'logpush' or 'tail_consumers') take effect after your next deployment using the command wrangler versions deploy

Changes to triggers (routes, custom domains, cron schedules, etc) must be applied with the command wrangler triggers deploy

@github-actions

Copy link
Copy Markdown
Contributor

Cloudflare deployment

Deployement ID: de571779-71ba-4168-ae7d-138a4ae9b24e
Deployment Environment: preview

⛅️ wrangler 4.130.0
────────────────────
✨ Compiled Worker successfully
Uploading... (8878/8880)
Uploading... (8879/8880)
Uploading... (8880/8880)
✨ Success! Uploaded 2 files (8878 already uploaded) (1.74 sec)

✨ Uploading _redirects
✨ Uploading Functions bundle
🌎 Deploying...
✨ Deployment complete! Take a peek over at https://de571779.rescript-lang.pages.dev
✨ Deployment alias URL: https://test-homepage-performance-gu.rescript-lang.pages.dev

Add production Playwright coverage for prerendering, hydration, navigation, clipboard behavior, and image loading. Track initial asset, DOM, and media baselines in CI before the homepage optimization stack changes them.
Align the Playwright container and deterministic homepage budgets with the React Router, Vite, and Playwright versions now on master.
Run the production prerender build on the standard Ubuntu runner and install Chromium explicitly, avoiding the React Router temporary-server failure inside the Playwright job container.
Run Lighthouse three times against the exact Cloudflare Pages deployment URL and enforce conservative category and Core Web Vitals baselines. Upload the generated reports as workflow artifacts for inspection.
Persist a branch-scoped Lighthouse baseline with the full reports, restore it on the next deployment, and publish a sticky PR comparison comment with a direct artifact link. Cancel stale branch deploys and remove superseded artifacts so each branch retains one current baseline.
Continue collecting and comparing Lighthouse results without failing the performance stack while the homepage optimizations are still in progress.
Restore the Lighthouse artifact for each pull request's base branch instead of the previous artifact from its head branch. Report missing target baselines as N/A so the first stack layer can establish the initial baseline without implying a zero score.
Query the pull request API when selecting the Lighthouse target artifact so stacked pull requests compare against their current base branch even when the workflow event payload is stale.
@github-actions

Copy link
Copy Markdown
Contributor

Docs preview

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant