Welcome to the Treehouse Community

The Treehouse Community is a meeting place for developers, designers, and programmers of all backgrounds and skill levels to get support. Collaborate here on code errors or bugs that you need feedback on, or asking for an extra set of eyes on your latest project. Join thousands of Treehouse students and alumni in the community today. (Note: Only Treehouse students can comment or ask questions, but non-students are welcome to browse our conversations.)

Looking to learn something new?

Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and a supportive community. Start your free trial today.

JavaScript Introduction to jQuery DOM Traversal find(), prev(), and next()

Learning coding
seal-mask
.a{fill-rule:evenodd;}techdegree
Learning coding
Front End Web Development Techdegree Student 9,937 Points

Why would you want to cut down searches in the DOM?

If searching in the DOM goes automatically why would you mind about it? I would say press the button and let it search. Or does cutting down searching the DOM improve sites performance like rendering?

1 Answer

Steven Parker
Steven Parker
220,925 Points

Here's the answer I gave to your previous question on this same issue:

It's primarily a matter of efficiency.

As you suspected, fewer and/or more limited searches improve performance. It's faster to avoid replicating tasks than to do them repeatedly.

Also, there are many times when you have only a specific element to begin with, and DOM traversal will allow you to find a related element where no search could be constructed.