Run results for: DOMParser vs. createElement

Run details:

User agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/140.0.0.0 YaBrowser/25.10.0.0 Safari/537.36

Browser: Yandex Browser 25

Operating system: Windows

Device Platform: Desktop

Date tested: 8 months ago

createElement

2.1M/s

DOMParser

313K/s

View exact numbers

Test name	Executions per second
✓ createElement	2,074,921 Ops/sec
DOMParser	312,746 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