sitespeed.io is an open-source tool for comprehensive web performance analysis, enabling you to test, monitor, and optimize your website’s speed using real browsers in various environments.
MIT License
Bot releases are visible (Hide)
https://github.com/sitespeedio/sitespeed.io/compare/v34.0.1...v34.0.2
https://github.com/sitespeedio/sitespeed.io/compare/v34.0.0...v34.0.1
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!).
https://github.com/sitespeedio/sitespeed.io/compare/v33.5.0...v33.6.0
https://github.com/sitespeedio/sitespeed.io/compare/v33.3.0...v33.4.0
sitespeed.io -b firefox -n 1 --firefox.geckoProfiler --firefox.geckoProfilerParams.features "power" --firefox.powerConsumption https://www.sitespeed.io/
https://github.com/sitespeedio/sitespeed.io/compare/v33.2.0...v33.3.0
https://github.com/sitespeedio/sitespeed.io/compare/v33.1.1...v33.2.0
https://github.com/sitespeedio/sitespeed.io/compare/v33.1.0...v33.1.1
Published by soulgalore 8 months ago
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.
This is a breaking change if you use the compare plugin and do not set an id (--compare.id
) for your test.
measure.stopAsError(failureMessage, optionalURL)
. Perfect to use in a try/catch.--html.darkMode
, thank you petemyron for PR #4081.https://github.com/sitespeedio/sitespeed.io/compare/v32.0.0...v32.1.0
--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
--budget.suppressExitCode
hopefully it works better this time #4065.https://github.com/sitespeedio/sitespeed.io/compare/v31.2.0...v31.2.1
https://github.com/sitespeedio/sitespeed.io/compare/v31.1.1...v31.2.0
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) {
};
--firefox.powerConsumption true
and including power
as a geckoProfilerParams.features #2046.process.exitCode
in your scripting, it will be respected by sitespeed.io and exit with that exit code #4044.https://github.com/sitespeedio/sitespeed.io/compare/v31.0.0...v31.0.1
--userTimingWhitelist
to --userTimingAllowList
so if you use that functionality you need to change the name before you upgrade!https://github.com/sitespeedio/sitespeed.io/compare/v30.11.0...v31.0.0
https://github.com/sitespeedio/sitespeed.io/compare/v30.10.0...v30.11.0