Response time changes how an interface feels. The useful question is not whether the idea sounds persuasive. It is whether it helps someone understand the work, make a decision, or complete a task with less friction.
What is happening
A visually minimal page can still feel heavy when assets are uncached or every request repeats unnecessary work. Performance is perceived behavior.
This tends to become visible at the boundary between the organization and the person encountering it for the first time. Internal familiarity hides effort that remains obvious to a customer, reader, applicant, or collaborator.
A practical response
Cache immutable assets, use conditional page responses, keep scripts small, and measure the complete delivery path rather than file size alone.
The aim is a smaller, clearer system: one source for the record, one visible hierarchy, and one next action that behaves as expected. That approach improves the immediate page and makes later application or database work easier to add without rebuilding the public surface.