Enterprise Level Service Quote Request

We're here if you need us!

Send us a Message

Thank you for your inquiry! Please let us know a bit about your origanization, and how many sites you plan on deploying Pegasaas to.


Have a question before you purchase? Give us a call! We'd love to tell you all about our amazing plugin.


We answer the phones (Pacific Time):

  • 9:00am to 5:00pm
  • 9:00am to 2:30pm*
  • 9:00am to 5:00pm
  • 10:30am** to 5:00pm
  • 9:00am to 2:30pm***

These hours exclude Canadian statutory holidays and weekends, eh!

You may have noticed some shorter days because of:

  • * Team Building with Dr Green
  • ** Team Bouhaha Meeting
  • *** Because we're madly trying to address all the "I need this done before 5pm on Friday" requests


Pegasaas Accelerator Network

  • Online API Status
  • Online Image Optimization Status
  • Online CDN Status

Known Issues

As of August 11th, 2018, these are the following known issues/limitations that we are aware of:

WordPress Themes

  • Themify Themes
    • Themify injects JavaScript and CSS via inline JavaScript, that while in a non-render blocking situation (which Pegasaas invokes) cause the display to not be fully rendered upon first paint.  In addition, the Critical Path CSS is not fully realized by the Pegasaas CPCSS engine as the fully rendered styles are not applied until after the CPCSS engine has done it’s evaluation.  This results in the “deferral of render blocking resources” and “prioritization of visible content” penalties that will still happen after optimization of the page.
    • Using Pegasaas Accelerator with a Themify theme still results in a faster load, however the Google PageSpeed Insights score may not be as high as if a different theme solution were used.

WordPress Plugins

It should be noted that while Pegasaas Accelerator works with many third-party caching plugins being installed, you should disable any alternate caching plugin as most (if not all) features of those plugins are likely already included within the Pegasaas Accelerator system. It is best practice to not run more than one caching plugin at a time to avoid conflicts.

  • Elementor Page Builder
    • There have been some reports of a “deferral of render blocking resources” and “prioritization of visible content” Google PageSpeed Insights issue.  This is likely similar to the issue experienced by Themify themes.  We are working to investigate the issue further.
  • Really Simple SSL Plugin resolved
    • The .htaccess rules for the Really Simple SSL Plugin for wordpress must be put at the beginning of the .htaccess file, otherwise the redirects will come in the wrong order.  We will be building in functionality that will detect the placement of Rewrite rules that do not belong to pegasaas, and ensure they are in the correct order.
    • There is now no conflict with the Really Simple SSL Plugin — Pegasaas automatically detects the existance of the RS-SSL .htaccess rules, and places them in the correct location in the .htaccess file.
  • SG (SiteGround) Optimizer new
    • Within the “Super Cache” section of SG Optimizer, you need to have “memcached” DISABLED. Leaving Mecached enabled will result in our queries to the WordPress database being cached. This is critical for the safe operation of the plugin when checking to see which API requests are queued, or need updating. We are working on a solution to allow for Pegasaas to work with this feature enabled.
    • SG Optimizer injects instructions into the .htaccess file that instruct the server to redirect the user to HTTPS if the page requested is via HTTP. This causes the same problem as the (now resolved) Really Simple SSL Plugin issue. We will be implementing a patch for this shortly.
  • TTFB
    • The Lazy Load feature available in the TTFB plugin must be disabled as it is not compatible with “non-render-blocked” pages. If enabled, it will cause a Prioritization of visible content penalty. Pegasaas includes a “non-render-blocking” compatible lazy load feature.
  • NextGen Gallery Plugin new
    • The NextGen gallery uses a pre-loader that waits until all assets are loaded.  In this situation, the Critical Path CSS that is detected for injection ,prior to all of the NextGen gallery’s assets are injected into the page dynamically,  is insufficient to avoid a Prioritization of Visible Content penalty which also results in a Deferral of Render Blocking Resources penalty.  We are investigating possible solutions.

Content Delivery Network/Web Firewalls

  • Cloudflare resolved
    • If you are using Cloudflare, most services (Caching, Minification, Image Optimization) should be disabled as it will interfere with the core functionality of Pegasaas, which already provides these features.
    • There are currently no known issues with compatibility with Cloudflare.  Pegasaas Accelerator now communicates with the Cloudflare system (provided your Cloudflare API is saved to the plugin) to clear the appropriate page-cache (if you are using page rules).  Pegasaas bypasses the Cloudflare minification and image optimization systems by pushing resources through the Pegasaas CDN.
  • SiteLock
    • The SiteLock web application firewall does not allow the Critical Path CSS engine to scan pages for Critical Path CSS.  We are working on a method that will allow for this.
    • The SiteLock  web application firewall blocks the caching of some CSS/JS and Image resources.  We are working on a method that will allow for this.

Hosting Platforms

  • GoDaddy Hosting
    • Some GoDaddy servers do not respond well to the Pegasaas Accelerator’s requests to purge the native GoDaddy managed WordPress caching plugin.  If you experience issues with some Pegasaas functionality, use the provided GoDaddy “Flush Cache” option from the top menu in WordPress

Third Party (Off-Site) Resources

Often, third-party resources will specifically have a short (or no) cache lifetime. This is often on purpose and cannot (or should not) be circumvented. The following services/resources are ones that Pegasaas will not attempt to proxy. You should not be concerned with the small GPSI penalty that is a result of using these resources.

  • Google Tag Manager
    • GTM will cause a 1-2 point penalty for PageSpeed as Google does not set the cache limiters to avoid the “leverage browser caching” recommendation
  • Google Analytics
    • Google Analytics will cause a 1-2 point penalty for PageSpeed, same as with GTM
  • Google Maps
    • Google Maps are can cause an extended load time — they cannot be deferred, and if placed in the above-the-fold region will cause a “prioritization of visible content” as they take a while to load.  In addition, the scripts cannot be cached nor proxied.  Google Maps may cause a 5-10 point penalty.

Performance Limitations

Kinsta Hosting

Kinsta is considered a fast hosting environment, however the Pegasaas plugin can require more than the basic resources (PHP Worker Processes) available in the Starter/Pro/Business 1 plans.  If the PHP Worker processes are overtaxed, the site will become un-responsive.  To reactivate the site, log in to your Kinsta control panel, proceed to the Tools panel for your site, and click the “Restart PHP” button.

We are always looking at ways to optimize Pegasaas to not use as many resources to prevent this from happening.

One of the techniques that we are currently using to prevent Kinsta hosted sites from getting overwhelmed by our API is to use delayed pickup method, which runs every 5 minutes, to grab the latest requests from the Pegasaas API.  This will normally result in the Pegasaas Accelerator plugin dashboard only updating every 2-5 minutes with new data.

It is safe to continue using your WordPress site without having to sit on the Pegasaas Accelerator plugin dashboard, while your site optimizes.

SiteGround Hosting

SiteGround is considered a fast hosting environment, however the Pegasaas plugin can, at normal/moderate/maxium API response rates, exceed the 2 hour rolling and 24 rolling usage limits.

We are always looking at ways to optimize Pegasaas to not use as many resources to prevent this from happening.

One of the techniques that we are currently using to prevent SiteGround hosted sites from getting overwhelmed by our API is to use delayed pickup method, which runs every 5 minutes, to grab the latest requests from the Pegasaas API.  This will normally result in the Pegasaas Accelerator plugin dashboard only updating every 2-5 minutes with new data.

It is safe to continue using your WordPress site without having to sit on the Pegasaas Accelerator plugin dashboard, while your site optimizes.


We’ve been hard at work!  Follow all the changes and improvements we’ve made to the Pegasaas Accelerator WordPress web performance optimization plugin.


1.11.0 - Initialization Sequence/Interface Improvements

August 15, 2018 -- 6:24 (-07:00)

Initialization Sequence

As we have added more bells and whistles to the interface, sometimes the initial installation progress appears to hault.  We have added an initialization sequence that looks for there being at least one completed accelerated pagespeed score, and one benchmark pagespeed score before proceeding.

In most cases, the initialzation sequence (which shows a progress bar, and some light reading trivia) completes within 7 minutes.  It can often complete in under 5 minutes if the speed of the hosting server allows for it.

Interface Improvements

With the move from "page-by-page" analysis to a more "overview" approach to the speed scores, we have made the dashboard more front-and-center, while putting the individual page scores below the fold in the interface.


1.10.23 - Javascript Deferral

August 13, 2018 -- 6:25 (-07:00)

There was an issue in the Javascript deferral system where there may be blocks of HTML within a <script> tag that were being lumped in with the javascript that is deferred. 

Instead, these code blocks should have been excluded.

This has now been patched.


1.10.22 - Lazy Load YouTube

August 12, 2018 -- 13:25 (-07:00)

This patch addresses a style issue/conflict with the Thrive responsive video embed.


1.10.21 - Lazy Load YouTube

August 12, 2018 -- 13:20 (-07:00)

In a recent update, a small change was made to the lazy_load_youtube function in order to allow for other types of WordPress embedded links.  The logic for detecting the YouTube link was not fully tested and resulted in the lazy_load_youtube function not lazy loading youtube videos.

This has now been patched and tested.


1.10.20 - Google Fonts Import Injection

August 12, 2018 -- 13:00 (-07:00)

We've added additional auto-injection of Google Fonts directly into the HTML, for situations where the Google Font was being loaded via a <link> tag.


1.10.19 - Page Level Critical Path CSS

August 12, 2018 -- 11:50 (-07:00)

While the Post-Type CPCSS should be adequate for most pages, there may be situations where Page-Level CPCSS would be more accurate.

When Pegasaas Accelerator receives a GPSI score, the plugin evaluates whether there is a "Prioritization of Visible Content" issue.  If there is such an issue, then the plugin will request a Page-Level CPCSS scan, and then upon receiving the Page-Level CPCSS, Pegasaas Accelerator will re-request a new GPSI score.

There are times, however, when you will want to outright want a Page-Level CPCSS -- such as when the system is not detecting a rendering issue, or it is obvious that the Post-Type CSS is inappropriate for the page requested.  For this puprose, we have added new options to the CPCSS drop down menu (to the immediate left of the benchmark GPSI scores on the Accelerator dashboard overview). 

You can now explicitly re-build the Page-Level CPCSS.  You can now also explicitly build Page-Level CPCSS if there was none already existing.


1.10.18 - Image srcset Issue

August 12, 2018 -- 11:17 (-07:00)

Images that have had the srcset attribute set may not have had the proper mapping of the optimized version of the alternate image version if the protocol of the alternate images didn't exactly match the protocol as defined in the src attribute.

For example:


srcset='https://mydomain.com/myimage2.jpg 300w'

In this scenario, the srcset defined image was not mapped to the correct url.

This has now been patched.


1.10.17 - Google Fonts Import Injection

August 12, 2018 -- 10:39 (-07:00)

Rather than use the default font-loading mechanism of asking the web browser to fetch the current font-face information from the fonts.googleapis.com system, Pegasaas now directly injects the font-face definitions into the HTML, skipping a browser induced resource call that could be deferred causing a Prioritization of Visible content issue.


1.10.16 - Javascript Minification

August 12, 2018 -- 9:45 (-07:00)

Yet another small patch.  This one is designed to be a final catch-all for the issue that has occured as described in the previous several JS Minification patches.


1.10.15 - Javascript Minification

August 12, 2018 -- 9:23 (-07:00)

Small patched to correct a unique variable that was modified in error with the previous Javascript Minification patch.


1.10.14 - Removed Testing Output

August 11, 2018 -- 17:13 (-07:00)

Testing output was inadvertantly left in the previous patch.  Oopsies!


1.10.13 - Critical Path CSS Injection Point, Category CPCSS

August 11, 2018 -- 17:11 (-07:00)

Critical Path CSS Injection Point

A small change was made to ensure that the injection point was before the first stylesheet.  In a recent version, the code was updated to ensure the injection point matched with a <link> tag that was not within comments.

This left a situation where the injection could happen before a <link rel='preload' as='image' ...> which was unacceptable in some situations where there was a <style> block defined between the matched tag, and the first <link rel='preload' as='style' ...> or <link rel='stylesheet' ...>

This patch addresses that.

Category CPCSS

There was a situation within the code handling for processing GPSI scores, that if the resource was a category, it was attempting to fetch the incorrect backup CPCSS. The deficiency was found and patched.


1.10.12 - CPCSS for Category Layouts

August 11, 2018 -- 14:22 (-07:00)

That existing a situation where the Critical Path CSS for a category (based off of the post type for the cateogry) was inadquate to avoid a "Prioritization of Visible Content" penalty.  Pegasaas Accelerator is designed to request a specific page-level copy of the CPCSS if the post-type-level CPCSS is adequate.

Post categories do not have a "post id".  However, the section of the routine that requests and stores and processes the CPCSS was attemping to use an associated "post id" to store the CPCSS for the page-level CPCSS.  This resulted in the CPCSS not being stored correctly.

The solution was to use our internal PegsaasUtils->get_post_object() functionthat retrieves a pseudo post object based on a resource id which is formatted like a URL, rather than the WordPress get_post() function that requires a post id.


1.10.11 - Custom Post Types CPCSS, Javascript Minification

August 11, 2018 -- 9:24 (-07:00)

Custom Post Types CPCSS

A couple of custom post types were removed from the auto-critical-path-css detection system, as the custom post types involved were not used for publicly available pages.

Javascript Minification

A further improvement to the previous patch was implemented, which should catch all further issues described in 1.10.10


1.10.10 - Javascript Minification

August 10, 2018 -- 17:26 (-07:00)

When minifying javascript, the minification routine strips out whitespace (spaces, new lines).  The trouble with this, is when you have certain operators that require a space before them.  Such as:

var x = y - --z;

In this situation, the --z needs to be wrapped in parentheses.

var x = y - (--z);

So that the resulting minified code looks like:

var x=y-(--z); // correct

Instead of:

var x=y---z; // wrong

This patch includes an update that corrects this situation.


1.10.9 - Dynamic Link Injection Resolved

August 10, 2018 -- 11:35 (-07:00)

WordPress has a great feature where you can paste a link into your content editor, and it will provide a card with summary about the link. 

Pegasaas Accelerator was incorrectly identifying these embedded links as YouTube vidoes, and was attempting to lazyload them as youtube elements resulting in an unexpected placeholder being injected into the page.

This has now been patched.


1.10.8 - Semaphore Locking Improved

August 10, 2018 -- 10:08 (-07:00)

In certain conditions, if a website's database is hosted offsite, there maybe a degree of latency involved in writing and reading data.  In these situations, it is important to ensure that there is a period (albiet short) that a request for a semphore lock waits for the lock to be released.

In all previous versions, we were waiting for periods of 500 milliseconds, which was too little, and instead have now changed it to .5 seconds (or 500,000 milliseconds), if a semaphore is found to be locked.


1.10.7 - Added Additional Logging

August 10, 2018 -- 6:49 (-07:00)

Small patch to add additional logging in the semaphore functionality.


1.10.6 - SiteGround Optimizer Cache Issue

August 10, 2018 -- 6:24 (-07:00)

When installed to a SiteGround server and the SG Optimizer plugin is installed, Pegasaas Accelerator will automatically purge the SG cache on demand.

Since a recent update, the purge was happening, but the script was terminating prematurely.  This has now been patched.


1.10.5 - WordLift JSON-LD Issue

August 9, 2018 -- 15:44 (-07:00)

Resolved issue with the WordLift.io API JSON-LD being corrupted.  Although the wl-api/ path was excluded, if Pegasaas did not set itself as disabled "early", the output was in binary form.  Further investigation is planned, however the patch does resolve the issue.



1.10.4 - External Image Optimization URL Mapping

August 9, 2018 -- 14:12 (-07:00)

The External Image Optimization functionality was inoperable due to a change in a function that was used in the URL re-mapping functionality.  This issue has now been patched, so that external images are once again being optimized.


1.10.3 - Cache Fix, SVG Images, Google Fonts, CPCSS Injection

August 9, 2018 -- 13:49 (-07:00)

Cache Fix

There was a problem with file based cache when the WordPress installation was housed within a subfolder.  This has now been patched.

SVG Images

SVG Images were not being properly pushed through the CDN.  The CDN now accepts SVG images and properly serves them.

Google Fonts in Critical Path CSS

There was a recent update where URLS that contained query string arguments were stripped of those query string arguments.  This, unfortunately, this caused any references to such resources as fonts.googleapi.com/css?family=fontname to be truncated to fonts.googleapi.com/css -- this has now been patched.

Critical Path CSS Injection Location

As the location of the CPCSS in the page is critical to how well the page renders, there was a deficiency in the injection routine where it was placing the CPCSS into a region that then was stripped from the page, if the first <link> reference was immediately preceeded by a comment tag.  

A new set of logic was created to identify the proper location for the Critical Path CSS injection.


1.10.2 - Cloudflare Check Bug

July 31, 2018 -- 5:12 (-07:00)


On sites that referenced HTTPS but were using a broken certificiate, the system would error out when testing the site for cloudflare support.  This is now patched.


1.10.1 - Beaver Builder CSS Cache

July 27, 2018 -- 10:27 (-07:00)

Beaver Builder CSS Cache

When using the Beaver Builder plugin for WordPress, when the builder functionality is saved, often the CSS files are rebuild according to what is within the page.

Pegasaas now clears any Javascript or CSS file stored in the /wp-uploads/bb-plugin/cache/ folder, if found witin the code of a page upon save.


1.10.0 - WebP / Cloudflare / Google Fonts

July 26, 2018 -- 14:12 (-07:00)

WebP Images via secondary CDN (beta)

We have have improved automatic WebP image delivery through a second CDN system.  These requests will show (if you're inspecting network connections) as img-cdn.pegasaas.io requests, rather than the typical cdn.pegasaas.io requests.  This is still in beta testing, and will be released to most installations in the coming weeks.


Pegasaas now detects if you are using cloudflare, and prompts you to enter your API key and Account Email, so that Pegasaas can automatically clear the appropriate resources when you update your site. 

When Cloudflare is installed, and the API credentials are valid, you will now have a Purge Cloudflare button available from the top Admin Menu -> Pegasaas menu.

Google Fonts

If you have the Optimize Google Fonts option enabled, request for Google Fonts will now flow through a new Pegasaas CDN zone called "fonts-google-cdn.pegasaas.io" and "static-fonts-google-cdn.pegasaas.io".  This drastically improves the delivery of webfonts from the Google Fonts system.  As the resources are temporarily cached as they are open source and static.

Miscellaneous Improvements

There have been a few bug issues that have been patched in 1.10.0, including:

  • Issue with Divi themes that loaded so fast, that a critical window.load call was not triggering
  • When document.write scripts were detected, the system was not loading the postscript code correctly
  • A locking semaphore was not being released on save_cache call when query-string arguments were being called.  This was happening often when critical path css was being built.
  • The log.txt file that was being included with the package was not a zero file size.

1.9.2 - Removed testing output, updated accuracy of new progress bars

July 19, 2018 -- 9:16 (-07:00)

Testing output was being displayed in overview dashboard.  

Progress bars are more accurately showing the progress.


1.9.1 - Removed testing output "post not accelerated"

July 16, 2018 -- 9:42 (-07:00)

Output at PegasaasScanner::get_scanned_objects #881 was removed.


1.9.0 - New Dashboard Interface

July 16, 2018 -- 9:36 (-07:00)

This update features a completely revamped dashboard interface that provides more information about how fully accelerated your site is.

The primary metric, the Accelerated Site Score is now front and center, with the Non-Accelerated Site Score shifted to the left.  To the right is a gauge that shows the number of pages in your site that are accelerated, being accelerated, and/or not accelerated.

In addition, there are three new progress bars just below the main display that show the number of Benchmark (non-accelerated pagespeed) scans, PageSpeed Scans (accelerated pagespeed), and Critical Path CSS Scans that are in progress.


1.8.0 - Setup Wizard, Partial Acceleration, Bulk Actions, Pagination, Lazy Loading

June 29, 2018 -- 10:59 (-07:00)

Setup Wizard / Partial Acceleration

This is also a new "setup wizard" that is invoked when you install the plugin for the first time.  This new wizard currently has two steps:

  1. Specify Your API Key
  2. Choose the # of Pages/Posts that you want to have accelerated upon initialization.

Bulk Actions

Because you can now choose a partial site acceleration through the new setup wizard, there are new "Bulk" options available from the Edit Posts, Edit Posts, or any Edit Post Type page.

  • Accelerate (this will turn acceleration on for a post)
  • Disable Acceleration (this will turn acceleration off for a post)
  • Clear HTML Cache (if HTML cache exists, this will clear it for the specified post)

Overview Interface Updates

There are now two new toolbars on the Pegasaas Accelerator overview page that help you to view the results that are displayed:

  • Sort/Filter Bar (left)
    • Show: All, Pages, Posts, or any available post types
    • Issue: Any, Minification, Image Optimization, or any other PageSpeed optimization issue
    • Results Per Page: limit the number of results per page
  • Pagination Bar (right)
    • Navigate Back or Forward in the list of accelerated pages

Lazy Loading

Non-render blocking lazy loading is now enabled with Pegasaas. 

Because in a render-blocking (slow) page load, lazy loading typically happens before the rendering of the page, lazy loading is typically seamless. 

However, in a non-render-blocking (fast) page load, lazy loading should only be done on resources that are below the fold of the page.  Because offset heights cannot be determined until the document object model has been rendered, we cannot run a typical lazy load script on the page.  Instead, the Pegasaas Lazy Load system will lazy load after a user defined number of images. 

By default, this number is set at 5, however you can change this cofiguration on your Pegasaas plugin settings page.


1.7.16 - Page Level Caching Setting

June 5, 2018 -- 16:09 (-07:00)

You can now explicitly disable file based caching on a page-by-page basis.


1.7.15 - PegasaasCache Clearing Deferred JS

June 5, 2018 -- 10:55 (-07:00)

A fatal error existed when the auto-crawl cron job was attempting to clear deferred js, as the path to the required "includes/file.php" was incorrect.

This resulted in some sites experiencing a truncated page that was then cached.

This has now been patched.

If you experienced this, clear your Pegasaas HTML page cache and allow the system to re-crawl your pages to build the appropriate cache.


1.7.14 - External Images

June 4, 2018 -- 6:12 (-07:00)

Restricted external image optimization to those images with .jp[e?]p/.png file extensions, in response to dynamically generated images, such as Google User Content that did not have a file extension.


1.7.13 - Cache Build Requests now Non-Blocking

June 1, 2018 -- 15:33 (-07:00)

Typical cache requests are blocking.  If the server is slow, these blocking requests can slow down the requesting script significantly, and in some cases cause a timeout.

With this update, we have made the PegasaasCache->touch_url() function invoke the wp_remote_request with a non-blocking call, rather than the traditional manual CURL requests that we have been using up until this point.


1.7.12 - Pantheon Advanced Page Cache

June 1, 2018 -- 11:26 (-07:00)

Added 'pantheon-advanced-page-cache' to the list of supported third-party caching plugin.


1.7.11 - Resolved Fatal Error in PegasaasUtils Line #35

June 1, 2018 -- 11:15 (-07:00)

Wrapped "posix_uname()" call in a test to see if function exists first.  This code was throwing a fatal error on those servers which did not have a "posix_uname" function defined within the PHP build.


1.7.10 - Elementor Page Builder / Facebook pixel

June 1, 2018 -- 10:15 (-07:00)

Exclude the elementor library pages from the post types that are scanned, as they are not publicly visible pages.

Exlclude any images from facebook.com from being optimized by the external image optimizer.


1.7.9 - Pages/Posts Overview Bug Fix

May 31, 2018 -- 5:42 (-07:00)

Resolved an issue with the ability to turn acceleration for individual pages on or off.

At the same time, updated the overview to show size of HTML and JS if the system uses file based caching.


1.7.8 - Interface Tweaks

May 30, 2018 -- 20:06 (-07:00)

Disabled the click action on the new Page Cache and Critical Path CSS.


1.7.7 - Exclude script with type text/html from deferred-js.js

May 30, 2018 -- 16:25 (-07:00)

1.7.6 - Support for build-cpcss via proxy

May 30, 2018 -- 15:35 (-07:00)

1.7.5 - Lazy Load YouTube

May 30, 2018 -- 14:25 (-07:00)

Fixed a display issue with the thumbnail being stretched.


1.7.4 - Interface Updates, Support for Cache Header Inspection

May 30, 2018 -- 14:04 (-07:00)

Updates to the interface including:

- removal of the "last scan date"

- addition of "scan with gtmetrix"

- addition of "scan benchmark with pegasaas, gpsi, and gtmetrix"

- page cache status icon

- critical path css status icon


Also added, via the .htaccess file modifications, an X-Pegasaas-Cache header with a value of HIT or MISS.  The API, if finding a MISS when about to scan for GPSI score will defer the request until later.


1.7.3 - Patch Fatal Error Experienced in PegasaasAccelerator

May 23, 2018 -- 14:38 (-07:00)

File was truncated for unknown reason.


1.7.2 - Clear Critical Path CSS on Post Type CPCSS

May 23, 2018 -- 14:27 (-07:00)

In the event that the returned CPCSS was blank, for a post type, we were trying to clear the cache for that resource (which was non existant).  Have patched PegasaasAccelerator::process_critical_css and added lines 1724-1726


1.7.1 - GoDaddy Caching

May 23, 2018 -- 13:26 (-07:00)

In this version, we've added the ability to explicitly export the Varnish cache that is used with GoDaddy caching.  This will be helpful to have in future revisions where we detect if Varnish is used with other hosting environment.

Minor cosmetic changes:

Removed sub-menu options

Updated ability to enable/disable features without reloading interface

Disabled features now show as a "red box" on the settings page.


1.7.0 - Interface Updates, Kinsta Friendly

May 10, 2018 -- 6:16 (-07:00)

This update comes with some cosmetic updates to make the interface easier to use.

There has also been a number of improvements to help with compatibility with resource limited hosting platforms.


1.6.5 - Lazy Load Update / Inline Encode Images

May 5, 2018 -- 13:40 (-07:00)

The Lazy Loading of images/iframes and youtube videos has been vastly improved.

Also, we have patched support for inline encoded images.


1.6.4 - Themify Compatibility

May 2, 2018 -- 16:53 (-07:00)

Added missing functionality.


1.6.3 - Themify Compatibility

May 2, 2018 -- 16:47 (-07:00)

Recommit changes that didn't publish


1.6.2 - Themify Compatibility

May 2, 2018 -- 13:58 (-07:00)

Added automatic clearing of themify generated CSS from the CDN cache, upon save close.  Also resolved an issue that was being experienced in the "save_post" handler, where Themify was modifying the post ID in such a way that it was passing the incorrect id for the post (it was instead passing the revision id).

To get around this, we changed the hook we use from "save_post" to "edit_post". 


1.6.1 - The power of one missing semi-colon

May 1, 2018 -- 12:35 (-07:00)

PegasaasAccelerator::defer_render_blocking_css() line 4619


1.6.0 - Data Delivery System Update

May 1, 2018 -- 10:06 (-07:00)

In this version, we have revamped how the data is delivered on slow or metered web servers.

On those sites that are on a "normal" or higher setting, the data is delivered as it is assembled.

On those sites that are on a "cautious" delivery rate, the data is delivered via a queue, once there has been a suitable amount of time since the last hit.

On those sites that are on the "slowest" or Kinsta/SiteGround, then the server will hold the data until the plugin installed on the client website requests the data via a pickup.

There are also improvements for the Themify themes in this update.


1.5.28 - Resolved cache-build rate overloading servers

April 16, 2018 -- 6:31 (-07:00)

In the PegasaasScanner::submit_scan_requests(), added new code to help with the appropriate build rate.


1.5.27 - On feature change, fatal error

April 10, 2018 -- 16:40 (-07:00)

in PegasaasAccelerator.


1.5.26 - PegasaasUtils::check_curl_load_time

April 10, 2018 -- 14:26 (-07:00)

Function was missing.


1.5.25 - PegasaasUtils::is_siteground_server

April 10, 2018 -- 6:25 (-07:00)

Added error supression on the psoix_uname function, as it is not supported on some systems.


1.5.24 - LiteSpeed .htaccess Write Bug

April 9, 2018 -- 14:35 (-07:00)

Was not writing to the server as the server was identifying as LiteSpeed


1.5.23 - PegasaasCache::save_page_cache

April 7, 2018 -- 15:51 (-07:00)

Fatal error when page with args passed in on line #537


1.5.22 - Scanner Not Working

April 7, 2018 -- 15:08 (-07:00)

Resolved issues in scanner not receiving GPSI scores.


1.5.21 - Resolved FATAL error in PegasaasScanner::submit_scan_request

April 7, 2018 -- 13:49 (-07:00)

Bug introduced on 1674 due to incorrect reference to api method.


1.5.20 - Resolved WARNING in PegasaasScanner::get_page_speed_opportunities

April 7, 2018 -- 13:39 (-07:00)

Introduce on line # 666 because array was not initialized.


1.5.19 - Support for Pantheon Hosting

April 5, 2018 -- 17:14 (-07:00)

Added in integrated automatic support for the Pantheon caching system on Pantheon Hosting.


1.5.18 - PegasaasScanner::pegasaas_process_pagespeed_score_requests

April 3, 2018 -- 19:57 (-07:00)

Fixed line #1073 that referred to $this when it should have been $pegasaas


1.5.17 - Fix to PegasaasCache

April 3, 2018 -- 10:32 (-07:00)

Solved a fatal error when clearing an individual page cache on 352


1.5.16 - Clear Cache on CPCSS API Received

April 3, 2018 -- 9:36 (-07:00)

Updated the PegasaasAccelerator:process_critical_css() function to clear cache upon critical path css being received.

Updated the PegasaasCache::clear_cache() function to not clear the entire directory tree in ever situation.


1.5.15 - Bootstrap Conflict

April 2, 2018 -- 12:52 (-07:00)

Tweaked the PegasaasInterface::admin_enqueue so that our bootstrap is not running on all admin pages.


1.5.14 - Fix problem on accounts panel #2

April 2, 2018 -- 12:31 (-07:00)

1.5.13 - Fix problem on accounts panel

April 2, 2018 -- 12:26 (-07:00)

1.5.12 - Support for Caching Plugins

April 2, 2018 -- 12:24 (-07:00)

Now supporting:


LiteSpeed Cache

WP Rocket

WP Fastest Cache

WP Super Cache

WP Total Cache

Hyper Cache


1.5.11 - Test Package Version

March 29, 2018 -- 12:01 (-07:00)

1.5.10 - Bug Report Fix 5

March 29, 2018 -- 10:26 (-07:00)

1.5.9 - Bug Report Fix 4

March 29, 2018 -- 9:51 (-07:00)

1.5.8 - Bug Report Fix 3

March 29, 2018 -- 9:43 (-07:00)

1.5.7 - Bug Report Fix 2

March 29, 2018 -- 9:33 (-07:00)

1.5.6 - Bug Report Fix

March 29, 2018 -- 7:31 (-07:00)

Parse error: syntax error, unexpected 'public' (T_PUBLIC) in /var/www/vhosts/michaelwebster.co.uk/httpdocs/selected/wp-content/plugins/pegasaas-accelerator/_inc/classes/pegasaas-interface.class.php on line 630


Have added newline, and removed public declaration.


1.5.5 - Small patch

March 29, 2018 -- 6:12 (-07:00)

Removed message "done clearing" that was outputed when pagspeed requests were cleared.


1.5.4 - Clear Cache / Stuck Score Loading

March 29, 2018 -- 5:55 (-07:00)

With this version, the plugin code has been better organized into objects with related code.

The clear-all cache functionality should now clear all files.


1.5.3 - Broken Plugin

March 22, 2018 -- 14:06 (-07:00)

Fatal Error fix.


1.5.2 - Save Post was outputting Debugging Message

March 22, 2018 -- 13:54 (-07:00)

1.5.1 - Front End Admin Bar Fix

March 22, 2018 -- 13:52 (-07:00)

CSS/JS for the Admin Bar Menu on the front end, were not loading.


1.5.0 - Load Time, Interface Updates, Caching Improvements

March 22, 2018 -- 12:52 (-07:00)

In this version, we have included the before and after load time estimates.

The interface as has a guided help button, and we have resolved caching issues that have been existed since 1.4.


1.4.8 - Google Map No Proxy

March 9, 2018 -- 6:09 (-08:00)

Google Maps are now locked down, so we cannot proxy the code.  

For the time being, those pages will need to have their Google Code included in the page.  

At this time, we are not forcing it to async, which will mean that it will fail the "render blocking resources" aspect of GPSI.

This is currently unavoidable.  


1.4.7 - Uploaded loadCSS Fix

March 8, 2018 -- 16:13 (-08:00)

Added the pre-load fallback into the code.


1.4.6 - Caching Update

March 8, 2018 -- 13:43 (-08:00)

Fixed issue with requests that had query string arguments, saving to cache.  Added #6448-6451.

Aso, fixed issue with kinsta_exists() function throwing an error.


1.4.5 - Direct cache fixed

March 7, 2018 -- 13:17 (-08:00)

The only page that was utilizing the direct-cache via the .htaccess method was the home page.  This is now resolved.


1.4.4 - Fav Ico via CDN / Page Cache

March 6, 2018 -- 16:14 (-08:00)

Pegasaas now pushes Fav ICO files, provided they are specified in the page HTML, through the CDN.

Fixed a bug that was not saving the Page Caching setting via the API, and thus top tier page caching was not enabled via the .htaccess file -- as well, the .htaccess file wasn't altered unless the plugin was disabled then re-enabled.  This is now resolved.


1.4.3 - Google Font Deliver Optimization Implemented

March 4, 2018 -- 14:00 (-08:00)

Pegasaas will now concatenate the Google CSS font loads.


1.4.2 - Fix broken Kinsta patch!

March 3, 2018 -- 14:37 (-08:00)

kinsta_exists function needed a test to include plugin.php if it wasn't preloaded.  Wupz.


1.4.1 - Added support for Kinsta Caching plugin

March 3, 2018 -- 14:01 (-08:00)

Kinsta Cache is now supported. When Pegasaas cache is cleared, so is the Kinsta Cache.


1.4.0 - GZIP (via PHP), interface reload issue fix

March 2, 2018 -- 12:26 (-08:00)

Added ob_gzhandler functionality to check_cache() and init() for those servers that do not have GZIP automatically enabled in PHP.


1.3.9 - Small Tweak

March 1, 2018 -- 12:48 (-08:00)

Added handling for situation where "is_user_logged_in" function isn't loaded.  This is possible when a script has loaded just the basic functionality required to access the WPDB object.


1.3.8 - Updated handling of Pegasaas API calls for WordFence

March 1, 2018 -- 11:55 (-08:00)

WordFence was blocking submissions by the Pegasaas API with critical data.

The work around involved 


1.3.7 - Debug patched

March 1, 2018 -- 10:34 (-08:00)

Had to change the GET argument of "debug" to "pegasaas_debug" due to a conflict with an installed theme.


1.3.6 - Added ability to output debugging for certain functions

March 1, 2018 -- 10:30 (-08:00)

submit_benchmark_requests and submit_scan_request are now possible values for the get argument "debug", while in the plugin dashboard


1.3.5 - Performance Updates / Logging / Caching

March 1, 2018 -- 9:54 (-08:00)

This update moves the deferred-js to the file system, as well as adds back in the .htaccess routed file caching.

In addition, we are now starting to support logging.

Improvements were made to the HTML caching as well.

There is now a section on the "Cache Panel" that shows the PHP memory usage, and when the usage grows to 90% of the PHP memory limit, pegasaas will halt all new optimizations.


1.3.4 - WooCommerce/WP Ecommerce/Tribe Events Support

February 26, 2018 -- 13:57 (-08:00)

Validated against WooCommerce/WP E-Commerce and Tribe Events Calendar.


1.3.3 - Custom Post Types

February 23, 2018 -- 13:12 (-08:00)

Added support for Custom Post Types, as well as made the deferred-js load from the CDN.


1.3.2 - Fixed Auto-Load Lazy-Load

February 22, 2018 -- 12:53 (-08:00)

The lazy loading of images was not happening automatically for above the fold images on page load.  Updated line # 5680.


Also, there were spaces missing in the "replace" functionality in line 5649 and 5691, which caused some images to not render.


1.3.1 - Use CDN for Google Analytics

February 22, 2018 -- 9:51 (-08:00)

1.3.0 - Mobile Page Speed Scores

February 22, 2018 -- 5:54 (-08:00)

Added Mobile PageSpeed scores to the interface.

Bug fix for additional CDATA in the defer_render_blocking_resources function (5995/5996)


1.2.6 - Page Caching Upgrade

February 19, 2018 -- 20:02 (-08:00)

Upgraded page caching to include file-based caching, which is the new default.


1.2.5 - Benchmark Score Issue

February 17, 2018 -- 16:53 (-08:00)

1.2.4 - Removed API Output

February 17, 2018 -- 15:31 (-08:00)

1.2.3 - Small Bug Fixes

February 17, 2018 -- 14:33 (-08:00)

1.2.2 - Recommended Actions Report

February 6, 2018 -- 6:49 (-08:00)

Implemented much of the recommended actions report.


1.2.1 - External CSS Proxy Support

February 5, 2018 -- 9:12 (-08:00)

Added support for the proxying of external CSS.

Began implementing the recommended actions report.


1.2.0 - Improvements to Caching

February 4, 2018 -- 8:12 (-08:00)

Updated admin menu bar to include support for clearing external cache from the front end.


1.1.6 - Google Analytics

January 25, 2018 -- 5:57 (-08:00)

Fixed issue with Google Analytics not loading.


1.1.5 - Image Handling

January 24, 2018 -- 14:01 (-08:00)

Support for new image quality option, as well as transparent lazy load placeholder.


1.1.4 - Added compatibility for Jetpack optimized images

January 19, 2018 -- 6:50 (-08:00)

Accelerator now excludes externally optimized images handled by wp.com via the Jetpack plugin.


1.1.3 - Render Blocking JS Error Resolved

January 19, 2018 -- 5:56 (-08:00)

Had to strip paragraph tags due to <script> placed within rich text editor.


1.1.2 - WordPress as Subfolder Site / CDN Support

January 16, 2018 -- 16:32 (-08:00)

Have now added support for WordPress as a Subfolder Site.

We have also built in support for the pegasaas CDN for the upcoming PLUS plans.


1.1.1 - Deferred JS Issue / Clear Cache

January 13, 2018 -- 15:03 (-08:00)

There appears to have been a race condition that wasn't properly resolved in the check_cache() function that was resulting in the deferred JS being erased prematurely.

In addition, the cache was not auto re-built when the home page was updated, due to the get_page_by_path() wordpress function not returning the proper post id for the home page.

Also added in support for auto clearing of the cache when a post is updated, for those sites that run the blog as the home page.


1.1.0 - CSS Deferral Engine Updated

January 11, 2018 -- 21:53 (-08:00)

Now using loadCSS v2 to load in CSS files.


1.0.7 - Added Support for Developer Affiliate ID

January 10, 2018 -- 13:38 (-08:00)

1.0.6 - Resolved doubled up HTML

January 9, 2018 -- 15:44 (-08:00)

In the sanitize_output routine, we were concatenating the html to itself, rather than a straight assignement, in line # 4524.


1.0.5 - Critical Path Escape Characters

January 9, 2018 -- 15:35 (-08:00)

1.0.4 - Critical Path CSS Insertion Point

December 28, 2017 -- 14:42 (-08:00)

ON the fly debugging.


1.0.3 - Critical Path CSS Insertion Point

December 28, 2017 -- 14:39 (-08:00)

Fatal Error


1.0.2 - Critical Path CSS Insertion Point

December 28, 2017 -- 14:38 (-08:00)

Resolved fatal error.


1.0.1 - Critical Path CSS Insertion Point

December 28, 2017 -- 14:36 (-08:00)

Added the ability to insert the critical path css before the first <link> tag if that was before the first <style> tag, automatically.


1.0.0 - Full Non-Beta Version

December 28, 2017 -- 14:09 (-08:00)

0.9.1 - Blog Feed Errors Resolved

December 19, 2017 -- 10:34 (-08:00)

Added the /xmlrpc.php and /feed/ urls to those that should not have the <!--pegasaas://accelerator -- page level override (accelerator disabled) --> appended to the end of the output


0.9.0 - Render Blocking JS Error Resolved

December 19, 2017 -- 10:13 (-08:00)

Patched error introduced with Post-Script and comments in inline-script code.

Also, resolved bug introduced in version 0.8.8


0.8.9 - Render Blocking JS Error Resolved

December 19, 2017 -- 9:52 (-08:00)

Wrap Inline JS in Try/Catch


0.8.8 - WordPress AJAX object

December 16, 2017 -- 16:55 (-08:00)

Resolved bug introduced in previous patched, where the ajax_object variable in the page was being stripped out due to the code being surrounded in a CDATA wrapper.


0.8.7 - Render Blocking JS Error Resolved

December 16, 2017 -- 16:07 (-08:00)

Resolved a bug that occured when inline javascript included HTML tags that should not have been there.  This was happening when <script>..</script> was placed within the rich text editor.


0.8.6 - Updates to Image Optimization

December 9, 2017 -- 20:20 (-08:00)

Added support for thumb.php thumbnailer.


0.8.5 - Isotope Gallery Tweaks 2

December 9, 2017 -- 16:02 (-08:00)

Same as previous.


0.8.4 - Isotope Gallery Tweaks

December 9, 2017 -- 15:37 (-08:00)

This are a theme level update for the Diavlo HD theme.


0.8.3 - Deferral of inline CSS imports

December 9, 2017 -- 14:40 (-08:00)

Added support of deferral of inline CSS imports.


0.8.2 - Results Display Discrepancies

December 9, 2017 -- 13:47 (-08:00)

Some results were showing as scanning, even though they were not.  There had to be an update to how the scannable items were sorted.


0.8.1 - Semaphore Clearing

December 8, 2017 -- 10:00 (-08:00)

Tweaked the code that detects which semaphores are locked.


0.8.0 - Curl SSL Issue / Install / Semaphore Clearing

December 8, 2017 -- 9:58 (-08:00)

The system will now pre-detect if the server that it is installed to has a bad certificate file, or SSL is non functional over CURL, and if it is, then disable SSL verify peer.

Also, on some installations, the Update button (when specifying your API key) would not submit. 

Also, there is now a button on the Cache panel that will allow administrators to clear semaphore locks -- this should only be used by Pegasaas tech support in troubleshooting.


0.7.7 - Semaphore Bug Fix

November 20, 2017 -- 11:47 (-08:00)

Adding missing 'release' for the auto_accelerate_pages semaphore.


0.7.6 - Installation Wizard Updated

November 20, 2017 -- 11:36 (-08:00)

Updated instructions and double checked installation routine


0.7.5 - Shorted the refresh time

November 20, 2017 -- 11:07 (-08:00)

Reduced the refresh time to 100 page requests (down from 250) which should refresh the page in a half an hour. 


0.7.4 - Further Implementation of Semaphore

November 20, 2017 -- 10:29 (-08:00)

All critical variables are now protected with semaphore locking.


0.7.3 - Fix Stale Requests and Implemented Throttling to AJAX Requests

November 17, 2017 -- 10:31 (-08:00)

After 15 minutes, if a request has not been fulfilled, the Accelerator will now clear the stale request.  For future, we would probably want to poll the server to ensure that the request has been fulfilled rather than arbitrarily clearing the request, as the server may be offline or overloaded.

Also, depending upon the response rate setting int he account, the interface will poll once every 5 seconds (Maximum), 10 seconds (Aggressive), 15 seconds (Normal), 30 seconds (Cautious).

Benchmarking on one beta-testing site showed that a rate of 5 seconds per poll, with a 25 page website, will incur about 1200 executions or 500CPU seconds.  By reducing the rate to 15 seconds, this can reduce the impact on the server dramatically.


0.7.2 - Semaphore Implemented

November 16, 2017 -- 10:25 (-08:00)

Fixed issue related to race conditions.


0.7.1 - PageSpeed reports not saving - patch

November 13, 2017 -- 11:44 (-08:00)

Modified if/then statement in function that handles the processing of pagespeed scor requests.


0.7.0 - First Flight Ready

November 13, 2017 -- 9:47 (-08:00)

Updated API key check to handle event where pegasaas.io may be inaccessible -- plugin no longer disables.


0.6.7 - Performance Fixes

November 12, 2017 -- 18:50 (-08:00)

Ensuring no duplicate scan request.


0.6.6 - Bug Fix

November 12, 2017 -- 18:30 (-08:00)

Double-check critical CSS cache cleared.


0.6.5 - Performance Fixes

November 12, 2017 -- 18:16 (-08:00)

Fix for a fix -- unexpected scalar.


0.6.4 - Performance Fixes

November 12, 2017 -- 17:29 (-08:00)

Fixed a fatal-error bug.


0.6.3 - Performance Fixes

November 12, 2017 -- 17:27 (-08:00)

Improvements to the new nonce replacement.


0.6.2 - Performance Fixes

November 12, 2017 -- 16:26 (-08:00)

No longer using wp_create_nonce


0.6.1 - Performance Fixes

November 12, 2017 -- 14:40 (-08:00)

Resolved data conflict issues between old and new object references.


0.6.0 - New object data reference mechanism

November 12, 2017 -- 13:19 (-08:00)

This mechanism will allow for future optimization of non page/post urls.  

Previous to this update, stored data was referenced via the page/post ID.  Objects such as category pages, tag pages, archives, do not have a unique page/post id associated with them.

In the current version of Accelerator, pages and posts are optimized, however category/archive/tag pages are not, as they do are not as important to search engine optimization.

This new mechanism, however, will allow for an expansion into managing those objects are non page/posts in the future.


0.5.2 - Queried Object Bug Fix

November 9, 2017 -- 16:01 (-08:00)

Resolved an issue where blog posts did not have their proper post object stored while the page was being rendered.


0.5.1 - Twitter Widget Lazy Load / Thrive Theme Fixes

November 9, 2017 -- 12:57 (-08:00)

There is now support to delay the load of the Twitter Feed widget.  This was needed as Google finds the load of unoptimized, non-cached images from Twitter is detrimental to the loading of the page.  By delaying the load of the Twitter feed, the initial load time of the page is not impacted.  The delay time is configurable, but by default is 5 seconds.

We have also added some support for the Thrive theme grid-layout, which by default does not respond well to deferred render blocking CSS.


0.5.0 - External Image Optimization

November 7, 2017 -- 16:33 (-08:00)

Resolved a CART-before-HORSE situation with the external image optimization mechanism. 


0.4.9 - Settings Panel and External Image Optimization

November 6, 2017 -- 15:23 (-08:00)

Updated the UI for the in-app settings panel with feature descriptions.

There is now the ability to have any external images, that are referenced from within your pages, to be auto-optimized.

Images optimization can now be set to High Quality (Default), Mid-Quality, or Low quality.


0.4.8 - Page Level Overrides

November 3, 2017 -- 10:40 (-07:00)

You can now override most Accelerator settings on a page-by-page basis.  This is useful in the situations where one or more features for specific pages causes adverse behaviour and you want to disable those features causing a problem.


0.4.7 - Lazy Load Image Support

November 2, 2017 -- 9:36 (-07:00)

Added support to lazy load images.


0.4.6 - FAQs and Support Form Added to Plugin

October 31, 2017 -- 10:04 (-07:00)

The Accelerator plugin now includes an FAQ page that pulls from real-time FAQs on the pegasaas.com website.

There is now also a support form directly within the plugin which allows you to report any issues with the plugin.


0.4.5 - Lazy Load Iframes

October 30, 2017 -- 16:19 (-07:00)

You can now enable/disable lazy-loading of iframes.


0.4.4 - JS Deferral / Individual Scan Item Updates

October 30, 2017 -- 10:21 (-07:00)

There is now the ability to specify whether to use End Of Page inline javascript deferral (default) or End Of Page ansyncronous external load, for javascript deferral.

Also, now when an individual page has a scan requested, the system will first check to see if the critical CSS has been built, and if not, queue that first, and then once that has been built, build the cache for the page, and then finally request the pagespeed score.


0.4.3 - Ability to Clear individual Page/Post Cache

October 27, 2017 -- 12:40 (-07:00)

Resolved an issue where the HTML cache was not clearable on a page-by-page basis.


0.4.2 - Benchmark Scan Display Issue Resolved

October 27, 2017 -- 6:05 (-07:00)

When the initial scan of the site was being performed, many pages were showing a 'red bar' instead of the 'blue scanning bar'.  This is now resolved.


0.4.1 - Added iframe lazy load functionality [beta]

October 24, 2017 -- 6:39 (-07:00)

This update implements a lazy load for iframes. This helps to reduce the initial load of resources that may not be needed, especially those that reference sites that do not serve cachable objects, which could impact the initial load time of the page and your Google PageSpeed score.


0.4.0 - Caching Fixes, UI issues Resolved

October 17, 2017 -- 11:39 (-07:00)

Fixed a problem, introduced in 0.3.1 when the Blog as Front Page was added to the auto scan, where blog pages were not caching correctly.

Also resolved the issue of when multiple scan requests were submitted in short-order, that some request were not being handled correctly.

UI display issues for scan results also improved.


0.3.2 - CSS Updates

October 4, 2017 -- 6:12 (-07:00)

Disable WordPress "update-nag" while on the Pegasaas Accelerator plugin page. 


0.3.1 - Added Blog as Front Page to Auto Scan

October 3, 2017 -- 13:54 (-07:00)

As of this update, the front page, when it is set as the blog, as is the case for a traditional WordPress blog, now auto builds the Critical-Path CSS, calculates benchmark and accelerated pagespeed score.


0.3.0 - Stable BETA Release

October 3, 2017 -- 9:39 (-07:00)

This is the first stable BETA release.  

Features Included

This version automatically accelerates pages and posts, and analyzes the page speed of your pages and posts with and without Pegasaas Accelerator running.


0.2 -

August 30, 2017 -- 9:56 (-07:00)

Terms of Service

Terms of Service and Support


This is the “Terms of Service and Support” policy for products and services provided by Lucky Marble Solutions Corp dba Pegasaas (Pegasaas).

Table of Contents

  1. General Terms
  2. Products and Services covered under this policy
  3. Acceptable Use Guidelines
  4. Support and Service Guidelines
  5. Compatibility
    1. Web Hosting
    2. Themes/Page Builders/Frameworks & Plugins
    3. Third Party Scripts
  6. Other Limitations
    1. Images
  7. Updates
  8. Search Engine Rankings
  9. Cancellation and Refunds
  10. Intellectual Property
  11. Disclaimer of Warranty
  12. Governing Law

1. General Terms

  • The subscription, download of plugin, or use of our service indicates your acceptance of this agreement.
  • Pegasaas reserves all rights not expressly granted herein and the right to update this sets of terms at any time.

2. Products and Services Covered Under This Policy

This includes, but is not limited to:

  • Pegasaas Accelerator WordPress Plugin
  • Pegasaas API
  • Pegasaas Support
  • Pegasaas Web Performance Services
  • Any other product or service developed or given by Pegasaas or any of its agents

3. Acceptable Use Guidelines

Being polite and courteous is a requirement of all correspondence done with Pegasaas. You will attract a much better response being gracious than if you were to be belligerent.

We reserve the right to limit the service or support we offer to you, which could include the termination of our relationship with you, without any compensation to you (this includes revoking any possible reason to issue a refund), should your behaviour, in corresponding with us, meet any of the following reasons:

  • Use of any rude, vulgar, lewd, or profane language.
  • Issuing threats of any manner
  • Being aggressive or belligerent in any way

4. Support and Service Guidelines

  • Standard Support for the Pegasaas Accelerator product is included with your subscription.  Standard support includes a response time of 24-48 hours.
  • Priority Support is an extension of Standard Support, which moves your ticket into a priority status for review.   There is an additional charge for Priority support.
  • All support is provided via our ticket system only and is not available via telephone.

5. Compatibility

A. Web Hosting

Web hosting is possibly the very first aspect of website performance that you should address.  If your website is on a slow server, it will take longer to load.

Not all web hosting platforms respond equally to our API and WordPress plugin.  An example of a type of web hosting platform that may not respond in an intended manner are:

  • Slow hosting platforms
  • Metered hosting platforms
  • Resource limited hosting platforms

Slow hosting platforms are identified by their response to page requests being longer than is typical.  An average web host will have the WordPress dashboard login page respond in under 3 seconds.  If your host takes longer to respond, then it would be considered “Slow”.  If you find yourself on a slow hosting platform, you should consider switching to a web host that provides faster servers.

Known Slow Hosting Platforms

  • GoDaddy – The shared hosting plans from GoDaddy often take 6-10 seconds to respond.

Metered hosting platforms are those that limit the number of hits or CPU cycles for a given time period.   These platforms are normally very fast. Some metered hosting platforms will suspend your account if you exceed the allotted number of hits or CPU cycles for a given time period, others may bill you above and beyond your subscribed plan.

Known Metered Hosting Platforms

  • SiteGround – The shared hosting plans from SiteGround are very fast, but are metered for any given 2 hour period, as well as 24 hour period.

Resource limited platforms are those that limit the number of PHP worker processes.  This means that the sever often runs very fast, but you can only sustain the use for short periods of time.  Often, these resource limited platforms will begin to display “Bad Gateway” errors if too many hits to the PHP system are incurred over a short period of time.

Known Resource Limited Platforms

  • Kinsta – All of the plans from Kinsta include a limited number of PHP worker processes.  While this is normally fine in a environment where the front end pages are cached and additional hits to the cached pages do not incur any PHP resource usage, when Pegasaas is initially optimizing and scanning your site for your PageSpeed scores, the API is responding to the WordPress AJAX system which will incur resource usage.  In order not to overload the limited number of PHP worker processes on Kinsta, Pegasaas slowly drip feeds the optimizations and scores back to the WordPress system.

Pegasaas automatically throttles the API responses accordingly for slow, metered, and resource limited web hosting platforms, so as not to cause your web server to become unresponsive.  This will result in a longer period to optimize your WordPress website.

B. WordPress Themes, Page Builders, Frameworks, and Plugins

Different WordPress themes, Page Builders, Frameworks and Plugins can affect the display of a web page in unexpected ways.  While many WordPress web pages and sites will respond very well to the Pegasaas Accelerator, there are some third-party Themes, Page Builders, Frameworks and Plugins that when installed will cause undesired results that may not be rectified.

If you find yourself with a third-party solution that conflicts with, or does not achieve great PageSpeed scores, we will investigate to see what we can do to improve the Pegasaas Accelerator plugin’s compatibility.   There may be limitations to how much optimization your web pages can experience with third-party plugins.

Known Issues with Themes

  • Themify uses components that require the jQuery library to be loaded in order to be rendered.  In an optimized environment where JavaScript is no longer render-blocked, this will result in a short flash of unstyled content, as well as a continued “Render Blocking Resources” penalty, and “Prioritization of Visible Content” penalty.  Your web pages will load significantly faster, however the PageSpeed scores may not reflect this.

Known Issues with Plugins

  • Really Simple SSL injects its code into the bottom of the .htaccess file.  In order for Really Simple SSL to work correctly, it needs to have the .htaccess instructions placed at the top of the file.

C. Third Party Scripts

While we attempt to optimize all third party scripts, there are some which cannot be fixed due to usage policies, or dynamic JavaScript injection of additional resources.  If you include these scripts within your web pages, expect that they will result in a small PageSpeed penalty.

Known Issues with Third Party Scripts

  • Google Analytics (1 point)
  • Google Tag Manager (1 point)
  • YouTube video (5 points) — this can be mitigated by using our YouTube lazy loading
  • Yandex Metrica (1-2 points)
  • Intercom (1-2 points)

6. Other Limitations

A. Images

Images are automatically optimized by the Pegasaas system.  That being said, it is your responsibility to size your images according to the container that they reside in within your web page, or provide a width and height attribute in the “img” html tag.  If you provide a width and height attribute for an image, Pegasaas will automatically size the image as well as compress it.

If you do not size your images appropriately, or do not provide appropriate width/height attributes in the image attributes, those images may be perceived by Google PageSpeed Insights as being too large, which may result in an “Image Optimization” penalty.

7. Updates

We periodically update our plugin with new features and patches to resolve any discovered compatibility issues.  If you choose to update the plugin through the plugin dashboard, understand that the updated version may not operate the same as previous version.

We recommend you run a backup utility that you can use to restore the previous version, should you find the updated version is not to your liking.  Currently, we do not provide any facility to revert to older versions of the plugin.

8. Search Engine Rankings

We are not responsible for how your web pages are ranked by search engines (example: “Google”, “Bing”, “Yahoo”, etc).  While having a faster website is beneficial to your rankings as well as retaining your visitors, your rank position is also determined by many other factors as well.

If you have not also optimized your website for on page as well as off-page factors, you should consider hiring an SEO or SEM firm to market your site for the search engines.

9. Cancellation and Refunds

You can cancel at any time.  If you sign up for the trial but forgot to cancel your subscription, if your payment was made in the last 30 days, we will refund your payment.

10. Intellectual Property

The content found on Pegasaas.com is the exclusive property of Lucky Marble Solutions Corp, which the holds the rights to any and all related intellectual property.


By subscribing to the Pegasaas Accelerator plugin and API, you are granted license to use the product on one site per API key.  Some plans may include the ability to create multiple-licenses which will allow you to deploy the plugin on a determined number of multiple sites.

By downloading the  product, you agree not to copy, reproduce or attempt to resell the Pegasaas Accelerator plugin or any of the code provided within it.

The granting of a license for use of the Pegasaas Accelerator does not include the transfer of intellectual property rights for the product.

11. Disclaimer of Warranty

  • All products and services, in part or in whole, are sold, or in some cases given away, “AS IS” AND WITHOUT WARRANTIES AS TO PERFORMANCE OF MERCHANTABILITY OR ANY OTHER WARRANTIES WHETHER EXPRESSED OR IMPLIED.
  • Because of the various hosting environment or third-party software installed in the website that  Pegasaas Accelerator may be installed to, NO WARRANTY OF FITNESS FOR A PARTICULAR PURPOSE OF ANY KIND IS OFFERED.
  • The user must assume the entire risk of using the product.
  • Pegasaas is not responsible for the user’s level of ability to use the software required (WordPress) to install and operate Pegasaas.

12. Governing Law

  • This agreement shall be governed by International Copyright Laws, International Treaty Provisions and the laws of Canada.
  • By accepting and installing any product or service purchased from Pegasaas, you understand and agree to the terms and conditions of this license. If you do not agree to these terms, do not download, install, copy, subscribe to, or use the product or service.

Privacy Policy

Pegasaas Privacy Policy

Pegasaas Accelerator – Automated WordPress Speed Optimization Plugin

This privacy policy has been compiled to better serve those who are concerned with how their ‘Personally Identifiable Information’ (PII) is being used online. PII, as described in US privacy law and information security, is information that can be used on its own or with other information to identify, contact, or locate a single person, or to identify an individual in context. Please read our privacy policy carefully to get a clear understanding of how we collect, use, protect or otherwise handle your Personally Identifiable Information in accordance with our website.

Personal Information Privacy Act (BC)

As required by British Columbia (CANADA) law, a full PIPA Privacy Policy is available for review.

PIPA Policy

What personal information do we collect from the people that visit our blog, website or app?

When ordering or registering on our site, as appropriate, you may be asked to enter your name, email address, mailing address, phone number, credit card information or other details to help you with your experience.

When do we collect information?

We collect information from you when you register on our site, place an order, subscribe to a newsletter, respond to a survey, fill out a form, Use Live Chat, Open a Support Ticket or enter information on our site.

How do we use your information?

We may use the information we collect from you when you register, make a purchase, sign up for our newsletter, respond to a survey or marketing communication, surf the website, or use certain other site features in the following ways:

  • To personalize your experience and to allow us to deliver the type of content and product offerings in which you are most interested.
  • To improve our website in order to better serve you.
  • To allow us to better service you in responding to your customer service requests.
  • To administer a contest, promotion, survey or other site feature.
    To quickly process your transactions.
  • To ask for ratings and reviews of services or products
  • To follow up with them after correspondence (live chat, email or phone inquiries)

How do we protect your information?

Our website is scanned on a regular basis for security holes and known vulnerabilities in order to make your visit to our site as safe as possible.

We use regular Malware Scanning.

Your personal information is contained behind secured networks and is only accessible by a limited number of persons who have special access rights to such systems, and are required to keep the information confidential. In addition, all sensitive/credit information you supply is encrypted via Transport Layer Security (TLS) also commonly known as Secure Socket Layer (SSL) technology which is no longer used.

We implement a variety of security measures when a user places an order enters, submits, or accesses their information to maintain the safety of your personal information.

All transactions are processed through a gateway provider and are not stored or processed on our servers.

Do we use ‘cookies’?

Yes. Cookies are small files that a site or its service provider transfers to your computer’s hard drive through your Web browser (if you allow) that enables the site’s or service provider’s systems to recognize your browser and capture and remember certain information.

For instance, we use cookies to help us remember and process the items in your shopping cart. They are also used to help us understand your preferences based on previous or current site activity, which enables us to provide you with improved services.

We also use cookies to help us compile aggregate data about site traffic and site interaction so that we can offer better site experiences and tools in the future.

We use cookies to:

  • Understand and save user’s preferences for future visits.
  • Keep track of advertisements.
  • Compile aggregate data about site traffic and site interactions in order to offer better site experiences and tools in the future. We may also use trusted third-party services that track this information on our behalf.

You can choose to have your computer warn you each time a cookie is being sent, or you can choose to turn off all cookies. You do this through your browser settings. Since each web browser is a little different, look at your browser’s Help Menu to learn the correct way to modify your cookies.

If users disable cookies in their browser:

  • If you turn cookies off it will turn off some of the features of the site.

Third-party disclosure

We do not sell, trade, or otherwise transfer to outside parties your Personally Identifiable Information unless we provide users with advance notice.

This does not include website hosting partners and other parties who assist us in operating our website, conducting our business, or serving our users, so long as those parties agree to keep this information confidential.

We may also release information when it’s release is appropriate to comply with the law, enforce our site policies, or protect ours or others’ rights, property or safety.

However, non-personally identifiable visitor information may be provided to other parties for marketing, advertising, or other uses.

Third-party links

Occasionally, at our discretion, we may include or offer third-party products or services on our website. These third-party sites have separate and independent privacy policies. We therefore have no responsibility or liability for the content and activities of these linked sites. Nonetheless, we seek to protect the integrity of our site and welcome any feedback about these sites.


Google’s advertising requirements can be summed up by Google’s Advertising Principles. They are put in place to provide a positive experience for users. https://support.google.com/adwordspolicy/answer/1316548?hl=en

We use Google AdSense Advertising on our website.

Google, as a third-party vendor, uses cookies to serve ads on our site. Google’s use of the DART cookie enables it to serve ads to our users based on previous visits to our site and other sites on the Internet. Users may opt-out of the use of the DART cookie by visiting the Google Ad and Content Network privacy policy.

We have implemented the following:

  • Remarketing with Google AdSense
  • Google Display Network Impression Reporting
  •  Demographics and Interests Reporting

We, along with third-party vendors such as Google, use first-party cookies (such as the Google Analytics cookies) and third-party cookies (such as the DoubleClick cookie) or other third-party identifiers together to compile data regarding user interactions with ad impressions and other ad service functions as they relate to our website.

Opting out:

Users can set preferences for how Google advertises to you using the Google Ad Settings page. Alternatively, you can opt out by visiting the Network Advertising Initiative Opt Out page or by using the Google Analytics Opt Out Browser add on.


How does our site handle Do Not Track signals?

We honor Do Not Track signals and Do Not Track, plant cookies, or use advertising when a Do Not Track (DNT) browser mechanism is in place.

Does our site allow third-party behavioral tracking?

It’s also important to note that we allow third-party behavioral tracking

Children’s Privacy Protection

While there is currently no Canadian legislation that enforces how websites run by Canadian entities should should operate, with respect to children under the age of 13, we are sensitive to the heightened need to protect the privacy of this demography.

We do not specifically market to children under the age of 13 years old.

Fair Information Practices

The Fair Information Practices Principles form the backbone of privacy law in the United States.  While we are a Canadian entity, we voluntarily adhere to many of the guidelines of FIPP.

Should a data breach occur,  we will take the following responsive action:

  • We will notify you via email
    • Within 1 business day
  • We will notify the users via in-site notification
    • Within 1 business day


The CAN-SPAM Act is Canadian legislation that sets the rules for commercial email, establishes requirements for commercial messages, gives recipients the right to have emails stopped from being sent to them, and spells out tough penalties for violations.

We collect your email address in order to:

  • Send information, respond to inquiries, and/or other requests or questions
  • Process orders and to send information and updates pertaining to orders.
  • Send you additional information related to your product and/or service
  • Market to our mailing list or continue to send emails to our clients after the original transaction has occurred.

To be in accordance with CANSPAM, we agree to the following:

  • Not use false or misleading subjects or email addresses.
  • Identify the message as an advertisement in some reasonable way.
  • Include the physical address of our business or site headquarters.
  • Monitor third-party email marketing services for compliance, if one is used.
  • Honor opt-out/unsubscribe requests quickly.
  • Allow users to unsubscribe by using the link at the bottom of each email.

If at any time you would like to unsubscribe from receiving future emails, you can email us at support@pegasaas.com

  • Follow the instructions at the bottom of each email.
    and we will promptly remove you from ALL correspondence.

Contacting Us

If there are any questions regarding this privacy policy, you may contact us using the information below.

Pegasaas Policy Department
PO Box 56017
Victoria, BC     V9A 2P0

Last Edited on 2018-05-05

PIPA Policy

Personal Information Protection

Private Sector Privacy Legislation

Personal Information Protection Policy

Lucky Marble Solutions Corp dba Pegasaas

Personal Information Protection Policy

At Lucky Marble Solutions Corp (dba Pegasaas), we are committed to providing our clients, customers, members with exceptional service. As providing this service involves the collection, use and disclosure of some personal information about our clients, customers, members, protecting their personal information is one of our highest priorities.

While we have always respected our clients, customers, members privacy and safeguarded their personal information, we have strengthened our commitment to protecting personal information as a result of British Columbia’s Personal Information Protection Act (PIPA). PIPA, which came into effect on January 1, 2004, sets out the ground rules for how B.C. businesses and not-for-profit organizations may collect, use and disclose personal information.

We will inform our clients, customers, members of why and how we collect, use and disclose their personal information, obtain their consent where required, and only handle their personal information in a manner that a reasonable person would consider appropriate in the circumstances.

This Personal Information Protection Policy, in compliance with PIPA, outlines the principles and practices we will follow in protecting clients’, customers’, members’ personal information. Our privacy commitment includes ensuring the accuracy, confidentiality, and security of our clients’, customers’, members’ personal information and allowing our clients, customers, members to request access to, and correction of, their personal information.

Scope of this Policy:

This Personal Information Protection Policy applies to Lucky Marble Solutions Corp (Pegasaas).

This policy also applies to any service providers collecting, using or disclosing personal information on behalf of Lucky Marble Solutions Corp (Pegasaas)


  • Personal Information: means information about an identifiable individual. Personal information does not include contact information (described below).
  • Contact information: means information that would enable an individual to be contacted at a place of business and includes name, position name or title, business telephone number, business address, business email or business fax number. Contact information is not covered by this policy or PIPA.
  • Privacy Officer: means the individual designated responsibility for ensuring that Pegasaas complies with this policy and PIPA.

Policy 1 – Collecting Personal Information

  1. Unless the purposes for collecting personal information are obvious and the client, customer, member voluntarily provides his or her personal information for those purposes, we will communicate the purposes for which personal information is being collected, either orally or in writing, before or at the time of collection.
  2. We will only collect client, customer, member information that is necessary to fulfill the following purposes:
    • To verify identity (when requesting login information to access files we may collect phone number or city, state location)
    • To verify creditworthiness (if an order that is placed is deemed suspicious, we may try to contact a home phone number if provided)
    • To open and manage an account
    • To deliver requested products and services (communication with the user is required to send/receive products/services)
    • To send out association membership information
    • To ensure a high standard of service to our clients

Policy 2 – Consent

  1. We will obtain client, customer, member consent to collect, use or disclose personal information (except where, as noted below, we are authorized to do so without consent).
  2. Consent can be provided orally, in writing, or electronically or it can be implied where the purpose for collecting using or disclosing the personal information would be considered obvious and the client, customer, member voluntarily provides personal information for that purpose.
  3. Consent may also be implied where a client, customer, member is given notice and a reasonable opportunity to opt-out of his or her personal information being used for mail-outs, the marketing of new services or products, fundraising and the client, customer, member does not opt-out.
  4. Subject to certain exceptions (e.g., the personal information is necessary to provide the service or product, or the withdrawal of consent would frustrate the performance of a legal obligation), clients, customers, members can withhold or withdraw their consent for Pegasaas to use their personal information in certain ways. A client’s, customer’s, member’s decision to withhold or withdraw their consent to certain uses of personal information may restrict our ability to provide a particular service or product. If so, we will explain the situation to assist the client, customer, member in making the decision.
  5. We may collect, use or disclose personal information without the client’s, customer’s, member’s knowledge or consent in the following limited circumstances:
    • When the personal information is available from a public source (e.g., a telephone directory)
    • For the purposes of collecting a debt
    • To protect ourselves from fraud
    • To investigate an anticipated breach of an agreement or a contravention of law

Policy 3 – Using and Disclosing Personal Information

  1. We will only use or disclose client, customer, member personal information where necessary to fulfill the purposes identified at the time of collection [or for a purpose reasonably related to those purposes such as:
    • To conduct client, customer, member surveys in order to enhance the provision of our services
    • To contact our clients directly about products and services that may be of interest
    • We will not use or disclose client, customer, member personal information for any additional purpose unless we obtain consent to do so.
  2. We will not sell client, customer, member lists or personal information to other parties.

Policy 4 – Retaining Personal Information

  1. If we use client, customer, member personal information to make a decision that directly affects the client, customer, member, we will retain that personal information for at least one year so that the client, customer, member has a reasonable opportunity to request access to it.
  2. Subject to policy 4.1, we will retain client, customer, member personal information only as long as necessary to fulfill the identified purposes or a legal or business purpose.

Policy 5 – Ensuring Accuracy of Personal Information

  1. We will make reasonable efforts to ensure that client, customer, member personal information is accurate and complete where it may be used to make a decision about the client, customer, member or disclosed to another organization.
  2. Clients, Customers, Members may request correction to their personal information in order to ensure its accuracy and completeness. A request to correct personal information must be made in writing and provide sufficient detail to identify the personal information and the correction being sought.
  3. If the personal information is demonstrated to be inaccurate or incomplete, we will correct the information as required and send the corrected information to any organization to which we disclosed the personal information in the previous year. If the correction is not made, we will note the clients’, customers’, members’ correction request in the file.

Policy 6 – Securing Personal Information

  1. We are committed to ensuring the security of client, customer, member personal information in order to protect it from unauthorized access, collection, use, disclosure, copying, modification or disposal or similar risks.
  2. The following security measures will be followed to ensure that client, customer, member personal information is appropriately protected:
    • The use of user IDs, passwords, encryption, firewalls
    • Restricting employee access to personal information as appropriate (i.e., only those that need to know will have access; contractually requiring any service providers to provide comparable security measures.
  3. We will use appropriate security measures when destroying client’s, customer’s, member’s personal information such as deleting electronically stored information.
  4. We will continually review and update our security policies and controls as technology changes to ensure ongoing personal information security.

Policy 7 – Providing Clients, Customers, Members Access to Personal Information

  1. Clients, Customers, Members have a right to access their personal information, subject to limited exceptions.
  2. A request to access personal information must be made in writing and provide sufficient detail to identify the personal information being sought.
  3. Upon request, we will also tell clients, customers, members how we use their personal information and to whom it has been disclosed if applicable.
  4. We will make the requested information available within 30 business days, or provide written notice of an extension where additional time is required to fulfill the request.
  5. A minimal fee may be charged for providing access to personal information. Where a fee may apply, we will inform the client, customer, member of the cost and request further direction from the client, customer, member on whether or not we should proceed with the request.
  6. If a request is refused in full or in part, we will notify the client, customer, member in writing, providing the reasons for refusal and the recourse available to the client, customer, member.

Policy 8 – Questions and Complaints: The Role of the Privacy Officer or designated individual

  1. The Privacy Officer or designated individual is responsible for ensuring Pegasaas compliance with this policy and the Personal Information Protection Act.
  2. Clients, Customers, Members should direct any complaints, concerns or questions regarding Pegasaas’ compliance in writing to the Privacy Officer. If the Privacy Officer is unable to resolve the concern, the client, customer, member may also write to the Information and Privacy Commissioner of British Columbia.

Contact information for Pegasaas Privacy Officer or designated individual:

Brandon Devnich
PO Box 56017
Victoria, BC   V9A 2P0 

Pegasaas Accelerator Refund Policy

We think our Pegasaas Accelerator is pretty awesome and we hope you do too.  But, we also understand that it cannot work perfectly for 100% of the people for 100% of themes on 100% of hosting platforms 100% of the time.

The Free Trial Option

Wouldn’t it be nice to take a Tesla Roadster out for a spin, for two weeks, before purchasing it?  Yeah, this is why we offer a 14-day Free Trial option, so that you can try Pegasaas and evaluate for yourself it is going to work for your website.

If for any reason you decide that you do not want to continue automatically making your WordPress site blazing fast by automating the entire caching and site speed optimization process, if you Really enjoy doing it manually or pouring through page after page and site after site of guides and explanations and spending day after day continuously monitoring, testing, and tuning each page and post rather than using Pegasaas, you can cancel your subscription at any time.

The 48-Hour “[Facepalm]” Clause

Okay, we’ve all been there.  We intended to cancel a subscription.  We got the notification about the upcoming charge, but we forgot to deal with it.  [facepalm]

Like that (completely hypothetical, really…) “one time” that we forgot to cancel that gym membership.  Even though we probably should continue going…

Anyway, we have a 48-hour refund policy on any charge.  If you get notified of a charge, but you want to cancel, simply contact us and we’ll reverse the charge and close out your account.

Browser Caching

What is browser caching?

Browser caching is one of the easiest to implement website speed performance optimization tasks.  And while it may have little impact on the initial load time of your web page, it can make subsequent page views significantly faster.


Everything You Need to Rise Above The Cloud

We built Pegasaas because we needed a plugin that provided full Web Performance Optimization to make our websites ridiculously fast. PageSpeed Optimization, Image Optimization, fully automated integrated Content Delivery Network... all included, and you don't need to be a rocket scientist to make it work. Just install, and you're done.

  Pegasaas Accelerator: WordPress Speed Optimization
LiteSpeed Cache
WP Super Cache
W3 Total Cache
Plugin Focus
Caching Caching Caching Caching
Easy of Use
Instant Setup
Manual/Auto Acceleration NEW
PageSpeed Site Scores
PageSpeed Page Scores
Page Level Configuration
Automatic Critical Path CSS
Defer CSS Loading
Defer JS Loading
Google Fonts Optimization NEW
Disable WP Emoji NEW
Lazy Load ULTRA
Lazy Load YouTube
Automatic Image Optimization
Off-Site Image Optimization
Content Delivery Network (CDN)
Browser Caching
GZIP Compression
Page Caching
Cache Preloading
Not Supported
Get Accelerator Now