Here at Raygun, improving performance is baked into our culture. We don't just think about our application performance, but more broadly, we look at our own infrastructure and ask if there's anything we can do to make it more performant for our business and for our customers. Two years ago, we switched our API from Node.js to .NET Core and achieved a 2000% increase in throughput. To continue that story, we recently upgraded .NET Core 2.1 to 3.1 and saw a 12% increase in performance. We enjoy presenting our performance findings, so in this post, we'd like to give some context into why we upgraded and the conditions that helped us achieve the 12% performance lift.

Raygun helps thousands of software teams diagnose and resolve performance problems faster and more efficiently. We understand that in today's current climate, there is even more pressure on teams to ensure software quality across the whole stack, all while being cost-effective. It's no easy task! But we know that consolidating tools can help.

Loading speeds of websites will always be a tricky thing to manage. They depend on anything and everything between your user's choice of device and the server hardware your site runs on. There are many web performance killers that can be removed as you develop your web page. Removing as many of these barriers as possible is critical if you want your website to load smoothly and quickly for the majority of your users. Here are some suggestions for streamlining everything that is within your control to allow for the fastest possible load times for your users.

In our latest release, we're rolling out a whole series of improvements to Raygun Real User Monitoring that gives you the instance-level data you need to understand exactly how your application is performing in every single user session. Armed with this level of diagnostic information, you and your team will know exactly where to spend time when improving the performance of a particular page.