<?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: Now Online</title>
    <description>The latest articles on DEV Community by Now Online (@nowonlinedk).</description>
    <link>https://dev.to/nowonlinedk</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%2F3123655%2Ff64afa51-9b9e-4857-9652-ab404da11c5b.png</url>
      <title>DEV Community: Now Online</title>
      <link>https://dev.to/nowonlinedk</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/nowonlinedk"/>
    <language>en</language>
    <item>
      <title>How we get small-business WordPress sites under 2 seconds</title>
      <dc:creator>Now Online</dc:creator>
      <pubDate>Tue, 10 Nov 2026 09:11:53 +0000</pubDate>
      <link>https://dev.to/nowonlinedk/how-we-get-small-business-wordpress-sites-under-2-seconds-47nh</link>
      <guid>https://dev.to/nowonlinedk/how-we-get-small-business-wordpress-sites-under-2-seconds-47nh</guid>
      <description>&lt;p&gt;At our small web agency in Odense, Denmark, most clients are local businesses: consultants, webshops, therapists, craftsmen. They don't care about Core Web Vitals as a metric. They care that the site loads on a phone and that people call them. Here is the checklist we run on every new WordPress build.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. Start with a lean theme
&lt;/h2&gt;

&lt;p&gt;We build with a lightweight theme and Elementor, but keep the global widget set small. Every unused add-on pack we remove is JavaScript the browser never has to parse.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Fix images before anything else
&lt;/h2&gt;

&lt;p&gt;On small-business sites, oversized hero images are the number one cause of slow pages. We convert to WebP, cap hero images at around 200 KB, and lazy-load everything below the fold.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Cache at the server, not just with a plugin
&lt;/h2&gt;

&lt;p&gt;We host on Danish servers with server-side page caching, then add a caching plugin only for what the server can't handle. Two layers fighting each other is a common reason for weird bugs.&lt;/p&gt;

&lt;h2&gt;
  
  
  4. Audit plugins every quarter
&lt;/h2&gt;

&lt;p&gt;The typical site we inherit has 30+ plugins. Most can be removed or replaced with a few lines of code. Fewer plugins means faster pages and fewer security updates.&lt;/p&gt;

&lt;h2&gt;
  
  
  5. Measure on a real phone
&lt;/h2&gt;

&lt;p&gt;Lighthouse scores are useful, but we always test on a mid-range Android over 4G. That is what the customer's customers use.&lt;/p&gt;

&lt;h2&gt;
  
  
  The result
&lt;/h2&gt;

&lt;p&gt;With these steps most of our builds load in under two seconds on mobile, and clients can still edit everything themselves. If you're curious how this looks in practice, here is how we approach a &lt;a href="https://nowonline.dk/ny-hjemmeside/" rel="noopener noreferrer"&gt;new website for small businesses&lt;/a&gt; (the page is in Danish).&lt;/p&gt;

&lt;p&gt;What's on your performance checklist? I'd love to hear what other agencies do.&lt;/p&gt;

</description>
      <category>wordpress</category>
      <category>webdev</category>
      <category>performance</category>
      <category>seo</category>
    </item>
  </channel>
</rss>
