How can you optimize page load performance in a large Wicket application?

1. Favor stateless pages and StatelessForm for high-traffic, mostly-anonymous views, avoiding the memory and serialization overhead of a full stateful page instance per visitor.
2. Use LoadableDetachableModel everywhere a component references data from a database or another expensive source, keeping the session small and avoiding accidental serialization of heavyweight or non-serializable objects.
3. Mark truly static markup as raw and skip rendering wrapper components where a component adds no real behavior, so Wicket doesn't spend cycles managing components that don't need lifecycle tracking.
4. Enable resource caching and aggregation for CSS/JS resource references, and rely on Wicket's built-in support for combining and minifying resources rather than shipping many separate small files.
5. Tune the page store — controlling how many historical page versions are retained in the session, and whether older pages spill to disk — since an unbounded history under high concurrency is a common, avoidable memory pressure source.

The common thread across all of these is reducing what Wicket has to serialize, hold in memory per session, or manage as live component state, since that overhead (not raw HTML rendering speed) is usually where a large Wicket application's real performance cost accumulates.