Run results for: RegEx.test vs. String.includes vs. String.match with multiple searches

Run details:

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

Browser: Chrome 136

Operating system: Mac OS X 10.15.7

Device Platform: Desktop

Date tested: one year ago

Test name	Executions per second
RegEx.test	38724100.0 Ops/sec
String.includes	59528156.0 Ops/sec
String.match	20774654.0 Ops/sec

Script Preparation code:

var string = "Lorem ipsum dolor sit amet, consectetur adipiscing elit. Sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.";
var searches = ['ipsum', 'tempor', 'foobar', 'dolore', 'est']
var regex = new RegExp(searches.join("|"));

Tests:

RegEx.test
regex.test(string);
String.includes
for (const search of searches) { if (string.includes(search)) break; }
String.match
string.match(regex);