Core Web Vitals & WebPack Migration

Project scope Improve the page load time of pages in hiverhq. We have close to 310 landing pages in total. These landing pages can be broken down in 3 types/categories of pages broadly. Page within the same category use the same base design template with some customizations on the top, Set up guidelines and best practices to follow from design/dev perspective to keep things fast and smooth on mobile for new pages + optimising existing pages Opportunities to improve the Core Web Vitals Moving from Gulp to Webpack Currently, we bundle all our js in one file, all.js. However , 95% of the JS is unused when individual pages load because each file has a different design / JS implementation. Moving to Webpack can help solve this problem. Eliminate render-blocking resources Please refer to [login to view URL] for more details. Remove unused CSS Please refer to [login to view URL] for more details. Implement Critical to extract, minify and inline above-the-fold CSS automatically Please refer to [login to view URL] You can find more information about opportunities here - [login to view URL] Skill Requirements A minimum of 5 years of frontend development experience Should have undertook at least one project of similar nature where a load time frontend performance improvements were needed Experience working with CDN services (CloudFront, Cloudflare) Deliverables Acceptance Criteria We would require the PageSpeed Insights score for a mobile devices to reach the below numbers: First contentful paint (FCP) should be less than 1 second Speed Index should be less than 4.3 seconds Largest contentful paint (LCP) should be less than 2.5 seconds Time to interactive (TTI) should be less than 3.8 seconds Total Blocking Time (TBT) should be less than 300ms First input delay (FID) should be less than 100ms Cumulative layout shift (CLS) should be less than 0.1 The PageSpeed Insight for the Desktop device should continue to be as it is now or improved. The current PageSpeed Insights score on desktop is about 75 on an average. Tools that assess Core Web Vitals compliance should consider a page passing if it meets the recommended targets at the 75th percentile for all of the above three metrics.