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/v29.2.1...v29.3.0
https://github.com/sitespeedio/sitespeed.io/compare/v29.2.0...v29.2.1
https://github.com/sitespeedio/sitespeed.io/compare/v29.1.3...v29.2.0
https://github.com/sitespeedio/sitespeed.io/compare/v29.1.2...v29.1.3
--platform linux/amd64
and in Docker desktop turn on "Use Rosetta for x86/amd64 emulation".https://github.com/sitespeedio/sitespeed.io/compare/v29.1.1...v29.1.2
https://github.com/sitespeedio/sitespeed.io/compare/v29.0.0...v29.1.0
The breaking changes in this release will not break anything, however some behaviours are changed in rare cases, please read:
Changed timestamp for Graphite/InfluxDB metrics/annotations. The old implementation used the start time for the test all metrics sent except browsertime.run metrics (data for each run). This fix changes so metrics (and annotations) uses the browsertime.pageSummary runTime (when the actual first iteration happen for a test). This makes more sense if you test multiple pages within the same test #3900.
When the slug concept was introduced in 17.0.0 also a bug was accidently added that add the domain as a slug if the slug was missing. As long as you added --slug
that was not a problem and you will not be affected by this bug. However if you do not use --slug
(you really should since 20.0.0) the slug portion would be automatically populated #3901.
--cpu
we will now also collect the number of elements that needs recalculate styles before FCP/LCP. There will be a blog post about this change later on.https://github.com/sitespeedio/sitespeed.io/compare/v28.1.0...v28.2.0
--graphite.proxyPath
to add extra proxy path to an annotation event in Graphite. Thank you Jonathan Goodman for PR #3893.https://github.com/sitespeedio/sitespeed.io/compare/v28.0.0...v28.1.0
There where a bug in how the browsertime.pageSummary
message was created where data was attached to the browserScript key (for example, the HAR file was attached to the element). This has been fixed and everything will work as before except if you have created your own plugin and listen to browsertime.pageSummary
messages and where using the faulty attached data.
The changes where done in #3888 and #3890.
https://github.com/sitespeedio/sitespeed.io/compare/v27.9.2...v27.9.3
https://github.com/sitespeedio/sitespeed.io/compare/v27.9.1...v27.9.2
https://github.com/sitespeedio/sitespeed.io/compare/v27.9.0...v27.9.1
https://github.com/sitespeedio/sitespeed.io/compare/v27.8.0...v27.9.0
https://github.com/sitespeedio/sitespeed.io/compare/v27.7.0...v27.8.0
https://github.com/sitespeedio/sitespeed.io/compare/v27.6.5...v27.7.0
https://github.com/sitespeedio/sitespeed.io/compare/v27.6.4...v27.6.5
https://github.com/sitespeedio/sitespeed.io/compare/v27.6.3...v27.6.4
https://github.com/sitespeedio/sitespeed.io/compare/v27.6.2...v27.6.3