Read More The Web Platform Baseline project aims to track when exactly Web features became available in all major browsers (Chrome, Edge, Firefox, Safari). This is important since not all browsers implement all features at the same time; using cutting edge feature X on browser A might mean you leave some of your users on browser B out in the cold (or having to implement a costly fallback).However, you also don't want to only use features from Baseline 2017, "just to be safe", because that would mean missing out on many already widely available features. In practice, you want to utilize features that almost all of your users will benefit from.To help you figure out which features those are and which Baseline year you should target, the RUM Archive Insights has added a Baseline section outlining how RUM data intersects with Baseline features. Supported percentages are of observed Desktop and Mobile RUM Archive traffic on the first Tuesday of April 2024 that had support for ALL the featur

Read More Latest mPulse RUM Data LoadedWe've completed an export of mPulse daily RUM data into the BigQuery akamai-mpulse-rumarchive project up through 2024-04-30.This brings the RUM Archive's mPulse dataset to a running total of 617 straight days of data available since 2022-09-01. (There is also first-of-month data going back to 2021-10-01).Minor Versions for Safarai, iOSFrom 2024-04-01 onward, the USERAGENTVERSION and OSVERSION columns now contain the Minor version information for a subset of browsers and operating systems. For example, you'll see rows with user agent version of 17.5 for Safari instead of just 17.Both the mPulse Page Load and Third-Party Resource tables now include minor version numbers for the following browsers:SafariMobile SafariMobile Safari UI/WKWebViewIn addition, the mPulse Page Load and Third-Party Resource tables now include minor version numbers for the following operating systems:iOSiPadOSAll other browsers and operating systems will continue to only cont

Watch on youtube.com

Watch on youtube.com

Read More We're excited to announce a preview of a new type of data available in the RUM Archive: Third-Party ResourcesAt mPulse, we are using boomerang.js to capture RUM data. Boomerang uses the ResourceTiming API to gather data about all of the sub-resource fetches on the page (such as JavaScript, CSS, images, etc) for every Page Load beacon. This data is compressed and beaconed to mPulse for analytics purposes.From this data, viewed in aggregate across all of our customers, we can easily spot common third-party components such as:Tag Managers (Google Tag Manager, GTag)Analytics (Google Analytics, mPulse)Widgets (Pinterest, Twitter, Bazaar Voice, Youtube)Fonts (Google Fonts)Beacons (Meta Pixel, mPulse, Google Analytics, Doubleclick)Ads (Google, Amazon, Criteo)Libraries: (jQuery)For this new table, we're going to begin exporting the Top 500+ third-party resources we see each day, similar to how we share Page Load data. Each third-party resource URL will have information on its popular

Read More RUM Insights are now available!For this past year, the RUM Archive website has mainly been a README with instructions on how to query the archive's database yourself and how to interpret the results.However, we recognize that setting this up yourself can be a big technical (and financial) hurdle to using the wealth of data the archive contains.As such, we now also provide RUM Insights: a collection of pre-made visualizations and diagrams for results from typical queries you might want to run against the database! These visualizations will be refreshed monthly with the latest data, to make sure you always have the freshest data to work from.We will focus on showing data that makes the RUM Archive unique: insights about how real users visit pages, about how Web platform features are used in the wild and how this impacts real-world performance for a distributed audience.At this time, the available visualizations are still somewhat limited in number, but we intend to expand upon

Read More The RUM Archive was released about a year ago during the performance.now() 2022 conference in Amsterdam! Let's review what's happened with the project over the last year, and then we can share some exciting new features we're adding.First, a few notes on our October data release.Latest mPulse RUM Data LoadedWe've completed an export of mPulse daily RUM data into the BigQuery akamai-mpulse-rumarchive project up through 2023-10-31.This brings the RUM Archive's mPulse dataset to a running total of 425 straight days of data available since 2022-09-01. (There is also first-of-month data going back to 2021-10-01).We plan to continue this daily export of the mPulse RUM data for the forseeable future. Right now, we're updating the BigQuery tables roughly on a monthly cadence, where we release the previous month's data by the first few days of the next month. We plan on automating this process further so that we can upload data on a daily cadence.RUM Archive Data In the WildOne of our

Read More Latest mPulse RUM Data LoadedWe've completed an export of mPulse daily RUM data into the BigQuery akamai-mpulse-rumarchive project up through 2023-09-30.This brings the RUM Archive's mPulse dataset to a running total of 394 straight days of data available since 2022-09-01. (There is also first-of-month data going back to 2021-10-01).Interaction to Next Paint (INP) DataFrom 2023-09-01 onward, Interaction to Next Paint (INP) measurements are now in the mPulse RUM data, as part of the following columns:INPHISTOGRAM (JSON): HistogramINPAVG (FLOAT64): Weighted averageINPSUMLN (FLOAT64): Sum of the natural logarithmsINPCOUNT (INTEGER): Number of measurements takenAt this time, INP data will not be as common as other timers such as Page Load Time (PLT*) or even First Input Delay (FID*), as capturing the INP measurement requires mPulse customers to be on a recent (1.766+) version of boomerang.Let's review the current rate of INP data vs. something like FID:SELECT SUM(BEACONS) AS BEAC

Read More Latest mPulse RUM Data LoadedWe've completed an export of mPulse daily RUM data into the BigQuery akamai-mpulse-rumarchive project up through 2023-02-28.This brings the RUM Archive's mPulse dataset to a running total of 180 straight days of data available since 2022-09-01. (There is also first-of-month data going back to 2021-10-01).We have plans to automate this process so that the mPulse RUM data is added on a weekly or daily cadence, but it is currently a manual process that we do at the end of each month. We are currently able to release each new month's data within a few days of the end of the month.Breaking Change to rageClicksHistogramStarting with the RUM Archive's mPulse dataset from 2023-01-01, there is a breaking change to the rageClicksHistogram column.For mPulse RUM data from 2021-10-01 through 2022-12-31, the column rageClicksHistogram had histogram bucket numbers off-by-one from what was intended.For review, all of the other Timers' histograms like PLT, DNS, et

Watch on youtube.com

Read More The Akamai mPulse team studies Real User Monitoring (RUM) data to help our customers understand how to optimize website performance and how user behavior may be altered by changes to configurations or resource requests on their site. As a data scientist on the mPulse team, I search for patterns in our data and identify problem areas on customer websites in order to recommend actionable improvements toward the end user experience.Typically, I work with a specific customer’s dataset at any given time. However, there are cases where it is more appropriate to use an anonymized, aggregated dataset across many customers in order to investigate a change or patterns occurring across the web.For example, we may want to measure the responsiveness of different types of devices[1], or perhaps geographic differences in patience waiting for a page to load[2]. Alternatively, we may want to validate an outage for a specific geographic region[3]. My colleagues and I at Akamai are afforded the

Read More A few weeks ago at performance.now(), we were able to announce the initial availability of a new public dataset of RUM data - the RUM Archive.I'd like to take a few minutes to discuss our motivation for the project, what kind of data the RUM Archive contains, how you can access it, its limitations, and some ideas for what it could be used for.Why have a RUM Archive?The RUM Archive is heavily inspired by projects like the Wayback Machine, the HTTP Archive, and the Chrome UX Report (CrUX).Those projects have lead the way in being fantastic community-lead efforts that help share and preserve the history of the web and web performance.We hope the RUM Archive will be a good compliment to those projects. While the HTTP Archive focuses on metrics captured from synthetic crawls, and CrUX draws its RUM data from Chrome navigations across the globe, the RUM Archive offers another view of RUM data, and one that is across all browsers.Our aim is to have RUM data available for researchers