Speed and benchmarks

What "fast" should mean

• Focus on user-perceived responsiveness rather than abstract benchmark claims.
• Explain why framework benchmark contests are often misleading.

Where performance is necessary

• Slow queries.
• Heavy rendering.
• Asset size.
• Network round trips.

Practical performance guidance

• Measure user-facing operations.
• Optimise after finding real bottlenecks.
• Use architecture and simplicity as performance tools.
• Explain how static-first pages, thin page logic, and server-rendered HTML affect performance.

---

Finally, let's move to the repository-entity pattern page to complete the further reading chapter.