Optimising search query

Question

I was wondering if there is a better way to do a query like this, it takes a long time to execute and I know setting the parent variable is where there's a problem but am not sure of an alternative way to do it. Appreciate any and all help!

{% set searchResults = craft.entries.section(['post']).search(searchQuery).with(['catalogue', 'postImage']).where({'field_show': 1}).limit(20) %}
{% paginate searchResults as pageInfo, pageEntries %}

<div class="list">
  {% for item in pageEntries %}
        {% set image = item.postImage[0] ?? null %}
    {% set catalogue = item.catalogue[0] ?? null %}
    <a href="{{ item.url }}" class="item row {{ loop.first ? 'active' }}">
            <div class="col-8 col-sm">
              {{ item.title }}
            </div>
        </a>
    {% endfor %}
    <div class="pagination">
        <div class="row">
            <div class="col">
                {% if pageInfo.prevUrl %}<a href="{{ pageInfo.prevUrl }}">Previous</a>{% endif %}
            </div>
            <div class="col text-center">
                Showing page {{ pageInfo.currentPage }} of {{ pageInfo.totalPages }} pages
            </div>
            <div class="col text-right">
                {% if pageInfo.nextUrl %}<a href="{{ pageInfo.nextUrl }}">Next</a>{% endif %}
            </div>
        </div>
    </div>
</div>
<div class="preview">
    {% for item in pageEntries %}
      {% set image = item.postImage[0] ?? null %}
      {% set catalogue = item.catalogue[0] ?? null %}
      {% set parent = craft.entries.section('parents').relatedTo({targetElement: catalogue, field: 'catalogue'}).one() %}
        <h2>{{ item.title }}</h2>
        <p><a href="{{ parent.url }}" title="{{ parent.title }}">{{ parent.title }}</a></p>
        <p>{{ parent.date|date('l jS F Y') }} {{ parent.time and parent.archived != '1'  ? parent.time|time('g:iA') }}</p>
    {% endfor %}
</div>

Answer 1

It's hard to see what you're actually trying to achieve here, but yes it's likely to do with the amount of queries you're doing on the page.

I would either re-consider the page layout (without knowing what you're trying to achieve by having two loops it's hard to judge) OR pull some, or all of the results asynchronously using javascript so the page rendering isn't blocked whilst the query is being processed.

The newly released sprig plugin may be of interest.