WebPageTest Change Log
- September 17 Instead of exposing the Net Priority for requests, we now map that back to Chrome's Dev Tools priorities.
- September 16 The custom waterfall page has been refreshed to provide better visual hierarchy and update the waterfall dynamically as you make adjustments.
- August 30 WebPageTest now provides an "experiments" tab in the resource dialog to make it
easier to test the performance impact of requests on WebPageTest
- August 16 The API now provides a test balance endpoint to programmatically check your remaining API balance for the current billing period.
- August 10 All EC2 instances of the WebPageTest testing agents now use static IP addresses.
- July 20 Any render blocking resources are now indicated in the Waterfall with an orange icon, making it easier to zero-in on one of the most common performance bottlenecks.
- July 13 The waterfalls now treat HTTPS as the default experience instead of HTTP. This means HTTPS requests no longer show a lock icon. Instead, HTTP requests are actively marked as insecure, cleaning up the waterfall and making it easier to spot insecure requests at a glance.
- July 1 WebPageTest now has an option to use Chrome's built-in traffic shaping instead of the packet-level network shaping it normally uses. (Not recommended for normal testing.)
- June 30 The visual comparison page now has a compare all runs button that makes it easier to quickly see all runs of a given test so you can investigate variability.
- June 30 We added a new Web Vitals test. It provides all the same level detailed results as a normal test, but the form is greatly simplified and lands directly on the core web vitals diganostics page.
- June 1 If an image or background image triggers Largest Contentful Paint, the vitals page will now auto-highlight the request in the waterfall and display the image at full size to make it more obvious. The Total Blocking Time of the page now also shows the origins with the largest scripting-related CPU time and provides a quick link to the Chrome Developer Tools timeline for the test.
- May 25: Recalibrated the mobile CPU emulation throttling (Most devices needed around twice as much throttling).
- May 24: Updated the Wappalyzer engine and detections to the latest.
- May 24: %ORIGIN% can be used in your scripts.
- May 19: Fixed an issue where video capture may have terminated prematurely (at 30 seconds). Particularly noticeable when running SPOF comparison tests.
- May 17: WebPageTest custom metrics now can access the full accessibility tree in Chromium-based browsers using the $WPT_ACCESSIBILITY_TREE placeholder.
- May 13: The Cumulative Layout Shift section of the core web vitals page lets you hover over a thumbnail to see what content is moving and why.
- May 5: WebPageTest now has a core web vitals diagnostics page to help debug your core web vitals by exposing additional context and providing focused visualizations.
- May 3: The plot full results page now allows folks to force the graphs to start at zero (issue #1485) to help normalize for comparison (here's an example). We also now show metric tables for all tests on the graph results page, not just the first test (issue #1484).
- April 30: WebPageTest now defaults to using the
httpsprotocol if the protocol is left off a test URL.
- April 15: The mobile emulation devices are now also available directly in the browser dropdown for any locations that support testing with Chrome. It will use Chrome stable for the emulation. Emulating mobile with beta or canary is still possible by manually selecting the emulation options in the Chromium tab of advanced settings.
- April 14: Cumulative Layout Shift was updated to use the new windowed approach. The filmstrip also now shows layout window scores, and additional context is available in the JSON. PR #1478
- April 9: WebPageTest test results now pull in URL-specific field data from Chrome User Experience Report
- April 6: WebPageTest moved to a new account management system. The enhanced and fully supported WebPageTest API was released to general availability.
- March 23, 2021: The default desktop browser size was changed from 1024x768 to 1376x768. A dropdown was added to choose from a number of other resolution sizes.
- March 22, 2021: First Contentful Paint, Largest Contentful Paint and Layout Shifts were added to the WebPageTest waterfall
- March 22, 2021: A new interface for WebPageTest.org was released
- February 15, 2021: When test agents are terminated (during OS shutdown for example), re-queue the test they are working on for another agent to test. This helps with support for autoscaling cloud agents so jobs are not lost when agents are terminated.
- January 28, 2021: Added support for testing Safari with the iOS simulator on Intel and Apple silicon Macs.
- January 25, 2021: Added test options for disabling AVIF and WebP support in Chrome for testing impact of the new formats on performance.
- January 6, 2021: Added Largest Contentful Paint visualizations to the filmstrip view.
- December 12, 2020: Changed video rendering to be done on the fly and added support for generating animated Gifs.
- November 30, 2020: Added layout shift visualizations to the filmstrip view.
- November 13, 2020: Added support for testing WebKit on Linux.
- November 4, 2020: Mobile emulation user agent strings were changed to always be up to date with the version of Chrome that they are running on.