The idea came from a pattern I kept seeing when talking to web designers: tools like Lighthouse and PageSpeed produce a lot of metrics, but turning those signals into something meaningful for client conversations is difficult.
I started experimenting with a deterministic scoring model that analyses performance, structure and security signals and tries to identify the primary constraint affecting a site.
The output is a structured diagnostic report that highlights:
• the primary constraint affecting the site • the fixes most likely to produce the biggest improvement • explanations developers can use when discussing issues with clients
The goal isn’t to replace Lighthouse or PSI but to interpret those signals into something closer to a technical diagnosis.
Curious to hear whether developers think this kind of prioritisation model makes sense or if it misses the point.
david_iqlabs•1h ago
I’m especially interested in whether developers think this kind of prioritisation actually reflects real-world debugging workflows.