TYPO3's DMEXCO 2025 Recap
The TYPO3 team traveled to Cologne for this year’s DMEXCO. Our latest appearance at Europe’s largest digital marketing conference was a special…
Intended Audience
This article is intended for TYPO3 administrators who are considering client-side caching of content to improve performance.
You should be able to install and configure TYPO3 and know about the basics of TypoScript.
How it started
The Danish Consumer Agency runs the consumers' portal <link http: www.forbrug.dk _blank>forbrug.dk which is one of the largest TYPO3 installations in the world with 130,000 unique visitors giving 13 million hits per month.
This was managed with only 1 server for the website and database and 1 server for delivering mail. During the fall 2004 they experienced spikes in their traffic (usually caused by being mentioned on TV and net media). These spikes were more than the installation could handle.
Possible solutions
Upgrading the CPUs in the server was quickly ruled out as a solution: Doubling the speed would have cost at least 15,000 Euro in hardware alone.
So a software solution was needed. They analyzed their documents and most of them are not changed during 24 hours – these could be cached without any problems. A few, however, must never be cached as they change (e.g. the result of a search).
„We tried making a small change where all pages were cached for 24 hours using Apache's proxy module as caching engine. While this gave a remarkable speed up (in the order of 10 times) this proved fatal to the few pages that must never cached.
The right thing to do was of course to make TYPO3 compliant with current caching practices (e.g. RFC-2616). After identifying the changes needed in term of HTTP-headers that should be generated, we turned to Kasper Skårhøj and had him implement the changes. The identification process took in the order of a man week, and implementing the changes in TYPO3 and testing them took also in the order of a man week.“ (Ole Tange, www.forbrug.dk)
The page was cached by TYPO3
No *_INT or *_EXT objects were on the page (e.g. USER_INT)
No frontend user is logged in
No backend user is logged in
The TYPO3 team traveled to Cologne for this year’s DMEXCO. Our latest appearance at Europe’s largest digital marketing conference was a special…
When I submitted the Q3/2025 budget request, one of the most exciting parts of the proposal was the integration of the Search Engine Abstraction Layer…
Step‑by‑Step Guides are hands-on tutorials focused on completing a single, practical task from start to finish. Here’s what they are, how they differ…
The 2025 TYPO3 Conference is only a few months away. The preliminary schedule for T3CON25 is now live on our website and will continue to be updated…
The call for community budget ideas for the fourth quarter of 2025 was successful: Nine of nine ideas have made it to the poll. These ideas can now be…
Georg Ringer provides an update on his Community Budget for Q3/2025: In the third quarter of 2025, I had the opportunity to work on a new extension…