PageSpeed Insights - Core Web Vitals & Real User Metrics

Get Google PageSpeed Insights data including real-user experience from Chrome UX Report (CrUX) and Lighthouse lab data. Core Web Vitals: LCP, FID/INP, CLS. Performance scores for mobile and desktop. Supports batch URL analysis. Features: Real-World Field Data from Chrome UX Report (28-day rolling averages), Lab Data from Lighthouse, Core Web Vitals (LCP, FID, CLS), Performance/Accessibility/SEO scores, Mobile and Desktop strategies, Batch URL processing, Webhook integration. Built by John Rippy (https://www.linkedin.com/in/johnrippy/ | https://johnrippy.link/).

Features

• Automated data collection
• Structured output format
• Error handling
• Pay-per-event billing

Quick Start

{
  "input": "your input here"
}

Demo Mode

Set demoMode: true to test with sample data (no charges). When you're ready for real results, set demoMode: false or omit it.

{
  "demoMode": true,
  ...
}

Input Parameters

Parameter	Type	Required	Default	Description
demoMode	boolean	No	false	Run with sample data (free, no API calls)
url	string	No*	-	Single URL to analyze
urls	array	No*	-	Array of URLs to analyze
strategy	string	No	"both"	Device strategy: "mobile", "desktop", or "both"
apiKey	string	No	-	Your Google PageSpeed API key for higher rate limits
webhookUrl	string	No	-	Webhook URL for Zapier/Make/n8n integration

*Either url or urls is required (unless using demoMode)

---

Output Format

{
  "url": "https://example.com",
  "strategy": "mobile",
  "timestamp": "2024-12-25T12:00:00.000Z",
  "hasFieldData": true,
  "performanceScore": 85,
  "accessibilityScore": 92,
  "bestPracticesScore": 100,
  "seoScore": 98,
  "coreWebVitals": {
    "lcp": {
      "value": 2.1,
      "unit": "seconds",
      "rating": "good",
      "source": "field"
    },
    "fid": {
      "value": 45,
      "unit": "milliseconds",
      "rating": "good",
      "source": "field"
    },
    "cls": {
      "value": 0.05,
      "unit": "score",
      "rating": "good",
      "source": "field"
    },
    "fcp": {
      "value": 1.2,
      "unit": "seconds",
      "rating": "good",
      "source": "field"
    },
    "ttfb": {
      "value": 0.4,
      "unit": "seconds",
      "rating": "good",
      "source": "field"
    },
    "inp": {
      "value": 120,
      "unit": "milliseconds",
      "rating": "good",
      "source": "field"
    }
  },
  "labData": {
    "lcp": 2.3,
    "tbt": 150,
    "cls": 0.02,
    "fcp": 1.4,
    "speedIndex": 2.8
  },
  "audits": {
    "passed": 42,
    "failed": 3,
    "opportunities": [
      {
        "id": "render-blocking-resources",
        "title": "Eliminate render-blocking resources",
        "potentialSavings": "1.2s"
      }
    ]
  }
}

---

Pricing

This actor uses pay-per-event billing: This actor uses the Google PageSpeed Insights API which is free for most usage. Apify platform usage is billed separately based on compute units used.

• Demo Mode: Free (no API calls, uses sample data)
• With API Key: Higher rate limits from Google
• Without API Key: Standard rate limits apply

---

Use Cases

• SEO Audits - Core Web Vitals are a Google ranking factor
• Performance Monitoring - Track real-user experience over time
• Competitor Analysis - Compare your site's performance vs competitors
• Client Reporting - Include CrUX data in SEO reports
• Before/After Analysis - Measure impact of performance optimizations

---

---

Common Problems & Solutions

"Invalid API key" error

Cause: Your API key is wrong, expired, or doesn't have the right permissions. Fix: Double-check your API key. Make sure you copied it exactly without extra spaces.

"Rate limit exceeded" error

Cause: You've hit the API's rate limits. Fix: Wait a few minutes, then try again. Consider reducing the number of concurrent requests.

Empty or incomplete results

Cause: The target may have anti-scraping protection or the data doesn't exist. Fix:

• Check if the URL/search query is correct
• Try with different parameters
• Some sites may block automated access

Demo data showing instead of real results

Cause: demoMode is still set to true. Fix: Set demoMode: false and provide your API key(s).

---

Built by John Rippy | Actor Arsenal