Fight the no_cache parameter

2.050.000 is a disaster

When I search for the term “no_cache=1″ the Google search machine shows me 2.050.000 hits this morning (17. Apr. 07). 11 days ago Ernesto reported 1.650.000 hits. Either the Google results are very volatile or the amount of non cached pages is extremely growing. However, it is alarming at all.

“no_cache=1″ what does this mean? I think we can assume that the mayority of the hits, result from TYPO3 page parameters. It’s unlinkely that another WCMS uses this specific pattern or that millions of pages write about it. Counting at least one for a link tag to the page and one for the URL itself, the real amount of Google indexed pages is still below 1million. But we can say, that there are already several hundred thousand of TYPO3 pages out there, that are not cached at all.

• The page is not indexed.
• It can be found by Google but the internally TYPO3 site search engine “Indexed search” doesn’t work for it.
• A page is fully rerenderd for each call.
• The visitor has to wait some seconds for the result.
• Waiting is not acceptable for most visitors.
• The success of the sites decrease distinctly.
• Each rendering process needs a lot of memory.
• The server can only serve a part of the regular amount of pages.
• As a result each call requires a multiple of resources.
• The additional resources require a multiple of energy.
• Each no_cache parameter out there is a sign of unprofessionality of the developing agency and negative publicity.