agentleFS
stoffl6781stoffl6781/claude-skill/skills/laravel-performance/SKILL.md

laravel-performance

Skill1 starsChanged 7 months agoMITView on GitHub

Performance-Audit für Laravel. Ziel: jede Seite unter 2 Sekunden. Nutze bei: "Performance", "Seite ist langsam", "Ladezeit", "Caching", "N+1", "Query optimieren", "PageSpeed", "Core Web Vitals", "TTFB", "zu viele Queries", "Cache aufsetzen", "Bilder optimieren", "lazy loading", "OPcache", "Redis", "CDN".

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read Replicas für SELECT-lastige Apps

    line 78

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Laravel Performance Audit

Ziel: Jede Seite unter 2 Sekunden (TTFB < 500ms, LCP < 2.0s).

Performance-Budget

MetrikZielKritisch
TTFB< 200ms> 500ms
FCP< 1.0s> 2.0s
LCP< 2.0s> 3.0s
CLS< 0.1> 0.25
INP< 200ms> 500ms
Page Size< 500KB> 1.5MB
Requests< 25> 50
DB Queries/Request< 10> 30

Core Web Vitals sind auch SEO-Ranking-Faktor → SEO Skill.

Workflow

  1. MESSEN → Baseline (vorher)
  2. BACKEND → Queries, Caching, PHP
  3. FRONTEND → Assets, Bilder, Fonts
  4. SERVER → OPcache, Compression, CDN
  5. MESSEN → Nachher vergleichen
  6. REPORT → Verbesserungen dokumentieren

1. Baseline messen

# Laravel Debug Bar aktivieren (nur lokal!)
# Oder: php artisan debugbar:enable

# Response-Zeiten messen
curl -o /dev/null -s -w "TTFB: %{time_starttransfer}s\nTotal: %{time_total}s\n" {URL}

# DB Queries zählen (Telescope oder Debugbar)

2. Backend-Optimierung

N+1 Queries finden und fixen:

// VORHER (N+1)
$posts = Post::all();
$posts->each(fn($p) => $p->author->name);

// NACHHER (Eager Loading)
$posts = Post::with('author')->get();

Caching:

Cache::remember('key', 3600, fn() => expensiveQuery());

// Laravel Caches
php artisan config:cache    // Config
php artisan route:cache     // Routes
php artisan view:cache      // Views
php artisan event:cache     // Events

Indexes: EXPLAIN auf langsame Queries, fehlende Indexes in Migration hinzufügen.

DB-Tuning (große Tabellen >1M Zeilen):

  • Partitioning nach Datum
  • Read Replicas für SELECT-lastige Apps
  • Connection Pooling (ProxySQL/PgBouncer)

3. Frontend-Optimierung

Vite:

// vite.config.js – Code Splitting
build: { rollupOptions: { output: { manualChunks: { vendor: ['alpinejs'] }}}}

Bilder: WebP/AVIF, lazy loading (loading="lazy"), richtige Größen (srcset), Spatie MediaLibrary Conversions.

Fonts: Lokal hosten, font-display: swap, nur benötigte Weights, preload im <head>.

CSS/JS: Purge unused CSS (Tailwind macht das), defer/async für Scripts.

4. Server-Optimierung

OPcache: opcache.enable=1, opcache.memory_consumption=256, opcache.jit=1255

Compression: Brotli > Gzip in nginx/Apache.

Cache Headers:

# Vite Assets (hashed filenames)
Cache-Control: public, max-age=31536000, immutable

# HTML
Cache-Control: no-cache

CDN (Cloudflare empfohlen):

  • Image Optimization (WebP), Brotli, Page Caching
  • DSGVO: Cloudflare mit EU-Rechenzentren konfigurieren

5. Monitoring

  • Sentry – Error + Performance Monitoring
  • Lighthouse CI – Automatische PageSpeed-Reports in CI
  • Laravel Telescope – Query/Request Profiling (nur lokal)

Pest Performance-Tests

it('homepage responds under 500ms', function () {
    $start = microtime(true);
    $this->get('/')->assertOk();
    expect(microtime(true) - $start)->toBeLessThan(0.5);
});

it('homepage uses less than 15 queries', function () {
    DB::enableQueryLog();
    $this->get('/');
    expect(DB::getQueryLog())->toHaveCount(lessThan: 15);
});

Report-Format

# Performance Report – {Projekt}

| Metrik | Vorher | Nachher | Budget |
|--------|--------|---------|--------|
| TTFB   | 450ms  | 120ms   | <200ms |
| LCP    | 3.2s   | 1.8s    | <2.0s  |
| Queries| 47     | 8       | <10    |

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.