Running on-call rotations in a team of six engineers

Our product grew faster than our team, and now six engineers share responsibility for a service that customers use around the clock. Night pages have become frequent enough that people dread their on-call week, and two colleagues have mentioned burnout.

We started by deleting alerts nobody acted on, writing short runbooks for the most common incidents and giving whoever is on call a lighter sprint load. Pages dropped by half within two months. How do other small teams keep on-call sustainable, and do you compensate engineers for it?