This is a bit off topic I guess, but I don't think the goal of fixing a slow Web can be achieved by building a faster Web browser. Developers will build and test (or not test) things on their powerful Macbooks, and usually ship things that aren't noticeably slow
for them, then a user with a $300 Windows laptop from Walmart will struggle to click on things. This is the nature of web dev. Increasing the speed of the browser just means web devs will accept that code is fast enough when
they use it, regardless of whether or not its fast enough when a user on a less powerful machine uses it. Essentially, web pages will always expand to fill the available resources of the dev's machine and if you use their code on a less powerful computer you're out of luck.
If we want a faster web we need to get web devs to test on slower browsers and more realistic target devices.
(I can actually think of an alternative solution that browser vendors could do ... Browsers could just display a blank screen whenever a web site falls below 60fps. Websites would get a lot faster pretty quickly if Chrome did that.)
EDIT: Actually... This is possible. Chrome should display a blank screen when a website falls below 60fps when devtools is open. That would have no impact on users, but would push web developers to fix their slow pages. I'm genuinely tempted to find the time to make a PR...