MSSQL Page Split Spike on AlwaysOn Readable Secondary

Recently I caught a massive page-split spike on an AlwaysOn Secondary instance that was not mimicked in any way by the active primary. I'm interested in what might cause this on a readable secondary since everything is "read-only".