How to disable cache in pagespeed module? - caching

It is possible to disable cache in mod_pagespeed and just use the rewrite_images,resize_images filters?

Related

How we can speed up Joomla webpage

Using Joomla System - Page Cache, my webpage is now around 4-5 sec.
But i have few pages which will be shown only to registered users. I just checked its taking around 10-15 sec. When i inspected using chrome, i can see few things, i have livechat, which is taking around 2 sec, and few things. But live chat is showing in homepage also. but that page is speed.
Wanted to know is Joomla system cache plugin will not work for registered users visible page. or any other plugin i can use to speed up this type of pages.
Joomla have one JCH Optimize plugin which will decrease your website load speed.
It will compress all css and js file into one file.That file will store in cache so website speed will be up.
This plugin will be helpful to you.
Thanks
Are you using Joomla.
for some components only had the problem of page cache. if u need to clear cache.
and you need to speed up the joomla site
follow the basic step:
Enable Gzip Compression
Using the Gzip Compression feature, you can compress your website pages before sending them to the user. After that, they will be uncompressed by the user’s browser. And this process takes less time than transferring uncompressed pages.
Enable Cache System
Optimization Settings (Images, CSS, Java Scripts…)
Now Check Your Joomla Website Speed
it may use full to speed up your site.
Wanted to know is Joomla system cache plugin will not work for registered users visible page.
Per the Joomla! Documentation, Page Caching:
Only caches pages for guest visitors (not for logged in visitors)
or any other plugin i can use to speed up this type of pages.
Aside from JCH Optimize (which was already mentioned), another component I recommend is JotCache, which is far better than just the Joomla! default cache.
You may, also, use GTmetrix to analyze your site against both Google PageSpeed and Yahoo! Yslow.
Finally, you may try using a CDN to speed up resource delivery. Here are a few:
MaxCDN
Amazon CloudFront
Azure CDN
CDN77
CDNetworks
CDNlion
CacheFly
EdgeCast Networks
KeyCDN
SkyparkCDN
You can use CDN for Joomla! to incorporate the CDN technology.
Overall, your best bet is going to be a combination of the CDN and JCH settings to trim down the overall weight of the site using GTmetrix to compare the site after each change.
Further reading: Joomla Performance & Speed

Joomla content cahcing issue

I have a strange issue with Joomla content caching, the articles themselves take up to 10 mins to refresh their titles, images, text.
i have disabled System - Page Cache
Note i am also using cloud flare
Thank You.
If I'm not mistaken, cloud flare has some serious problems with caching. Check with them and they may send you some lines that you have to throw in your .htaccess to disable their caching.
If you have specifically enabled page rules in CloudFlare to cache static content, then it's possible this is CloudFlare related, It's easy enough to check by deleting any page rules which could cause this.
I have dozens of Joomla sites using CloudFlare and I've never seen that there was a problem combining them, or that ClouldFlare would try and cache articles by default.
As you will know, by default CloudFlare will cache static content like javascript and CSS files, but from what you describe, it's seems unlikely that this could be a cause.
I know you mention that articles are being cached, but if you have double checked that
- Extensions > Plugins > System - Page Cache is disabled
- You have cleared System > Page Cache
- You don't have any other caching enabled on your site
- You haven't specified custom ExpiresByType or mod_headers settings in .htaccess
then try setting System > Global Configuration > System > Cache to Off and on the same window if you have selected memcache(d) for the cache handling, change it to File.
These last settings under System > Cache should only affect module caching, not article caching but it doesn't hurt to rule it out.
Good luck!

boost and mollom: if both are configured, boost doesn't cache the page which consists of mollom enabled form

boost drupal module and mollom drupal module: if both are configured, boost doesn't cache the page which consists of mollom enabled form
I configured boost and caching was successful for the expected page.
But after enabling mollom module and its captcha functionality for a form place within that page, caching for this page has stopped.
To recheck if the problem is because of mollom, i disable mollom captcha and checked. It worked fine.
Can anybody explain a certain approach for caching this page or solution for this.
Thanks.
Found the solution: for mollom configuration, disabled captcha option, enabled text analysis option

Leverage browser caching (chrome audit)

im trying to learn about browser caching techniques.
all is going good so far, apart from one bit im stuck on.
when i run an audit on google chrome. i get
Leverage browser caching (1)
The following resources are explicitly non-cacheable. Consider making them cacheable if possible:
www.noelie.localhost.com/
i fixed the css and javascript with
<FilesMatch "\.(css|js|png|jpg)$">
Header set Cache-Control "max-age=31536050, public, cache"
</FilesMatch>
how do i cache the homepage www.noelie.localhost.com.
thank you for your time. noelie

RequireJS and proxy caching

We need to implement cache busting for our RequireJS modules, but it needs to be done such that it can still leverage proxy caching.
This Google best practices article talks about not using querystring data for versioning your URLs.
Also, this discussion points to this article that explains how to implement cache busting by versioning filenames and using URL rewrites to strip the version from the filename.
But this approach won't work for RequireJS modules.
Has anyone implemented cache busting for RequireJS modules that supports proxy caching?
Update:
I just found this article, but it again talks about using RequireJS urlArgs for versioning via querystring. Won't this defeat proxy caching?
Update 2:
Unfortunately, I was right. According to that article, urlArgs will indeed defeat proxy caching:
The optimal cache busting method involves changing the file name itself, such as main.1.1.0.0.js instead of main.js?v=1.1.0.0. There are several packages that will do this for you on the fly (example), but they don't integrate with RequireJS. So we'll stick with query strings in the rest of this article.

Resources