Talks
Speakers
Events
Topics
Sign in
Home
Talks
Speakers
Events
Topics
Leaderboard
Use
Analytics
Sign in
Suggest modification to this talk
Title
Description
Date
Summarized using AI?
If this talk's summary was generated by AI, please check this box. A "Summarized using AI" badge will be displayed in the summary tab to indicate that the summary was generated using AI.
Show "Summarized using AI" badge on summary page
Summary
Markdown supported
In the presentation titled 'How I brought LCP down to under 350 ms for Google-referred users', Paweł Pokrywka discusses his successful strategies for decreasing the Largest Contentful Paint (LCP) metric, vital for web performance and optimization. Key points of the presentation include: - **Introduction to LCP**: LCP measures the time it takes for the largest element on a webpage to load, reflecting page performance. Google encourages lower LCP for improved search result rankings and higher conversion rates. - **Personal context**: Paweł, founder and CTO of Planu V, shares how their application, which relies heavily on Google traffic, adopted Next.js as part of a frontend migration. - **Demonstration of performance**: Through a live demo, Paweł shows an LCP of 140 milliseconds by employing gzip compression and prefetching techniques. The demo illustrates how his site ranks second for specific search phrases. - **Technical exploration**: The session transitions to reverse engineering the performance by analyzing network requests while utilizing developer tools, highlighting the significance of prefetching elements in enhancing load times. - **Critique of AMP**: Paweł discusses issues with AMP (Accelerated Mobile Pages), advocating for a system allowing developers to retain control of their designs while ensuring fast loading through Signed Exchanges (SXG). These enable caching with enhanced privacy measures. - **Implementation of SXG**: He describes the simple activation process for Cloudflare users and emphasizes the importance of crafting cache-friendly responses due to stricter SXG requirements, including avoiding personalization and limiting cookie use. - **Optimizing Sub-resources**: Emphasis is placed on prefetching sub-resources to reduce loading times, detailing the use of Link HTTP headers for advanced resource management. - **Monitoring and adjusting strategies**: Paweł reminds participants of the need for continual adjustments to caching strategies to maintain performance despite potential Google updates or changes in website configurations. In conclusion, Pawel advocates for exploring these SXG strategies further through his blog, emphasizing the importance of optimizing both user experience and web performance metrics like LCP.
Suggest modifications
Cancel