Pegasaas Accelerator WP

Descripcion

We believe everyone should be able to have a fast website without having to spend countless hours learning how different web performance plugins operate.

Pegasaas Accelerator WP optimizes your WordPress web pages and posts for maximum speed via the Pegasaas API, applying over 20 different web performance methods, in harmony. Some of the optimizations automatically performed on your pages include:

  • Automatic Detection and Injection of Critical CSS
  • Deferral of Render Blocking CSS
  • Deferral of Unused CSS (Basic)
  • Deferral of Render Blocking JavaScript
  • Minification of CSS
  • Minification of JavaScript
  • Minification of HTML
  • Automatic Image Optimization (Basic)
  • Removal of Query Strings from Static Resources
  • DNS Prefetching
  • Page Caching
  • Auto Clear Page Cache
  • Automatic Pre-Caching (Optimizing) of your Pages
  • Combine CSS (Basdic)
  • Combine JavaScript (Basic)
  • Google Fonts Optimization
  • Minimize Critical Requests Depth
  • Default Web font-display
  • Preload Resources
  • Lazy Load Foreground Images
  • Lazy Load Background Images
  • Lazy Load IFRAMEs
  • Lazy Load YOUTUBE
  • Lazy Load Scripts
  • Enabling of Browser Caching
  • Enabling of GZIP Compression
  • Disable WP Emoji
  • Cache Favicons

Additional Features

  • Reporting of PageSpeed Scores
  • Reporting of Load Time Metrics and Speed Scores

Compatibility

  • WooCommerce Compatible
  • eCommerce Compatible
  • Varnish Compatible
  • Redis Compatible

Web Performance Benchmarking

So that you know how your web pages are performing, the plugin displays the PageSpeed Score for your pages, posts, and custom enabled post types, as well as the newest web performance metrics available from Google PageSpeed Insights Version 5 and Google Lighthouse, including:

  • Time To First Byte
  • First Contentful Paint
  • First Meaningful Paint
  • Speed Index
  • First CPU Idle
  • Time To Interactive

Premium Features Available

  • Additional Optimization Credits
  • Automatic Global CDN Integration for Static Resources
  • Automatic WebP Image Delivery
  • External (off-site) Image Optimization
  • Automatic Image Resizing
  • Advanced Lazy Loading of Scripts
  • Advanced Combine JS
  • Advanced Combine CSS
  • Advanced Deferral of Render Blocking Resources
  • Advanced Deferral of Unused CSS
  • Optimize on-the-fly for e-commerce pages
  • Development Mode
  • Compare Optimized/Non-Optimized Pages with Inspector Mode

Video Tour

Screenshots

  • Interface
  • Installation Wizard
  • Installation Progress
  • Page Scores
  • Settings Panel
  • Pages/Posts Panel

Installacion

Use our GUEST (free) API access and start optimizing immediately. GUEST API includes:

  • 100 Monthly Web Performance Optimizations: Optimize 100 pages once per month or 10 pages ten times per month. Optimization cache is automatically cleared when you modify a Page or Post, or you can manually clear individual page/post cache via the Pages/Posts panel. On initial setup, the plugin will optimize up to 100 pages for you automatically, and then upon request for those resources that optimization is enabled
  • 100 Monthly Image Transformations: Your images will automatically be optimized for and cached to your WordPress website.
  • **10 Pages Scanned for PageSpeed and Web Performance Metrics
  1. Upload pegasaas-accelerator-wp folder to the /wp-content/plugins/ directory, or upload the provided zip through your WordPress Dashboard « Plugin » panel.
  2. Activate the plugin through the ‘Plugins’ menu in WordPress
  3. Sign up for GUEST API Access, or if you feel you will need more than 100 monthly optimization credits, sign up for a Premium API key.
  4. Agree to the Terms of Service
  5. Choose the number of pages, posts, or post-type objects to accelerate
  6. Sit back and wait for the initial optimizations and benchmark and accelerated PageSpeed scores to be retrieved — this takes approximately 5 minutes

FAQ

Do I need another caching plugin other than Pegasaas Accelerator WP?

No, we recommend you do not use other optimization plugins at the same time as Pegasaas Accelerator WP, as doing so may cause a conflict.

Can I use other web performance optimization plugins while using Pegasaas Accelerator WP?

We do not recommend you operate other optimization plugins as doing so could cause a conflict in operations, as well as cause your WordPress website to run unnecessarily slow due to a duplication of functionality.

Reviews

abril 29, 2019
Just wanted to say I was on the fence about trying your plugin after hitting so many brick walls with others (and killing a few dev sites) but seeing your quick, thorough replies really helped me decide to try it out. Kudos on the customer service. It's a rarity these days.
març 5, 2019
I'm giving this plugin 5 Stars but based on the quality of the plugin and excellent support on offer id give it more stars if I could! I have used other "top" optimization plugins in the past and never really noticed much difference. With this plugin, there is an almost instant, noticeable difference. My scores on Pingdom, GTMetrix and Google Pagespeed have massively increased. Cant big this Plugin up enough, excellent quality plugin and an author who is passionate and goes above and beyond with his customer care highly Recommended!!
febrièr 15, 2019
I cannot say enough great things about Pegasaas. Our customers are thrilled at how fast our website is now! We have a very heavy picture based site and this product handles it like a dream. Quick, easy to use and amazing customer service! This team works hard to produce results, and they succeed!
febrièr 15, 2019
I was one of the early adopters and I a glad to see it is finally here in WordPress repository. It turned my crawling site into an absolutely lightening fast loader. Users have loved how pages just pop up. Mobile users are even more excited. Google ratings are really high. Highly recommend it. Support is superb and timely, I don't think the support team ever sleeps.
Read all 10 reviews

Contributors & Developers

“Pegasaas Accelerator WP” is open source software. The following people have contributed to this plugin.

Contributors

Changelog

2.7.3

Exposed PHP Notice
* This patch supresses a PHP Notice message that was displaying on some servers.

2.7.3

Microsoft Windows IIS Permalink Check / Exposed PHP Notice
* This patch resolves an issue with the Permalink check on installation, when the website is served by a Microsoft IIS system.
* In a recent update, certainly handling for query string arguments was modified. This in turn caused a PHP Notice to be exposed for those systems that display PHP Notices. This has now been resolved.

2.7.2

Debugging Improvements
* This patch includes further updates to resolve cache folder mapping issues introduced in 2.7.0

2.7.1

Cache Folder Bug Resolution For Installations that Reside in Subfolder
* This patch resolves a bug introduced in 2.7.0 for installations that reside within a subfolder where the « content » folder was not mapped correctly.

2.7.0

**WordPress Multisite Network Compatibility **
* Pegasaas now supports the WordPress Multisite Network feature, where you have a network administrator that manages multiple websites, or multiple versions of the same website, for testing development purposes.  This new level of compatibility required changes across the entire plugin to properly map the location of cache files which needed to exist in parallel for multiple sites.
* Alternate « wp-content » folder location is now supported.

2.6.0

**Advanced Performance Metrics / Combine CSS and Combine JS Upgrade **
* Advanced Performance Metrics (Time to First Byte, First Contentful Paint, First Meaningful Paint, First CPU Idle, Speed Index, and Time To Interactive) are now available for each page displayed in the Pegasaas Accelerator WP dashboard for those using the « Advanced » display level. Intermediate will show a limited set of performance metrics.
* The Combine CSS feature was upgraded for Premium subscribers — you now will have the ability to specify the number of stylesheets to serve — by default, the system will build a single massive stylesheet for Guest API users.
* A new feature, Combine JS, performs the same mechanism for JavaScript as the Combine CSS feature does for stylesheets. This feature is currently tied to the « Deferral of Render Blocking Javascript », but will be expanded in the future should someone want to combine JS but not defer it. By default, the system will build a single JS file, however Premium subscribers will have the ability to split it into up to 4 files.
* Additional support for a deprecated cURL error code has been added for those servers running older versions of cURL.
* Bug fixes to the dashboard that displayed « NAN » to the « PageSpeed Change » value once a PageSpeed scan was complete.

2.5.0

Script Lazy Loading
* For those users of the Guest API, we have opened the up basic script lazy loading feature.  If you have a script in your page that we’ve determined can be reliably lazy loaded until the user scrolls, then it will be.  You can, of course, disable this feature if you find it interferes with the operation of your page.
* If you have a premium subscription, you can take full advantage of the more robust capability of this advanced system.  For each script on your web page, you can specify if and when it is lazy loaded.  Be forewarned: lazy loading a script which has dependants can cause functionality in your page to break.
* This update also includes analytics opt-out code for pages that are requested via the ?accelerate=off query, which is typically used for Google PageSpeed Insights requests.
* Better support for sites protected with a password using HTTP AUTHENTICATION was included in this release.

2.4.2

Benchmark PageSpeed Scan Bug
* Resolved a bug introduced in version 2.4.0 where the system did not detect an existing Benchmark PageSpeed scan, which resulted with the interface indicating « Queued » scans, and then the request of unnecessary scans from the API.

2.4.1

Lazy Loading Scripts added to Standard Edition for Premium API subscribers
* Adding custom lazy loaded scripts was previously only available in the Pro Edition of the plugin. It is now avalable in the Standard Edition for Premium API subscribers.

2.4.0

Data Management Improvements
* This update dramatically improves the load time of the Pegasaas Accelerator dashboard (and by proxy, the entire WordPress system when using Pegasaas)
* Bug fix that resolved warning messages generated by the PegasaasInterface::admin_posts_column_content() function.
* Bug fix that resolved the modal overlay on first load of the Pegasaas dashboard, if using a mobile device.

2.3.9

Compatibility with WooCommerce API
* Previously, Pegasaas would append some code to the response for wp-json/ and wc-auth/ requests, causing the wc-auth requests to fail.  This release fully resolves this issue.

2.3.8

Cache and Data Management
* This update includes a few small improvements to the cache handling system related to mapping of URLs to the appropriate cache resource.

2.3.7

Compatibility (mod_pagespeed, Apache htaccess) Handling
* Instructions are automatically added to the .htaccess, disabling mod_pagespeed. This replaces the previous behaviour where the end user was required to manually disable the mod_pagespeed plugin themselves via their web hosting control panel.
* Added conditional satements to check for mod_header and mod_setenvif Apache modules to prevent a server error in the event that either of those Apache modules are not installed
* Created a mechanism to test whether the new .htaccess file will cause a 500 Internal Server Error, prior to saving the updated .htaccess file to the root.

2.3.6

Caching Related Issues Resolved
* This update removes the date/time check for cache, as this is no longer a relevant reason to invalidate cache as cache is already auto cleared through the cron system.

2.3.5

Caching Issue Bug Fix
* This update resolves a bug that was caused by an improperly assessed cache date for those installations which use a non-typical date format.

2.3.4

Support for WP Dashboard when Port Explicitly Declared
* This update adds support for a situation where the WP dashboard is accessed using a port #, such as https://somewebsite.com:443/wp-admin/

2.3.3

WP Engine Compatibility Patch
* Caching: Additional support has been added to clear invididual page level cache.
* Dynamic Resource Optimization: The WP Engine hosting platform was preventing the plugin from optimizing resources which were to be optimized on-the-fly. Modifications had to be made to the file naming convention (.optimized-css rather than .css-optimized)

2.3.2

Compatibility Patch
* Avada: The plugin will now resolve an issue where some Avada code was executing in a cart-before-the-horse situation in the main.js file. This resolves javascript errors resulting from incomplete rendering of the page.
* WooCommerce: Advanced support for WooCommerce Product Caterores/Tags has now been added to the Premium Edition.
* Flywheel: Initial support for the Flywheel hosting platform has been added. Flywheel maps the /wp-admin/ folder from a symbolically linked /www/.wordpress/wp-admin/ folder
* Cloudflare: Further support for the Cloudflare system was added to ensure that temporary cache is cleared when an optimization has been submitted to the plugin from the API.

2.3.1

Simplified operation of some features
* Deferral of Render Blocking JavaScript features have been simplified for the Standard edition.
* Deferral of Unused CSS feature has been simplified for the Standard edition.
* Removed the « recommended improvements » icon / popup
* Simplified up the « more » (vertical ellipsis) button beside the PageSpeed scores

2.3.0

Added suport for a new ‘Development’ mode in the Premium edition
* The new premium edition Development mode is supported with updates to this release.
* Contextual Help added to the top of the pages/posts panel
* Clarified the LIVE/Diagnostic mode with a new switcher at the top of the dashboard interface
* Added improved compatibility with W3 Total Cache

2.2.19

Database Performance Improvements
* Reduced the load time of the dashboard by half by adjusting a number of database queries.

2.2.18

Improved WP-CLI Compatibility
* Resolved an issue with the plugin that was caching output run by WP-CLI in rare situations.

2.2.17

Novice/Intermediate/Advanced Mode
* Added a new step to the installation wizard so asking web performance experience level. Interface is tailored to the level of experience — streamlining it for novice users.

Static Resources Cache Handling
* There is now a new tab in the dashboard labelled « Cache », which provides the ability to view all of cached static resources, and their level of optimization. User can also delete individual items, as well as re-optimize the resource.

Improvements
* Resolved issue with installations being deployed to Bluehost as there was a recent change to the Endurance caching plugin which prevented the installation wizard from starting.
* Added improved support for subdirectory installations.

2.2.16

Custom Pages Installation Bug
* Resolved a problem with the installation routine when a user selected a custom selection of pages, that included the home page. In this scenario, all pages then had the acceleration enabled.

2.2.15

**Head, Footer, and Post Injections Compatibility **
* Resolved an issue where the « hefo_callback » was being suppressed by the Pegasaas Accelerator WP buffer capture system.

2.2.14

Compatibility
* When an image was being fetched for optimization, there was an issue that if the server did not respond with a source file, even though the file existed, a placeholder image of zero bytes was being stored.  This behaviour has now been updated so as to just return a 404 result and exit early with no optimization.
* We have changed how the plugin responds to conflicting plugins, so that third-party caching plugins are currently considered conflicting if Cloudflare is installed.  When more than one caching plugin is present (Pegasaas + one other) the ability for the system to succesfully fetch optimized pages is diminished.  We have plans to resolve this issue, but for the time being, it is best to consider other third party caching plugins not compatible in this scenario.
* At installation, we are now prompting for Cloudflare credentials if the system detects that Cloudflare is present.
* We have added compatibility with the « Accelerated Mobile Pages » plugin to allow mobile redirection.
* Additional support for Pagely hosting (through SSL detection) has been added.
* We are now detecting possible hung installations through the installation wizard.  If the system detects a possible hung installation, it will notify the Pegasaas team so that we can investigate, while attempting to retry.  If, after the typical initialization duration, the optimization request are not performed as anticipated, it will display a message indicating that the initialization did not proceed, that the Pegasaas team has been notifiede, and to initiate a support ticket.
* A new system to notify you when you are runing low on credits is now in place.

2.2.13

Compatibility
* Added support for permalinks that do not have a trailing slash /, and confirmed support for permalinks formatted in the /index.php/path/to/resource/ manner.
* Resolved the case of the system incurring a 500 server error when initialized on a site with a space in the document root folder (or parent folders).  The .htaccess contained two RewriteCond instructions which each contained a path that needed to be wrapped within quotes.

Lazy Loading
* Added ability for the user to define image paths to be excluded from lazy loading foreground and background images

Static Resource Handling
* Added handling for situations where static resources are not handled by the WordPress 404 system — previously, the plugin could not optimize CSS/JS/images if static resources were excluded from being handled by the WordPress 404 system.

2.2.12

Installation Routine
* Added support form that is now accessible in the event that the installation hangs
* Test for invalid SSL certificate and warn that installation cannot be complete until the SSL certificate issues is resolved
* Added new test for a non-existant .htaccess file, which attempts to create a .htaccess file if the environment supports it, based upon the permalink settings of the site
* Added support for installations that allocate 1GB+ of memory to PHP

Image Optimization
* Added support for installations that migrate from a website that uses a /~userdir/ 
* Resolved possible conflict of the lazy loading images code with other scripts that use boilerplate IntersectionObserver code

Caching
* Resolved an issue where the plugin was requesting optimized versions of pages on a POST request, possibly storing submitted data to a form if the form utility injected submitted values into the form.
* Added a new feature (Dynamic URLs) where the user can specify if they want query string arguments to bypass the cached optimized page.  This may be required for those installations that use a plugin which passes query string arguments in order to display a dynamic page.  With this new feature, you can also specify arguments to ignore, such as those that are associated with pay-per-click or tracking systems, that do not require a dynamically generated page.

2.2.11

Installation Routine
* New Step #1 which explains what the installation wizard does, and allows the user to choose their interface color
* Existing « Light » interface syle is updated with cloud background
* New « Plain » interface is more netutral than the « Light » interface.
* Updated final step of Installation Wizard simplifies how you choose which pages/posts to optimize, with a new « Advanced » option where the user can choose individual posts, pages, or custom post types
* If a user does not have enough credits to complete the basic installation, it will warn them once the installation wizard has been submitted.

Installation Bug Fixes
* Resolved an issue when the dashboard is being referenced via HTTPS but the website is set as HTTP in the WordPress general settings page.  This was causing installations to hang at 93% as the optimized page was not being saved due to an inconsistent « resource id ».
* Resolved an issue where a server side firewall existed, that was preventing the submission of large post data (the optimization request) by implementing a notify-then-fetch routine.

Builder Compatibility
* Added compatibility for the new Divi builder by excluding URLS from being optimized that contained the et_fb=1 or et_bfb=1 arguments
* Added compatibility for the Cornerstone (X) builder by excluding any URLS from being optimized that contained /x/, or were referred by /x/

2.2.10

Cache Management
* Added support for Pagely server side (Varnish based) caching system 
* Detect and alert user if « mod_pagespeed » installed on the server (as mod_pagespeed will conflict with Pegasaas functionality)
* Resolved isssue where incorrect subfolder paths were created in the wp-content/ folder, when optimized pages were returned from the API
* Added new feature where the user can choose to enable « auto clear » of page cache on a weekly or monthly basis

Memory Management
* Migrated the use of native page setting and page cache state variables stored in WordPress wp_options table to a pegasaas_page_config and pegasaas_page_cache tables, to avoid bloat to the wp_options table that can occur with very large installations

Usability
* Added a « Welcome Tour » video to the interface upon first installationAdded a check for a valid email on Guest API key request
* Added a new tab labelled « Tools » which now has options to « Enable All » or « Disable All » acceleration for each of the page, post, or custom post types
* Added post level configurations for all custom post types — previously, this was available only for pages and posts
* Added a new tab labelled « Changelog » which includes a list of recent updates
* Added a check for plugin being installed to a installation on « localhost » — system cannot be installed on « localhost » as there is no way to scan « localhost » or return optimizations or scans to « localhost » from the API
* Added ability for Developer Edition to ‘optimize on the fly’ if dynamically generated page (query string, logged in user, ecommerce) is detected

2.2.9

  • Added server speed check warning into interface
  • Added notification alert when tracking/analytic scripts possibly slowing site down into interface
  • Added « upgrade » link into the plugin listing in plugins.php panel
  • Added detection and handling for .htpasswd (Basic HTTP Authentication) protected /wp-admin/
  • Added detection and handling for Wordfence block of API requests
  • Added link to contact support on the installer
  • Changed the API communication request timeout from 1 second to 5 seconds
  • Added a « pickup optimizations » service for Siteground/Kinsta/slowest response rate installations
  • Changed the « autoload » setting for any Pegasaas data stored via WP native « update_option » to « no »
  • Changed the « manage » link in the plugin panel, for white label subscriptions, to the pa-web-perf alias
  • Improved handling for write-protected .htaccess file

2.2.8

  • Removed debug output when unoptimized page is requested.

2.2.7

  • Added support for non-latin characters used in page slugs (permalink)
  • Resolved issue where permalinks that had not been recalculated since a site had been switched from http to https causing a redirect issue preventing the scanning of pages
  • Added feature to inform the individual running the initialization sequence that they can navigate away and the installation routine will continue in the background.
  • Added feature that notifies the website operator via email once the initialization sequence has gathered the initial optimizations and scans
  • Resolved issue where PageSpeed scans were being requested on pages with an un-optimized cache
  • Added system check to verify that a permalink structure is enabled
  • Adjusted interface to show when pages that are cached are un-optimized are not pending optimization if no optimization credits are remaining

2.2.6

  • Update to PegasaasUtils::has_acceleration_enabled to resolve issue of home page and categories not being identified as having acceleration enabled

2.2.5

  • Added compatibility for DreamPress by DreamHost cloud hosting
  • Added auto detection of Varnish server side caching
  • Added a number of third-party caching and optimization plugins as non-comaptible with a prompt to disable incompatible plugins
  • Resolved dashboard display prompts
  • Improvment to temporary cache handling when an optimization is completed
  • Addition of an « Optimize Now » option for the « Bulk » options in the Pages and Posts panel
  • Resolved JavaScript error on edit page/post page.
  • Resolved issue with superfluous PageSpeed scans being requested
  • Added caching of ttf/woff/woff2/eot/svg files to the pegasaas-cache folder
  • Removed DB optimization calls as they can slow down the response time of the application and are no longer required
  • Added « X-Powered-By » header to the request headers

2.2.4

  • Update to PegasaasAPI::post to resolve API timeout issue

2.2.3

  • Updates to Interface and Addition of Temporary Cache

2.2.1

  • Patch problem with initialization sequence.

2.2.0

  • Initial WordPress Repository Version.