It’s the number of calls to our API. Note that the number of API hit is different from the number of page visits (sometimes also called page hits). Theoretically, every page request will trigger one hit to our API. However, this is not necessary (a waste of API quota) if you install a server caching plugin such as WP Rocket, WP Fastest Cache, WP Super Cache or similar caching plugins – which you should anyway if you are concerned about page speed.
Here’s how it works:
(1) Assuming the server cache is cleared, and your home page receives a new visit which will result in the page being cached.
(2) As part of the first page visit mentioned above, an API call will also be made to our server. At this time, 1 hit will be deducted from your account.
(3) Since the page is now cached, subsequent visits will not trigger a call to our API. The next time our API will be called to clean up CSS is when you update a particular page which causes cache rebuilt.
As you can see, the rate at which your site makes calls to our API really vary depending on how often you update your page. If your page is not updated often, which means the cache are not cleared for days, it means our API will not be called by your site for those periods.
Note – do not confuse “server cache” with “browser cache”. Your visitors clearing their browser cache won’t trigger your website to make call to our API.
