In this document:
Introduction
This guide explains why Simply Schedule Appointments queries may appear on every page of your site, even if there’s no Appointment Types block embedded.
We’ll explain why these queries are necessary and how SSA is designed to be as optimized as possible, minimizing any impact on your site’s performance.
The Query monitor plugin shows that SSA database queries are loading even on pages without SSA.
SSA needs to run certain queries across all pages of your site for the following reasons:
- To ensure the SSA appointment WordPress block works correctly across your site, it is registered on every page load during WordPress’s init action. This lets WordPress recognize the block everywhere and load its code and styles when needed. This is by design when working with a WordPress block.
- SSA consistently checks for any version changes or database migrations that need to be run – this is to ensure a seamless booking experience and avoid having any broken features/UI
That’s why SSA must run queries on all your site pages; without it, SSA won’t perform some functions properly.
Do SSA queries affect my site’s performance?
We’ve already optimized SSA to:
- Run only the queries essential to plugin functionality site-wide.
- Trigger only the necessary SSA logic to ensure minimal performance impact on your site.
Hence, the effect of the SSA queries should be minimal on the overall site performance.
If you’re experiencing slow loading of the booking calendar on your site, check out our guide on how to fix that.
Related Guides
-
Asset CleanUp Pro Conflict – Redirecting to Homepage
-
All-In-One Security (AIOS): “You are not authorized to perform this action”
-
AMP Conflict — Loading Issues on Mobile
-
Email Delivery Issues