內容簡介
CacheVanta Performance Toolkit 是一款獨立的效能工具包，所有處理都在您的 WordPress 主機上進行，無需帳戶、API 金鑰、CDN、付費訂閱或外部優化服務。此外掛旨在提升網站效能，簡化快取管理。
【主要功能】
• 支援公共 GET 請求的選擇性快取
• 自動排除登入用戶及特定請求
• WooCommerce 特定快取排除
• 快取失效管理功能
• 本地 WebP 圖片生成
• 手動清理修訂版和過期資料
外掛標籤
開發者團隊
② 後台搜尋「CacheVanta Performance Toolkit」→ 直接安裝（推薦）
原文外掛簡介
CacheVanta Performance Toolkit is a self-contained performance toolkit. All processing happens on your WordPress hosting. It requires no account, API key, CDN, paid subscription, or external optimization service.
Features include:
Opt-in page caching for eligible public GET requests.
Automatic cache exclusions for logged-in users, previews, searches, feeds, REST requests, personalized cookies, and requests with query strings.
WooCommerce cart, checkout, account, endpoint, API, and session exclusions.
Cache invalidation when posts, comments, menus, themes, widgets, or relevant settings change.
Optional cache preload of up to 100 recently modified public URLs in small WP-Cron batches.
Conservative HTML minification.
Optional script deferring with built-in core and WooCommerce exclusions.
Native iframe lazy loading for post and widget content.
Optional featured-image preload hints.
Local WebP generation for new Media Library JPEG and PNG files when the host supports WebP.
Emoji, embed, guest Dashicons, and Heartbeat controls.
Manual cleanup for revisions, auto drafts, trash, spam, and expired transients.
Settings import and export.
Local environment, image-support, and cache-conflict diagnostics.
Potentially compatibility-sensitive features are disabled by default. Enable one feature at a time and test the public website, forms, interactive elements, and complete WooCommerce purchase flow.
CacheVanta Performance Toolkit does not collect or transmit personal data. The cache preloader makes loopback requests only to public URLs on the same WordPress site.
Privacy
CacheVanta Performance Toolkit does not collect, store, or send analytics, visitor information, site content, or administrator details to its developer or any third party. Page-cache entries and settings remain inside the site’s own WordPress database. Cache preload requests target the same site’s public URLs.
