---
title: "Comment by Tarun Sharma on \"Responsive Table Mobile Layout: Rows to Cards in React\" | Hashnode"
description: "Rendering both layouts and hiding one with CSS is the right call for the first paint. One cost the hidden copy still carries: it mounts, so row level hooks and"
url: "https://hashnode.com/posts/responsive-table-mobile-layout-rows-to-cards-in-react/6adc6943a6d3c5bbf61931ce/comment/6adda9e328dd52e7a8073330"
---

[Discussion](https://hashnode.com/posts/responsive-table-mobile-layout-rows-to-cards-in-react/6adc6943a6d3c5bbf61931ce)

Comment [Responsive Table Mobile Layout: Rows to Cards in React](https://hashnode.com/posts/responsive-table-mobile-layout-rows-to-cards-in-react/6adc6943a6d3c5bbf61931ce)

[Tarun Sharma](https://hashnode.com/@101beardo)

[Oct 25](https://hashnode.com/posts/responsive-table-mobile-layout-rows-to-cards-in-react/6adc6943a6d3c5bbf61931ce/comment/6adda9e328dd52e7a8073330)

Rendering both layouts and hiding one with CSS is the right call for the first paint. One cost the hidden copy still carries: it mounts, so row level hooks and avatar images run twice. Putting loading="lazy" on images keeps the hidden layout's images from being fetched, which matters once the list gets long.
