Without understanding what your requirement is, it is extremely hard to tell if Go will outperform node in terms of use case.
Performance is not just a simple a-b criteria. It depends on how long you took to write the code, how proficient you are in the development environment, what is your system requirement etc. Thinking that Go will outstrip node everywhere is wrong.
AFAIK go does well in concurrent work load. Even if node is async in nature, it relies heavily on event loop clearing callback queue which in turn gets processed in single execution stack (my knowledge is old, forgive me if this is not the case any more). Go on the other hand uses something called "Goroutine" which in layman's term is ultra light threads which performs much better than event loop-execution stack-async architecture of Node. Check out this blog blog.golang.org/pipelines
Another area Go is really good is building small scale microservices. Resource Vs Performance tradeoff is way more in case of node as compared to Go, for microservices.