# Does discourse have a cache? **URL:** \ **Category:** Product Support\ **Created:** [March 27, 2019, 1:08pm UTC](https://meta.discourse.org/t/does-discourse-have-a-cache/112698 "2019-03-27T13:08:43Z")\ **Posts on this page:** 1\ **Showing post:** 9
**Author:** ![Stephen](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/stephen/32/95011_2.png) [@Stephen](https://meta.discourse.org/u/Stephen)\ **Post date:** [March 28, 2019, 3:23am UTC](https://meta.discourse.org/t/does-discourse-have-a-cache/112698/9 "2019-03-28T03:23:12Z")
WordPress is designed to serve a high volume of pages with little to no change to a high volume of users. Write **little** , read **lots** which requires **little** resources to do. You can use plugins to build gzipped static copies of pages, database queries can be cached in-memory and the whole site can be front-ended with a product such as Varnish. Most Wordpress sites serve the majority of their sessions to logged-out users. Discourse on the other hand serves views tailored to the individual. The majority of the users are logged in. Write **frequently** , read **frequently** which comparatively requires **lots** of resources. There’s really no comparison. Your test is based on a flawed premise, particularly when you consider this: > **Do you load linked resources/assets?** > No. Our load generators only know about the URLs you give us when you create a test. We don’t parse the HTML and we don’t download javascript, CSS, or images linked to within pages. Their test doesn’t even load Discourse correctly. Source: [Loader.io](https://support.loader.io/article/39-do-you-load-linked-resources-assets) --- _[View the full topic](https://meta.discourse.org/t/does-discourse-have-a-cache/112698)._