Smitty is the product manager for Family.com, a website for genealogists. Earlier this year, many comments from site feedback complained about poor performance. Working with the site marketing and development teams, Smitty created a plan where the site performance metrics couldn't fall below a certain level. Which plan type is Smitty's plan?

Smitty's plan is a performance budget. A performance budget sets quantifiable limits on various performance metrics (like load time, page weight, or number of requests) that a website or application must adhere to. This ensures that performance doesn't degrade over time, especially during new feature development. The plan's goal is to prevent performance from falling below a certain level, which directly aligns with the definition of a performance budget. A "speed plan" is too general and not a recognized term for this specific strategy. A "performance plan" is also too broad; while it involves performance, it doesn't specifically imply the setting of strict, measurable limits. A "latency limit" is a specific type of performance metric limit, but a performance budget encompasses a broader set of metrics, not just latency.