Description
PagePulse shows clear, good-looking feedback whenever visitors wait: while a page loads, when they follow a link, submit a form, add a product to the cart, or when your own scripts fetch data. It is built to be safe on real sites: it never delays navigation, never changes how forms submit, never leaves a page covered, and never loads files a page does not need.
PagePulse improves perceived loading. It does not make your pages load faster, and it is designed not to make them slower: no jQuery, CSS-only animations, a deferred script, and only the CSS of the loaders you use.
Loading modes
- Initial page loading – a full-screen loader from the first paint until the page is ready (DOM ready or full load). Whole site, homepage, selected post types, page IDs or URL patterns; desktop only, mobile only, or once per visit. Without JavaScript it never appears, and it always removes itself after a maximum time, even if a script fails.
- Page navigation – overlay and/or a progress bar when a visitor follows an internal link: menus, archives, pagination, search. Never for external links, downloads,
mailto:/tel:, new tabs, Ctrl/⌘-clicks, in-page anchors, the dashboard or the login page. - Element loader – a loader inside any element (overlay, inline or skeleton), from dashboard rules,
data-pagepulseattributes or the JavaScript API. - Form submissions – spinner in the submit button, overlay on the form, or full-screen, shown only after the browser accepted the submission. Contact Form 7, WPForms, Gravity Forms, Ninja Forms and WooCommerce product/cart forms are supported. Checkout, payment, login and account forms are never touched.
- AJAX requests – feedback for the requests you choose (admin-ajax.php actions, REST routes or URL patterns). Background, analytics and heartbeat requests never show anything. jQuery requests are observed through jQuery’s own events; watching
fetch()/XMLHttpRequestis opt-in. - WooCommerce – add-to-cart button spinner (classic and block buttons), variation lookups, cart updates, coupons, shipping, mini-cart removals and product filters.
- Progress indicators – top/bottom bar or corner ring. Indeterminate (or a clearly labelled estimate) when progress cannot be measured; real percentages only for measured upload/download progress.
- Skeleton placeholders –
[pagepulse_skeleton]shortcode and a Skeleton placeholder block: text, image, card, avatar, table, product, list and custom shapes, with wrapped content revealed when loading finishes. Optional shimmer placeholders for images.
Animation library
33 loaders in four groups, every one pure CSS (with a little SVG) and configurable in colour, size, speed, direction and intensity:
- Classic: circular spinner, dual ring, three dots, bouncing dots, pulse circle, rotating square, wave bars, bar loader, progress ring, orbit, ripple, minimal rotating line.
- Modern: gradient spinner, liquid fill, morphing shape, expanding rings, elastic dots, animated gradient border, glowing pulse, rotating gradient, smooth wave, minimal line.
- Brand: website logo, custom image, text shimmer, brand colours, custom SVG.
- Creative: typing, letter by letter, logo reveal, circular text, geometric, and a custom keyframes builder.
The seven transitions of PagePulse 0.1 are kept (slide top-bottom, slide bottom-top, fade, clip top/bottom, clip left/right, animated slides) plus zoom fade and none.
Dashboard
Settings → PagePulse has an overview, the animation library, loading triggers, a live builder with desktop/mobile preview and contrast check, ten presets plus your own, advanced settings, tools (frontend preview, compatibility diagnostics, recent errors, export/import, restore defaults, safe mode, temporary disablement) and developer documentation. The builder and its preview load only in the dashboard.
Accessibility
- Loading states are announced through a polite live region; busy regions get
aria-busy, buttonsaria-busyandaria-disabled, progress barsrole="progressbar"with real values only. - Visitors who prefer reduced motion get a static indicator with text, a gentle fade or text only (your choice).
- Esc closes a full-screen loader; Tab dismisses the page-load overlay. Keyboard users are never trapped.
- The page-load overlay is decorative: content underneath stays available to screen readers.
Works with
Tested with WordPress 5.8, 6.1 and 7.1 on PHP 7.4 and 8.4; block and classic themes (Twenty Twenty-Five, Twenty Twenty-One, Storefront, Astra); Gutenberg, Elementor, WooCommerce (block and classic shop, classic cart), Contact Form 7, WPForms, Ninja Forms and the AJAX Loading plugin (1.1, and the 2.x event contract). The Gravity Forms integration (AJAX iframe mode) follows that plugin’s documented events. Caching and optimisation plugins are supported (see FAQ). PagePulse stays out of page-builder editing canvases (Elementor, Beaver Builder, Divi, Bricks, Oxygen).
AJAX Loading integration
When AJAX Loading is active, it loads the content and PagePulse shows the transition. PagePulse listens to AJAX Loading’s lifecycle events (wp_ajax_load_start, wp_ajax_load_complete, wp_ajax_load_error, wp_ajax_load_cancel in 2.x; History.js state changes in 1.x), keeps a single overlay (AJAX Loading’s own indicator and 1.x page dimming are not shown at the same time) and respects PagePulse’s link exclusions. Neither plugin requires the other. Turn the integration off under Loading triggers → Page navigation.
For developers
window.PagePulse (no dependencies):
const h = PagePulse.show({ type: 'dots', text: 'Saving…' }); h.hide();
PagePulse.element.show('.product-container');
PagePulse.element.hide('.product-container');
PagePulse.button.show('#save', { text: 'Saving…' });
PagePulse.progress.set(60); // measured progress only
PagePulse.track(fetch(url), { target: '#results' });
Loaders are reference counted (finishing one operation never hides a loader another operation still needs) and every loader times out on its own. Data attributes (data-pagepulse, data-pagepulse-target…), DOM events (pagepulse:start/pagepulse:end in, pagepulse:show/hide/timeout… out) and PHP hooks (pagepulse_should_load, pagepulse_frontend_config, pagepulse_animations, pagepulse_presets, pagepulse_overlay_markup…) are documented on the Developers tab and in DEVELOPERS.md.
Privacy
PagePulse loads no remote files, sets no cookies and sends nothing to third parties. “Only on the first page of a visit” uses the browser’s sessionStorage. Debug mode records PagePulse’s own JavaScript errors for administrators only.
Configuration guide
- Animations – choose a loader and the overlay transition. Brand loaders use your site title, logo, an image or an SVG.
- Loading triggers – decide when PagePulse appears: initial loading (pages, devices, timing), navigation (overlay, progress bar, scope and exclusions), element rules, forms, AJAX rules, WooCommerce.
- Design – background (colour, gradient, opacity, blur), colours, size, speed, layout (full-screen, floating panel, top of page), message, logo, timing, progress indicator, reduced-motion and mobile behaviour, skeleton colours. Everything previews live; Save as preset stores a design.
- Advanced – administrators only, safe mode, debug mode, URL exclusions, custom CSS (requires the
edit_csscapability). - Tools – frontend preview, diagnostics, recent errors, export/import, restore defaults, temporary disablement.
Clear your page cache after changing settings.
Element loader
Mark an element and call the API:
<div class="product-container" data-pagepulse="true" data-pagepulse-loader="dots">…</div>
<button data-pagepulse-target=".product-container">Load more</button>
The button shows a loader on .product-container until its content changes (or the maximum time). Without code, add a rule under Loading triggers → Element loading: while the page loads, after a click until the content changes or during matching AJAX requests.
Skeletons
[pagepulse_skeleton type="card" count="3" /]
[pagepulse_skeleton type="product" count="4" columns="4" until="load"]…your content…[/pagepulse_skeleton]
Types: text, image, card, avatar, table, product, list, custom. Options: count, lines, rows, columns, width, height, until (load, delay, manual), delay, max, label, class. Use the self-closing form (/]) when a page mixes standalone and wrapping skeletons. Standalone placeholders are replaced by your script (PagePulse.skeleton.replace(el, html)) or removed after max milliseconds.
Installation
From the Plugins screen
- Plugins → Add New, search for “PagePulse”, install and activate.
- Settings → PagePulse → Overview → Turn on PagePulse.
- Pick an animation (Animations tab) or a preset (Presets tab), check it with Preview on site, then save.
Manually
- Upload the
pagepulsefolder to/wp-content/plugins/. - Activate it under Plugins and continue with step 2 above.
FAQ
Will this make my site faster?
No. Loaders change how waiting feels, not how long it takes. PagePulse is built not to add to the wait: without jQuery, with CSS-only animations and a deferred script, the recommended setup added about 2 ms of script time and 17.6 KB of compressed files to a test page (PagePulse 0.1 added jQuery: 35.9 KB and 14 ms). The page-load overlay hides as soon as the page is ready unless you set a minimum display time.
The loader covers my page for too long
Set Hide when to “The page is ready”, lower Maximum display under Loading triggers → Initial page loading, or turn the initial loader off and keep navigation feedback only.
A loader never disappears / something conflicts
Every loader has a maximum duration, so it cannot stay forever. To investigate: Tools → Safe mode (only the navigation progress bar and the API run), turn on debug mode (Advanced) and check the browser console and Tools → Recent errors, run Tools → Diagnostics. Emergency switches: add ?pagepulse-off to a URL, or define( 'PAGEPULSE_DISABLE', true ); in wp-config.php.
Does it work with page caching?
Yes. Device rules and “once per visit” are decided in the browser. Clear the cache after changing settings. If your optimisation plugin delays JavaScript, exclude “pagepulse”; the early snippet already carries data-no-optimize, data-no-defer and data-cfasync="false".
My theme does not call wp_body_open()
The overlay is then printed in the footer and a plain background covers the page until it is ready. Diagnostics shows which case applies.
Does it work on multilingual sites?
Yes. Default texts (“Loading…”, “Sending…”) follow the site language. Custom texts (message, loader text, button texts) are registered with WPML String Translation and Polylang (Languages → Translations, group “PagePulse”) and shown in the visitor’s language.
Can I hide PagePulse on some pages?
Advanced → Exclusions (URL patterns), the pagepulse_should_load filter, the class no-pagepulse or data-pagepulse="false" on links and forms.
Will my 0.1 settings survive?
Yes. On upgrade the 0.1 settings (on/off, effect, background colour and opacity) are migrated and the site keeps looking as before: the coloured overlay without a loader inside, shown until the page has loaded, on link navigation and on form submission. A copy of the original 0.1 settings is kept.
How do I roll back to 0.1?
Install 0.1 again: it reads the same option, which PagePulse 1.0 keeps up to date (on/off, effect, colour, opacity). Settings that only exist in 1.0 are kept in a backup and restored when you upgrade again.
Screenshots









Changelog
1.0.1
- Updated: new PagePulse logo on the settings screen, matching the new plugin icon and banner.
1.0.0
- New: 33 CSS loaders in four categories, configurable colour, size, speed, direction and intensity; custom keyframes builder; custom SVG, image, logo and text loaders.
- New: trigger engine – initial page loading with page, post type, URL and device targeting; navigation loader with scope and exclusions; element loader; form submission feedback; AJAX request rules; WooCommerce events.
- New: progress bar and ring (indeterminate, labelled estimate, or measured), skeleton shortcode and block, image placeholders.
- New: dashboard with overview, animation library, live builder, ten presets and custom presets, diagnostics, export/import, safe mode, temporary disablement, recent errors and developer documentation.
- New: JavaScript API (
window.PagePulse), DOM events, data attributes and PHP hooks. - New: AJAX Loading integration (1.x and 2.x).
- New: accessibility – live region announcements, aria-busy, progress semantics, reduced-motion options, Esc/Tab dismissal.
- Improved: no jQuery on the frontend; deferred script; only the CSS of loaders in use; no
unload/beforeunloadhandlers (back/forward cache works). - Fixed: the page could stay covered when JavaScript failed, a form was submitted with AJAX or validation, a download started, or the page was restored from the back/forward cache.
- Fixed: “Slide bottom-top” was not shown as selected and was overwritten on save.
- Fixed: admin styles and scripts loaded on every dashboard page; the overlay was printed inside
<head>; settings were saved without a capability check. - Upgrade: 0.1 settings are migrated without changing how the site looks; rollback to 0.1 keeps working.
0.1
- Initial Public Release
