
Pagespeed Insights Webpage Analyzer
Pricing
$3.00 / 1,000 urls

Pagespeed Insights Webpage Analyzer
Get Lighthouse Web Audits and Chrome User Experience Reports for a list of urls or for your whole website. Get a detailed report or aggregated results to monitor performance, accessibility, SEO and more. Schedule the analysis to keep track of the state of your website over time.
0.0 (0)
Pricing
$3.00 / 1,000 urls
11
Total users
148
Monthly users
30
Runs succeeded
>99%
Last modified
8 months ago
You can access the Pagespeed Insights Webpage Analyzer programmatically from your own applications by using the Apify API. You can also choose the language preference from below. To use the Apify API, you’ll need an Apify account and your API token, found in Integrations settings in Apify Console.
{ "mcpServers": { "apify": { "command": "npx", "args": [ "mcp-remote", "https://mcp.apify.com/sse?actors=baldasseva/pagespeed-insights-webpage-analyzer", "--header", "Authorization: Bearer <YOUR_API_TOKEN>" ] } }}
Configure MCP server with Pagespeed Insights Webpage Analyzer
You have a few options for interacting with the MCP server:
Use
mcp.apify.com
viamcp-remote
from your local machine to connect and authenticate using OAuth or an API token (as shown in the JSON configuration above).Set up the connection directly in your MCP client UI by providing the URL
https://mcp.apify.com/sse?actors=baldasseva/pagespeed-insights-webpage-analyzer
along with an API token (or use OAuth).Connect to
mcp.apify.com
via Server-Sent Events (SSE), as shown below:
{ "mcpServers": { "apify": { "type": "sse", "url": "https://mcp.apify.com/sse?actors=baldasseva/pagespeed-insights-webpage-analyzer", "headers": { "Authorization": "Bearer <YOUR_API_TOKEN>" } } }}
You can connect to the Apify MCP Server using clients like Tester MCP Client, or any other MCP client of your choice.
If you want to learn more about our Apify MCP implementation, check out our MCP documentation. To learn more about the Model Context Protocol in general, refer to the official MCP documentation or read our blog post.