# waitForPageLoad not really waiting for the page to finish loading

**URL:** <https://forum.katalon.com/t/waitforpageload-not-really-waiting-for-the-page-to-finish-loading/30677>\
**Category:** Web Testing\
**Tags:** katalon-studio\
**Created:** [August 1, 2019, 2:18pm UTC](https://forum.katalon.com/t/waitforpageload-not-really-waiting-for-the-page-to-finish-loading/30677 "2019-08-01T14:18:43Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Russ\_Thomas](https://dub1.discourse-cdn.com/katalon/user_avatar/forum.katalon.com/russ_thomas/32/11884_2.png) [@Russ\_Thomas](https://forum.katalon.com/u/Russ_Thomas)\
**Post date:** [August 1, 2019, 2:26pm UTC](https://forum.katalon.com/t/waitforpageload-not-really-waiting-for-the-page-to-finish-loading/30677/2 "2019-08-01T14:26:38Z")

</div>

Annoying, right?

The question is, what does page load actually mean? In effect, it’s the resources identified by the HTML document (including the HTML itself, images, JavaScript and CSS). Problem then becomes, if the page sends requests to the server for _more_ resources (ajax calls for example) the page isn’t actually “ready” even though it is technically “loaded.”

The cure:

Wait for a set of things unique to the page that should be present and visible. You could also add a fixed delay _after_ that.

If you can nail that requirement for all your pages, you can say good bye to “is the page really ready” issues.

So, there is no one-shot command/API to solve this – the solution is in the (your) approach.

Hope that helps?

---

_[View the full topic](https://forum.katalon.com/t/waitforpageload-not-really-waiting-for-the-page-to-finish-loading/30677)._