內容簡介
fepo Image & Font Optimizer 外掛可將圖片壓縮為 WebP 和 AVIF 格式，並在本地伺服器上進行轉換，無需將圖片上傳至外部伺服器，確保安全性與隱私。此外掛提供免費的優化次數，並能有效提升網站載入速度。
【主要功能】
• 本地轉換圖片為 WebP/AVIF
• 支援 PHP-Imagick，無限次免費轉換
• 50 次免費優化，無需註冊帳號
• 自動保留原始圖片作為備份
• 針對重要圖片優化載入順序
• 網頁字型在本地子集化，無需外部請求
外掛標籤
開發者團隊
② 後台搜尋「fepo Image & Font Optimizer – Compress Images to WebP/AVIF locally」→ 直接安裝（推薦）
原文外掛簡介
Compress your images to WebP and AVIF without sending them anywhere. If your server has
PHP-Imagick, the conversion happens right there — unlimited and free, and your images never
leave your server.
Our “Server environment” test shows you if PHP-Imagick is enabled. It runs a real test
conversion, so you see whether your server can actually create AVIF and WebP — not just whether
the extension is loaded. If it cannot, everything still works: fepo converts your images instead,
free of charge (fair-use daily limit; large batches may wait in the queue). Local conversion is
faster — ask your hosting provider to enable PHP-Imagick.
Fonts are different: subsetting needs the characters your site uses (collected locally from your
published content, sent as a list of code points only), so it always
runs on fepo’s servers and uses credits. PHP cannot create WOFF2 files.
Every site starts with 50 free font optimizations — no purchase, no account required. After that,
one-time credit packs keep you going, and credits never expire. Images never use credits. Optimised files live on your own
server — no CDN, no monthly lock-in, and deactivating never breaks the site.
The most important image loads first. The second image in the page gets
fetchpriority=”high” — usually the LCP element, the one Core Web Vitals
measures. Everything below it is deferred with loading="lazy". Your theme’s
own loading attribute is always respected, and an image already marked as
high priority is never lazy-loaded.
Originals are always kept as a fallback, so a page can never break.
Coming soon: automatic conversion to WebP/AVIF on upload.
How it works: tags are wrapped in
fallback), CSS background-images are served as AVIF via an injected style block, and web fonts
are subsetted and served locally — with the theme’s Google Fonts request removed, so no visitor
IP is sent to Google for fonts.
What gets optimised — and what doesn’t
So you know exactly what to expect — we’d rather under-promise:
Images from 10 KB are converted to WebP/AVIF (original kept as fallback). Smaller images
are left unchanged — the gain isn’t worth it.
CSS background-images (raster jpg/png) are served as AVIF via an injected style block
(no edits to your CSS).
Google Fonts from 50 KB are subsetted to the characters your pages actually use and
served locally; the matching Google Fonts is removed (closing the GDPR concern of
visitor IPs going to fonts.googleapis.com). All weights of a family come in one file.
Smaller Google Fonts, italic styles and families without a variable master file are not
subsetted — the plugin copies Google’s files 1:1 to your server instead (no credits), so the
Google request still goes away.
Fonts from other providers (Adobe Fonts, MyFonts and the like) cannot be subsetted —
their master files are not publicly available. They are reported, not changed.
Already-optimal formats are left untouched: images already served as AVIF, and SVG
(vector — stays as-is).
Only assets from your own domain are optimised. Images and fonts embedded from third
parties (maps, external widgets, etc.) are never touched — they stay on their original server.
Known limits: images injected by JavaScript after page load (some sliders/lazy-loaders)
and background
External services
This plugin connects to two external services. Both are described below.
1. portal.fepo.app (fepo optimization service)
Operated by fepo, this service generates optimized images and subsetted fonts.
Font subsetting always runs on fepo’s servers. The plugin detects your Google Fonts locally and collects the characters your site uses locally from published content; fepo’s server never fetches your pages for this. Image conversion runs on fepo’s servers only when
your own server cannot do it — with PHP-Imagick available, images and CSS background images are
converted locally and their URLs are never sent anywhere.
What is sent and when:
When you optimize fonts: the names and weights of the detected Google font families, so fepo’s server can download them from Google Fonts and subset them.
When you optimize fonts (since 1.3.0): the set of characters your site uses, as a list of Unicode code points (numbers, not text), and your site’s language. The plugin collects them locally from the published and scheduled content in your WordPress database and sends no text, no word order, and nothing from drafts or private posts. fepo adds these characters to its base character set so the subsetted font covers what your site really shows; at most 2000 characters are used, beyond that the base set plus language applies.
When images or CSS backgrounds have to be converted by fepo (no PHP-Imagick, or it could not produce a smaller file): the URLs of those images, so fepo’s server can fetch and process them. Images converted locally are not sent.
An anonymous site hash and your site’s hostname, so your credit balance is tied to your account.
After a run was downloaded and unpacked successfully: the ID of that run, so fepo can delete its temporary copy of the optimized files right away.
Once a day, while the plugin is active: the same anonymous site hash, as a sign that this installation is still in use. Accounts with no activity for 60 days are deleted automatically (data minimisation), and since images are now converted locally there may otherwise be no contact for months. This daily signal starts only after an account exists and stops when you deactivate the plugin.
With that daily signal (since 1.1.6): five technical values about your server — the ImageMagick major version (or that it is missing), whether the PHP extension imagick is loaded, whether AVIF and WebP can be written, and the PHP version (e.g. “8.2”). No domain, no file paths, nothing personal. fepo stores them only as anonymous daily totals (“so many sites have AVIF”), never linked to your site, to learn how many hosts can convert images locally.
What is NOT sent: no personal data of your visitors, no text from posts, pages, or comments (only the character list described above), no other database contents, and no file contents of images or fonts that are not being optimized.
Image conversion is performed by fepo’s server fetching the given image URLs (like any browser would) and returning WebP/AVIF images; fonts are subsetted from the font families and character list you send and returned as subsetted files. No private endpoints are accessed. The optimized files are then stored on your own server — not on a CDN — and delivered directly from there.
You must explicitly consent to this data transmission via a checkbox before the first optimization. The consent applies to this plugin and its own wording only — a consent given in another fepo plugin does not count here. It is stored locally and can be withdrawn at any time with the “Withdraw consent” link on the plugin page; this stops all transmission to portal.fepo.app, including the daily signal. Already optimized files stay on your server and keep being delivered.
Terms of service: https://fepo.app/agb
Privacy policy: https://fepo.app/datenschutz
2. Google Fonts (fonts.googleapis.com)
To show the real download size of a Google Font on the Fonts tab, the plugin asks Google’s Fonts API — from your WordPress server, in wp-admin — how large the browser-loaded WOFF2 files for a given font family are.
What is sent and when: only the font family name and its weights (e.g. “Roboto” with weights 400,700), and only while you are viewing the Fonts tab in the admin. No visitor data, no personal data, and no site content are sent. The request is made server-to-server (from your host to Google), not from your visitors’ browsers.
Copying fonts to your server: when you click “Optimize fonts”, fonts that are not subsetted (under 50 KB, italic styles, families without a variable master file) are downloaded once from Google (fonts.googleapis.com for the CSS, fonts.gstatic.com for the WOFF2 files) to your uploads folder and served from there. Only the family name, weights and style are sent; afterwards your visitors no longer contact Google for these fonts.
Terms of service: https://policies.google.com/terms
Privacy policy: https://policies.google.com/privacy
Disclaimer
This plugin is provided “as is”, without warranty of any kind. fepo is not liable for any damage, data loss, or downtime arising from its use. Your originals are always kept as a fallback, so an optimization can never break your page.
