Business
Jobs
  • About Us
  • Solutions
    • Job Postings
      Post your job and receive qualified candidates in 48h.
    • Candidate Assessments
      500+ technical and psychological tests, plus anti-fraud.
    • Headhunting
      Tailor-made executive search from start to finish.
    • Payroll + EOR
      Payroll dispersal and EOR across 15+ LATAM countries.
  • Pricing
  • Jobs

0

135
Views
Why does the Image Component from next/image take a long time to load images?

Why do the images that I display using the Image component take much longer to load than those that I display using the img tag? My images are in webp format. In the screenshot https://ibb.co/jLsnLd4, the two links at the bottom are just an img tag, then some waiting and next/image loads the images. Maybe it's because the lazy loading functionality is implemented this way? The Image component uses hook useIntersection: https://github.com/vercel/next.js/blob/52139a41e90b668aa7e393c18990f1d1f5db9e22/packages/next/client/image.tsx#L10 Then this hook uses IntersectionObserver: https://github.com/vercel/next.js/blob/0af3b526408bae26d6b3f8cab75c4229998bf7cb/packages/next/client/use-intersection.tsx#L89 Or maybe the reason is that the Image img component always has decoding="async"? https://developer.mozilla.org/en-US/docs/Web/API/HTMLImageElement/decoding Can this affect the download speed in any way? Do you have any suggestions?

about 4 years ago · Juan Pablo Isaza
Answer question
Find remote jobs

Discover the new way to find a job!

Top jobs
Top job categories
Business
Post vacancy Pricing Sales
Legal
Terms and conditions Privacy policy
© 2026 PeakU Inc. All Rights Reserved.
Andres GPT
Show me some job opportunities
There's an error!