Sitespeed.io Versions Save

Added

• Updated to Chrome 124 and Firefox 125 in the Docker container #4142 and #4142.

Fixed

• Add new tag: axeType for axe data in InfluxDB #4139. Before the fix there was no way to query some of the Axe data.

https://github.com/sitespeedio/sitespeed.io/compare/v33.5.0...v33.6.0

Added

• Chrome 123, Firefox 124 and Edge 122 in the Docker container #4114.
• Browsertime 21.6.0 with updated Chrome/Edgedriver and a fix for runnin .stopAsError.

https://github.com/sitespeedio/sitespeed.io/compare/v33.3.0...v33.4.0

Added

• Show Long Animation frames (enabled in Chrome 123) #4180. Using the timeline/profiling is still best doing your tests but long animation frames can help you if you do not have it turned on or familiar with thart data in RUM. Please create an issue if you have any ideas on how we shoudl display the metrics/information!
• Show CPU power consumption (when using Firefox) #4104. You can try it with: sitespeed.io -b firefox -n 1 --firefox.geckoProfiler --firefox.geckoProfilerParams.features "power" --firefox.powerConsumption https://www.sitespeed.io/

Fixed

• Updated to Browsertime 21.5.3 containing various bug fixes.

https://github.com/sitespeedio/sitespeed.io/compare/v33.2.0...v33.3.0

Added

• Updated to Browsertime 21.5.0 in #4103 also included changes released in 21.4.0.
  • Firefox:
    • Move injectJS functionality to Bidi #2088. This makes it possible to inject JS in Firefox on mobile.
    • Expose Bidi in commands #2091. You can now use webdriver bidi direct in your commands.
  • Fixed command action.clear() that actually didn't clear the command #2095.
  • Added the following trace categories for Chrome that now is used by default when you turn on the timeline: 'disabled-by-default-devtools.timeline.frame', 'disabled-by-default-devtools.timeline.invalidationTracking','loading', 'latencyInfo' - done in #2086.
  • Added a simple Loaf-script to get the 10 largest loaf. Lets iterate over the script and see how we can get the most useful information from it #2087.

https://github.com/sitespeedio/sitespeed.io/compare/v33.1.1...v33.2.0

Fixed

• Updateds to Browsertime 21.3.1 that has an updated version of the Chromedriver isntaller that fixes the bug installing on Windows #4096.

https://github.com/sitespeedio/sitespeed.io/compare/v33.1.0...v33.1.1

Added

• Firefox 123 and Chrome 122 in the Docker container #4090 and #4089.
• Chromedriver 122 and Edgedriver 121
• Browsertime 21.3.0.

Announcement: In the next major release we will remove all support for WebPageTest. If you still plan to use WebPageTest you can probaly still use the plugin for a while if your WebPageTest installation works.

Breaking

This is a breaking change if you use the compare plugin and do not set an id (--compare.id) for your test.

• If you auto generate the id for your compare test, this PR add browser, connectivity name and slug to the file name where the compare metrics is stored #4083.

Added

• Updated to Browsertime 21.2.0 that adds a new way to stop your measureemnts if your navigation fails measure.stopAsError(failureMessage, optionalURL). Perfect to use in a try/catch.
• Use darkmode for result HTML by adding --html.darkMode, thank you petemyron for PR #4081.

Fixed

• Update co2.js to 0.14.2 #4074
• More solid error handling if one page fail in scripting. This fixes so that the HTML for the rest of pages should be generated #4079.
• Remove console.errors of errors (they have already been reported in the log) #4080.
• Fix automatically switch to Throttle as engine on Mac and Linux if you add -c THROTTLING#4082.

Added

• Chrome and Chromedriver 121 in the Docker container #4069.
• Browsertime 21.1.0 #4070.

https://github.com/sitespeedio/sitespeed.io/compare/v32.1.0...v32.2.0

Added

• Updated the WebPageReplay version in the Docker container #4067.
• Firefox 122 in the Docker container #4068.

https://github.com/sitespeedio/sitespeed.io/compare/v32.0.0...v32.1.0

Breaking change

• If you use the compare plugin (--compare.saveBaseline) you need to remove your old baseline when you upgrade. The reason is that the original implementation was very narrow to some Browsertime metrics. The new version will be able to show more information (more metrics) between the baseline and the current test. This version allo disables comparing the CDP performance metrics, making the compare page easier to understand #4064.

https://github.com/sitespeedio/sitespeed.io/compare/v31.2.1...v32.0.0