NextJS Expert Required

I have a website. I am indexing the website in Google webmaster. In google webmaster, I tried - PageSpeed Insight - [login to view URL] It has given me following things to improve: 1. First Contentful Paint 10.0 s 2. Serve images in next-gen formats 11.7 s Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. 3. Properly size images 11.25 s 4. Serve images that are appropriately-sized to save cellular data and improve load time. 5. Efficiently encode images 9 s 6. Optimized images load faster and consume less cellular data. 7. Remove unused CSS 7.35 s Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity. 8. Remove unused JavaScript 1.2 s Remove unused JavaScript to reduce bytes consumed by network activity. Learn more. If you are not server-side rendering, split your JavaScript bundles with `[login to view URL]()`. Otherwise, code-split using a third-party library such as loadable-components. 9. Eliminate render-blocking resources 0.9 s Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. 10. Ensure text remains visible during webfont load Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. 11. Does not use passive listeners to improve scrolling performance Consider marking your touch and wheel event listeners as `passive` to improve your page's scroll performance 12. Image elements do not have explicit width and height Set an explicit width and height on image elements to reduce layout shifts and improve CLS. 13. Avoid enormous network payloads Total size was 4,600 KiB Large network payloads cost users real money and are highly correlated with long load times. 14. Avoid chaining critical requests The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. 15. User Timing marks and measures Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. 16. Keep request counts low and transfer sizes small 47 requests • 4,600 KiB To set budgets for the quantity and size of page resources, add a [login to view URL] file. 17. Largest Contentful Paint element 1 element found 18. Avoid large layout shifts 5 elements found These DOM elements contribute most to the CLS of the page. 19. Avoid long main-thread tasks 7 long tasks found Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. 20. Avoid non-composited animations 4 animated elements found Animations which are not composited can be janky and increase CLS Your job is to fix all above 20 issues. I will provide access to my google webmasters.