Status

Pegasaas Accelerator Network

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

Known Issues

As of June 4th, 2018, these are the following known issues that we are working on:

  • 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.
  • Cloudflare
    • 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.
  • GoDaddy Hosting
    • Some GoDaddy servers do not respond well to our attempts 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
  • 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.
  • 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.
  • Gravity Form Builder
      • Currently Pegasaas will not work with Gravity Form Builder
    • 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.