Waiting Strategies for Dynamic Pages
Master explicit, implicit, and fluent waits in Selenium so your scraper reliably handles content that loads asynchronously.
Waiting Strategies for Dynamic Pages is a free Web Scraping & Bots lesson on CoddyKit — lesson 4 of 4. You can read the complete lesson below for free — then practise it hands-on in the browser with a built-in code editor and a 24/7 AI tutor. It is part of the Web Scraping & Bots learning path, one of 4 lessons in the course, and your progress syncs across the web and the CoddyKit app.
The Timing Problem
Dynamic pages render content after the initial HTML loads. If your scraper grabs an element before JavaScript injects it, you get a NoSuchElementException or empty data.
Waiting strategies tell Selenium to pause until the page is ready, making automation reliable instead of flaky.
Why Not Just sleep()
A fixed time.sleep(5) is tempting but bad: it wastes time when the page is fast and still fails when the page is slow. Smart waits poll until a condition is true, then continue immediately.
import time
time.sleep(5) # fragile: arbitrary, blocking, often wrongImplicit Waits
An implicit wait sets a global timeout. Selenium retries finding any element for up to that many seconds before failing.
Simple, but it applies to all lookups and cannot wait for arbitrary conditions like visibility or text.
driver.implicitly_wait(10) # seconds, applies globallyExplicit Waits
An explicit wait targets one specific condition. Use WebDriverWait with an expected_conditions check. This is the recommended approach for scraping.
from selenium.webdriver.support.ui import WebDriverWait
from selenium.webdriver.support import expected_conditions as EC
from selenium.webdriver.common.by import By
element = WebDriverWait(driver, 10).until(
EC.presence_of_element_located((By.ID, 'results'))
)Common Expected Conditions
The expected_conditions module covers most needs:
presence_of_element_locatedin the DOM.visibility_of_element_locatedis rendered and visible.element_to_be_clickableready for interaction.text_to_be_present_in_elementwaits for content.
EC.visibility_of_element_located((By.CLASS_NAME, 'price'))
EC.element_to_be_clickable((By.ID, 'load-more'))Waiting for Text
When you need a specific value to appear (for example a price loaded by an API call), wait on the text rather than mere presence.
WebDriverWait(driver, 15).until(
EC.text_to_be_present_in_element((By.ID, 'status'), 'Loaded')
)Fluent Waits
A fluent wait lets you tune the polling interval and ignore specific exceptions while waiting. Useful for slow APIs that throw transient errors.
wait = WebDriverWait(driver, timeout=20, poll_frequency=1,
ignored_exceptions=[StaleElementReferenceException])
wait.until(EC.presence_of_element_located((By.ID, 'data')))Handling Stale Elements
If the DOM re-renders, a stored element reference becomes stale. Re-fetch the element inside the wait or after the page settles instead of reusing the old handle.
from selenium.common.exceptions import StaleElementReferenceException
try:
el.click()
except StaleElementReferenceException:
el = driver.find_element(By.ID, 'btn')
el.click()Waiting for Page Load State
You can poll the document's readyState via JavaScript to confirm the whole page finished loading before scraping.
WebDriverWait(driver, 10).until(
lambda d: d.execute_script('return document.readyState') == 'complete'
)Combining Strategies Wisely
Best practice: avoid mixing implicit and explicit waits (they compound unpredictably). Pick explicit waits for scraping, keep timeouts realistic, and wait for the precise condition your data depends on.
A Reliable Pattern
Wrap waits in a helper so every lookup is robust. This keeps your scraping code clean and consistent.
def wait_for(driver, locator, timeout=10):
return WebDriverWait(driver, timeout).until(
EC.visibility_of_element_located(locator)
)
price = wait_for(driver, (By.CLASS_NAME, 'price')).textQuick Check
Test your understanding of waiting strategies.
Recap
You learned to handle asynchronous content with implicit, explicit, and fluent waits, target conditions like visibility and clickability, recover from stale elements, and avoid fragile fixed sleeps.
Reliable waiting is the foundation of stable dynamic-page scraping.
Frequently asked questions
Is the “Waiting Strategies for Dynamic Pages” lesson free?
Yes — the full text of “Waiting Strategies for Dynamic Pages” is free to read here on the web, and the Web Scraping & Bots course includes 4 lessons in total. To practise it interactively (a built-in code editor and a 24/7 AI tutor) and unlock the rest of the Web Scraping & Bots course, upgrade to CoddyKit PRO.
What will I learn in “Waiting Strategies for Dynamic Pages”?
Master explicit, implicit, and fluent waits in Selenium so your scraper reliably handles content that loads asynchronously. You practise Web Scraping & Bots with hands-on code you run directly in the browser, and a 24/7 AI tutor answers your questions as you work through the lesson.
Do I need any experience to start Web Scraping & Bots?
No prior experience is required. Web Scraping & Bots on CoddyKit is structured for beginners through advanced learners; this is — lesson 4 of 4, so you can start here or from the beginning and move at your own pace.
How long does the “Waiting Strategies for Dynamic Pages” lesson take?
Most CoddyKit lessons take about 5–10 minutes. Each one is bite-sized and interactive, so you make steady progress and pick up exactly where you left off across the web and the app.
Can I write and run code in this Web Scraping & Bots lesson?
Yes. Every Web Scraping & Bots lesson includes a built-in code editor, so you write and run real code right in your browser and get instant AI feedback — no local setup required.
All lessons in this course
- Introduction to Selenium
- Automating Browser Interactions
- Extracting Data from JavaScript
- Waiting Strategies for Dynamic Pages