Refer to the exhibit. An engineer works to optimize a website by reducing the page-load time to below 500 ms. The engineer set up a Cisco ThousandEyes page-load test to baseline the current website…

Question

Options

• AOptimize the AJAX query calling functions.
• BMove IMG elements to the bottom of the document body.
• CImplement lazy loading for objects on the page.
• DUse a CDN to load fonts faster.

• A
  6% (2)
• B
  9% (3)
• C
  82% (28)
• D
  3% (1)

Explanation

Lazy loading (C) is correct because a ThousandEyes page-load waterfall showing many objects loading simultaneously - especially below-the-fold images and media - is the classic signal that resources are being fetched before the user needs them. Lazy loading defers those non-critical resources until they're about to enter the viewport, directly cutting initial page-load time.

Why the distractors are wrong:

• A (AJAX optimization): AJAX queries affect dynamic data fetching after the page loads, not the initial load time. Unless the waterfall specifically shows blocking XHR calls, this isn't the right lever.
• B (move IMG to bottom): Modern browsers parse HTML and load images in parallel regardless of position; moving <img> tags doesn't meaningfully change load time and can break page layout.
• D (CDN for fonts): CDNs reduce latency for font files, but fonts are typically small and already cacheable - they rarely account for hundreds of milliseconds of load time. A CDN would help if font loading was the identified bottleneck, but it's not the general fix.

Memory tip: Think "lazy = wait until needed." When a page has lots of images or media and load time is high, the exam is almost always pointing at lazy loading as the targeted, low-effort fix - CDN is a red herring unless the exhibit specifically highlights geographic latency or font waterfall spikes.

No community discussion yet for this question.