| 开发者 | kinetichub |
|---|---|
| 更新时间 | 2026年9月6日 18:23 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
wp_body_open, with a wp_footer fallback), so it works with classic themes, block themes, and page builders that render normal frontend pages. Session and daily frequency are tracked in the browser, so pages stay cacheable alongside caching and performance plugins, and the loader includes failsafe handling for setups that delay frontend JavaScript.
Lightweight and accessible
prefers-reduced-motion by collapsing animations to an instant transitionaria-hidden visual overlay with no focus trap, so keyboard focus stays on the page belownoscript fallback hides the loader for visitors with JavaScript disabledInstall and activate KineticHub Page Loader, then go to Settings -> Page Loader. Enable the loader, add your logo or text, pick a preset and the options you want, and save. The loading screen appears on the next frontend page load.
Yes. Upload any image from the WordPress Media Library. If no logo is set, a text fallback is shown instead, defaulting to your site name. You can add logo reveal effects (fade, grayscale to color, soft scale, shine sweep, zoom bloom, mask reveal), logo shapes (original, rounded, circle), and an animated loading ring.
Yes. Smart Progress offers Top Bar, Bottom Line, Logo Ring, Center Glow Line, and Minimal Percentage styles, or None. This is simulated visual progress: a timed animation, not a measurement of the actual network loading percentage.
Yes. Show it site-wide or on the homepage only, to everyone or to visitors only, and exclude specific post/page IDs, URL paths, or WooCommerce cart, checkout and account pages. Desktop and mobile visibility are independent.
Yes. Show frequency can be every page load, once per session, or once per day. On repeat views within that window the loader is suppressed before it can paint, so there is no flash of a loading screen.
It is designed to. WooCommerce cart, checkout, and account pages can be excluded with one toggle, and the loader is theme- and builder-agnostic because it renders through normal WordPress frontend hooks. Frequency tracking happens in the browser, so pages stay cacheable, and failsafe handling covers setups that delay frontend JavaScript. Third-party configurations vary, so compatibility with every possible combination cannot be guaranteed.
No. It changes the visual loading experience and perceived presentation. It does not reduce server response time or optimize your assets.
Yes. When prefers-reduced-motion: reduce is set, animations collapse to an instant transition. The overlay is marked aria-hidden so screen readers skip it, there is no focus trap, and the loader is removed from the DOM after hiding. With JavaScript disabled, a noscript block hides the loader so the page is never blocked.