Compression, logging, and limits are not part of the handler. They are a chain around it, and the order of the chain is a decision with a consequence.
About 1 min of reading
Write the chain order
Write the chain
Before you run it, say out loud what it will print. Then open the answer.
Swap two links and name the change
Before you run it, say out loud what it will print. Then open the answer.
Write the reason for the order
Before you run it, say out loud what it will print. Then open the answer.
Building per request is work per request. A chain built at start is a chain that cannot drift per request.
Each link is work on every response. The work is measured per link, which is why the links are named.
A limit before compression bounds the compressed bytes. A limit after bounds the original ones.
The order is a list. A list in a file is a list that can be reviewed before it is deployed.
A link that writes a response ends the request. The end is why the chain has an order at all.
Each one is defined here on this site. Open the entry for the full definition and the other words it points at.