Once you know how fast your site is via mPulse, you can identify how to improve its speed. As each beacon of data arrives, the mPulse dashboard gives you a summary of back-end and front-end timers, plus spark lines that show performance over time. It also gives you a visual breakdown of front- and back-end performance and traffic over time. mPulse lets you directly measure how your users are impacted by delays on your site, which leads to a much more accurate estimate of what your target speed should be and helps you identify where you should prioritize improvements.

mPulse collects the following categories of data from real user

• Core Web Vitals, such as Largest Contentful Paint (LCP), First Input Delay (FID), and Cumulative Layout Shift (CLS)
• Performance metrics (for example, TTI, TTFB, page load, and DOM loaded)
• Top level (including domain, timestamp, and IP address)
• Session (session ID and session start time)
• User agent (such as browser family, major version, and device type)
• Geographical (country, region, etc.)
• Bandwidth (including kbps and bandwidth block)
• Custom metrics (for example, conversion and revenue)
• Custom dimensions (which can include store number, logged in status, or origin server)
• Third-party analytics (including Google, Adobe, and IBM Digital Analytics)
• Resource timing data (for example, startTime, dns_start, and dns_end)
• JavaScript error

Even if ​Akamai​ isn’t delivering your web traffic, you can still use mPulse to collect and analyze performance data. The workflow is pretty much the same, with a few minor exceptions. To start, you’ll need to create an mPulse app, then either manually place the mPulse snippet on your site’s pages at the origin server or use a tag manager for that task.