DEV Community: Code Cat

Scaling 98/100 PageSpeed for 100+ Pages: My Technical Workflow

Code Cat — Thu, 02 Apr 2026 04:13:06 +0000

Optimizing a single landing page is one thing. Maintaining a "Green Zone" score across 100+ pages (services, districts, and blog) is a technical challenge.

I managed to hit 93–98 on Mobile and 98–100 on Desktop without a huge dev team, using Claude AI as my co-pilot. Here is the exact technical workflow.

1. The LCP Revolution: `fetchpriority` over Preload

Largest Contentful Paint (LCP) is the most critical Core Web Vital. I ditched CSS background-image for all Hero banners.

The Fix: Moved to standard <img> tags with fetchpriority="high".
The Logic: This signals the browser to prioritize the image immediately in the HTML stream. While I use <link rel="preload"> on the homepage, the <img> + fetchpriority combo is much cleaner to maintain across 40+ unique service templates without cluttering the <head>.

2. Taming the "Analytics Tax"

Tracking scripts (Google Analytics, Yandex Metrica, Roistat) are performance killers. On mobile, they can strip 10–15 points off your score.

The Hack: I wrapped all tracking scripts in a requestIdleCallback with a 3000ms timeout.
The Result: Scripts load only when the main thread is idle. If a user bounces in under 3 seconds, they weren't going to convert anyway. For everyone else, the UI is instant.

3. Rational Image Strategy: WebP vs JPG

I didn't follow the "WebP everywhere" dogma blindly:

Home & District Pages: Use WebP for maximum byte savings on high-traffic entry points.
Service Pages: Kept optimized JPGs.

With fetchpriority="high", the LCP difference is negligible, but the visual fidelity of JPG remains superior.

4. The Infrastructure

Critical CSS: Inlined core styles for the first fold directly into the <head>.
Self-hosted Fonts: Switched to local woff2 files (Inter) to eliminate external DNS lookups.
Server-side: Configured .htaccess for a 1-year static cache and Gzip/DEFLATE compression.

5. Scaling with AI

Optimizing 100+ pages manually is a nightmare. I used Claude to:

Refactor 40+ PHP templates.
Generate complex .htaccess rules.
Audit Schema.org JSON-LD for every page type.

The Bottom Line: Performance isn't just a metric; it's clean engineering. By focusing on native HTML5 attributes and smart script loading, you can achieve elite speeds at scale.

What’s your go-to trick for LCP optimization? Let’s discuss in the comments!

The $20 "Easy Button" Illusion: Why Claude Won't Save Your Shitty Project

Code Cat — Sun, 29 Mar 2026 13:37:27 +0000

Introduction

The feed is flooded with "success" stories: "I fired my dev team, bought a $20 Claude subscription, and built a SaaS in an afternoon." As a marketing lead and crisis manager used to putting out digital fires, let’s be blunt: this is a dangerous trap. Claude is not a replacement for a professional; it’s a force multiplier. If you think a LLM is your new "everything" department, you’re not building a business—you’re building a house of cards. Claude is a jet engine that will either propel you to the moon or smear your project across the pavement if you don’t have a license to fly.

The Reality Check: Why Claude Isn't a "Silver Bullet"

Many beginners expect Claude to deliver a "polished diamond" from a prompt like "Make me a SEO-optimized cleaning service website." On the surface, you get code. It might even run. But here is where the "AI magic" hits the brick wall of reality:

Infrastructure Blindness: Claude doesn’t know your server's PHP version, your Nginx config, or your database limits. It gives you "average" code that often breaks in specific production environments.

The Core Web Vitals Nightmare: AI can write logic, but it rarely accounts for DOM size, render-blocking JS, or Cumulative Layout Shift (CLS). You might get a working site that Google’s search bots absolutely despise.

Logic Hallucinations: In complex scripts, Claude can confidently invent non-existent functions or create security loopholes. If you can’t read the code you’re generating, you’re essentially blindfolded at the wheel.

Why AI Won't Replace Specialists (Yet)

Business Context is King: Claude doesn't know your CPA is bleeding or that you have a cash flow gap tomorrow. It provides technical solutions in a vacuum, ignoring the strategic "why" behind the "how."

Garbage In, Garbage Out: A vague prompt leads to bloated, messy code. To manage Claude effectively, you must understand site architecture better than the AI does.

Crisis Management: When your site goes down at 3 AM after an update, Claude won't SSH into your server to fix the bug. You still need to know how to use a terminal.

The Verdict

AI is an amplifier for your brain, not a substitute for it. It’s a hammer that builds a house in the hands of a carpenter, but only smashes thumbs in the hands of an amateur.

If you want to move 10x faster, learn the fundamentals. Claude accelerates the pros; it only helps the posers fail at record speed.

Is your site builder hurting your ROI?

Code Cat — Sun, 29 Mar 2026 07:52:48 +0000

Most marketers love Tilda for its simplicity, but for SEO, it’s a bottleneck. Bloated code and limited control over how bots crawl your site lead to higher lead costs.

I decided to break free. Using Claude AI, I’ve built a custom site from scratch.
The result?
✅ 100% control over indexation.
✅ Lightning-fast performance.
✅ SEO updates that take seconds, not hours.

Stop paying for limitations. Start owning your code. 🛠️