Breeze – WordPress 快取外掛

描述

Breeze 由 Cloudways 團隊所開發,是個輕巧、功能強大且方便使用的 WordPress 快取外掛。它提供了各種設定來為不同層級的 WordPress 效能進行最佳化,且同時適用於 WordPress、WooCommerce 及多站點。

Breeze 在以下幾個方面表現優異:

  • 效能:Breeze 除了能改進網站速度及主機資源最佳化外,還包含了檔案層級快取系統、資料庫清理、最小化、支援 Varnish 快取及簡化 CDN 整合設定等功能。

  • 便利:在 WordPress 網站中,直接安裝及設定 Breeze 相當容易。設定 Breeze 相當簡單,且按照預設值便能在多數的環境中運作良好。建議設定應該能在所有 WordPress 網站上無痕般的運作。

  • 簡單:Breeze 設計成要讓所有人都能輕鬆上手。僅需安裝並啟用這個外掛,便能立刻體驗到絕佳的效果。

Breeze 內建 Varnish 支援是它成為表現優異的 WordPress 快取外掛的主要原因。如果你的主機並未安裝 Varnish,Breeze 依舊能透過內部快取機制,大幅提昇 WordPress 網站的效能。

技術支援:我們樂於提供技術支援!請在我們的 WordPress.org 技術支援論壇進行提問,如果你是我們 Cloudways 的客戶,你可以在 Cloudways 社群論壇提出問題。

特別感謝:特別值得一提的是,WP Speed of Light 對 Breeze 所帶來的啟發。

環境需求

為獲得較佳效能表現,建議採用 PHP 5.3 以上版本、PHP7 或 7.1、還有 WordPress 4.5 以上版本

Installation

透過 WordPress 控制台安裝外掛:

  • 在 WordPress 管理後台的選單上,按一下 [外掛] -> [安裝外掛]。
  • 以 Breeze 為關鍵字進行搜尋。
  • 搜尋到 Breeze 外掛後按一下 [安裝] 直至安裝完畢,然後按一下 [啟動]。

手動安裝外掛:

  • 下載並解壓縮外掛壓縮檔。
  • 上傳 breeze 資料夾至 /wp-content/plugins/ 遠端主機目錄中。
  • 透過 WordPress 的 [外掛] 選單啟用外掛
  • 從 WordPress 管理後台 -> [設定] -> [Breeze] 進行設定。

常見問題

安裝說明

透過 WordPress 控制台安裝外掛:
1. 在 WordPress 管理後台的選單上,按一下 [外掛] -> [安裝外掛]。
2. 以 Breeze 為關鍵字進行搜尋。
3. 搜尋到 Breeze 外掛後按一下 [安裝] 直至安裝完畢,然後按一下 [啟動]。

手動安裝外掛:
1. 下載並解壓縮外掛壓縮檔。
2. 上傳 breeze 資料夾至 /wp-content/plugins/ 遠端主機目錄中。
3. 透過 WordPress 管理後台的 [外掛] 選單啟用外掛。
4. 從 WordPress 管理後台 -> [設定] -> [Breeze] 進行設定。

Breeze 是否支援 Varnish?支援到哪個程度?

Breeze 預設支援 Varnish,且完全相容於 Cloudways 已預先安裝 Varnish 的伺服器。如果你使用的主機並非由 Cloudways 所提供,建議向你的主機託管服務提供商洽詢關於 Varnish 的支援。

Breeze 是否支援 WooCommerce?

Breeze 與 WooCommerce 完全相容,安裝啟用後即可開始執行,且無須進行任何特殊設定。

Breeze 是否支援 WordPress 多站點功能?

Breeze 與 WordPress 多站點功能完全相容,且無須進行任何額外設定。

Breeze 如何處理 WordPress 多站點網站的快取?

Breeze 統一處理所有 WordPress 多站點中所有網站的快取。所有針對多站點的設定,均屬於超級管理員層級。

Breeze 是否與其他 WordPress 快取外掛相容?

我們並不建議在任何 WordPress 網站上同時使用兩個快取外掛。
我們強烈建議在網站上使用 Breeze,將它作為唯一的快取外掛。如果網站上使用了其他快取外掛,請確保在安裝 Breeze 前已將其停用。

Breeze 是否與 HTTPS 相容?

Breeze 無須任何特殊設定,便能同時處理 HTTP 與 HTTPS 頁面。

Breeze 是否與其他外掛有相容性問題?

Breeze 已與 WordPress.org 上知名的外掛進行過相容性測試,如有任何相容性問題,請在 WordPress 技術支援論壇或 Cloudways 社群論壇回報。

Breeze 是否支援 CDN?

Breeze 支援 CDN 整合,整合後便可由 CDN 處理它所產出的所有靜態檔案,如圖片、CSS 以及 JS 檔。

Breeze 的資料庫最佳化功能作用為何?

眾所周知,WordPress 資料庫儲存了文章版本以及垃圾迴響等資訊。網站經營一段時間之後,資料庫便會變的臃腫龐大;定期清除資料庫中不需要的資訊,是減少資料庫大小及增進最佳化的最佳方式。

Breeze 的資料庫最佳化功能,能夠讓你一鍵清除所有不必要的資料。

啟用 Breeze 快取外掛後,網站上的迴響及其他動態產生的內容會即時顯示嗎?

迴響能否即時顯示,會依照網站管理員對迴響系統的設定或稽核原則而定;而對動態內容所進行的變更,則必須進行完整的快取清除操作後才能顯示。

是否能從快取中排除個別檔案及頁面的網址?

Breeze 的設定提供了設定排除項目的欄位,透過提供檔案網址或檔案類型 (也就是檔案的副檔名) 便能從快取中加以排除。Breeze 不會對排除在外的項目進行快取。

Varnish 啟用後,你會需要在 Varnish 設定中將網址及檔案類型加以排除。如果你的 WordPress 網站託管於 Cloudways 提供的伺服器,請參閱這篇知識庫文章以瞭解如何從 Varnish 快取機制中排除特定網址內容。

Breeze 可以執行於各家主機服務提供商的主機嗎?

Breeze 在主要的主機服務提供商都進行過測試。此外,Breeze 的主要功能如 Gzip、瀏覽器快取、檔案最小化、資料庫最佳化及 CDN 整合,在所有主機均能正常執行。

我在何處可以取得 Breeze 外掛的技術支援?

你可以在 WordPress 技術支援論壇上提出問題並得到回覆。如果你是 Cloudways 的客戶,隨時可以在 Cloudways 社區論壇進行討論。

我如何測試及驗證 Breeze 的快取效果?

你可以近乎即時的觀察到 Breeze 快取外掛對網站的加速效果,我們也建議使用下列工具產生指標報告藉以評估成效:
Google Page Speed
WebPagetest
Pingdom

Breeze 是否能與各款視覺化編輯器一起執行?

是的,Breeze 相容於各款視覺化編輯器。

Breeze 支援哪些熱門的 CDN?

Breeze 支援下列 3 個熱門的 CDN:
MaxCDN
KeyCDN
Amazon Cloudfront

Breeze 是否支援主動式 CDN?

否,Breeze 不支援主動式 CDN,但你可以透過第三方外掛讓 Breeze 與主動式 CDN 同時執行。

Breeze 是否能與 CloudFlare 一起執行?

可以。要讓 CloudFlare 與 Breeze 一起執行的設定程序相當簡單,請參閱這份知識庫文章以取得詳細資訊。

Breeze 如何運用 Gzip 功能?

啟用 Gzip 功能後,Breeze 便能壓縮使用者請求的檔案、進一步減少下載檔案的大小,藉以加速以提昇使用者體驗。

Reviews

Pretty good plugin, great support

I think the plugin is great. It is really simple, which saves a lot of configuration trouble. Also, in just a few clicks you have set up CDN, Varnish and page caching. And it works for sure. Cut our page load time at least in half. We now have a rather heavy website loading in 1 – 1,5 sec.

I had a small issue, but cloudways solved it for me after I contacted them about it.

The only thing I would recommend cloudways to improve is the compilation of CSS and JS files. It seems like every page, or at least a lot of pages, generate different CSS files. While imo the same stylesheet could be used accross the whole page.

I don’t know how this works. Maybe it is inline CSS or something that is added to the dynamic CSS file, which is why the plugin creates a different CSS file. Not sure what happens, but if I check my NET console I can see that there are multiple CSS files with different names being generated across different pages. The reason one wouldn’t want this is of course because of browser caching. Now a new page sometimes loads a new CSS file, which actually is the same (should be).

I am of course curious to hear if CloudWays has something to tell about this?

Impressive speed gains. Less than 1 sec load times. On Cloudways hosting plan.

I tried this plugin mainly because I develop a site which hosts via Cloudways. But these poor review were a bit shocking to me. So I was slow to give it a try…

That said, I love this plugin. It’s simple, fast and straightforward. True, there are some advanced options missing, but it makes setting Breeze up on multiple sites very, very simple.

My pagespeed grade on my Cloudways-hosted site has gone from the 60s to 90s and, along with a few other small tweaks, I have my page load speed down to about less than 1 sec. Impressed!

BUT… This plugin also breaks a Dreamhost site I develop, so it’s not for everyone. Maybe it’s only meant for Cloudways customers?

there are still some bugs in multisite setup

all sites in multisite setup use the same breeze-config.php. Each site should has it own breeze-config.php.

For example: I have multisite setup a.com (woocommerce activated) and b.com (no woocommerce)

1.network activate Breeze plugin
2.go to site a.com dashboard > Breeze setting > save changes. The breeze-config.php will be written with exclude_url array like this

‘exclude_url’ => array ( 0 => ‘/checkout/(.*)’, 1 => ‘/cart/’, 2 => ‘/my-account/(.*)’ )

3.go to site b.com dashboard > Breeze setting > save changes. The breeze-config.php will be overwrite with exclude_url array like this

‘exclude_url’ => array ( )

Please consider and fix this issue on next update.

CORS Policy is still blocked

This is extremely disappointing…. I left a review on the first week of using for this very same issue, and as it was the first review that was left, you guys had it removed, even though it was a genuine concern. Shame on you cloudways

The ironic thing is, this is an issue with your own cloudways servers!

MONTHS down the line, and this issue still has not been fixed. All fonts that are loaded from within the same application is refused with the error

Access to Font at ‘xxxxxxx’ from origin ‘xxxxxxx’ has been blocked by CORS policy: No ‘Access-Control-Allow-Origin’ header is present on the requested resource. Origin ‘xxxxxxx’ is therefore not allowed access.

This was meant to be fixed as was promised with the reply on the review, before it was removed.

Plugin contains viruses

I was using this plugin from last few months. I checked my website today on sucuri safeguarde etc. and found that this breez plugin is inserting virus script, starting with apu.php

I removed this plugin completely and again checked my website now its seems clean.

It’s basically Autoptimize, but worse…

I was expecting a lot more from the Breeze cache to be honest. A poor performance by Cloudways.

Still many simple bugs which need to be ironed out, seems like plugin is not tested before new editions are released.

The plugin is based off autoptimize plugin, yet has only a fraction of the original plugin features, with some very basic features missing…

Cons

– Combined JS files are loaded in head as render blocking, no option to load in footer or even to add defer/async tags
– since the last update, when in the admin area, in the top bar the ‘Purge All Cache’ link doesn’t work.
– When combining JS files, only selective scripts are combined.
– Combining of JS files can often result in 2 or more combined files, whilst it does reduce the number of external requests, why not combine into 1 file like so many other plugins can?

When you raise issues with support, you get fobbed off to have a look at documentation, even when you’ve clearly specified exactly what the issue is. I did eventually get a response though that told me to manually combine javascript files the plugin did not catch… wow. I’ll just uninstall and use a plugin which works. Thanks.

Very disappointed.

My advice: just stick with Autoptimize and use a second plugin to handle varnish purging if you have it enabled.

閱讀全部 25 評論

貢獻者與開發者

“Breeze – WordPress 快取外掛” is open source software. The following people have contributed to this plugin.

貢獻者

“Breeze – WordPress 快取外掛” has been translated into 3 locales. Thank you to the translators for their contributions.

Translate “Breeze – WordPress 快取外掛” into your language.

Interested in development?

Browse the code, check out the SVN repository, or subscribe to the development log by RSS.

Changelog

1.0.9

  • 新增:[將 JS 檔案移至頁尾] 功能
  • 新增:[延後載入 JS 檔案] 功能
  • 新增:[包含內嵌 CSS] 功能
  • 新增:[包含內嵌 JS] 功能

1.0.8

  • 修正:為傳回狀態碼並非 200 的頁面排除快取

1.0.7

  • 修正:PHP 7.1 的 [合併檔案] 及 [最小化] 問題
  • 修正:版本更新後清除快取問題
  • 修正:增加快取檔案大小問題
  • 修正:找不到伺服器錯誤通知
  • 修正:預設 WordPress 迴響顯示無須清理快取

1.0.6

  • 修正:所有多站點網站,僅會以超級管理員層級所進行的設定執行快取運作

1.0.5

  • 修正:JS 最小化的問題

1.0.4

  • 修正:WooCommerce 工作階段的快取問題
  • 修正:停用 Gzip/瀏覽器快取後,清理 .htaccess 中的 Breeze 規則
  • 修正:修正規則運算式,以便接受啟用 [最小化] 功能後,來源網址首尾不含引號
  • 新增:加入 [常見問題集] 標籤頁內容

1.0.3-beta

  • 修正:停用 WooCommerce 購物車、商店及帳號頁面的瀏覽器快取
  • 修正:停用瀏覽器快取及 Gzip 壓縮功能後,移除 .htaccess 內的相關設定
  • 修正:CDN 服務未提供全部設定內容的 CDN 問題

1.0.2-beta

  • 修正:與 WooCommerce 的相容性問題

1.0.1-beta

  • 修正:快取清除問題。僅管理員具有清除快取的權限
  • 新增:[意見反應] 連結

1.0.0

  • 新增:首個 Beta 版