<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
        <title>Performance on Popular AI</title>
        <link>https://nxfuga.com/tags/performance/</link>
        <description>Recent content in Performance on Popular AI</description>
        <generator>Hugo -- gohugo.io</generator>
        <language>en-us</language>
        <lastBuildDate>Mon, 20 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://nxfuga.com/tags/performance/index.xml" rel="self" type="application/rss+xml" /><item>
            <title>Static Sites at the Edge: Cache Rules Matter More Than Frameworks</title>
            <link>https://nxfuga.com/posts/note-9c2e4f8b0d/</link>
            <pubDate>Mon, 20 Apr 2026 00:00:00 +0000</pubDate>
            <guid>https://nxfuga.com/posts/note-9c2e4f8b0d/</guid>
            <description>&lt;h2 id=&#34;static-sites-at-the-edge-cache-rules-matter-more-than-frameworks&#34;&gt;Static Sites at the Edge: Cache Rules Matter More Than Frameworks&#xA;&lt;/h2&gt;&lt;p&gt;Generators like Hugo turn Markdown into HTML fast; that part is rarely the bottleneck once you ship. What dominates perceived performance is &lt;strong&gt;how long assets stay correct at the edge&lt;/strong&gt;: HTML can be short-lived while immutable hashed assets can be cached aggressively.&lt;/p&gt;&#xA;&lt;p&gt;Treat HTML as dynamic with respect to navigation and metadata updates, even when the origin is static storage. Give long &lt;code&gt;max-age&lt;/code&gt; only to fingerprinted files (&lt;code&gt;main.abc123.css&lt;/code&gt;), and pair that with a purge or version bump path when you redeploy. If you skip invalidation, users see the new layout with old CSS—or vice versa—and it looks like a “framework bug.”&lt;/p&gt;&#xA;&lt;p&gt;Instrumentation completes the picture. Measure Time to First Byte and Largest Contentful Paint by region, not only locally. The winning setup is boring: predictable URLs, explicit cache classes, and automation that updates both content and its references in one coherent release.&lt;/p&gt;&#xA;</description>
        </item></channel>
</rss>
