# Slow panel due to fields with big queries

**URL:** <https://forum.getkirby.com/t/slow-panel-due-to-fields-with-big-queries/25583>\
**Category:** Questions\
**Tags:** v3\
**Created:** [May 25, 2022, 7:02am UTC](https://forum.getkirby.com/t/slow-panel-due-to-fields-with-big-queries/25583 "2022-05-25T07:02:41Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![sebastiangreger](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.getkirby.com/sebastiangreger/32/16176_2.png) [@sebastiangreger](https://forum.getkirby.com/u/sebastiangreger)\
**Post date:** [May 25, 2022, 8:40am UTC](https://forum.getkirby.com/t/slow-panel-due-to-fields-with-big-queries/25583/4 "2022-05-25T08:40:47Z")

</div>

You could of course implement your own lightweight caching solution – calling a custom site method from your `fetch` statement which would return an index of pages that you can cache using Kirby’s plugin cache (plus a hook setup that flushes your cache when content is changed).

There’s actually a brilliantly detailed thread on caching, with [this post particularly addressing the task you are looking at](https://forum.getkirby.com/t/remember-this-caching-in-kirby/23705/4); that could contain some valuable ideas.

---

_[View the full topic](https://forum.getkirby.com/t/slow-panel-due-to-fields-with-big-queries/25583)._