Create profiling for Scheme and JavaScript code

Check which Scheme function or macro is called the most times during the unit test run.

Optimizing the most used functions or macros can make a difference in speed.

- [ ] Find or create a new tool for profiling
- [ ] Run profiling on Scheme code
- [ ] Run profiling on JavaScript code

Start by examining how the unit test run executes Scheme and JavaScript code and what profiling tools are already available. Done means selecting or creating a profiling tool, then producing profiling results for both Scheme and JavaScript code that identify the most frequently called functions or macros.

Written by the indexing model from the issue text.