Resources · glossary
Cache
A stored result of earlier work, served instead of doing the work again. The cheapest way to speed up a website and the most common reason for the question “why can't I see my changes”.
- cache
- caching
- web cache
- browser cache
- 01
Where it builds up
In the visitor's browser, in the content delivery network, on the application server and in the database itself. A content change has to pass through all these layers, which is why a fix can be visible to you and invisible to a customer.
- 02
Why it is not a trifle
A site that builds every page from scratch on every visit needs a server many times more powerful than a site that serves a ready result. The difference in the bill can be bigger than the difference in the build price.
- 03
A typical sign it is set up badly
An updated price that some visitors still see as the old one. That is not a content error but a cache that was not invalidated after saving, and it is fixed in the system, not by typing the price in again.
- 04
What to do before you report a bug
Open the page in a private window. If you see the new version there, the problem is in your browser; if not, it is on the server side.
Related terms
- CDN (content delivery network)A network of servers spread around the world that serve images and files from the point closest to the visitor. It cuts loading time and takes traffic off your server.
- TTFB (time to first byte)The time from a click to the server's first response, before the browser starts drawing anything. It measures the server and hosting, not how the page looks.
15 minutes. No sales pitch.
A term in a proposal sounds foreign? In 15 minutes we explain what it means for your project.