Laravel Debugging Query Performance

Context:

I'm encountering significant performance degradation in a specific data retrieval scenario. After refactoring some Eloquent queries, the application is noticeably slower, particularly on pages involving complex relationships.

Problem:

Using Laravel Debugbar, I'm seeing unusually high query execution times, often exceeding 1.5 seconds for what should be relatively straightforward data fetches. The raw SQL generated appears efficient, leading me to suspect the issue might be within Eloquent's hydration or relationship loading, or possibly an overhead from Laravel debugging tools themselves.

Example Code Snippet:

$users = User::with(['posts' => function($query) {
    $query->where('status', 'published');
}])->get();
// This particular query, or similar complex ones, are showing high times in Debugbar.

Question:

What are the common pitfalls in Eloquent relationship loading that could cause such discrepancies between raw SQL efficiency and reported execution times in a Laravel debugging context?