Catches slowdowns on publish
Every Webflow or HubSpot publish kicks off a performance check. If a page gets slower, shifts around, or feels sluggish, we ping the right people in Slack within minutes.
Private beta · waitlist open
Your marketing team just broke the pricing page. You’ll find out in three weeks.
CorePulse monitors your landing pages and tells you the moment a publish hurts performance — before Search Console does.
We’ll email you the moment we open up. No spam.
Tells you what changed
When something breaks, CorePulse points at the specific script or image that’s most likely responsible — not just ‘your page got slower’.
Watches GTM rot quietly
A weekly automated audit of your GTM container. Stale tags, duplicates, governance gaps. The same rule engine that powers PageCheckup, on a schedule.
Built for marketing ops, not engineers
No P95 charts. No CI integration. Plain-language alerts your marketing team can act on without paging a dev.
Slack-first, email second
Marketers live in Slack. So that’s where performance alerts land. Email is a fallback, not the main channel.
One Monday digest
A weekly summary of what regressed, what improved, and where GTM health is heading. Short enough to read on a phone.
The alert
Plain English, named culprit, named publisher.
CorePulse alerts read like a useful Slack message, not a stack trace. The metric is named (loading speed, not LCP), the likely cause is called out, and so is whoever hit Publish. Click the link and you’re inside the full report.
Questions buyers usually ask first
If yours isn’t here, email hello@corepulse.dev.
What is a “monitored page” for billing purposes?
A monitored page is any URL you add to your CorePulse dashboard. Starter allows up to 25; Growth allows up to 100. Adding a page doesn’t use your limit until it receives its first audit, so you can set up your workspace without worrying about the clock.
How does CorePulse test my pages?
When your Webflow or HubSpot site publishes, CorePulse runs a synthetic Lighthouse test against each of your monitored pages — the same methodology Google uses for PageSpeed Insights. We compare the results to the previous run and alert you if Core Web Vitals regress beyond your thresholds.
Will CorePulse install any script on my site?
No. CorePulse uses your CMS’s publishing API to detect when a page changes, and runs tests from our own infrastructure. We never inject code into your site.
I already use SpeedCurve / DebugBear / Calibre. Is this different?
Those are excellent tools built for engineering teams. CorePulse is built for the marketing and ops teams who actually publish the pages — different dashboards, different language, different alerts. Many teams use CorePulse alongside their existing performance tooling.
How does the GTM monitoring work?
Connect your GTM account and CorePulse runs a weekly audit using the same rule engine that powers PageCheckup, the free GTM audit tool. Stale tags, duplicates, deprecated UA tags, broken references, consent-mode gaps. All on a schedule, no manual work.
What happens when I hit my page limit?
We’ll let you know when you’re approaching your limit (80% and 100%). When you hit it, new pages can’t be added but existing ones continue to be monitored. No surprise charges — upgrade or remove a page to add a new one.
Is CorePulse GDPR compliant?
CorePulse stores performance metrics (LCP, CLS, INP scores, resource lists) and account data. We do not install tracking on your site or access your end users’ data. Our sub-processors are listed in the Privacy Policy. A Data Processing Agreement is available on request — email hello@corepulse.dev.
What’s the refund policy?
If CorePulse doesn’t work for you within the first 30 days of your first paid month, email us and we’ll refund in full. No questions asked.
Stop finding out about page slowdowns from your CEO.
Connect a Webflow or HubSpot site, pick the pages that matter, and CorePulse takes it from there.