Recently someone asked me: why does on-chain data sometimes "pause," even though blocks are being produced? Basically, many times it's not the chain slow, but the layer you're viewing is slow: the frontend first makes an RPC call to fetch events, and when RPC rate limits, it has to queue; indexers/Subgraphs also need to fetch logs, replay, write to the database, and then serve your queries. If any step stutters, you'll see prices/positions freeze for a moment. Layer2 now constantly debates TPS, fees, subsidies, but I think the stability of these "data pipelines" has the biggest impact on user experience. No matter how generous the subsidies are, users will complain if they see loading spinners. Watching these things for a long time makes my eyes a bit sore, and my neck stiff... I now prefer to refresh a little less, keep key data locally for verification, to avoid being "paused" and influenced by the rhythm.