Month: January 2019

Can you use WP Rocket with Pegasaas Accelerator WP?

Can you use WP Rocket with Pegasaas Accelerator WP?

As Pegasaas Accelerator WP includes fast caching as a part of its web performance optimization functionality, and because Pegasaas Accelerator WP contains all of the optimization features that you will need to speed up your website, it is recommended that you do not have the WP Rocket plugin installed in parallel with Pegasaas Accelerator WP.  Running WP Rocket may cause a conflict which could cause your website to not operate as expected.

A change was made to the website but the the change is not visible in the page or post.

A change was made to the website but the the change is not visible in the page or post.

When a page (or post) is saved/updated, the cache is flushed for that page.

However, when you make a change to a “Builder Layout” or to a Widget through the “Appearance > Widgets” panel, the cache for the page that use the layout or widget will need to be cleared manually.

If the change is expected on a few pages, then you can go to the Pages or Posts panel, find the page/post in the list provided, hover over the name, and then click the “Clear Cache” link that appears once you hover over the page/post title.  Alternately, you can select the “checkbox” next to the page/post title, and then from the “Bulk Actions” drop down at the top of the list select “Clear HTML Cache” option and then click the “Apply” button.

If the change is global (site-wide), hover over the “Accelerator” toolbar menu option at the top of the WordPress dashboard, and select the “Delete Cache” button under the section labelled “Page Optimizations” or “Page Cache”.

If you are still not viewing the change on your page, it may be that your web browser is retaining a copy of the cached page in the browser cache.  Be sure to clear your web browser’s cache.

If you are still not viewing the change on your page, there may be a permissions issue with the plugin not clearing the cache file.  Contact the support team if you are still not viewing your changes.

 

A web page is not displaying properly once optimized.

A web page is not displaying properly once optimized.

There are three types of display issues that may be experienced.  If you encounter any of these, try the recommended actions.  If the recommended fix does not resolve the issue, please contact the support team so that we may investigate.

Upon page load, there is a brief period (1-2 seconds) when the page appears to be un-styled or only partially styled.

This can happen if the Critical CSS for the page is inadequate for a full render of the above-the-fold portion of the page.  This can happen if parts of the above-the-fold content is render via a javascript rendered component that is built after page is loaded.  In this scenario, the Critical CSS API system may not be able to grab a full snapshot of the required Critical CSS.

Recommended Actions

  1. A possible solution is to disable “Defer Unused CSS”.  If you disable this feature, re-optimize your page, and the page is suddenly viewing fine, then you may be able to configure the Defer Unused CSS in more detail so that the system is deferring all stylesheets except the one or two that may require to not be deferred.  Please read the article on ‘Configuring the Defer Unused CSS feature’.
  2. If solution #1 does not work, you may need to also disable the “Defer Render Blocking CSS” feature.  If you disable this feature, re-optimize your page, and the page is suddenly viewing fine, then you may be able to configure the “Defer Render Blocking CSS” feature in more detail.  Please read the article on ‘Configuring the Defer Render Blocking CSS feature’.
  3. If solution #2 does not work, you may need to also disable the “Defer Render Blocking Javascript”.  If you disable this feature, re-optimize your page, and the page is then viewing fine, then we would recommend contacting us with the details of the issue so that we can investigate the issue.  The root cause may be due to a JavaScript error in the optimized ‘deferred JavaScript ‘.

Upon page load, the page is partially un-styled until you click or scroll down through the page.

Recommended Actions

  1. This issue is related to the “Defer Unused CSS” feature.  If you disable this feature, re-optimize your page, and the page is suddenly viewing fine, then you may be able to configure the Defer Unused CSS in more detail so that the system is deferring all stylesheets except the one or two that may require to not be deferred.  Please read the article on ‘Configuring the Defer Unused CSS feature’.
  2. If solution #1 does not work, please contact the support team.

A slider does not initialize or display as anticipated.

Recommended Actions

  1. Try change the ‘Defer Render Blocking JavaScript” setting from “Default” to, “Externally Deferred at end of Page”.
  2. If solution #1 does not solve the problem, attempt to disable the “Defer Render Blocking JavaScript” feature altogether.  Please contact the support team if solution #1 does not work, and whether or not solution #2 does work.  It may be there is a load-time configuration setting that we can add to the system so that you can use the “Defer Render Blocking JavaScript” feature.
How long does it take for Pegasaas to optimize a web page?

How long does it take for Pegasaas to optimize a web page?

From the moment that a request for an optimized version of a web page is submitted to the Pegasaas API until it has been completed and been cached by your web sever, can take as little as 15 seconds.   Depending upon how many optimizations are in the API queue, this may take longer.  You can check status if the API (and how many requests are in the queue) by going to the API Status page.

API Optimization Request Life Cycle

  1. Public web page is requested, or an explicit request for an optimized version of the page is submitted via the Pegasaas Accelerator WP plugin dashboard.
  2. Request enters queue
  3. Queued request is at the front of the queue and optimization begins
  4. Optimization is complete
  5. Completed optimization is submitted back to the web server and cached OR if the requesting web server is throttled to “Slow”, “Cautious”, “Siteground” or “Kinsta”, then the request is queued for submission back to the requesting web server

 

What if my optimized Time-To-First-Byte (TTFB) is slow?

What if my optimized Time-To-First-Byte (TTFB) is slow?

Typically, your TTFB, when pages are optimized and cached, should be < 300 milliseconds.  If your page is scanned on a non-cached page, the TTFB may be > 1000 milliseconds (1 second).

If you experience a TTFB greater than 300 milliseconds, it could be caused by one of the following reasons:

  • the page cache is not saving (TTFB >1000 milliseconds)
  • the web page is very large (TTFB >500 milliseconds)
  • the web server that you are hosted on is overloaded (TTFB > 500ms)
  • the web server that you are hosted on is uses poor technology (TTFB > 500ms)

Page Cache Not Saving

If you experience a TTFB that is greater than a second, it typically means that the page cache is not saving, or that the PageSpeed scan that has been performed is being done on a non-optimized/non-cached web page.  You can attempt to re-request a PageSpeed scan, to see if the TTFB improves.  If you view the headers for your web page, and it returns a “X-Pegasaas-Cache: MISS” then it means that the cache is currently not yet built.  If this is the case, then you may need to wait while the optimized version of the web page is built.

Web Page Is Very Large

If your web page is very large, it may take longer to transfer the HTML from the server to the requesting browser.  This typically only happens in web pages that have over 1MB of HTML.

Web Server Is Overloaded

One of the very first things you should do when optimizing your website for web performance is to ensure that your web host is fast. To see how your web server stacks up against other hosting providers, check out our Hosting Provider Comparison tool.  You may ask your web hosting provider to move to a different, faster web server.

Web Server Uses Poor Technology

It may be that your web hosting provider does not use fast hosting technology.  You can check out our Hosting Provider Comparison tool to see how well your web hosting provider performs.