Free2 abilities

PageSpeed ability reference

Reference for the GoBuildWP Free 1.18.6 source. Installed schemas and policy remain authoritative.

The PageSpeed ability reference covers a measurement request and the separate Site Kit sharing operation. Use the report to investigate a specific URL, with its returned source and diagnostics, rather than treating one score as a verdict on the whole site.

By GoBuildWPContent updated 12 October 2026How we check claims

Read-only, write and destructive groups describe the source annotations. They do not establish a minimum safety profile, human approval or undo support. Those controls are separate: check the installed ability, the connected user and the active site policy before calling it. A read can still return sensitive data. These pages are not evidence that every operation passed an end-to-end runtime test.

What PageSpeed needs before these load

Included in GoBuildWP Free. PageSpeed checks require an administrator capability and an available data source. Site Kit data also depends on its connection and permissions. Provider errors, quotas or missing field data can prevent a complete result.

Understand which source answered

The check tries connected, readable Site Kit, the GoBuildWP Cloud PageSpeed service, a configured PageSpeed API key and Google's keyless API. The response identifies the answering source and failed attempts. Availability of the fallback chain is not proof that a particular provider is currently working.

Results are cached for fifteen minutes unless refresh is requested. A fresh check can take substantially longer than an ordinary tool call. Compare the same URL, device strategy and testing conditions when assessing a change.

Keep lab results separate from visitor data

Lighthouse describes a simulated load. Field data is returned only when Google has it. A good lab result does not establish that real visitors pass Core Web Vitals, and a missing field report is not a zero score.

Sharing is a separate permission change

Enabling Site Kit dashboard sharing changes which administrators can read connected modules through the owner's account. It requires an eligible, Google-connected administrator and must be an intentional action. Running a PageSpeed check does not authorize changing sharing preferences.

Representative call sequence

This sequence describes the documented calls and checks to perform. It is not a recorded result from an installed WordPress site. Inspect returned errors and partial results, then verify the saved values and affected output before proceeding.

Investigate a slow landing page after changing its hero.

01 wppilot/pagespeed-check Request the page and device strategy, inspect the returned source and opportunities, then repeat under comparable conditions after the fix.

PageSpeed reads

Ability What it does

wppilot/pagespeed-checkPageSpeed Check Runs Google PageSpeed Insights (Lighthouse) on a page of this site and returns its scores (performance, seo, accessibility, best_practices, 0-100), lab metrics (fcp_ms, lcp_ms, tbt_ms, cls, si_ms, ttfb_ms), Core Web Vitals field data when Google has it, the opportunities ordered by the time they would save, and failing diagnostics. Needs no Google key from anyone: it asks Site Kit by Google when its PageSpeed module is connected and readable by this user, otherwise GoBuildWP Cloud's PageSpeed service (GoBuildWP's own Google key), then a PageSpeed API key the site owner saved in the plugin settings, then Google's keyless API. source says which answered and attempts why earlier ones did not. One run takes 10-60 seconds; results are reused for 15 minutes unless refresh=true. Lab numbers are one simulated load, not what visitors experienced; field_data is what visitors experienced, when there is any.

Ability	What it does
`wppilot/pagespeed-check`PageSpeed Check	Runs Google PageSpeed Insights (Lighthouse) on a page of this site and returns its scores (performance, seo, accessibility, best_practices, 0-100), lab metrics (fcp_ms, lcp_ms, tbt_ms, cls, si_ms, ttfb_ms), Core Web Vitals field data when Google has it, the opportunities ordered by the time they would save, and failing diagnostics. Needs no Google key from anyone: it asks Site Kit by Google when its PageSpeed module is connected and readable by this user, otherwise GoBuildWP Cloud's PageSpeed service (GoBuildWP's own Google key), then a PageSpeed API key the site owner saved in the plugin settings, then Google's keyless API. `source` says which answered and `attempts` why earlier ones did not. One run takes 10-60 seconds; results are reused for 15 minutes unless refresh=true. Lab numbers are one simulated load, not what visitors experienced; field_data is what visitors experienced, when there is any.

Destructive PageSpeed calls

Ability What it does

wppilot/site-kit-enable-sharingEnable Site Kit Dashboard Sharing Turns on Site Kit by Google's Dashboard sharing (read-only) for Search Console, Analytics 4 and PageSpeed Insights to the Administrator role, through Site Kit's own sharing settings route, exactly as Site Kit > Dashboard sharing does. Administrators who are not signed in to Site Kit with Google can then read those modules through the owner's account, which is what lets Site Kit reads and PageSpeed checks made through GoBuildWP work for them. Never reads or writes a Google token, and never changes who may manage sharing. Site Kit only accepts the change from an administrator signed in to Site Kit with Google who owns the module (any signed-in admin for PageSpeed Insights); modules this user may not change are reported as not_permitted with their owner. Modules not connected to Google are skipped. Undo with wppilot/rollback-change.

Ability	What it does
`wppilot/site-kit-enable-sharing`Enable Site Kit Dashboard Sharing	Turns on Site Kit by Google's Dashboard sharing (read-only) for Search Console, Analytics 4 and PageSpeed Insights to the Administrator role, through Site Kit's own sharing settings route, exactly as Site Kit > Dashboard sharing does. Administrators who are not signed in to Site Kit with Google can then read those modules through the owner's account, which is what lets Site Kit reads and PageSpeed checks made through GoBuildWP work for them. Never reads or writes a Google token, and never changes who may manage sharing. Site Kit only accepts the change from an administrator signed in to Site Kit with Google who owns the module (any signed-in admin for PageSpeed Insights); modules this user may not change are reported as not_permitted with their owner. Modules not connected to Google are skipped. Undo with wppilot/rollback-change.