MeteorGPLby WebbingApps

WP-Optimize Premium - Clean, Compress, Cache

Plugin
Seguir 0 Dar estrella 0
Instalar

Get caching and more with this powerful cache plugin. Cache, optimize images, clean your database and minify for maximum performance.

  • 0 estrellas
  • 0 seguidores
  • 0 descargas
  • Licencia no declarada

Versiones 0

Las más recientes primero · cada versión se analiza antes de publicarse
Mostrar 146 versiones aún no disponibles

Lanzamientos que figuran en el registro de cambios del proveedor o en WordPress.org y que el repositorio aún no tiene.

  1. 4.7.0 Aún no disponible Fecha de lanzamiento no indicada

    FEATURE: Dashboard overview showing a summary of all WP-Optimize modules (cache, images, minification, and database), including active statu...

    Entrada del registro de cambios

  2. 4.6.1 Aún no disponible Fecha de lanzamiento no indicada

    FIX: CSS exclusions added via Minify -> Advanced -> Exclude are now saved on separate lines, preventing invalid exclusion entries

    Entrada del registro de cambios

  3. 4.6.0 Aún no disponible Fecha de lanzamiento no indicada

    FEATURE: Premium - Automatically preloads the page’s Largest Contentful Paint (LCP) element to improve initial load speed and perceived perf...

    Entrada del registro de cambios

  4. 4.5.5 Aún no disponible Fecha de lanzamiento no indicada

    TWEAK: Update the bundled common-libs version

    Entrada del registro de cambios

  5. 4.5.4 Aún no disponible Fecha de lanzamiento no indicada

    FIX: WebP image compression breaking in some cases

    Entrada del registro de cambios

  6. 4.5.3 Aún no disponible Fecha de lanzamiento no indicada

    SECURITY: Prevented path traversal security risk. Thanks to Wordfence for the responsible disclosure

    Entrada del registro de cambios

  7. 4.5.2 Aún no disponible Fecha de lanzamiento no indicada

    FIX: Bug pregmatch() fails on wildcard patterns in browser agents exclusion list

    Entrada del registro de cambios

  8. 4.5.1 Aún no disponible Fecha de lanzamiento no indicada

    FIX: Fixed compatibility issue with WP Remote

    Entrada del registro de cambios

  9. 4.5.0 Aún no disponible Fecha de lanzamiento no indicada

    FEATURE: Premium - Cache – Added ability to cache only selected URLs

    Entrada del registro de cambios

  10. 4.4.1 Aún no disponible Fecha de lanzamiento no indicada

    FIX: Onboarding wizard RTL issue

    Entrada del registro de cambios

  11. 4.4.0 Aún no disponible Fecha de lanzamiento no indicada

    FEATURE: Added Onboarding Wizard

    Entrada del registro de cambios

  12. 4.3.1 Aún no disponible Fecha de lanzamiento no indicada

    FIX: Prevent PHP fatal error occurring when cache is enabled and the "Aelia Currency Switcher for WooCommerce" plugin is active

    Entrada del registro de cambios

  13. 4.3.0 Aún no disponible Fecha de lanzamiento no indicada

    FEATURE: Premium - Cache - Cache REST API requests

    Entrada del registro de cambios

  14. 4.2.4 Aún no disponible Fecha de lanzamiento no indicada

    FIX: Potential PHP fatal error when no site is selected during database optimization in multisite

    Entrada del registro de cambios

  15. 4.2.3 Aún no disponible Fecha de lanzamiento no indicada

    FIX: Cache - Resolved PHP warning caused by excessively long cache file names

    Entrada del registro de cambios

  16. 4.2.2 Aún no disponible Fecha de lanzamiento no indicada

    FIX: Cache - Resolved unwanted output in WP-CLI and fatal error related to WooCommerce's country-specific files, introduced in v4.2.0

    Entrada del registro de cambios

  17. 4.2.1 Aún no disponible Fecha de lanzamiento no indicada

    FIX: Cache - Compatibility issue with other plugins due to late start of output buffering

    Entrada del registro de cambios

  18. 4.2.0 Aún no disponible Fecha de lanzamiento no indicada

    SECURITY: On multisite installs (only), a logged-in site administrator could use an unsanitised parameter to inject unwanted content into SQ...

    Entrada del registro de cambios

  19. 4.1.1 Aún no disponible Fecha de lanzamiento no indicada

    FIX: Page builders not working with Delay JS option enabled

    Entrada del registro de cambios

  20. 4.1.0 Aún no disponible Fecha de lanzamiento no indicada

    FEATURE: Premium - Improve performance by caching Gravatar images locally.

    Entrada del registro de cambios

  21. 4.0.1 Aún no disponible Fecha de lanzamiento no indicada

    FIX: File system usage issue

    Entrada del registro de cambios

  22. 4.0.0 Aún no disponible Fecha de lanzamiento no indicada

    FEATURE: Delay JavaScript execution

    Entrada del registro de cambios

  23. 3.8.0 Aún no disponible Fecha de lanzamiento no indicada

    FEATURE: Added a system status page

    Entrada del registro de cambios

  24. 3.7.1 Aún no disponible Fecha de lanzamiento no indicada

    TWEAK: Resolved a PHP notice caused by translation loading too early when caching is enabled, introduced in WordPress 6.7

    Entrada del registro de cambios

  25. 3.7.0 Aún no disponible Fecha de lanzamiento no indicada

    FEATURE: Added an option to automatically preload URLs immediately after cache content is purged

    Entrada del registro de cambios

  26. 3.6.0 Aún no disponible Fecha de lanzamiento no indicada

    FEATURE: Premium - Auto-detect images lacking dimension attributes and add them to improve CLS

    Entrada del registro de cambios

  27. 3.5.0 Aún no disponible Fecha de lanzamiento no indicada

    FEATURE: Premium - Host Google and minimal analytics scripts locally

    Entrada del registro de cambios

  28. 3.4.2 Aún no disponible Fecha de lanzamiento no indicada

    FIX: Removes unnecessary heartbeat calls for retrieving information about images

    Entrada del registro de cambios

  29. 3.4.1 Aún no disponible Fecha de lanzamiento no indicada

    FIX: Issue with bulk editing on the posts and pages edit screen

    Entrada del registro de cambios

  30. 3.4.0 Aún no disponible Fecha de lanzamiento no indicada

    FEATURE: Premium - Smush - Bulk compress / restore from media library

    Entrada del registro de cambios

  31. 3.3.2 Aún no disponible Fecha de lanzamiento no indicada

    FIX: Ensure the admin bar is not cached when caching is enabled for both logged-in and guest users

    Entrada del registro de cambios

  32. 3.3.1 Aún no disponible Fecha de lanzamiento no indicada

    FIX: Cache - Compatibility issue with Jetpack's infinity scroll feature

    Entrada del registro de cambios

  33. 3.3.0 Aún no disponible Fecha de lanzamiento no indicada

    FEATURE: Premium - Ability to preload and purge caches from individual post/page

    Entrada del registro de cambios

  34. 3.2.22 Aún no disponible Fecha de lanzamiento no indicada

    TWEAK: Cache - Show a notice in the admin if the config file is missing and caching is enabled

    Entrada del registro de cambios

  35. 3.2.21 Aún no disponible Fecha de lanzamiento no indicada

    FIX: Prevent PHP fatal error when updating from older versions of WP-Optimize

    Entrada del registro de cambios

  36. 3.2.20 Aún no disponible Fecha de lanzamiento no indicada

    FIX: WebP - Performance issue because of possible infinite loop

    Entrada del registro de cambios

  37. 3.2.19 Aún no disponible Fecha de lanzamiento no indicada

    FIX: Cache - Relevant caches are now purged upon updating homepage display settings and posts per page settings

    Entrada del registro de cambios

  38. 3.2.18 Aún no disponible Fecha de lanzamiento no indicada

    FIX: A bug in the v3.2.17 release that caused certain database optimization buttons to be disabled has been fixed

    Entrada del registro de cambios

  39. 3.2.17 Aún no disponible Fecha de lanzamiento no indicada

    FIX: Automatically compress newly-added images feature now works on multisite in case of attachment ID is the same in both sites

    Entrada del registro de cambios

  40. 3.2.16 Aún no disponible Fecha de lanzamiento no indicada

    FIX: HTML minify should not remove title tag added by AIOSEO

    Entrada del registro de cambios

  41. 3.2.15 Aún no disponible Fecha de lanzamiento no indicada

    FEATURE: Premium - Cache - Added compatibility with the "WooCommerce Multilingual & Multicurrency" plugin's multi-currency feature

    Entrada del registro de cambios

  42. 3.2.14 Aún no disponible Fecha de lanzamiento no indicada

    FIX: Compatibility with WordPress 6.2 when using PHP 8.x

    Entrada del registro de cambios

  43. 3.2.13 Aún no disponible Fecha de lanzamiento no indicada

    FEATURE: WebP - Ability to convert to webp format from media library

    Entrada del registro de cambios

  44. 3.2.12 Aún no disponible Fecha de lanzamiento no indicada

    SECURITY: Today's 3.2.11 release (free version only - there was no 3.2.11 Premium release) checked nonces incorrectly, opening up the possib...

    Entrada del registro de cambios

  45. 3.2.11 Aún no disponible Fecha de lanzamiento no indicada

    FIX: Empty query string updates cache

    Entrada del registro de cambios

  46. 3.2.10 Aún no disponible Fecha de lanzamiento no indicada

    FIX: Prevent php warning and increase SendInBlue mailin plugin compatibility

    Entrada del registro de cambios

  47. 3.2.9 Aún no disponible Fecha de lanzamiento no indicada

    FEATURE: Import and export settings

    Entrada del registro de cambios

  48. 3.2.8 Aún no disponible Fecha de lanzamiento no indicada

    FIX: Build system error led to a missing file in 3.2.7 which could cause an error when using related functions

    Entrada del registro de cambios

  49. 3.2.7 Aún no disponible Fecha de lanzamiento no indicada

    FEATURE: A CLI command for generating lists of unused images as a CSV file (Premium)

    Entrada del registro de cambios

  50. 3.2.6 Aún no disponible Fecha de lanzamiento no indicada

    FIX: Incorrect static method calling causes parse Error in PHP 5.6.36

    Entrada del registro de cambios

  51. 3.2.5 Aún no disponible Fecha de lanzamiento no indicada

    FIX: Fix a fatal error that could occur in 3.2.4 if settings had not been saved

    Entrada del registro de cambios

  52. 3.2.4 Aún no disponible Fecha de lanzamiento no indicada

    FEATURE: Create a cron job to delete expired cache files

    Entrada del registro de cambios

  53. 3.2.3 Aún no disponible Fecha de lanzamiento no indicada

    FEATURE: Minify: Pre-generate assets

    Entrada del registro de cambios

  54. 3.2.2 Aún no disponible Fecha de lanzamiento no indicada

    FEATURE: Cache - Allow debugging of which cache file is chosen

    Entrada del registro de cambios

  55. 3.2.1 Aún no disponible Fecha de lanzamiento no indicada

    FIX: Apply different image compression levels

    Entrada del registro de cambios

  56. 3.1.12 Aún no disponible Fecha de lanzamiento no indicada

    FEATURE: Ability to defer js files and asynchronously load css files

    Entrada del registro de cambios

  57. 3.1.11 Aún no disponible Fecha de lanzamiento no indicada

    FIX: Cache - Don't cache pages for logged-in users when 'Serve cached pages to logged in users' option (new in 3.1.10) is enabled

    Entrada del registro de cambios

  58. 3.1.10 Aún no disponible Fecha de lanzamiento no indicada

    FEATURE: Premium - Cache - User-specific cache. Useful for subscription websites, and websites where tailored content is offered to logged-i...

    Entrada del registro de cambios

  59. 3.1.9 Aún no disponible Fecha de lanzamiento no indicada

    FEATURE: Power Tweak - Change metakey field length and create new index

    Entrada del registro de cambios

  60. 3.1.8 Aún no disponible Fecha de lanzamiento no indicada

    FIX: Cache - Warning failed to open dir

    Entrada del registro de cambios

  61. 3.1.7 Aún no disponible Fecha de lanzamiento no indicada

    FEATURE: Premium - Preload key requests (Preload fonts and other assets)

    Entrada del registro de cambios

  62. 3.1.6 Aún no disponible Fecha de lanzamiento no indicada

    FIX: Fix wrong class name

    Entrada del registro de cambios

  63. 3.1.5 Aún no disponible Fecha de lanzamiento no indicada

    FEATURE: Introduction of Power tweaks (premium feature)

    Entrada del registro de cambios

  64. 3.1.4 Aún no disponible Fecha de lanzamiento no indicada

    FIX: Prevent fatal error when updating

    Entrada del registro de cambios

  65. 3.1.3 Aún no disponible Fecha de lanzamiento no indicada

    TWEAK: Added Oasis Workflow Pro tables to the list

    Entrada del registro de cambios

  66. 3.1.2 Aún no disponible Fecha de lanzamiento no indicada

    TWEAK: Only load minify dependencies when the feature is enabled, reducing the risk of conflicts with plugins with obsolete/incompatible lib...

    Entrada del registro de cambios

  67. 3.1.1 Aún no disponible Fecha de lanzamiento no indicada

    FIX: Minify - Make the feature unavailable when W3 Total Cache is active (an ancient version of the library in that plugin is incompatible a...

    Entrada del registro de cambios

  68. 3.1.0 Aún no disponible Fecha de lanzamiento no indicada

    FEATURE: Major new feature: JS and CSS combination and minification. Read more at: https://getwpo.com/faqs/category/minification/

    Entrada del registro de cambios

  69. 3.0.19 Aún no disponible Fecha de lanzamiento no indicada

    FIX: Fix force tables optimisations checkboxes

    Entrada del registro de cambios

  70. 3.0.18 Aún no disponible Fecha de lanzamiento no indicada

    TWEAK: Wipe WP-Optimize settings function

    Entrada del registro de cambios

  71. 3.0.17 Aún no disponible Fecha de lanzamiento no indicada

    FIX: Show image as uncompressed after restoring backup from the media modal

    Entrada del registro de cambios

  72. 3.0.16 Aún no disponible Fecha de lanzamiento no indicada

    FIX: Premium - Unused images - Fixed detection of -rotated and -scaled images

    Entrada del registro de cambios

  73. 3.0.15 Aún no disponible Fecha de lanzamiento no indicada

    FIX: Image compression - Fix restoration on multisite

    Entrada del registro de cambios

  74. 3.0.14 Aún no disponible Fecha de lanzamiento no indicada

    FIX: Fixed default option values for smush backup automatic deletion

    Entrada del registro de cambios

  75. 3.0.13 Aún no disponible Fecha de lanzamiento no indicada

    FIX: Don't show VIEWs as corrupted database tables

    Entrada del registro de cambios

  76. 3.0.12 Aún no disponible Fecha de lanzamiento no indicada

    TWEAK: Cache - Purge cache files when updating menu, saving the customizer and editing widgets

    Entrada del registro de cambios

  77. 3.0.11 Aún no disponible Fecha de lanzamiento no indicada

    FIX: Check the results of opendir() when emptying the cache, to prevent a possible infinite loop if it fails

    Entrada del registro de cambios

  78. 3.0.10 Aún no disponible Fecha de lanzamiento no indicada

    TWEAK: If short-circuiting the attachmentfieldstoedit filter result, return the pre-existing value

    Entrada del registro de cambios

  79. 3.0.9 Aún no disponible Fecha de lanzamiento no indicada

    FIX: Fix bug in logic for sending "Content-Encoding: gzip" header that could cause it to be sent prematurely with non-cached pages

    Entrada del registro de cambios

  80. 3.0.8 Aún no disponible Fecha de lanzamiento no indicada

    FIX: Lazy-loading regression in recent Premium release

    Entrada del registro de cambios

  81. 3.0.7 Aún no disponible Fecha de lanzamiento no indicada

    FIX: Fix some logic bugs related to the decision whether to send gzip-encoded cached content

    Entrada del registro de cambios

  82. 3.0.6 Aún no disponible Fecha de lanzamiento no indicada

    FIX: Regression causing incorrect JavaScript filenames in the Premium release in 3.0.5

    Entrada del registro de cambios

  83. 3.0.5 Aún no disponible Fecha de lanzamiento no indicada

    FIX: Short-circuit UpdraftSmushManager::addcompressbuttontomediamodal() outside of a dashboard context, so that plugins or themes that hook...

    Entrada del registro de cambios

  84. 3.0.4 Aún no disponible Fecha de lanzamiento no indicada

    FIX: Fixed a regression in 3.0 with orphaned relationship data optimization

    Entrada del registro de cambios

  85. 3.0.3 Aún no disponible Fecha de lanzamiento no indicada

    TWEAK: Prevent saving of page cache settings when the page cache was already off and another page cache plugin was active from over-writing...

    Entrada del registro de cambios

  86. 3.0.2 Aún no disponible Fecha de lanzamiento no indicada

    TWEAK: Rename in order to cache-bust sites that cached old versions of the JS admin scripts

    Entrada del registro de cambios

  87. 3.0.1 Aún no disponible Fecha de lanzamiento no indicada

    FIX: Prevent a potential stray line of text appearing

    Entrada del registro de cambios

  88. 3.0.0 Aún no disponible Fecha de lanzamiento no indicada

    FEATURE: Adds a caching feature, with page cache, browser cache control and gzip control

    Entrada del registro de cambios

  89. 2.3.4 Aún no disponible Fecha de lanzamiento no indicada

    FIX: Incorrect file paths on multisites

    Entrada del registro de cambios

  90. 2.3.3 Aún no disponible Fecha de lanzamiento no indicada

    FIX: Revert faulty change to the default settings page in 2.3.2, which prevented optimization buttons working

    Entrada del registro de cambios

  91. 2.3.2 Aún no disponible Fecha de lanzamiento no indicada

    FIX: Non-ASCII filenames could get mangled in the image optimization preview, resulting in images not shown (and WP 404 generation on the ba...

    Entrada del registro de cambios

  92. 2.3.1 Aún no disponible Fecha de lanzamiento no indicada

    FIX: Fix a code path that could cause a fatal error on PHP 5.2

    Entrada del registro de cambios

  93. 2.3.0 Aún no disponible Fecha de lanzamiento no indicada

    FEATURE: Compress images using lossy and lossless compression - both existing images, and newly uploaded

    Entrada del registro de cambios

  94. 2.2.13 Aún no disponible Fecha de lanzamiento no indicada

    FIX: Fixed RTL layout

    Entrada del registro de cambios

  95. 2.2.12 Aún no disponible Fecha de lanzamiento no indicada

    TWEAK: Updated information on More plugins tab

    Entrada del registro de cambios

  96. 2.2.11 Aún no disponible Fecha de lanzamiento no indicada

    FIX: A regression in the "identify table by owner" feature caused optimizing to silently fail on some tables

    Entrada del registro de cambios

  97. 2.2.10 Aún no disponible Fecha de lanzamiento no indicada

    FEATURE: Added the ability to download unused images list (Premium version) as a CSV file

    Entrada del registro de cambios

  98. 2.2.9 Aún no disponible Fecha de lanzamiento no indicada

    FIX: Change a newly-introduced fragment that was not compatible with PHP 5.2

    Entrada del registro de cambios

  99. 2.2.7 Aún no disponible Fecha de lanzamiento no indicada

    RE-FACTOR: Refactoring and reorganisation of the UI

    Entrada del registro de cambios

  100. 2.2.6 Aún no disponible Fecha de lanzamiento no indicada

    FEATURE: Added Gzip compression support

    Entrada del registro de cambios

Ver en el registro de cambios los 146 lanzamientos aún no disponibles

Léame

Licencia

WP-Optimize Premium - Clean, Compress, Cache

Get caching and more with this powerful cache plugin. Cache, optimize images, clean your database and minify for maximum performance.

MORE THAN A CACHING PLUGIN

WP-Optimize is trusted by more than 1 million WordPress website owners to boost performance and reduce page load times to improve your site's user experiences and SERP rankings in Google.

It does this in four clever ways:

1. It caches your site

Caching is the process of storing a temporary HTML version of your site on the server so it can be retrieved more quickly for the user.

It's a sure-fire way to ensure web pages load at lightning-fast speed. Turn it on in just one click.

2. It compresses images

Large images can really impact page speed load times. WP-Optimize makes it easy to identify and compress images to your preferred lossy / lossless settings in a couple of clicks.

3. It cleans the database

Your WordPress database stores everything that you need, plus some things that you don't. WP-Optimize cleans and optimizes the database to speed up your site and save server resources.

4. It minifies

On top of its three main features, WP-Optimize Cache also has the more advanced minification feature.

Together with caching, minification dramatically improves performance and page speed load time.

Qué añade

  • WP-CLI: optimize
  • Se integra con WooCommerce

Installation

There are 3 different ways to install WP-Optimize Cache, as with any other wordpress.org plugin.

Using the WordPress dashboard

  1. Navigate to the 'Add New' in the plugins dashboard
  2. Search for 'WP-Optimize'
  3. Click 'Install Now'
  4. Activate the plugin on the Plugin dashboard

Uploading in WordPress Dashboard

  1. Download the latest version of this plugin from https://wordpress.org/plugins/wp-optimize/
  2. Navigate to the 'Add New' in the plugins dashboard
  3. Navigate to the 'Upload' area
  4. Select the zip file (from step 1.) from your computer
  5. Click 'Install Now'
  6. Activate the plugin in the Plugin dashboard

Using FTP

  1. Download the latest version of this plugin from https://wordpress.org/plugins/wp-optimize/
  2. Unzip the zip file, which will extract the wp-optimize directory to your computer
  3. Upload the wp-optimize directory to the /wp-content/plugins/ directory in your web space
  4. Activate the plugin in the Plugin dashboard

Faq

Isn't it better to use a dedicated caching plugin to cache my site?

We've built WP-Optimize Cache around the most advanced and powerful caching technology. Our caching tests and feedback from real-world users show that the caching feature alone can make your site faster than any other cache plugin or optimization. See these speed test results.

Is optimizing my database safe?

Yes; optimizing does not involve any "tricks" or poking around in dangerous ways. It involves running routine clean-up operations using well-defined, common MySQL commands. Nevertheless, we always recommend backups, which cover every possibility; not just database malfunctions, but hackers, human errors, etc. We recommend UpdraftPlus.

What savings can I expect to make?

This is a "how long is string?" sort of question. It depends completely on your site - how big it is, how many users interact on it, how long it has been running, and when you last optimised it. However, the savings and speed-ups can be substantial; it is always worth making sure that your database is optimised.

How do I get support?

In our support forum, here: https://wordpress.org/support/plugin/wp-optimize/

WP-Optimize does not make large savings on my database

This is rare; it's probably because you're with a shared web hosting company that doesn't allow scripts to run an optimize command via SQL statements (SQL "OPTIMIZE" instruction). Please consult your web hosting company on this matter.

Is the plugin tried and tested?

Yes - WP-Optimize Cache is WordPress's #1 most-installed optimisation plugin, with over 800,000 users and a pedigree going back over 8 years.

Does WP-Optimize support InnoDB tables?

WP-Optimize will disable some features if it detects InnoDB tables. Optimization of the database tables on-disk is not available, but other clean up features would work.

Can you help me restore my database?

Not unless you have an existing backup. Please ensure that you make a backup of your entire database before using WP-Optimize for the first time, and when you upgrade to a major new version of it. We recommend UpdraftPlus.

Are there any bugs in this plugin?

The plugin is an ongoing work; that means that it is impossible to rule out unforeseen situations and bugs. So I would recommend you to test it out on your local system or make a backup of your database (just to be extra careful).

How do I stop transient options from coming back automatically each time I clear them?

When WordPress uses a particular transient, that specific transient is re-created automatically. So, it's normally for ones which are in active use to gradually re-appear. The best way to keep things optimal is to clear the transient options on a scheduled basis. For example, WordPress may create 50 transient option in a week. If you schedule WP-Optimize Cache to clear these options on a weekly basis, you'll have far fewer building up.

The table size shows wrong / Not optimizing

Please check your database for corrupted tables. That can happen, usually your web hosting company can run the repair command on the db.

Which WordPress and PHP versions are supported?

To use all features in the plugin, a minimum of version WordPress 4.9 with PHP 7.2 are required. But we do recommend to use the latest version of WordPress. Using PHP 7.2+ is also highly recommended, as our caching feature will work even faster.

Which optimisation will make the biggest difference?

This depends on your setup (theme, number and quality of plugins used, etc...), but generally, caching will make the biggest visible difference to your website's performance. Indeed, the cache functionality bypasses most of WordPress code to serve your pre-optimised cached pages directly to your visitor, significantly increasing the speed.

What is caching, or page caching?

"Caching", from Wikipedia: "In computing, a cache is a hardware or software component that stores data so that future requests for that data can be served faster; the data stored in a cache might be the result of an earlier computation or a copy of data stored elsewhere. A cache hit occurs when the requested data can be found in a cache, while a cache miss occurs when it cannot." — WP-Optimize cache does this by saving the page computed by WordPress on the disk. When a user visits a page, WP-Optimize will serve the cached page before WordPress is loaded. If the page wasn't cached before, it will be computed by WordPress, and WP-Optimize will then save the result to the cache.

Why should I use a caching plugin on my website?

You think your site is fast without caching? A caching plugin will make your website even faster. A faster cached website will increase SEO, it will improve your visitors experience. Caching will also save your server's resources.

Is the WP-Optimize page cache compatible with Gutenberg and WordPress 5.0+?

Yes, your Gutenberg pages will be cached, as well as those created with page builder plugins such as Elementor.

How do I know my webpage is being cached (or why it isn't)?

If cache is enabled, and in order to see if your page is cached, use the "View Source" function in your web browser to view the page source. To find caching information, scroll down to the bottom, and you should see a line added by the cache: <!-- Cached by WP Optimize - https://teamupdraft.com/wp-optimize/ - Last modified: Sat, 20 Jul 2019 21:17:19 GMT -> However, note that if you are using a further service that minifies HTML (e.g. Cloudflare), then this line may have been removed. Another method is to inspect the contents of the directory wpo-cache inside your wp-content directory. <a href="https://teamupdraft.com/documentation/wp-optimize/topics/caching/faqs/how-do-i-know-my-webpage-is-being-cached/>Further information can be read here Also note that if you do not preload the cache, a page or post will have to be visited once for the cache file to be generated.

How do I configure the page cache?

Go to WP-Optimize -> Cache and enable caching. For most people, that will be enough. If you run an e-commerce, have a custom login page or any page that has dynamic content, you might want to exclude certain urls from the cache. Visit documentation for help.

Is the caching feature compatible with e-commerce plugins?

Yes, caching with WP-Optimize Cache allows you to safely cache your products, with plugins like WooCommerce or Easy Digital Downloads, or any e-commerce that uses DONOTCACHEPAGE to exclude sensitive pages from caching (e.g. my account, cart or checkout pages).

Is the caching feature compatible with multilingual plugins?

Yes, WP-Optimize works with popular multilingual plugins like WPML or Polylang. However, it's important to note that when using WP-Optimize with multilingual plugins, the URL format for different languages should not include any query parameters, for example https://example.com/?lang=en. Instead, it should be in a pretty permalink format, such as https://example.com/en.

Do I need a special setup to use the caching feature?

No, if WordPress works properly, WP-Optimize will be able to cache your pages and posts.

Can I use the page caching feature together with another cache plugin?

No, because both cache plugins would need to use the drop-in plugin advanced-cache.php. If you turn off caching on WP-Optimize Cache, you can use any other caching plugin and still use the other features of WP-Optimize. But we do recommend using our caching solution.

Is WP-Optimize caching compatible with Cloudflare?

Yes! No special cache configuration is needed. Page caching on the WP site (that done by WP-Optimize Cache) is independent of proxy caching (e.g. Cloudflare) – you can use both, or neither, and they will complement each other and not interfere. Just one thing to note – Cloudflare will strip out the special HTML comment at the bottom of the source of a page that is helpful to confirm that page caching is working, so, don't be confused by that – it's absence doesn't indicate the cache is not working.

Can I empty the cache automatically when performing a custom action?

Yes, you can trigger a cache purge action using WP-Optimize Cache public functions. If you want to clear the whole cache, use the function wpo_cache_flush(). If you want to clear the cache files for a specific page or post, use WPO_Page_Cache::delete_single_post_cache($post_id);. Those cache options are available after WP action plugins_loaded.

Will the comments work even when page caching is enabled?

Yes, when using WordPress' commenting system, your users will still be able to post comments. Every time a comment is approved, the cache for that page or post will be cleared, allowing the next visitor to see an up to date list of comments.

What is "cache preloading"?

Usually, a page is cached when a user visits it. So the first user visiting won't be served a cached version of the page, and will wait longer than the next users. The cache preloading functionality will go through all your pages and posts, and simulate a visit by a user, allowing WP-Optimize to cache the pages before anyone visits them. Your first visitor will thus be served a cached version of the page, increasing its performance.

What frequency should I choose for the cache preloading schedule?

Choosing a frequency for the cache preloading schedule will depend on factors such as the frequency at which the website content is updated, the number of pages in the cache, the resources of the server and more. For example a site with hundreds of pages will require more resources to preload its cache. So choosing a high frequency will mean that the cache will be recreated often, and the resource usage will be higher. On a website where updates aren't as frequent, you can even disable the cache preloading schedule, or set a high cache lifespan and set the cache preloading schedule to follow it.

How do I cache only the home page?

Add /.+ to the cache option "URLs to exclude from cache" on the advanced settings tab.

How do I prevent WP-Optimize Cache from caching a certain page

To prevent a page from being cached, you can add the URL to the field "URLs to exclude from cache" in the cache "Advanced settings" tab. If you are developing a plugin and want to prevent a page from being cached, you can define the "DONOTCACHEPAGE" constant on the pages you need. Any request where "DONOTCACHEPAGE" is defined will not be cached.

Is the caching feature of WP-Optimize free?

Yes the caching feature is free. You will always be able to cache your website for free using WP-Optimize and we are constantly working on improving the existing cache feature. We will add more caching options to the free version and develop more specific caching options in the premium version to enable you to taylor the caching functionality to your needs.

Where does WP-Optimize Cache store the cached files?

The cached files are stored in the common "wp-content/cache" folder, inside a "wpo-cache" folder. Removing the "cache" folder will delete all of WP-Optimize's cache, as well as those from other plugins. Deleting the "cache" folder is generally safe, as those cached files will be regenerated.

How do I disable caching?

Go to WP-Optimize settings > Cache and toggle the "Enable page caching" option to on/off.

Will caching slow down my server?

No, caching will actually reduce the load on your server, by reducing the amount of PHP and mysql used. You might see a peak in resource usage when using the cache preloader, as this functionality will create the cache files for all your pages in a short amount of time. But once this is done, performance should increase and the load on your server will decrease. Every single major site uses caching to serve cached pages faster by using fewer resources.

Can I make certain parts of the page stay dynamic when cache is enabled?

The cached page is sent to the user before most of WordPress was loaded. The plugins aren't loaded yet, making it impossible for them to change the cached content at every request. So at the moment if you want to keep parts of your page dynamic (e.g. adverts, widgets, shopping cart...) AND keep it cached, you will have to use custom solutions using javascript and AJAX to fetch those dynamic parts from the server.

How do I delete the WP_CACHE define from wp-config.php?

WP-Optimize Cache will remove the "WP_CACHE" constant from wp-config.php when you disable page caching, or when you deactivate the cache plugin. If you need to remove it manually, you can use FTP to edit wp-config.php and delete the line define ('WP_CACHE', true ); If page caching is still enabled in the settings, WP-Optimize Cache will attempt to add the line again, as it is required for the caching functionality to work.

My filesystem is not writable to increase security. What do I need to do to make it compatible with the caching functionality?

WP-Optimize caching feature needs write access to the 'wp-content/cache' folder, as this is where the cache files will be stored. It also needs to define the constant 'WP_CACHE' in 'wp-config.php', it will need access once to 'wp-content/advanced-cache.php', as well as to the folder 'wp-content/wpo-cache' to write the cache settings.

How do I change file permissions?

If you need to change file permissions to enable caching, you can follow the instructions on this page https://wordpress.org/support/article/changing-file-permissions/

What is the maximum number of pages I can cache?

There is no limit to the number of pages you can cache. The only limit is the space on your server and the maximum number of subdirectories allowed by your server, as caching will write files in subdirectories following the permalink structure. If you were to reach a caching limit, it probably means that your server is not fit for the size of your website and caching needs.

How do I serve cached pages to people using a phone or tablet?

You can generate a separate cache by selecting "Generate separate files for mobile devices" in the page cache settings. This cache setting is only necessary if you use a specific theme for mobile devices, or for certain AMP plugins.

Does WP-Optimize Cache work with Nginx?

Yes, the cache feature works with Nginx. Should you want to enable browser caching or GZIP compression, you will have to do this yourself directly on the server settings.

Does caching work with Windows Server (IIS) ?

Yes, the cache feature works with

Screenshots

  1. Cache - plugins comparison benchmark
  2. Database optimization
  3. UpdraftPlus running a backup before an optimization proceeds
  4. Table Report
  5. Image compression
  6. Main cache screen
  7. Settings
  8. Real world tests show the cache feature alone can make your site faster than any other caching plugin
  9. Features comparison

Upgrade Notice

  • 4.7.0: A new Overview Dashboard, and a lot of tweaks and fixes - a recommended update for all

Instalar

composer require meteorgpl-plugin/wp-optimize-premium

Las comprobaciones de licencia del proveedor están intactas: activa el plugin en WordPress con una clave de licencia comprada al proveedor.

Licencia

El plugin no declara ninguna licencia. El código se redistribuye bajo la licencia que el proveedor declaró en las cabeceras del propio plugin.

Las ilustraciones, fuentes, archivos multimedia y documentos que puedan tener una licencia independiente no se redistribuyen; la página de licencias explica qué se sustituye o elimina, y la pestaña de seguridad lo detalla por versión. El soporte y el derecho a actualizaciones vienen con la licencia que compras al proveedor.

TeamUpdraft, DavidAnderson UpdraftPlus - Backup/Restore

meteorgpl-plugin/updraftplus

Backup, restore or migrate your WordPress website to another host or domain. Schedule backups or run manually. Migrate in minutes. Reliable and easy t...

plugin 2.26.15.26 GPL-3.0-or-later

Enviar comentarios

Qué funciona, qué no, qué falta: unas palabras ayudan.

Solo si quieres una respuesta.

Se toma en tu navegador, sin esta ventana. Las contraseñas, lo que escribiste en formularios, las claves y los tokens se omiten como bloques grises; puedes ocultar más antes de enviarla. Conservamos las capturas 90 días.

Lo guardamos con la dirección de la página, tu idioma, el tamaño de la ventana, el navegador y la dirección IP, y tu dirección de correo electrónico si nos la das. La dirección IP y el navegador se eliminan a los 90 días. Política de privacidad.

Todos los idiomas