Status

Pegasaas Accelerator Network

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

Theme/Builder Compatibility

While Pegasaas Accelerator has been deployed with many themes, these are the major platforms that we have tested Pegasaas Accelerator with, and any issues that you may experience.

Theme/BuilderCompatibilityComments
ThemifyGoodNo known issues
Elementor BuilderGoodPriorization of Visble Content / Deferral of REnder Blocking Resrouce issue with JET slider.  Please see notes in “Known Issues” section below.
ThriveGoodNo known issues.
Revolution SliderVariableBasic sliders included with the Revolution Slider plugin may work well with no rendering issues.  Advanced sliders, however, often incur extra round trips and cause  a “Render Blocking” and “Prioritization of Visible Content” penalty.
Beaver BuilderGoodNo known issues.
WP BakeryGoodOn some page layouts, there may be a warning about “Prioritization of Visible Content” due to a component that relies on a “Render-Blocking” web page.  You may submit a support request asking us to investigate to see if there is a possible solution to make the component “Immediate Rendering Compatible”
DiviGoodNo known issues.
GantryGoodNo known issues.
AvadaInvestigatingNo known issues.
The 7ModerateThe boilerplate demo that is included with The 7 theme uses the Revolution Slider which incurs additional javascript injected javascript file loads.  This results in no additional page load-time improvements, although you can still expect to dramatically reduce the page load time, and reduce the number of resources required to load.  The slider does load in in a jerky manner, as it requires after-the-fact javascript resources to be loaded, which is normally ‘hidden’ in a typical “render blocked” page load.

 

Known Issues

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

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.

  • 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.
  • Elementor JET Slider
    • This slider requires jQuery (which must be deferred) in order to render.  This ends up causing a prioritization of visible content penalty.  This particular slider is not recommended, as it is absolutely reliant on javascript in order to render, and does not have a fallback html/css option.

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
  • SiteGround with Cloudflare enabled
    • Pegasaas cannot detect Cloudflare when Cloudflare is set up using the Siteground internal systems.  We recommend Cloudflare in this scenario while we investigate a possible solution.

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.

General Web Design

  • Mobile-as-an-afterthought Design
    • The Critical Path CSS (CPSS)  generator works best when web pages are designed using a mobile-first design methodology, where the styles for mobile are defined first, and then media queries for larger devices are added second.  When media queries are done in reverse order, in a mobile-last, or mobile-as-an-afterthought environment, then the CPCSS that is generated will only be effective for desktop browsers.  We are considering a method whereby we provide the default CPCSS, run a GPSI scan, and if the mobile results indicate an issue with Deferral-of-render-blocking-resources but not with the desktop results, then re-fetch the CPCSS for a “mobile” sized browser.  In this situation, this alternate CPCSS should apply to both desktop and mobile.
  • Above-The-Fold content rendered with jQuery
    • In order to render the above the fold content without a prioritization of visible content penalty, the above the fold content should not rely on jQuery to render, and should have a CSS/HTML fallback.
      Example: Some Sliders that will not render without JQuery.

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.