I've built magento website but without full cache and lesti FPC cache the site is very slow, from time to time i need to clean the cache in the website to reveal changes to the catalog, is there a way to generate the cache after the cleaning except with building a basic crawler that scraps the whole website that loads every page so that next time it will be loaded from cache
This is covered in a Stackoverflow thread over here: Magento FPC Cache Warm with user groups, wget, Lesti FPC
I don't think you have much option other than to build your own cache warmer. The thread highlights different types of cache you may have/need.
Related
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
I'm helping friends with their blog, their admin panel is incredibly slow. After testing all the plugins, I saw that W3 Total cache was responsible of this slowness, more precisely the Object cache option. If I disable this option, the admin runs normally, so does the front of the website.
So, why don't I simply disable W3 Total Cache ?
When I do this, some content disapear from the homepage, some text changes...
I'm not sure how Object caching is working, so my question is : Why ? How can I fix this ?
W3 Total Cache tries to speed up the front end of the website by generating and caching HTML responses for each page. As a user requests a page, it is not processed by the bulk of the PHP that makes up wordpress and is quickly served a cached html page.
If the site is large, and the plugin isn't tuned correctly, it can dramatically slow down the admin side (which is run by PHP and not cached by the plugin).
To fix this, you will have to find the right balance on how often certain pages / post types are cached. If the site isn't a busy one, or if speed is not an issue (I can't see how speed wouldn't be an issue but that's an opinion) you are safe to remove the plugin.
W3 Total Cache has some good information on helping someone determine the settings that should be used. Use that info, along with page view stats to figure out your next steps.
What is difference between Full Page Catch (FPC) and Magento inbuilt caching?
Why we use FPC when already a caching system is available in Magento?
Which one is preferable?
With FPC complete page is cached and hole punching(container) system where by containers are replaced with complete html if needed.
In simple cache system blocks are cached and only blocks are checked if there cache exist.
with FPC on times application will not be initialized but complete page might be delivered from FPC which is not the case with normal block caching.
There was a comment on Adding in a hit counter to Joomla that the cache impacts the stock hit counter. Do you have any idea how I can fix that bug in Joomla or where I can start to look in the code?
I see it's submitted in the bug tracker but nobody is assigned to it. I believe the hits must be increased before the cache is served, and at the moment the function that generates the content is actually the one that calls the hit increasing function, so that's why the hits only increase upon a fresh article render.
Joomla counts and update the article hits when the page is built, but if the caching plugin is enabled and the page has been cached to disk, the page is loaded directly from the cache directory, without updating the number of views. You can try this joomla hack here:
Joomla Hit Counter Updater
Even though it's not free, it might help you.
Now that I've successfully cached my web page, how do I uncache it after making a change?
My user can't dl the latest version, even after I've changed a comment in my cache.manifest file.
My server is an IIS server.
The thing with caching is, well, stuff gets cached. Browsers won't, in general, try to download anything you've told them to cache until the cached items expire.
If you set everything to cache for a certain time span, the browser won't try to download any of the cached items until the end of it, which includes the cache.manifest file itself, by the sound of it.
Typically, you don't want to cache the content of the website, because then that makes it hard to change. Instead, you want to cache the various pieces, like images, css, and javascript, that the various pages of your site need. If you do this right, you can get a huge benefit for your users, and still have control over those resources, since you can always link to a different version of a particular resource in the content of the pages.
That said, if you do need to cache some portions of your pages, you can use server-side caching to reuse portions that are expensive to put together.