<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Ricky Hersey</title>
    <description>The latest articles on DEV Community by Ricky Hersey (@shopsitetemplates).</description>
    <link>https://dev.to/shopsitetemplates</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4211601%2Fd5ded10b-dd23-4d4c-8e9d-a2825c41c63f.png</url>
      <title>DEV Community: Ricky Hersey</title>
      <link>https://dev.to/shopsitetemplates</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/shopsitetemplates"/>
    <language>en</language>
    <item>
      <title>Building Single-File HTML Templates: Clean Code Without the Framework Overhead</title>
      <dc:creator>Ricky Hersey</dc:creator>
      <pubDate>Tue, 27 Oct 2026 20:31:52 +0000</pubDate>
      <link>https://dev.to/shopsitetemplates/building-single-file-html-templates-clean-code-without-the-framework-overhead-43fc</link>
      <guid>https://dev.to/shopsitetemplates/building-single-file-html-templates-clean-code-without-the-framework-overhead-43fc</guid>
      <description>&lt;p&gt;When building websites, it is easy to get caught up in modern framework stacks, build steps, and endless dependencies. However, for many business and landing pages, keeping everything clean, fast, and self-contained in a single file is hard to beat.&lt;/p&gt;

&lt;p&gt;Here is why keeping HTML, CSS, and JavaScript inline within a single document works so well for template efficiency:&lt;/p&gt;

&lt;h3&gt;
  
  
  The Advantages of Inline Single-File Builds
&lt;/h3&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Zero Build Steps:&lt;/strong&gt; No need for compilers, bundlers, or package managers. Just open the file and code.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Instant Deployment:&lt;/strong&gt; Uploading a single clean file via SFTP takes seconds and eliminates missing asset paths.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Streamlined Performance:&lt;/strong&gt; Less network overhead means lightning-fast load times and consistent 90+ PageSpeed Insights scores.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Complete Code Portability:&lt;/strong&gt; Anyone can easily inspect, understand, and customize the site without needing complex environments.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;By stripping away unnecessary framework bloat, you deliver pure performance directly to the browser.&lt;/p&gt;

&lt;p&gt;Do you prefer keeping small project setups completely self-contained, or do you still reach for build tools by default?&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>html</category>
      <category>css</category>
      <category>javascript</category>
    </item>
    <item>
      <title>How I Compress Website Images with Squoosh for Blazing-Fast Page Speeds</title>
      <dc:creator>Ricky Hersey</dc:creator>
      <pubDate>Tue, 27 Oct 2026 20:29:24 +0000</pubDate>
      <link>https://dev.to/shopsitetemplates/how-i-compress-website-images-with-squoosh-for-blazing-fast-page-speeds-45n4</link>
      <guid>https://dev.to/shopsitetemplates/how-i-compress-website-images-with-squoosh-for-blazing-fast-page-speeds-45n4</guid>
      <description>&lt;p&gt;Heavy, unoptimized images are one of the fastest ways to kill a website's load time and drag down your PageSpeed Insights scores. When you're building lightweight, single-file HTML templates, every asset needs to be lean.&lt;/p&gt;

&lt;p&gt;Here is my go-to workflow for keeping images small without sacrificing visual quality:&lt;/p&gt;

&lt;h3&gt;
  
  
  The Squoosh Optimization Process
&lt;/h3&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Resolution Cap:&lt;/strong&gt; I resize images down to a clean, crisp standard (typically 800x600 for optimal web display).&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Modern Formats:&lt;/strong&gt; I convert and compress everything into &lt;strong&gt;AVIF&lt;/strong&gt; and &lt;strong&gt;WebP&lt;/strong&gt; formats. These formats offer incredible compression ratios compared to traditional JPEGs or PNGs.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Quality Tuning:&lt;/strong&gt; I dial in the compression settings on &lt;a href="https://squoosh.app" rel="noopener noreferrer"&gt;Squoosh.app&lt;/a&gt; to get file sizes down significantly while keeping details sharp.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;By keeping image payloads minimal, every page loads instantly on mobile and desktop alike, keeping performance scores consistently in the 90s and 100s.&lt;/p&gt;

&lt;p&gt;How do you handle asset compression in your workflow?&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>performance</category>
      <category>frontend</category>
      <category>css</category>
    </item>
    <item>
      <title>Why I Hand-Code Lightweight, Single-File HTML Templates for Maximum Speed</title>
      <dc:creator>Ricky Hersey</dc:creator>
      <pubDate>Tue, 27 Oct 2026 20:23:41 +0000</pubDate>
      <link>https://dev.to/shopsitetemplates/why-i-hand-code-lightweight-single-file-html-templates-for-maximum-speed-gm4</link>
      <guid>https://dev.to/shopsitetemplates/why-i-hand-code-lightweight-single-file-html-templates-for-maximum-speed-gm4</guid>
      <description>&lt;p&gt;In a web landscape dominated by heavy frameworks and bloated dependencies, I build high-performance web templates using clean, hand-coded inline HTML, CSS, and JavaScript.&lt;/p&gt;

&lt;h3&gt;
  
  
  Why Single-File Lightweight Code Matters
&lt;/h3&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Lightning Speed:&lt;/strong&gt; Achieving 90+ PageSpeed Insights scores right out of the box.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Zero Dependency Overhead:&lt;/strong&gt; No npm packages, build tools, or complex setups required.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Pure Portability:&lt;/strong&gt; Easy to edit, inspect, and host on any server seamlessly.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Whether you are launching a quick landing page or looking for minimal code overhead, single-file development keeps things fast, clean, and direct. &lt;/p&gt;

&lt;p&gt;What's your take on lightweight static sites vs. modern framework stacks?&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>html</category>
      <category>css</category>
      <category>performance</category>
    </item>
  </channel>
</rss>
