And...? What is the point of your posts?
Are they to show that the M1 is not universally great at running every single application or benchmark on the planet, irrespective of whether they have been designed to run well on the M1? OK - it's a valid data point, so, err...thanks for your input. You still haven't demonstrated whether this is due to a failure on the part of the developers to create code optimised for the platform, or some inherent flaw in the processor, which seems to be the argument you are putting forward...
These results only matter if these are the applications you need to run, in which case, the information would be useful to you.
Fortunately, for the vast majority of existing MacOS applications, the M1 Macs run extremely well and most users are delighted with the performance, low temperatures, inaudible fan noise, and excellent battery life for the laptops.
[Addendum: to be fair, these kind of tests, when performed without some ulterior motive to re-enforce a subjective prejudice, are valid and useful. In my career, I have run specific benchmark tests against hardware to determine its suitability to run the required workload, .e.g. running Java benchmarks against a server to be used for running Java middleware. It doesn't matter if it runs other applications better or worse - it only matters if it runs what I need with acceptable performance.
These tests are becoming even more relevant with the growing availability of ARM-based cloud services. Some applications run extremely well on ARM and the price-performance ratio is compelling. Others are not so good, especially those that use features only found in specific Intel / AMD CPUs. You need to test before deploying in production so that you know how well things will run until real loads.]