Run results for: Traverse function vs NodeIterator vs TreeWalker

Run details:

User agent: Mozilla/5.0 (Linux; Android 10; K) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/133.0.0.0 Mobile Safari/537.36

Browser: Chrome Mobile 133

Operating system: Android

Device Platform: Mobile

Date tested: one year ago

NodeIterator with filter param

386K/s

TreeWalker with filter param

370K/s

Traverse function

110K/s

TreeWalker with filter function

33K/s

NodeIterator with filter function

13K/s

View exact numbers

Test name	Executions per second
✓ NodeIterator with filter param	386,145 Ops/sec
TreeWalker with filter param	370,433 Ops/sec
Traverse function	110,043 Ops/sec
TreeWalker with filter function	32,534 Ops/sec
NodeIterator with filter function	13,316 Ops/sec

Script Preparation code:

// language=HTML
const html = `
    <!-- article out start -->
    <article>
        <!-- article in start -->
        <h1>Lorem ipsum</h1>
        <p>Lorem ipsum dolor sit amet, consectetur adipisicing elit. Cumque, nostrum.</p>
        <!-- article in end -->
    </article>
    <!-- article out end -->

    <!-- article out start -->
    <article>
        <!-- article in start -->
        <h1>Lorem ipsum</h1>
        <p>Lorem ipsum dolor sit amet, consectetur adipisicing elit. Cumque, nostrum.</p>
        <!-- article in end -->
    </article>
    <!-- article out end -->

    <!-- article out start -->
    <article>
        <!-- article in start -->
        <h1>Lorem ipsum</h1>
        <p>Lorem ipsum dolor sit amet, consectetur adipisicing elit. Cumque, nostrum.</p>
        <!-- article in end -->
    </article>
    <!-- article out end -->
`;
const template = document.createElement('template');
template.innerHTML = html;

window.testTemplate = template;

window.testTraverse = function traverse(node, use) {
    if (!node) return;

    use(node);
    traverse(node.firstChild, use);
    traverse(node.nextSibling, use);
}

Tests: