Skip to content

Releases: sitespeedio/browsertime

v5.2.2

11 Jun 13:15
Compare
Choose a tag to compare
  • Use a tracium version that do not throw errors if the trace is not correct (#856) 3b5d268

v5.2.1...v5.2.2

v5.2.1

10 Jun 09:37
Compare
Choose a tag to compare
  • Include last 50 pixel when checking for orange. (#854) 4b38ac1
  • Remove automation switch to fix the removal of disable infobars (#853) be6cc6f

v5.2.0...v5.2.1

v5.2.0

07 Jun 19:32
Compare
Choose a tag to compare
  • Use Chrome 75 (and Firefox 67.0.1 in the Docker container) (#852) 7e3fffd
  • make it easy to enable screenshots in the trace log (#851) 02bd86a
  • Trying to fix the Chrome trace log missing Timings when you drag/drop… (#850) ea52d2f
  • Collect last meaningful paint (#848) 56cd644

v5.1.3...v5.2.0

v5.1.3

31 May 14:46
Compare
Choose a tag to compare
  • Use default Selenium 3.6 and use cyrus-and/chrome-remote-interface fo… (#846) 0d1830c
  • upgraded dayjs 2f7aeb4

v5.1.2...v5.1.3

v5.1.2

29 May 08:32
Compare
Choose a tag to compare

v5.1.1...v5.1.2

v5.1.1

27 May 18:35
Compare
Choose a tag to compare
  • Include HTML in the response for Chrome HAR included object instead of plain text (#842) 78e506c

v5.1.0...v5.1.1

v5.1.0

27 May 12:44
Compare
Choose a tag to compare

v5.0.0...v5.1.0

v5.0.0

16 May 18:15
Compare
Choose a tag to compare

Changed

  • Replaced Chrome-trace with Tracium in #816. This means we use a Chrome blessed parser that will mean less work for us within the team! Enable it with --chrome.timeline. It also means two changes:
  • We skipped reporting all internal events inside of Chrome and only report events that takes more than 10 ms. We do this because it makes it easier to understand which events actually takes time and are useful.
  • Instead of reporting: Loading, Painting, Rendering, Scripting and Other we now report the same categories as Tracium: parseHTML, styleLayout, paintCompositeRender, scriptParseCompile, scriptEvaluation, garbageCollection and other. This gives you a little more insights of CPU time spent.
  • We collect more trace log than before (following Lighthouse, the trace log will be larger on disk), this makes it easier for you when you want to debug problems.

Added

  • Collect CPU long tasks in Chrome using --chrome.collectLongTasks using the Long Task API. For the long tasks to work, we inject JS using the Page.addScriptToEvaluateOnNewDocument devtools command. We collect all long tasks and related data (not so much at the moment but will get better/more useful information when browsers supports it) and count the total number of long tasks, long tasks that happens before first paint and first contentful paint. Implemented in #821 and #825.

  • By default a long task is >50ms. Wanna change that? Use --minLongTaskLength to set that yourselves (it needs to be larger than 50 ms though) #838.

  • Throttle the CPU using Chrome with --chrome.CPUThrottlingRate. Enables CPU throttling to emulate slow CPUs. Throttling rate as a slowdown factor (1 is no throttle, 2 is 2x slowdown, etc). Implemented in #819.

  • You can now use a .browsertime.json file as a default config json file that will be picked up automatically #824.

  • Include the actual HTML in the HAR file for Chrome using --chrome.includeResponseBodies html #826

  • Use --blockDomainsExcept to block all domains except. Use it muliple times to have multiple domains. You can also use wildcard like *.sitespeed.io #840

  • Shortcut --cpu to enable --chrome.timeline and --chrome.collectLongTasks for Chrome #839.

Fixed

  • Bumped all dependencies that needed a bump #817.

v4.9.2

25 Apr 22:20
Compare
Choose a tag to compare

v4.9.1...v4.9.2

v4.9.1

24 Apr 08:03
Compare
Choose a tag to compare

v4.9.0...v4.9.1