Pegasaas
Forum Replies Created
-
The “proxy external css” feature is going to be removed in a future version, as it was only something that was required for minifying and GZIP’ing external files, for PageSpeed Version 4 (prior to November 2018).
The current scoring system (which is based more on overall speed) does not penalize based upon a single file not being minified or GZIP’d.
As FontAwesome should be properly encoded and minified already, I would simply turn off the “Proxy External CSS” feature
Thank you for bringing it to my attention though — I’ll move up the date for the removal of that feature which is no longer required (and hasn’t been properly maintained over the last few releases).
Kind regards,
Brandon Devnich
PegasaasForum: Plugins
In reply to: [Pegasaas Accelerator WP] Combine JSIt sounds like you consider this an important feature and I can see where in some situations it could be beneficial so I’ll look at adding it to the plugin over the next week or so.
Thanks so much for your viewpoint.
Forum: Plugins
In reply to: [Pegasaas Accelerator WP] Combine JSHey @disagree
Thanks so much for taking the time to share your thoughts.
You are quite correct. In the the Standard Edition / Guest API, combine JS is not currently one of the available features. I’ll explain why.
When combining JS, one option is to inject the entire JavaScript into the body of the page which causes a much larger initial document. While this means that the JS will parse early, it also means that the JS will not be cached and so every page load will be longer.
The other option is to bundle all of the JS (including inline) into a separate file, and then make a single call to that file at the end of the document. Unfortunately, browser caching of this file will only affect subsequent loads of the home page, and the parsing and execution of the JS is delayed. I believe this is how Autoptimize does it.
When JS is not combined, but deferred properly, the JS files can be properly cached so that on any subsequent page request, all JS is available immediately. Also, it means that the JS will execute in order which will often mean the above-the-fold content will render faster.
I agree, having many JS requests is reported as an issue with tools such as Pingdom and GTMetrix, however we always have to consider the larger scope of what is going on in the page as well. And, with HTTP2 being supported by more and more web hosts, many of those resource requests can be loaded in parallel which have a faster load time than if the JS were in a single combined file. Having JS combined by default may have been a feature that we would have considered enabled by default a few years back, but not so much now. In addition, we’ve found that when combining JS, the JS can have troubles parsing in some sites.
When I developed Pegasaas, I felt it was more important to make a plugin that applied the “best case” scenario without requiring features to be turned off or on. The Guest API access is designed so that it’s a “one and done”.
But, I admit, there are those websites that may respond better with more expert level configurations. We do have a premium version which allows for more fine-grained configurations, although the ability to combine JS is not a separate feature at this time but is actually a part of an advanced version of deferral of render blocking JS resources.
But I will consider having the JS combination broken out into it’s own feature though — for those who feel it will have a better impact on their site.
Again, I appreciate you taking the time to share your observations.
Best regards,
Brandon Devnich
Pegasaas- This reply was modified 7 years, 4 months ago by Pegasaas.
Forum: Plugins
In reply to: [Pegasaas Accelerator WP] is supporting mobile theme ?Hi @addy085,
When you say “mobile theme”, do you mean a responsive layout where what is displayed and how it is displayed is done so via CSS and media queries?
The Pegasaas “critical CSS” engine does support responsive design. So in that scenario, it is compatible.
If you’re referring to “adaptive” design, however, where a completely different HTML layout is displayed to the user based upon the user’s detected device, then Pegasaas, nor any other caching plugin, would be appropriate for your website.
If you’re referring to the “Revo” theme found at Themeforest (https://themeforest.net/item/revo-multipurpose-responsive-woocommerce-theme/18276186), it appears to be a “responsive” layout. So I would say that yes, Pegasaas would be compatible with this theme.
As always, if you find that it is not the right fit for your website, you can always uninstall the Pegasaas Accelerator plugin, and it will instantly revert your website back to its original state.
Forum: Reviews
In reply to: [Pegasaas Accelerator WP] Best Performance Plugin + Great SupportHey @jbijman!
I really appreciate you taking the time to share your experience! The plugin is in active development, so we’re adding more features (many of them suggested by users) monthly.
Best regards,
Brandon Devnich
Founder
PegasaasForum: Reviews
In reply to: [Pegasaas Accelerator WP] Seemingly good customer support.Hey @vd11,
Thanks so much for taking the time to share!
While our plugin is not going to make 100% of sites load in under 3 seconds, we are working doing everything in our power to make it as compatible as possible.
And the only way to do that is to take every bit of feedback or reported issue that someone has taken the time to share, and investigate.
Kind regards,
Brandon Devnich
Founder
PegasaasForum: Reviews
In reply to: [Pegasaas Accelerator WP] Site got stucked after 93%Hi @deepikaslk
I’m very sorry to hear about it getting stuck.
I believe that your site experienced a timeout when trying to connect to our API, due to geographic distance from our server.
We’re in the process of adding API nodes in different data centers to address this issue, however it may take a few weeks before I’d recommend you giving this another try.
Would it be alright if we contact you then when we have an API node in your area?
Sincerely,
Brandon Devnich
Founder / Product Development
PegasaasForum: Plugins
In reply to: [Pegasaas Accelerator WP] Homepage images not showing & A few other issuesMarking this issue as resolved. To summarize the issue, and the solution: This particular site was using permalinks without a trailing slash. The way our system was built, expected a trailing slash in the permalinks. This resulted in the optimized page cache not saving correctly.
Handling for this scenario was added to the plugin and tested with the site that was having a problem. That update will be included in the upcoming 2.2.13 release.
Thank you so much for your kind words @supplementgenie! We’re not happy if you’re not happy.
You have been so kind and patient while we debugged an issue with the plugin operating on your website and I am very grateful for the opportunity to dig into it to get the plugin working.
All the best on the success of your website!
Brandon Devnich
Founder / Product Development
PegasaasForum: Plugins
In reply to: [Pegasaas Accelerator WP] Homepage images not showing & A few other issuesHey @supplementgenie,
I’m sorry to hear about this and I appreciate you taking the time to submit your issue — I will do everything in my power to determine what is going on and come up with a resolution.
It sounds like a few things are going on:
1) It sounds like the path to the images are being updated to reference the optimized version (stored in the /wp-content/pegasaas-cache/ folder), that the plugin optimizes on the fly, but that they’re not being saved to the pegasaas-cache/ folder. This is possibly caused by a block by a firewall such as Cloudflare, or by permissions on the server being non-typical resulting the plugin not being able to save the optimized file.
2) The deferral of render blocking scripts should be automatic. If we’re still getting this flag from the PageSpeed system, then it indicates that those resources are likely being injected into the page via JavaScript, but are still considered render blocking. This can sometimes happen when the theme framework has attempted to provide their own web performance improvements, which actually counteract what our plugin is trying to accomplish. Another remote possibility is that the page that is being scanned is not actually optimized, but a server level cache (either Varnish, LiteSpeed, or CDN such as Cloudflare) that is serving a stale version of the page.
3) During the installation routine, there is an “Advanced” option to choose which pages you want optimized. If you happened to choose “Everything”, all pages will have the “acceleration” flag turned on. You can TURN OFF the acceleration flag individually by going to the Pages (or Posts) option in the WordPress menu, and then click the “toggle” button which is on the right side of the row for each page listed. If you want to disable acceleration for all pages, there is now a “Tools” tab on the “Accelerator” dashboard. The “Tools” tab is located below the “speed gauge” interface. When you select it, you can disable all acceleration for a given Page / Post / Custom Post Type.
Now, I would very much like to investigate issues #1 and #2. Please initiate a ticket through at https://pegasaas.com/contact/ with your website address (and reference this message) so that I can take a closer look. You will not need to take the plugin out of diagnostic unless I cannot figure out what is going on.
Again, I appreciate you taking the time to submit your issue.
Kind regards,
Brandon Devnich
Founder / Primary Developer
PegasaasForum: Reviews
In reply to: [Pegasaas Accelerator WP] Brilliant and wonderfulAh Jason, one of our early adopters! Your many suggestions of “have you considered such-and-such” have kept us on our toes and only helped to make this a much more robust plugin.
Thank you for taking the time to share your story!
Forum: Reviews
In reply to: [Pegasaas Accelerator WP] It’s easy and it worksKinda loving the way you turned it on an let it do its thing!
Wham bam alakazam!
If it was only “pretty much” and not “everything”, let us know and we’ll take your suggestion and see if we can fit it in to the development schedule.
Forum: Reviews
In reply to: [Pegasaas Accelerator WP] Brilliant PluginThanks @bromedia — glad we could help out.
Forum: Reviews
In reply to: [Pegasaas Accelerator WP] Absolutely greatYes! We’re super excited to hear about not just how fast your site is for your visitors, but also that your search positions are benefiting!
And yes, we do sleep, just in between support messages. 😉
Thanks for taking the time to write!
Forum: Reviews
In reply to: [Pegasaas Accelerator WP] Simple to use and AMAZING resultsThank you for your kind words!
We’re so pleased to hear how happy you (and your customers) are about how fast your site loads!