<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Nextjs on RPAlert Blog</title><link>https://rpalert.dev/blog/tags/nextjs/</link><description>Recent content in Nextjs on RPAlert Blog</description><generator>Hugo</generator><language>en</language><lastBuildDate>Thu, 16 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://rpalert.dev/blog/tags/nextjs/index.xml" rel="self" type="application/rss+xml"/><item><title>Most LCP Fixes Come Down to One Image</title><link>https://rpalert.dev/blog/posts/most-lcp-fixes-come-down-to-one-image-2i09/</link><pubDate>Thu, 16 Apr 2026 00:00:00 +0000</pubDate><guid>https://rpalert.dev/blog/posts/most-lcp-fixes-come-down-to-one-image-2i09/</guid><description>Most LCP issues trace back to one image — a CSS background-image, a missing fetchpriority, or a lazy-loaded hero. Find the LCP element first.</description></item></channel></rss>