Are there plugins that need to be disabled in order for Pegasaas Accelerator to operate?

Yes, primarily any plugin that includes caching as its primary focus will need to be disabled in order for Pegasaas Accelerator to operate.

This is because features — such as Minification, Image Optimization, Render-Blocking Resource Deferral, and Critical Path CSS Injection — that Pegasaas Accelerator applies to your WordPress pages, all happen to the uncached HTML. If that page is cached by an outside plugin, Pegasaas will not have access to provide the optimizations that you are installing Pegasaas for.

Although we are working to allow some secondary functionality of some optimization plugins, for now, the operation of Pegasaas Accelerator is dependent on there not being an existing plugin enabled that provides page caching.

What does support include?

If you experience a bug, you can report it through your WordPress plugin interface. We prioritize reports based upon the severity of the issue.

If your page is experiencing a sub-85 score, we will investigate and develop or recommend a solution to attain an 85+ score.

Initial response time is normally 24-48 hours during normal business operation. [Monday-Friday 9-5pm -08:00 UTC (West Coast North America)]

What is your cancellation policy?

You can cancel at any time. As soon as you cancel your service, your service will continue to be operational until the end of the current billing period (provided the current billing period has been paid for).

If you cancel within your free trial period, the service will be immediately disabled.

What on-page image sizing issues limit the effectiveness of Accelerator?

If you have an image that is larger than its container (for examploe a 3500×2000 pixel image within a region that is only 350 pixels in width), Accelerator will not know to resize it down UNLESS you specify an explicity width and height attribute in your image tag.

In other words, Accelerator can’t read minds, but it once you tell it what to do (with regard to how to size an image) it can perform some pretty powerful on-the-fly image optimization.

What types of third-party resources cannot be effectively Accelerated?

Any script which handles real-time rendering of external dynamic data, such as analytics services, hit tracking, geo-specific targeted content (weather reports), and Google Maps are types of resources which cannot be effectively accelerated.

These types of scripts cannot be cached as they often us session data to identify the user and their location.

Normally, if your page has any of these types of scripts on them, you will see an upper limit of 95/100 for your Google PageSpeed score.

How high of a PageSpeed score should I expect?

We guarantee a score of at least 85/100, however many pages will experience upwards of 95/100 or more.

There are some third-party JavaScript and CSS resources which cannot be effectively accelerated due to off-site caching policies outside of our control.

There may also be issues with the size of images uploaded to your website that can impact performance.¬† Please see the FAQ about “on page image sizing” for more information on this.