You can see comparisons between ES5 and ES2015 feature equivalents, as well as comparisons with older versions at <a href="https:&#x2F;&#x2F;kpdecker.github.io&#x2F;six-speed&#x2F;" rel="nofollow">https:&#x2F;&#x2F;kpdecker.github.io&#x2F;six-speed&#x2F;</a>.<p>It&#x27;s important to remember that implementation of ES2015 is merely the first pass; optimization comes soon after and will rapidly improve performance. General, absolute numbers (e.g. &quot;ES2015 is X% slower than ES5&quot;) are usually either nonspecific or soon out-of-date. The best advice is to revise your performance assumptions frequently based on real code.<p>r.e. ES5 side-effects: ES2015 adds language features and changes semantics of existing features in ways that necessarily change the execution path of code (including ES5 code). When V8 first tried implemented proper (ES2015) RegExp subclassing, for example, it regressed existing (ES5) RegExp performance by ~70%, but a subsequent optimization reduced the regression to ~9%. This is an unfortunate consequence of a rapidly evolving spec, but these cases are exceptional and will get better over time.<p>(Disclaimer: I&#x27;m a PM on the V8 team.)