Many premoves at once.

Perhaps, but too many premoves allow sandbagging.

Multiple premoves won't help you with stallers. They'll just derange fast chess.

Over there premoves cost time, unlike here. In any case, this has been requested before and we don't really want to implement them.

Yes but Premove on Lichess works for BOTS, its an adjustment to the LAG.

I play Maia Bot, it will flag me in a 2min game, I clocked it at AVG 00:00:02:01 sec per move. Or 2 milliseconds per move. On EVERY Move. No human can even depress a key that fast.
It only 'Appears' that Maia is taking time to calculate as the board does not update. The move is 'IN'.
In fact there are baked in command line instructions to account for this on the back end.

With that said, Sandbagging and other tactics DO need to be accounted for.

And Lichess should DEV a way to emulate OTB bullet.

IMO its not chess for people who are impaired, or do not have the hardware to compete (like a phone), just because of poor policy.

Also not sure why this hasn't been done already? I don't think it opens the door for exploitation. If I'm playing someone who 'Always' takes 2sec to move I start to get sus, But if I see a chain of premove in the middlegame, or a 3-4 combination premoved, I'm less sus.

Therefore I think they should Also make this metadata available in the player profiles. It makes for exciting Insights and more!

Example: Count of Premove per game, AVG lag, Count of premove in Opening/endgame/middlegame, Max Length of premove, QTY of games lost Durning premove, ELO most pre-moved, ECO most pre-moved and depth....etc.

@Ayushman_C said in #2:

Perhaps, but too many premoves allow sandbagging.

How?

Suppose your opponent plays an unexpected move. Then it all comes crashing down. Games will be lost for no reason. Ratings will fluctuate.