Track performance in GitHub, mark deploys with Netlify, CLI 3.0.0 and More

Profile photo of Karolina Szczur

Karolina Szczur

February 10, 2020

Release Notes is a monthly summary of new features and product improvements.

Integrate performance tracking into your developer workflow

Most performance and user experience issues are discovered when it’s already too late—long after they have already impacted your customers. Pull Request Reviews allows you to identify speed bottlenecks before they reach production, directly in your Pull Requests.

Pull Request Review performance report showcasing key metrics changes and pages tested.

If you’re using GitHub and one of the following deployment methods: Vercel (previously ZEIT), Heroku, Netlify or GitHub deployment statuses, you will be able to enable Pull Request Reviews and receive detailed performance reports on your work-in-progress. Read the announcement or learn how to get started.

Enable Deployment Tracking with Netlify

Previously, the only way to enable Deployment Tracking was to leverage the Node.js API, CLI or the HTTP Site API. You can now trigger Snapshots and add deployment markers to your charts with Netlify.

Generating credentials to enable a Netlify integration via a webhook.

You can enable the Netlify integration under Site → Settings → Integrations → Netlify → Add Webhook.

CLI 3.0.0

New major release of the CLI brings more functionality, customizability and better error handling. You can now:

  • add and manage tokens
  • get Agent Settings
  • create Sites with --schedule and --interval options
  • see relevant errors when trying to obtain data from a non-existing Snapshot

Read the full changelog or browse the API documentation.

See estimated savings on Lighthouse reports

When Lighthouse reports potential savings, you can now inspect their details to find out where exactly to look and how much time or bandwidth is there to be saved.

Example estimated savings for a request in the Performance Report.

New metric: Max Potential First Input Delay

Max Potential First Input Delay is calculated based on First Input Delay (FID). It portrays the maximum time it takes the browser to respond to a user action, such as clicking a button or trying to type something into a form. Max Potential FID can be used alongside Time to Interactive to quantify when your sites and apps can be successfully interacted with.

You can add Max Potential First Input Delay to the Pulse page through customising the Metric History view and set budgets against it.

Updated Performance Report median calculation

We updated our Performance Report calculations to give a better representation of the median scores across Test Profiles and Pages. Previously, a missing data point could skew the numbers significantly. Now, we calculate the median for each Page or Test Profile and generate an overall median based on granular results.

If you noticed slightly different results from week to week, this would be why.

Profile photo of Karolina Szczur

Karolina Szczur

Karolina is the Product Design Lead at Calibre. With years of design experience under her belt, she’s responsible for the comprehensive user experience spanning over product, visuals and content. Find her on Twitter or LinkedIn.

Related posts

Export your Data with Ease, Know How Fast Your Tests Run and More

Don’t miss another article

Be notified about new product features, releases and performance research.