GTmetrix
GTmetrix is a performance testing and monitoring tool that analyzes website speed, provides detailed performance reports, and helps optimize web applications for better user experience.
Verdict
Common use cases
- Audit staging site speed before deploy
- Compare mobile vs desktop load times
- Pull Core Web Vitals for sprint demo
- Investigate user-reported slowness by region
- Track performance trends across releases
Integration
- Vendor
- GTmetrix
- Category
- developer-tools
- Auth
- API_KEY
- Tools
- 16
- Composio slug
gtmetrix
Tools
- Delete Pagedestructive
Tool to delete a specific page in GTmetrix. Use when you need to permanently remove a page resource.
- Delete Reportdestructive
Tool to delete a GTmetrix report. Use when you need to remove an existing performance report from GTmetrix.
- Get API Account Status
Tool to retrieve the current API account state and remaining credits. Use to check available API credits, refill schedule, and account features.
- Get Browsers
Tool to retrieve the list of available browsers for GTmetrix performance tests. Use when you need to see which browsers are available and their testing capabilities.
- Get Location Details
Tool to retrieve location details from GTmetrix. Use when you need to get information about a specific GTmetrix test location including name, region, browser support, IP addresses, and access permissions.
- Get Locations
Tool to retrieve the list of available GTmetrix test locations. Use when you need to see which locations are available for testing and their details including supported browsers and access status.
- Get Page Details
Tool to retrieve page details from the user's GTmetrix account. Use when you need to get comprehensive page information including URL, testing configuration, and monitoring frequency.
- Get Page Reports
Tool to retrieve the report list associated with a monitored page in GTmetrix. Use when you need to access historical performance data for a specific page. Supports pagination, sorting, and filtering.
- Get Pages
Tool to retrieve the page list from your GTmetrix account. Returns a paginated collection of monitored pages with their configurations and latest report information. Use when you need to view all monitored pages, check page configurations,
- Get Report
Tool to retrieve a GTmetrix test report by its identifier. Use when you need to get comprehensive performance metrics, timing data, and links to resources for a specific report.
- Get Simulated Device
Tool to retrieve simulated device details. Use when you need information about a specific simulated device including its name, category, manufacturer, user agent, screen dimensions, and pixel ratio.
- Get Simulated Devices
Tool to retrieve the list of simulated devices available in GTmetrix. Use when you need to see available device profiles for testing.
- Get Test Details
Tool to retrieve test details for a specific GTMetrix test. Use when you need to check the status, configuration, or results of a previously initiated test.
- Get Tests
Tool to retrieve the test list from your GTmetrix account with pagination and filtering support. Use when you need to view tests with their state, timestamps, and configuration details.
- Retest Report
Tool to initiate a retest of a completed GTmetrix report with same parameters. Use when you need to rerun a test using the exact same analysis parameters as the original test.
- Start Test
Tool to start a new GTmetrix test for a specified URL. Use when you need to analyze website performance with configurable options like location, browser, and throttling.
Setup
Setup guide
- 11. Log into your GTmetrix account at gtmetrix.com and navigate to Account Settings → API. 2. Generate a new API key and copy it to your clipboard. 3. In Switchy, open your workspace settings and click Integrations → Add MCP. 4. Search for GTmetrix, select it, then paste your API key into the authentication field. 5. Click Connect and wait for the green confirmation banner. 6. Open any Space and type '@GTmetrix get locations' to verify the connection — you should see a list of test servers (Vancouver, London, Mumbai, etc.). 7. To run your first test, type '@GTmetrix get page details' and note a page ID from your monitored pages, then '@GTmetrix get page reports' with that ID to pull recent performance data. If you hit rate limits, check your remaining credits with '@GTmetrix get api account status'.
What teammates see: by default, memories from GTmetrix are scoped to the Project (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Projects have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Check Available Test Locations
@GTmetrix get locations and show me which regions support Chrome testing
Review Recent Page Reports
@GTmetrix get page reports for page ID abc123 and summarize the last 5 tests, highlighting any regressions
Verify API Credit Balance
@GTmetrix get api account status and tell me how many credits I have left this month
List Monitored Pages
@GTmetrix get page details and list the URLs and monitoring frequencies for all my pages
Compare Browser Performance
@GTmetrix get browsers and show me which versions of Chrome and Firefox I can test with
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@GTmetrix check my API credits and tell me when they'll refill
Your GTmetrix account currently has 127 API credits remaining out of your 500 monthly allocation. Credits refill on the 1st of each month at 00:00 UTC. Based on your current usage pattern (approximately 15 tests per day), you have enough credits to last through the end of the month. Your account tier supports testing from 8 global locations with Chrome and Firefox browsers available.
This example demonstrates the account status check capability. Requires a valid GTmetrix API key with read access. The credit count and refill schedule are account-specific, so actual responses will vary. Useful for monitoring API quota before running batch tests or setting up automated monitoring.
@GTmetrix run a performance test on https://example.com from London using Chrome and generate a report
Performance test initiated for https://example.com from London (location ID: 3) using Chrome 120. Test queued successfully with report ID: rpt_abc123xyz. The test will measure Core Web Vitals, page load time, total page size, and number of requests. Estimated completion time: 45-60 seconds. Once complete, the report will include PageSpeed and YSlow scores, waterfall charts, and actionable optimization recommendations. You can retrieve the full report using the report ID.
This showcases the core testing workflow that creates a new performance report. Note that test execution is asynchronous—the MCP initiates the test but doesn't wait for completion. You'll need to poll for results or set up monitoring. Each test consumes API credits, and some locations may have queue delays during peak hours.
@GTmetrix get the last 5 reports for my homepage and summarize the performance trend over time
Retrieved 5 recent reports for your monitored homepage spanning the last 14 days. Performance trend analysis: PageSpeed scores have declined from 92 to 87, primarily due to increased JavaScript bundle size (now 487KB, up 23% from first report). Largest Contentful Paint increased from 1.8s to 2.4s. Total page weight grew from 1.2MB to 1.6MB. However, Time to Interactive improved slightly (3.1s to 2.9s) thanks to better render-blocking resource handling. Recommendation: investigate the JavaScript bundle growth—recent reports show three new third-party scripts that may warrant lazy-loading or removal.
This example combines GTmetrix's historical data retrieval with AI analysis to identify trends. Requires that the page is already set up for monitoring in your GTmetrix account. The AI synthesizes multiple report data points to provide actionable insights. Particularly valuable for tracking the performance impact of deployments or identifying gradual regressions that might not be obvious in single-point measurements.
Use-case deep-dives
When GTmetrix beats manual lighthouse runs for frontend teams
A 3-person frontend team ships weekly. They used to run Lighthouse locally before each deploy, but results varied by network and machine state. GTmetrix's 16 tools let them schedule tests from consistent locations (Get Locations), compare reports across sprints (Get Page Reports), and catch regressions without blocking CI. The API key auth means any dev can pull the latest scores into Slack or a dashboard. This works until you're testing more than 10 pages daily—at that point, the credit burn (check with Get API Account Status) pushes you toward self-hosted tooling. If your team deploys once a week and monitors 3-5 critical pages, GTmetrix gives you the consistency of a third-party service without the overhead of maintaining your own performance lab.
Why agencies use GTmetrix for repeatable client reporting
A 6-person agency audits 20 client sites monthly. They need browser-specific scores (Get Browsers) and geographic variance (Get Location Details) to show clients how their site performs in target markets. GTmetrix's Delete Report tool keeps the account tidy between engagements, and the structured API output feeds directly into their white-label PDF generator. The limitation: if a client wants real-user monitoring or synthetic tests every 5 minutes, GTmetrix's page-monitoring model (Get Page Details shows frequency caps) won't scale. For monthly or quarterly audits where you need defensible, third-party scores and can tolerate 15-minute test intervals, GTmetrix's toolset hits the sweet spot between Lighthouse's variability and expensive RUM platforms.
GTmetrix as a deploy gate for small SaaS teams
A 5-person SaaS team deploys twice daily. They added a post-deploy step that triggers a GTmetrix test on their landing page and dashboard login flow, then checks if page load regressed by more than 10%. The Get API Account Status call warns them if they're about to burn through their monthly credits mid-sprint. This setup works because they're testing 2 URLs per deploy—40 tests a week fits comfortably in the free tier. The boundary: if you're deploying 10+ times a day or testing a dozen pages per deploy, you'll either blow your credit budget or need to throttle tests, which defeats the smoke-test purpose. For teams shipping a few times daily with a small critical-path surface area, GTmetrix's API gives you a lightweight performance gate without spinning up your own Lighthouse infrastructure.
Frequently asked
What does the GTmetrix MCP do in Switchy?
It lets your team run website performance tests and pull historical reports directly from chat. You can check page speed scores, delete old reports, see which test locations and browsers are available, and monitor your API credit balance. Instead of logging into GTmetrix's dashboard, your team asks the AI to fetch the data or trigger a test.
Do I need a paid GTmetrix account to use this MCP?
Yes. The MCP authenticates with a GTmetrix API key, which requires at least a Basic paid plan. Free GTmetrix accounts don't get API access. You'll paste your API key into Switchy once, and the MCP uses your account's credit pool for every test run or report fetch the team requests.
Can the GTmetrix MCP schedule recurring performance tests?
No. It can retrieve the monitoring schedule you've already set up in GTmetrix, and it can fetch historical reports from monitored pages, but it doesn't create or edit monitoring schedules. If you want automated daily tests, configure that in GTmetrix's web UI first, then use the MCP to pull results.
How is this different from just using GTmetrix's website?
The MCP brings performance data into your team's chat context. Instead of switching tabs to check if a deploy tanked your Lighthouse score, you ask the AI mid-conversation. It's faster for spot checks and comparing reports across pages, but GTmetrix's dashboard still has richer visualisation for waterfall analysis and filmstrip views.
Who on the team should connect the GTmetrix account?
Whoever owns your GTmetrix subscription and can generate an API key. That's usually a frontend lead or DevOps engineer. Once connected in Switchy, anyone in the workspace can ask the AI to run tests or pull reports, but they'll all draw from the same API credit pool and see the same monitored pages.