Pages matrix / analytical reporting view

[HyperGlide]

Feature request: Pages matrix / analytical reporting view

Summary

I'm proposing a new reporting view that displays Lighthouse scores in a matrix format: pages (or URLs) as rows, category scores (Performance, Accessibility, Best Practices, SEO) as columns. This would complement the existing project dashboard and build view rather than replace them.

Motivation

The current UI is well-suited for:

• Drill-down into a single URL over time (project dashboard)
• Comparing before/after runs for a single build (build view)

There's less support for:

1. Multi-page comparison – Seeing scores for many pages within a build side-by-side in a table
2. Cross-project aggregation – Optionally viewing data across multiple projects in one place
3. Summary / averages – An aggregated row (e.g., average scores) across selected pages
4. Visual at-a-glance – Pictorial representation of scores (e.g., bar charts or gauges) that makes it easy to scan many pages quickly, alongside numeric scores

Proposed solution

A new route/view that displays:

• Rows: Pages (URL + device type, e.g., Mobile/Desktop) from one or more builds/projects
• Columns: Performance, Accessibility, Best Practices, SEO
• Cells: Category score with both a pictorial representation (e.g., horizontal bar or gauge) and numeric score
• Optional: Summary/average row across visible pages; filters (project, branch, device, URL search); multi-project selection for cross-project comparison

Open questions

1. Should this live as a new top-level view (e.g. /pages or /analytics) or as a mode within an existing view?
2. What's the right API shape for aggregating across projects/builds (new endpoints vs. client-side aggregation)?
3. Are there performance considerations for large numbers of pages/projects?
4. Is there appetite for this direction, and would maintainers be open to a contribution?

Out of scope (for initial implementation)

• Page thumbnails / screenshots
• Historical trend comparison within this matrix (single-build snapshot first)
• Replacing existing views (additive only)

I'm happy to work on an implementation and can share a design/prototype if this aligns with the project's direction.