Run results for: Traverse function vs NodeIterator vs TreeWalker

Run details:

User agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/119.0.0.0 Safari/537.36

Browser: Chrome 119

Operating system: Linux

Device Platform: Desktop

Date tested: 2 years ago

NodeIterator with filter param

567K/s

TreeWalker with filter param

519K/s

Traverse function

77K/s

TreeWalker with filter function

53K/s

NodeIterator with filter function

20K/s

View exact numbers

Test name	Executions per second
✓ NodeIterator with filter param	567,485 Ops/sec
TreeWalker with filter param	518,686 Ops/sec
Traverse function	77,297 Ops/sec
TreeWalker with filter function	52,934 Ops/sec
NodeIterator with filter function	20,358 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: