---
title: "Comment by netproxy on \"I Built Nextvital to Turn Lighthouse Warnings Into Actual Next.js Fixes\" | Hashnode"
description: "The cache-before-rate-limit ordering is a thoughtful detail — cheap repeat lookups without weakening abuse protection. Also smart to build the AI prompt server-"
url: "https://hashnode.com/posts/i-built-nextvital-to-turn-lighthouse-warnings-into-actual-next-js-fixes/6aba15ca9744bc65f1c6df26/comment/6abaecda729b20536feee8da"
---

[Discussion](https://hashnode.com/posts/i-built-nextvital-to-turn-lighthouse-warnings-into-actual-next-js-fixes/6aba15ca9744bc65f1c6df26)

Comment [I Built Nextvital to Turn Lighthouse Warnings Into Actual Next.js Fixes](https://hashnode.com/posts/i-built-nextvital-to-turn-lighthouse-warnings-into-actual-next-js-fixes/6aba15ca9744bc65f1c6df26)

[netproxy](https://hashnode.com/@argumentmoney8117)

[Sep 28](https://hashnode.com/posts/i-built-nextvital-to-turn-lighthouse-warnings-into-actual-next-js-fixes/6aba15ca9744bc65f1c6df26/comment/6abaecda729b20536feee8da)

The cache-before-rate-limit ordering is a thoughtful detail — cheap repeat lookups without weakening abuse protection. Also smart to build the AI prompt server-side, so the model can only score real cached audit data.