EU-based RUM solution Other devs are already building with our MCP & API

Use cases

  • How our own Server-Timing header showed us where 437 milliseconds went

    • Published
    • reading time ±9 minutes

    We help other teams find out where their milliseconds go. So it was a little awkward to find out that one of our own documentation pages needed 481 milliseconds to build on the server, before a single byte left our origin.

  • Making sure paid traffic has the best page speed possible

    • Published
    • reading time ±2 minutes

    If your ecommerce depends on -or receives- a lot of ad traffic, it is a must to be sure they have the best possible experience in terms of Core Web Vitals and page speed. In this article, we explain how RUM ensured that the ad budget was spent well.

  • Don't make visitors on your website wait for the same page twice

    • Published
    • reading time ±5 minutes

    Are you sure your caching strategy is in order and that returning and successive visitors will benefit? This client found out that there are still a lot of performance gains to be made on the Time to First Byte (TTFB).