Google PageSpeed Insights
This page guides you through the process of setting up the Google PageSpeed Insights source connector.
- Log into your Airbyte Cloud or Airbyte Open Source account.
- Click Sources and then click + New source.
- On the Set up the source page, select Google PageSpeed Insights from the Source type dropdown.
- Enter a name for your source.
- For API Key, enter your Google PageSpeed
API Key
. - For URLs to analyse, enter one or many URLs you want to create PageSpeed Insights for. Example: https://www.google.com.
- For Analyses Strategies, enter either "desktop", "mobile" or both to define which Analyses strategy to use.
- For Lighthouse Categories, select one or many of the provided options. Categories are also called "audits" in some of the Google Lighthouse documentation.
- Click Set up source.
IMPORTANT: As of 2022-12-13, the PageSpeed Insights API - as well as this Airbyte Connector - allow to specify a URL with prefix "origin:" - like
origin:https://www.google.com
. This results in condensed, aggregated reports about the specified origin - see this FAQ. However: This option is not specified in any official documentation anymore, therefore it might be deprecated anytime soon!
The Google PageSpeed Insights source connector supports the following sync modes:
- Full Refresh
The Google PageSpeed Insights source connector supports the following stream:
- pagespeed: Full pagespeed report of the selected URLs, lighthouse categories and analyses strategies.
Feature | Supported?(Yes/No) | Notes |
---|---|---|
Full Refresh Sync | Yes | |
Incremental Sync | No |
When using the connector without an API key, Google utilizes an undocumented, but strict rate limit - which also depends on how many global requests are currently sent to the PageSpeed API. The connector will retry, using an exponential backoff interval.
If the connector is used with an API key, Google allows for 25.000 queries per day and 240 queries per minute. Therefore, under normal usage, the connector should not trigger any rate limits. Create an issue if you see any rate limit issues that are not automatically retried successfully.
Expand to review
Version | Date | Pull Request | Subject |
---|---|---|---|
0.2.1 | 2024-08-16 | 44196 | Bump source-declarative-manifest version |
0.2.0 | 2024-08-15 | 44143 | Refactor connector to manifest-only format |
0.1.17 | 2024-08-10 | 43617 | Update dependencies |
0.1.16 | 2024-08-03 | 43130 | Update dependencies |
0.1.15 | 2024-07-27 | 42770 | Update dependencies |
0.1.14 | 2024-07-20 | 42319 | Update dependencies |
0.1.13 | 2024-07-13 | 41706 | Update dependencies |
0.1.12 | 2024-07-10 | 41591 | Update dependencies |
0.1.11 | 2024-07-09 | 41155 | Update dependencies |
0.1.10 | 2024-07-06 | 41011 | Update dependencies |
0.1.9 | 2024-06-29 | 40439 | Update dependencies |
0.1.8 | 2024-06-22 | 40104 | Update dependencies |
0.1.7 | 2024-06-06 | 39272 | [autopull] Upgrade base image to v1.2.2 |
0.1.6 | 2024-05-21 | 38147 | Make compatable with builder |
0.1.5 | 2024-04-19 | 37171 | Updating to 0.80.0 CDK |
0.1.4 | 2024-04-18 | 37171 | Manage dependencies with Poetry. |
0.1.3 | 2024-04-15 | 37171 | Base image migration: remove Dockerfile and use the python-connector-base image |
0.1.2 | 2024-04-12 | 37171 | schema descriptions |
0.1.1 | 2023-05-25 | #22287 | 🐛 Fix URL pattern regex |
0.1.0 | 2022-11-26 | #19813 | 🎉 New Source: Google PageSpeed Insights [low-code CDK] |