Your testing methodology will fail horribly the moment the core component fails to produce results on real-world use cases, or scale up with the included module

Your testing methodology will fail horribly the moment the core component fails to produce results on real-world use cases, or scale up with the included modules that are required for it to even be called a modern day web-server. You eventually have to test the whole, not the part, unless you want to see benchmarks for useless/no-context metrics. On the other hand I do realize its fun to see tests like this, and they can even give you a bit of insight... For example, that Apache now comes close to competing with Nginx on static loads, especially for larger files (9KB vs 54KB).