You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+34Lines changed: 34 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -107,6 +107,40 @@ WebPageTest would test each run's First Contentful Paint. If the First Contentfu
107
107

108
108
109
109
The specs format provides tremendous flexiblity in which metrics you want to budget against. For more information, check out [the official documentation](https://github.com/marcelduran/webpagetest-api/wiki/Test-Specs).
110
+
111
+
### Testing against a deployment URL
112
+
If you are going to set and enforce performance budgets, **make sure to pass a preview URL** to test against to make sure that you're testing against the latest changes, not against a prior version of your site.
113
+
114
+
As an example, if you happen to be using a service like [Netlify](https://www.netlify.com/), they'll generate deploy previews for each PR. Here's an example of how you could run the WebPageTest action against the latest deploy preview using the [Wait for Netlify Action](https://github.com/JakePartusch/wait-for-netlify-action).
There are a _lot_ of [options available in WebPageTest](https://github.com/marcelduran/webpagetest-api#test-works-for-runtest-method-only) to customize your test results, record custom metrics, or do advanced scripting and multi-page flows.
0 commit comments