What I like most about NeoLoad is how it makes performance testing feel manageable once you get used to it. Getting tests up and running is pretty quick, which helps when you’re trying to move fast without overcomplicating things.
Another big plus is how clear the results are. The graphs are simple and easy to read, so you can understand what’s happening without spending a ton of time digging through data.
It also works smoothly with the other tools we already use, which makes a big difference day to day. Everything fits into the workflow nicely, so it feels less like a separate system and more like part of the overall process. Review collected by and hosted on G2.com.
One thing I don’t like about NeoLoad is that the initial learning curve can feel steeper than expected. When you’re new to it, some settings aren’t where you’d naturally look, so even simple tasks can take extra time at first. On top of that, building scripts for more complex scenarios usually takes longer than it seems like it should, especially when you’re trying to model real-world user behavior in detail.
I also feel the documentation is decent, but not always clear enough when you’re troubleshooting something specific. A lot of times, I end up digging through forums or community posts to find practical answers. And when test sizes get really large, performance can lag a bit, which slows things down right when you need fast feedback the most. Review collected by and hosted on G2.com.
