sitespeed.io

Fixed

• Update to Pug 3.0.3 #4172.

https://github.com/sitespeedio/sitespeed.io/compare/v34.0.1...v34.0.2

Fixed

• The +1 container has updated to code to take care of if GPSI is missing metrics GPSI #56.

https://github.com/sitespeedio/sitespeed.io/compare/v34.0.0...v34.0.1

Breaking

• Woho! There's now a way to deploy your own version of sitespeed.io online for your own testing using [onlinetest)[https://github.com/sitespeedio/onlinetest]! It has a HTML GUI and an API that you can use using sitespeed.io command line. There's one server part (the frontend and the API) and a testrunner part. You can run desktop, emulated mobile and Android test. I do not host a global version but I worked hard to make it easy to host yourself. I still work on the documentation but feel free to start to try it out before all documentation is finished :) If you have quick question and need help, please use the Slack channel. If you have more complicated problems, please feel free to create issues here.

• With this release we remove all dependencies to WebPageTest #4085. You are only affected if you used the plugin-webpagetest or the +webpagetest Docker container. If you still want to use WebPageTest with sitespeed.io you can build something on the archived plugin-webpagetest.

• The S3 plugin has been upgraded to @aws-sdk/client-s3 v3 #4138. If you are using the S3 plugin and not set region, that will now fail. The v2 version of the aws-sdk used us-east-1 region as default, but v3 has removed the default setting. If you didn't used to set region you can add --s3.region us-east-1 and it will work as before. If you do not do that, the uploads to S3 will fail.

• The -plus1 Docker container now has plugin-lighthouse and plugin-gpsi installed from npm instead of the git repository. It will work as before, but if you want to disable one of them, that has changed. To not run the GPSI plugin add --plugins.remove @sitespeed.io/plugin-gpsi and to disble Lighthouse you add --plugins.remove @sitespeed.io/plugin-lighthouse.

• Updated to Browsertime 22. This version of Browsertime drops the Browsertime extension and start use the kind of new HAR exporter using Bidi as the default HAR exporter! If you add request headers to your Firefox test or clear the cache inside of your script using Firefox, this will stop to work for now until support is added in Firefox (request headers are coming soon!).

Added

• Updated to Chrome 125, Firefox 126 and Edge 124 in the Docker container #4156.

Fixed

• Fix loading globally installed plugins #4167.
• Fix configurations documentation for scp, thank you Arash Hatam for #4166.

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

Fixed

• Another fix for --budget.suppressExitCode hopefully it works better this time #4065.

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

Fixed

• There was bug that caused budget.suppressExitCode to fail that I introduced and reported in #4062. It's fixed in #4063.

Added

• Collect statstics about how the page is built between runs. You can see these metrics on the "side by side"-page #4061.

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

Fixed

• When displaying interaction to next paint, there where some copy/paste from largest contentful paint that sometimes broke the HTML (my fault). Fixed in #4042.

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

We updated the scripting documentation to be generated directly from Browsertime (using JSDoc). This makes the documentation so much easier to navigate. It's not 100% perfect yet so please feel free to send PRs with updates :)

The new version of Browsertime also adds code completion/IntelliSense support. Read here on how to set it up. Make sure to start your scripting like this:

/**
 * @param {import('browsertime').BrowsertimeContext} context
 * @param {import('browsertime').BrowsertimeCommands} commands
 */
export default async function (context, commands) { 
 
};

Added

• Update to Browsertime 21.0.0:
  • Upgraded to Geckodriver 0.34.0 #2049.
  • Collect CPU consumption for Firefox. Turn that on with --firefox.powerConsumption true and including power as a geckoProfilerParams.features #2046.
  • Added more commands for mouse click on text #2054.
  • Updated AndroidCommand so you can run shell on your Android device as root #2055.
  • If you mark a test as failure, the exit code from Browsertime will be 1. If the exitCode is set in scripting, we use that and will not change that #2057.
  • Generate documentation for scripting using JSDoc #2059.
  • Make it easy to use Seleniums action API. Get access to the new command using commands.action.getActions() and chain the action. #2061
  • Make sure the visual metrics files are inlcuded in the Docker file #2053.
  • Removing QVH from the npm package (used for iPhone video recording but not working) #2051
  • Removing visual metrics test images from the npm package #2050.
  • Removed the Chromedriver fix that was needed when Chrome for testing broke testing on Chrome :D #2045.
  • Refactor of commands/context object to prepare for supporting JSDoc and a little TypeScript to add code completion/IntelliSense in editors #2047.
  • Updated documentation for scripting with better JSDoc #204.
  • The code for getting Interaction to next paint was broken. This PR fixes it, make the code cleaner and gives more attribution #2060.
• If you use process.exitCode in your scripting, it will be respected by sitespeed.io and exit with that exit code #4044.

Fixed

• If a run is markedAsFailure in your Browsertime script, sitespeed.io exits with an error code #4047.

Fixed

• Hopefully removing "rsd" metrics in InfluxDB see #4039.
• Fix showing sustainable metrics in pages page #4042.

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

Breaking

• Updated to Browsertime 20. The new version of Browsertime renames --userTimingWhitelist to --userTimingAllowList so if you use that functionality you need to change the name before you upgrade!

Fixed

• The new version of Browsertime also fix the bug in Firefox 121 on Mac so you can start it.

https://github.com/sitespeedio/sitespeed.io/compare/v30.11.0...v31.0.0

Fixed

• Moved functionality from co2 to sitespeed.io see #4034.

Added

• Upgraded the Docker container to use Firefox 121 #4033.
• Updated to Browsertime 19.3.0 #4031.

https://github.com/sitespeedio/sitespeed.io/compare/v30.10.0...v30.11.0