pafcore.site

Changelog

16 September 2026

  • "I fixed it, did it work?" is now a button on the report. It scans your live site again and compares it with the report you are looking at, judged against how much that page moves on its own. Three answers: it worked, it went the wrong way, or we cannot tell because the change is smaller than the page's own movement. 2 credits. Before this, the only thing offered after you fixed something was an email in three days telling you to run the report again and compare it yourself.
  • The same verdict now comes from one place, so the website and the Cursor tool answer that question identically. They could previously disagree.
  • The home page leads with the thing only we do: your score moves on its own, so a drop is not always a drop.

15 September 2026

  • Pages behind a login. Watch can now measure a page that only signed in users can reach. You hand over one session, from a right click and Copy as cURL in your own browser. It is encrypted before it is stored, shown to you only as a length and a last few characters, and sent to that one host and no other. Revoke removes it, and the next run goes back to being signed out. We test the session the moment you save it and tell you whether it worked, failed, or could not be judged either way. Guide: Watch (Pro).
  • Every client site on one screen. A portfolio view lists all your watched pages worst score first, so a morning check is one screen instead of one tab per client.
  • Regression alerts now know how much a page moves on its own. A change smaller than that movement is reported as being within the page's own noise, instead of as a drop. Before this, quiet pages were sending alerts about nothing.
  • Agency: $12 per client site a month, four sites minimum. It sits with the other plans on the pricing page. Pro's own limits are a floor, so moving up never takes anything away.
  • Naira pricing for customers in Nigeria. If you are in Nigeria you are sent to Paystack and charged in Naira, at prices set for Nigeria rather than converted from dollars. Everyone else is unchanged. Nothing to switch on: the right checkout is chosen for you.
  • A branded report no longer carries our name in the places a client reads.
  • Outage details now say what actually happened and what to check, instead of repeating the raw error.
  • A site that redirects is no longer called down. Uptime follows up to five redirects and checks each hop is still safe to visit. One real customer site was reported down for 72 minutes while it was up the whole time.
  • Shared report links could be put in a frame on any site. They cannot now.

14 September 2026

  • Your name on the client report. Pro and Agency accounts can set a company name, logo and colour. The report you download carries them, and reads as a document you can hand to a client rather than a page from our site.
  • The report now names the route or component next to the slow file, when the site ships enough information to say so honestly.
  • Paste ready code went from covering 9 findings in every 100 to 72.
  • A scan that was cancelled or failed still tells you which page it was on.
  • We now count the reports people save, so the client report can be judged on use rather than opinion.

13 September 2026

  • Uptime is live. We check whether your site answers at all, every minute for Pro, and tell you when it stops and when it comes back. It covers certificates and domain names about to run out, heartbeat URLs for jobs with no address to check such as a nightly backup, a public status page you can share, and maintenance windows so planned work stays quiet.
  • Outages are reported as one outage, not as the run of failed checks underneath it, and every failure is confirmed by a second check before you are told.
  • Watch became readable: a real chart, a summary strip along the top, shorter tabs, and one screen per monitor.
  • Bought credits never expire. Monthly Pro credits do not stack, and both are now said plainly on the pricing page.
  • Free and Pro were drifting apart from what the pricing page claimed. The code now gives away exactly what the page says and no more.

12 September 2026

  • Watch alerts: Send test on any rule. It sends a real message down the same path a real alert takes, so a typo in a webhook URL shows up now instead of during a real drop. Guide: Watch (Pro).
  • Each rule now says what it watches in plain words, and whether the last alert reached you. A failed channel names which one and why.
  • A webhook is tried twice when the far end times out, rate limits, or has a server fault. Never on a 404, and never on a redirect.
  • The alert limit box follows the metric you pick, so a paint limit no longer defaults to a score floor and fires on every run.
  • Test alerts are capped per account, and never quiet a real alert.
  • Alerts can be edited instead of deleted and rebuilt, and paused without removing them.
  • Watch alerts now name the cause of a drop, and say when the drop is small enough to be the page's own movement rather than a real change.
  • Test this for real now works on the commonest finding of all, scripts keeping the page too busy to answer taps. It measures the change the report advised: delaying the script it named. Before this, most reports had no way to prove a fix at all.
  • Watch pages show their latest score, so a list of client sites can be read at a glance, and a History button opens one in a single click.
  • Reports now separate what you can fix from what is not yours. Code you embedded, like a chat widget or a tag manager, no longer sits in the same list as your own files. It says what you can still change: when it loads, or whether you keep it.
  • Watch says why an action is blocked when you reach a fair use cap, on the page rather than in a tooltip. Picking hourly when hourly is full no longer changes your choice without telling you.
  • Watch now shows real visitor numbers next to the lab chart: largest content paint, tap response and layout shift, each graded on Google's own thresholds so it agrees with Search Console. Sites Google has no data for see an honest note instead of zeros.
  • Real visitor data (CrUX) now works on Watch. Small sites still see an honest "Google does not have enough data for this site yet" instead of a blank panel.
  • Scheduled checks now actually run. Watch schedules had never fired. Three faults were stacked on top of each other, and each hid the next. Fixed, and the first real scheduled check has completed.

5 September 2026 (later)

  • Security: alert webhooks must resolve to a public host; deliveries do not follow redirects.
  • Watch schedule ticks claim due rows atomically (no double queue on overlap).
  • Pro included credits are 60/mo (under pack value), not 250.

5 September 2026

  • Watch UI: domain proof, schedules, alerts, and history in the product (not API only). Guide: Watch (Pro).
  • Public reports open the full homepage report again (/?scan=…) with share and download.
  • Product emails share one light card layout (sign in, report, Watch alerts).
  • Sign in syncs Vemetric user identity when you are logged in.
  • Fair use on Pro: Watch runs stay free of credit spend; page and schedule caps protect capacity.
  • Pricing page and site nav refreshed for phone and desktop.

4 September 2026 (later)

  • Pro Watch is live: projects, schedules, history, alerts. $19/mo, 60 credits included (updated 5 Sep from 250). Start at /pro.
  • Share links: full report at /?scan=…; Plain / Technical at /share?scan=….
  • MCP: get_field_data. API: projects, domains, schedules, history, field, alerts (see Pro monitoring).

4 September 2026

  • Test this for real now covers slow-filling pages held up by a script we can name. Roughly two in five findings can be lab tested, up from one in three.
  • The button is decided by whether the report names the file, not by the kind of problem. If we could not pin the work on anything, you are told before you are charged, not after.
  • A lab test that fails gives the credit back.
  • Pressing the button twice runs one test and charges once.
  • Desktop reports no longer claim the machine was slowed to imitate a phone. Desktop is not slowed at all, and the report now says so, along with the fact that a desktop score follows the speed of the machine that measured it.
  • Sign-in emails are capped, so nobody can use the form to mail a stranger.

3 September 2026

  • Starter pack: $5 for 20 credits
  • Credits path on the web: sign in, buy, test, download, paste ready code
  • Engine CLI: login, scan, test, me, mcp install
  • MCP tools for Cursor: scan, findings, lab test, locate, verify change
  • API v1 curl guide for scans, findings, and experiment
  • Docs site launched (this site)