HKC Performance

Core Web Vitals and PageSpeed Insights monitoring, inside the WordPress admin — without slowing your site down, and with the Search Console figures that tell you whether the work pays off.

What it does

A look inside

The Performance dashboard: alerts, mobile score, lab metrics, plain-language hints, real-visitor data and the screenshot Google saw.
The dashboard, on mobile: the median score and its range, the lab metrics with Google’s thresholds, what to check in LiteSpeed Cache, then the Chrome UX Report figures for real visitors.
Weekly clicks from Google Search as bars, the performance score as a line, then the ranked list of things to look at.
Search Console clicks week by week, with the performance score on the same chart — then the improvements ranked by estimated impact, each explained in plain words.
A before / after table around a change: score, LCP, clicks, impressions, average position, and the whole site as a control.
Before / after a change to the site, 28 days on each side — with the whole site as a control, to tell a real gain from seasonality.

Screenshots taken on a demo site, with figures produced for the demonstration.

Requirements

Installation

  1. In WordPress, go to Plugins › Add New › Upload Plugin and upload hkc-performance.zip.
  2. Activate the extension and open the Performance menu.
  3. Click Connect Google, then Sign in with Google.

Updates then appear in the WordPress plugins screen like any other extension.

How Google sign-in works

HKC Performance calls three Google services on behalf of the site owner:

Google serviceWhat forAccess
PageSpeed InsightsLab test and 28-day real-visitor data of your reference pagesSign-in (openid)
Search ConsoleClicks, impressions and average position of your reference pages and of your whole site, to compare them with performance over time; suggestion of reference pagesRead-only (webmasters.readonly)
Google AnalyticsPages your visitors failed to reach, and the page that carried the broken link — only if you turn on the broken links module and choose a propertyRead-only (analytics.readonly)
Chrome UX ReportWeekly history of real-visitor Core Web VitalsThrough the sign-in service's API key

The sign-in goes through auth.hervekabla.com, the HKC Plugins sign-in service:

  1. A window shows which site is asking to connect, so you can check it before continuing.
  2. Google shows its consent screen: you choose the account and grant read-only access.
  3. The service hands a one-time code back to your site, which exchanges it — server to server, with a secret that never left your site — for the Google tokens.

Your Google tokens are stored encrypted in your own WordPress database. PageSpeed Insights and Search Console are then called directly by your site: your reports never pass through the sign-in service, which keeps no tokens and no reports. You can disconnect at any time from the extension or from your Google account permissions.

Sites that must not rely on any intermediary can use their own Google Cloud OAuth client instead (advanced option in the extension).

Details: privacy policy.