“Native performance” in this context means compared to scripting languages, not low-level languages like C. Of course, Go offers native performance relative to JavaScript. Your comment seems to assume the author was comparing Go to more systems-level languages like Rust or C. In those cases, Go may lag behind, but it still qualifies as native performance.
I think the author puts Rust and Go in the same basket, and it is something that I can't agree.
> scripting languages
The "script" is compiled all the way down to machine code by the runtime, for heavily used paths. The black/white distinction of "scripted" vs. "compiled" does not exist, has not for many years.
Too many of these discussions and arguments seem to be stuck in the 1990s technology level. It is much more mixed and complex now.