PageVitals provides website performance monitoring, synthetic testing, real-user monitoring reports, performance budgets, and optimization insights.
Add one or more explicitly supplied pages to PageVitals monitoring for a website. This persistent bulk operation can consume monitored-page quota and cause future synthetic tests, so call it only when the user explicitly requests every URL or path and alias. Never discover or scrape pages automatically.
Create a persistent PageVitals performance budget for a website. This changes monitoring and may change owner alerting behavior, so call only when the user explicitly requests the budget and supplies the complete metric, comparison direction, numeric threshold in the metric's native unit, and device scope. Never infer metric units or operator direction.
Create an empty PageVitals multistep test definition with an explicit name and device profile. This only saves persistent configuration: it does not run the test, trigger any synthetic checks, or consume test-run quota.
Add a domain to the PageVitals account and begin managing it. This may consume website quota and start monitoring, so call only when the user explicitly asks to add the domain.
Delete one PageVitals performance budget and stop enforcing its threshold. This is a destructive alerting mutation; use only when the user explicitly selects the exact budget ID for deletion.
Permanently delete one PageVitals configured page and all of its test results, including historical results. This is irreversible; use only for an explicit request naming the exact website ID and configured-page ID.
Permanently delete one PageVitals multistep test definition. This is irreversible; use only when the user explicitly identifies the exact website ID and test ID.
Permanently delete one PageVitals website and all of its tests, metrics, analytics, and configuration. This is irreversible; use only for an explicit request naming the exact website ID.
Get one multistep test definition, including its configured steps.
Get the latest Lighthouse and Chrome UX metrics for one configured page and device.
List Lighthouse improvement opportunities for a page/device, or return the full variable-shape details for one opportunity ID.
Get one historical timeline for a page/device: combined loading metrics, CrUX, network bytes, CPU time, or Google Search performance. Google Search requires that integration on the website.
Get the detailed Lighthouse, timing, resource, budget, and validation summary for one synthetic test. Provider values, nulls, metric scales, and JSON-looking strings are returned unchanged.
Get one specialized synthetic-test report: keyed Lighthouse opportunities, the request waterfall, or grouped HTML validation findings. Validation always omits the embedded raw HTML.
Get one synthetic test series and its individual tests, statuses, page IDs, device variants, and failure messages.
List performance budgets, current status, notification settings, and affected pages for a website.
List the raw pages configured for PageVitals monitoring on a website.
List historical runs for one multistep test, including status, duration, interaction, layout-shift, CPU, transfer-size, and blocking-time metrics.
List multistep tests configured for a website with recent metrics, state, and success rates. A website with no configured multistep tests returns an empty tests list.
List every configured page/device combination for a website with recent timeline and latest performance metrics.
List recent synthetic test series for a website, including status and failure counts.
List Lighthouse improvement opportunities aggregated across a website and the affected pages.
List websites visible to the connected PageVitals API key. Use the returned website IDs with all website-scoped tools.
Trigger exactly one named multistep test or intentionally fan out to every multistep test configured for a website. Every triggered run consumes PageVitals test quota and may incur cost. Choosing target='all' can start many jobs, so use it only when the user explicitly requests an all-tests run.
Trigger synthetic tests for selected page/device variants, or for every configured test when pages is omitted. This action consumes PageVitals test quota and may incur cost; call it only when the user explicitly requests a new run.
Replace a PageVitals performance budget's complete metric threshold and device scope. This may change monitoring alerts or notifications. Read the current budget first, use its exact website and budget IDs, and provide all four desired state fields because partial PUT behavior was not safely tested.
Update a configured PageVitals page's URL, display alias, or both. This changes persistent monitoring configuration; use the exact page ID from List Configured Pages and provide at least one new value.
Update a multistep test's alias and device. Both fields are required because PageVitals PUT replacement and partial-update semantics were not safely live-tested; read the current test first when preserving either value.
The PageVitals integration connects your Dench AI CRM directly to PageVitals, so agents can read and act on your PageVitals data as part of everyday work — answering questions in chat, keeping your CRM in sync, and running automations without anyone copying data between tools.
28 actions are available for agents to invoke on your behalf. Every call runs through PageVitals's own authorization, scoped to the account you connect.
Sign in to your Dench workspace and open Integrations.
Find PageVitals and click Connect — you'll authorize access through PageVitals's own sign-in flow. No API keys or code required.
Ask an agent to use PageVitals in chat, or call it from an automation.
Manage or disconnect the connection any time from workspace settings.
The Dench PageVitals integration connects your AI CRM to PageVitals, so AI agents can work with your PageVitals data as part of chats, automations, and CRM workflows. You connect your account once, and every agent in your workspace can use it — governed by your workspace permissions.
The PageVitals integration currently exposes 28 actions, including Add Configured Pages, Create Budget, Create Multistep Test, Create Website, Delete Budget, and Delete Configured Page. Agents invoke them on your behalf from chat or from automations.
No. You connect PageVitals from your Dench workspace using PageVitals's own sign-in and authorization flow — no API keys to copy, no glue code to maintain.
Connections are authorized through PageVitals's own authentication flow, and Dench stores only the authorization needed to act on your behalf. You can review and disconnect the PageVitals connection from your workspace settings at any time.