v8.6.4

Fixed

• When sending annotations with --graphite.annotationMessage and not providing a screenshot the message and the extraMessage used to get concatenated without any space. Thank you Markus Liljedahl for the PR #2332 that fixes that.

• Better error messages when sending data to Grafana. Thank you again Markus Liljedahl #2334.

• Waterfall chart had colliding texts, the font is now slightly smaller #2345.

v8.6.3

• Upgraded to Browsertime 4.4.7 with fix for better finding last visual change in the video.

v8.6.2

• Upgraded to Browsertime 4.4.6 that adds better error handling if your multi script is broken or if a URL fails to load.

v8.6.1

Fixed

• Upgraded to Browsertime 4.4.5 that changed so that 0.05% of the pixels could differ (instead of 0.01%) when finding the last visual change.

• Removed the Chrome specific setup in Chrome that was needed a long time ago #2322

8.6.0

Fixed

• Show larger screenshots in filmstrip for mobile, fixing colliding metrics HTML and last screenshot showing twice #2314.

• Fix wrong count for errors/warnings for console log send to Graphite/InfluxDB. Before we sent 1 instead of the actual number of logs per page #2316.

• Fix coach table colouring. Thank you Ferdinand Holzer for the PR #2317!

• Removed faulty guard in budget that made sure only internal metrics worked for Lighthouse/GPSI/WebPageTest.

• New Browsertime versions that fixes:

  • If a Visual Element wasn't found, we used to log that as an error, instead log as info #775.
  • When trying to find the last visual change, a 0.01 % difference in pixels are now OK. We had problems finding too small difference that was picked up by Visual Metrics #774.

Added

• Send console warnings by default to Graphite/InfluxDB per page (we used to only send errors by default) [#2315]-(#2315).

• Support for crawler exclude pattern, use --crawler.exclude. Thank you Ferdinand Holzer for the PR #2319.

Sitespeed.io 3.0.2

• fixes in the YSlow script so that some pages that fails, will work #549

Sitespeed.io 3.0.1

• Add experimental support for running yslow in SlimerJS #544
• Fix Google PageSpeed Insights that broke in 3.0 #545
• Better logs when screenshot fails and increased timeout to 2 minutes
• Upgraded to new Crawler with higher default timeout times #547
• Added parameter to configure which phantomjs version to use (--phantomjsPath)

Sitespeed.io 3.0.0

Yep, so we finally released 3.0!

• We moved (almost) everything to nodejs. We are still dependent on Java, because the (old) Java crawler is still used but now when there are nodejs crawlers that almost can do the job, we will aim to change it in coming 3.1 or 3.2.
• Support for PhantomJS 2. Yep we know, 2.0 is not released yet and we are really looking forward to it, so we added the functionality to use it already. What's extra cool with 2.0 (except that it is much faster) is that it supports the Navigation Timing API. We can get better timings just using PhantomJS
• We have rewritten BrowserTime to nodejs, and it now supports running whatever javascript snippet you want, meaning you can fetch whatever metric you want. It is not fully implemented yet in sitespeed.io, but with the current version it gives us Pat Meenans RUM SpeedIndex and support for getting resource timing API metrics.
• PostTask - when sitespeed.io has analyzed all pages and collected all metrics, you can run your own code to handle the result. This can be used to store the data in a database or create your own output.
• Send metrics to Graphite - one of the number one feature requests for sitespeed.io has been to collect data over time and graph it. Sitespeed.io now supports sending the metrics to Graphite and then you should use Grafana or other nice tools to build the Graphs. It can looks something like this
• Drive WebPageTest - you can now feed WebPageTest with URL:s to test and collect the metrics and include them in your sitespeed.io report.

Sitespeed.io 3.0.0-alpha

This is an early release of 3.0.

• The main goal with 3.0 has been to move to NodeJS. The crawler & BrowserTime still uses Java and we will try to move away from that in the future
• We use Handlebars templates (instead of the old Velocity ones).
• All data is JSON instead of XML as it was before.
• Drive/get/collect data from WebPageTest & Google Page Speed Insights
• HAR-files created from the browser you use when fetching Navigation Timing API metrics
• Generate JUnit XML files and/or send data to Graphite; now included as main functionality.
• Support for getting Navigation Timing data from PhantomJS 2.0
• Two new result pages: Slowest domains and Toplist (with information about assets). More info will come
• We use Handlebars templates (instead of the old Velocity ones).
• Yep, hate to say it but the parameters to the CLI has changed, so please check --help to see how you should do

Sitespeed.io 2.5.7

Here comes 2.5.7 with some bug fixes & tweaks:

• Upgraded to YSlow 3.1.8 (with configurable CDN)
• Added support for Basic Auth (only missing in Browser Time right now, meaning you can't use Basic Auth to get timings)
• Turned on CDN rule and made it possibly to supply CDN domains
• Added new crawler that solves problem when the crawler picked up URLs with wrong domain, thanks @ChrisSoutham
• Updated support for catching lazy loaded assests in YSlow/PhantomJS, thanks @dorajistyle
• Show the 90 percentile value for all timing metrics on the individual pages #380
• Mobile rules changed: Doc size max 14 kb and max server side 200 ms for Green
• Summary: Show max number of request per domain #384
• Summary: Show number of redirects per page #385
• The avoid scaled images rules has been changed: If the image is larger than X (100 pixels by default) the rule will kick in.
• The sitespeed.io-sites script now uses firstPaint as default if you use IE or Chrome, supports local config file & uses maxRequestsPerDomain
  as default column instead of max requests per domain #387
• DNSLookup hurts more than CSS requests in points for Critical Path Rule #392
• Bug fix: If an error happens when crawling, log that to the error.log #378
• Bug fix: User defined measurements get Velocity code as description #366
• Bug fix: Show one decimal for time metrics on pages #363
• Bug fix: Connect via any SSL protocol #379 thanks @tollmanz
• Kind of a bug fix: The crawler can now handle a href tags with a line break instead of space between the a & the href