PERFORMANCE
Caching repeat audits without serving stale data
The same business gets audited by more than one freelancer. Caching that result is free speed, until the site changes and the cache is wrong.
The same URL, audited twice
A popular local business can get audited by several different LeadScrapper Pro users independently. Re-running the full check every time wastes the latency budget on work that was already done, but a stale cached result is worse than no cache, since the whole point of the audit is that it's current.
The cache has a short enough window that a fresh audit for a business someone actually cares about is never more than a few hours behind reality, while still absorbing the cost of the common case: the same business showing up in more than one freelancer's search.