Run results for: Traverse function vs NodeIterator vs TreeWalker

Run details:

User agent: Mozilla/5.0 (Android 14; Mobile; rv:133.0) Gecko/133.0 Firefox/133.0

Browser: Firefox Mobile 133

Operating system: Android

Device Platform: Mobile

Date tested: one year ago

NodeIterator with filter param

607K/s

TreeWalker with filter param

522K/s

Traverse function

228K/s

TreeWalker with filter function

94K/s

NodeIterator with filter function

40K/s

View exact numbers

Test name	Executions per second
✓ NodeIterator with filter param	606,925 Ops/sec
TreeWalker with filter param	521,887 Ops/sec
Traverse function	227,954 Ops/sec
TreeWalker with filter function	93,855 Ops/sec
NodeIterator with filter function	40,420 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: