Is your contention that web applications are slow due to lack of understanding of CPU cache, pipelining or assembly? Because that doesn't match my experience at

Is your contention that web applications are slow due to lack of understanding of CPU cache, pipelining or assembly? Because that doesn't match my experience at all. In my experience, web sites and applications are most often slow due to: 1. Indiscriminate use of third-party scripts and network connections, particularly for marketing cruft such as ads, analytics, and trackers. 2. Pulling in large blobs of code, particularly frameworks, because it makes things easier. 3. Back-end issues, particularly distributed monoliths disguised as microservices, delaying time-to-first-byte by 100s of milliseconds. 4. Lack of awareness of the latency and bandwidth characteristics of real users' devices. Other reasons, too, but these are some big ones. Understanding CPU cache, virtual memory, etc. is way, way down the list, and certainly wouldn't "change web applications from their current abysmal levels of performance."