Toggle navigation
MeasureThat.net
Create a benchmark
Tools
Feedback
FAQ
Register
Log In
Run results for:
charCodeAt vs codePointAt actually using unicode chars
Go to the benchmark
Embed
Embed Benchmark Result
Run details:
User agent:
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/130.0.0.0 Safari/537.36
Browser:
Chrome 130
Operating system:
Windows
Device Platform:
Desktop
Date tested:
one year ago
Test name
Executions per second
charCodeAt
7595058.0 Ops/sec
codePointAt
7985870.5 Ops/sec
Script Preparation code:
var str = "some str😀ing heresome string he😀resome string heresome st😀ring heresome str😀ing heresome 😀string heresome string heres😀ome string heresome string heresome stri😀g heresome string heresome string heresome str😀ing heresome string heresome string heresome string her😀😀😀😀esome string heresome string here😀some string here"
Tests:
charCodeAt
str.charCodeAt(20)
codePointAt
str.codePointAt(20)