Sitespeed.io 2.1 release notes

This release focus on one thing: Break builds for Jenkins and Travis-CI if your browser Navigation Timing API metrics doesn't meet your limits.

Break builds if your pages are too slow

Configure the limits for your pages and break builds if the timings are higher than your configuration. You can use the timings in the Navigation Timing API or create your own custom timings. Choose how many times you want to test the page and use the median or different percentile values. Read more about it here.

Keep track of your timings

Using Jenkins you can easily create graphs of your browser timings. They look like they are from the 1980's but it's quite nice info (btw nicer graphs will come in later releases)!

Use sitespeed.io in your projects with Travis-CI

Drop the latest sitespeed.io release in your project, configure the Travis config file and break the build if it doesn't meet your limits. Checkout the example project on GitHub. Now you can break builds if you break your web performance best practices rules or if you exceed your timing limits. Read more about the Travis-CI integration.

Minor changes

  • Prepared for HTTP 2.0 rules & renamed the current rulesets. The new names: sitespeed.io-desktop & sitespeed.io-mobile
  • Better error handling: Output the input parameters to the error.log file so it is easy to reproduce the error. Also centralized the error logging
  • Made it possible to analyse sites with non signed certificates
  • Finetuned the logo
  • Bug fix: The crawler sometimes picked up URL:s linking to other content types than HTML (if you have linked to an image)
  • Bug fix: The JUnit XSLT outputted timings metrics
r>

See the changelog for changes done in the past.