Run results for: DOMParser vs. createElement

Run details:

User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/137.0.0.0 Safari/537.36

Browser: Chrome 137

Operating system: Mac OS X 10.15.7

Device Platform: Desktop

Date tested: one year ago

createElement

1.9M/s

DOMParser

397K/s

View exact numbers

Test name	Executions per second
✓ createElement	1,933,002 Ops/sec
DOMParser	396,707 Ops/sec

HTML Preparation code:

<!--your preparation HTML code goes here-->

Script Preparation code:

/*your preparation JavaScript code goes here
To execute async code during the script preparation, wrap it as function globalMeasureThatScriptPrepareFunction, example:*/
async function globalMeasureThatScriptPrepareFunction() {
    // This function is optional, feel free to remove it.
    // await someThing();
}

Tests:

DOMParser
const html = "<p></p>" const parser = new DOMParser(); const virtualDom = parser.parseFromString(html, 'text/html'); return virtualDom.body.innerText === ''
createElement
const html = "<p></p>" const el = document.createElement('div'); el.innerHTML = html; return el.innerText.trim() === '';

Run results for: DOMParser vs. createElement

Comparing the performance of parsing the innerText from DOMParser vs createElement SPOILER: DOMParser is 4x slower

DOMParser

createElement