Skip to content
sayak.webdesignerWeb · Software · Data · AI
Chrome extension · Live on Chrome Web Storev1.0.0 · Published Apr 2026

PagePulse Pro

Website speed checker built on PageSpeed Insights, plus an SEO auditor with AI-powered fix suggestions, history and PDF export.

518 ratings No data collection Manifest V3

Opens the official Chrome Web Store listing · works in Chrome, Edge and Brave

chrome://any-sitecontent script injects herePopup UIRunmanifest.jsonpermissions · host rules · MV3Service Workerevent-driven, no DOM, sleepsContent Scriptisolated world, DOM accesschrome.storagesync · local · session
Why we built it

This is the extension we built for ourselves first. Auditing a page properly means opening PageSpeed Insights, running mobile, running desktop, opening a separate SEO checker, cross-referencing findings, and then writing it all into a document for the client. On a site audit that is forty pages of the same loop.

PagePulse Pro collapses it into one click on the page you are already looking at. It pulls the PageSpeed Insights result including field data where it exists, runs a full on-page SEO audit in the browser, combines both into one ranked list of issues, and suggests a specific fix for each — not "improve your title tag" but the actual problem with the actual element.

It keeps a history per URL, so you can see whether last month's work moved anything, and it exports a PDF report you can hand to a client or a developer.

The problem it solves

The tooling that exists is fragmented. PageSpeed Insights tells you about performance and says almost nothing useful about on-page SEO. SEO extensions tell you about titles and headings and know nothing about Core Web Vitals. Neither keeps history, so you cannot tell whether anything improved.

And neither produces something you can send to someone else. A screenshot of a score is not a report, and turning findings into a document by hand is where most of the time actually goes.

Privacy commitments

  • The on-page SEO audit runs entirely locally in your browser.
  • The PageSpeed check calls Google’s public PageSpeed Insights API with the page URL, as any speed tool must.
  • Audit history is stored on your device and never transmitted.
  • No account, no analytics, no identifiers.

Permissions and why

  • activeTabTo read the page you have asked to audit — headings, meta tags, images, links and structured data.
  • scriptingInjects the audit script when you invoke the extension.
  • storageStores audit history and preferences locally on your device.
  • downloadsTo save the exported PDF report.
Features

What it actually does

PageSpeed Insights, both strategies

Mobile and desktop results including Core Web Vitals field data from real users where the page has enough traffic to report it.

Full on-page SEO audit

Title, meta description, heading hierarchy, canonical, robots directives, Open Graph, structured data validity, image alt coverage, internal links and word count.

AI-powered fix suggestions

Each finding comes with a specific recommended change for that element, ranked by likely impact rather than listed alphabetically.

History per URL

Every audit is saved, so you can see whether the work you did last month actually moved the numbers.

PDF report export

A formatted report with findings, scores and recommendations — something you can send to a client or a developer.

Works on staging and behind logins

The on-page audit runs in your own session, so pages that a public tool cannot reach are still auditable.

How to use it

Three steps, no configuration

011

Open the page you want to audit

Click the toolbar icon. The on-page audit runs immediately and the PageSpeed request starts in parallel.

022

Review the ranked findings

Performance and SEO issues in one list, ordered by likely impact, each with a specific suggested fix.

033

Save or export

The result is stored in history against that URL. Export a PDF report when you need to hand it on.

Questions

About PagePulse Pro

Including where another tool would serve you better. If you have found a bug or want a feature, tell us on WhatsApp — we read every message.

The on-page SEO audit, yes — it runs in your own browser session, so staging sites, pages behind a login and local development are all auditable. The PageSpeed portion requires a publicly reachable URL, because Google’s API has to fetch the page itself. The extension makes clear which findings came from which source.

It checks what is objectively checkable — title length, description presence, heading hierarchy, canonical correctness, structured data validity, alt coverage, indexability directives. It cannot judge whether your content is genuinely the best answer to a query, and it does not pretend to. Treat it as a technical checklist, not a ranking prediction.

They turn a finding into a specific proposed change for that element — a rewritten title within the character budget, a description that covers the page’s actual topic, an alt text for the specific image. You review and decide; nothing is applied automatically.

No. It audits the page you are on. For a site-wide crawl covering redirect chains, orphan pages and internal link structure you need a crawler. This is for the page-by-page loop that sits either side of that.

Behind this extension

How we build and keep a published extension alive

PagePulse Pro is built natively on Manifest V3 rather than ported from the older extension architecture, and that distinction matters more than it sounds. Manifest V3 replaced persistent background pages with ephemeral service workers that the browser is free to shut down at any moment. An extension written on the old assumptions works perfectly on a developer’s machine and behaves unpredictably on a user’s machine after their laptop has been asleep for four hours.

So state is persisted to storage and restored rather than held in memory, anything that must survive a worker restart uses an alarm rather than a timer, and long operations are structured as resumable steps. Where network behaviour is modified, it uses declarative rules evaluated by the browser rather than a JavaScript listener on every request — which is why the extension adds no measurable per-request cost to your browsing.

Permissions are the part users are right to scrutinise, and we design for the narrowest set that makes the feature work. Anything optional is requested at the point of use rather than at install, which is both more honest and, for a public extension, materially better for install conversion. Every permission this extension holds is listed on this page with the specific reason it exists.

Maintenance is the unglamorous half. Chrome ships changes on a six-week cadence, target sites change their markup without notice, and Web Store policy is updated periodically with limited warning. We monitor for breakage, publish fixes promptly, respond to reviews, and keep the listing compliant. An extension that is abandoned becomes uninstallable within about two years as platform requirements move — so we treat publishing as a commitment rather than a launch.

We maintain seven live extensions for exactly this reason: it is how we stay genuinely fluent in Manifest V3 behaviour, review policy and the operational reality of shipping to real users — which is what we then bring to the extensions we build for businesses.

Engineering notes

  • Manifest V3 native — service worker lifetime assumed, never persistent state in memory.
  • Declarative rules for any network behaviour, so there is no per-request JavaScript cost.
  • TypeScript throughout, with schema validation at every boundary where data enters.
  • Optional permissions requested at the point of use rather than at install.
  • Bundled dependencies — no remotely hosted code, which MV3 prohibits and reviewers check.
  • Chrome and Edge from one build; Firefox needs a compatibility layer, Safari a native shell.

Want this for your team?

If your staff retype data out of a supplier portal, a government site or a marketplace dashboard, the same engineering applies. A focused internal tool is typically three weeks, deployed through enterprise policy so it installs automatically and cannot be removed by users.

Next step

We build extensions for businesses too.

If your team retypes data out of a supplier portal, a government site or a marketplace dashboard, that is usually three weeks of work and hundreds of hours a year recovered.

Direct line

+91 70033 91355

Mon–Sat · 9:30 AM – 7:30 PM IST · Sealdah, Kolkata

Reply within one working hour NDA signed before any brief Fixed-price option on every scope
Verify us independently

Don’t take our word for it — ask an AI

Every page on this site is written to be read and quoted by AI answer engines, and we publish llms.txt and llms-full.txt so they can read us properly. One click opens the assistant with the question already typed.

The question we will ask for you

Tell me about the Pagepulse Pro Chrome extension built by Sayak Web Designer (sayakwebdesigner.in), an IT company in Kolkata, India.

Opens in a new tab. We do not see your conversation.

Call now WhatsApp Get quote