GTmetrix
for LuumenAI
Read GTmetrix reports for context, then rerun tests as approved steps
Connect GTmetrix and Luumen can read your monitored pages, their report history, and the resources behind each run — screenshots, HAR files, Lighthouse JSON. When you need fresh numbers after a deploy, it starts or retests a page using the same location, browser, and device settings, and shows you the plan before it runs.
The GTmetrix toolbox
20 tools: 15 read, 5 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadGet Browser DetailsRetrieve browser details from GTmetrix.
- ReadGet BrowsersRetrieve the list of available browsers for GTmetrix performance tests.
- ReadGet Location DetailsRetrieve location details from GTmetrix.
- ReadGet LocationsRetrieve the list of available GTmetrix test locations.
- ReadGet Page DetailsRetrieve page details from the user's GTmetrix account.
- ReadGet Page Latest ReportRetrieve the most recent test report for a monitored page in GTmetrix.
- ReadGet Page ReportsRetrieve the report list associated with a monitored page in GTmetrix.
- ReadGet PagesRetrieve the page list from your GTmetrix account.
- ReadGet ReportRetrieve a GTmetrix test report by its identifier.
- ReadGet Report ResourceGet a report resource such as screenshot, HAR file, video, PDF, or Lighthouse JSON.
- ReadGet Simulated DeviceRetrieve simulated device details.
- ReadGet Simulated DevicesRetrieve the list of simulated devices available in GTmetrix.
- ReadGet API Account StatusRetrieve the current API account state and remaining credits.
- ReadGet Test DetailsRetrieve test details for a specific GTMetrix test.
- ReadGet TestsRetrieve the test list from your GTmetrix account with pagination and filtering support.
- WriteDelete PageDelete a specific page in GTmetrix. Approval by default
- WriteDelete ReportDelete a GTmetrix report. Approval by default
- WriteRetest PageInitiate a retest of a GTmetrix page with same parameters. Approval by default
- WriteRetest ReportInitiate a retest of a completed GTmetrix report with same parameters. Approval by default
- WriteStart TestStart a new GTmetrix test for a specified URL. Approval by default
One prompt, start to finish
What a governed GTmetrix run looks like inside Luumen.
Questions
Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
Read actions answer immediately. Anything that writes — delete page, delete report, retest page, retest report, and more — is shown as a plan and requires approval by default, including the 2 actions classified as destructive. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.
You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.
Every call to GTmetrix — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.
Often connected alongside
All integrations
GitHubRepos, actions, and runbook code as context and as actions.
GitLabMerge requests and pipelines proposed, triggered, and rolled back.
BitbucketRead commits, diffs, and branches in Bitbucket, then open the fix as a held write.
Azure DevOpsAzure DevOps repos and pipelines as context — and as approved actions.Put GTmetrix to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.