Server-Side Image Thumbnail Generation: WebP, AVIF, Queues

Solving LCP and Page Weight: Automated Image Thumbnail Generation

Is your site loaded with images slow? Each page serves originals at 4000x3000 pixels – LCP skyrockets and users leave. Our experience shows that automatic server-side thumbnail generation is the only way to keep Core Web Vitals in check without manual processing of every file. We implement a turnkey solution in 2–3 days: queue setup, WebP/AVIF formats, CDN caching. This cuts data transfer volume by 40–60% and improves LCP by 30–50%, directly impacting conversion.

How Queue-Based Thumbnail Generation Works

Asynchronous generation is the standard for modern high-upload-load projects. After the user uploads an original to S3 or local storage, a task is dispatched to a queue (Laravel Job, BullMQ, or AWS SQS). It creates several sizes: thumb (200x200) for lists, medium (600x400) for cards, large (1200x800) for galleries. The user doesn't wait – the response comes immediately, and thumbnails appear seconds later. The queue does not block the web server; processing happens in the background.

Why Choose WebP/AVIF?

Modern lossy compression formats save 25–50% in size without noticeable quality loss. For browsers that do not support AVIF, WebP is automatically served via the <picture> element. This reduces LCP by 30–50%. AVIF (based on AV1) offers the best compression but requires more CPU resources for encoding. WebP is a universal choice, supported by 96% of browsers.

Choosing a Generation Strategy: Queue vs Lazy Generation

For sites with high upload frequency (photo galleries, marketplaces), an async queue is the only option – it doesn't block responses and allows horizontal scaling. Lazy generation via Glide suits projects with infrequent uploads or when thumbnail sizes are unknown in advance. It generates the image on the first request and caches it. However, the first visitor experiences generation latency. We help choose a strategy based on your metrics: daily upload count, average image size, infrastructure budget.

What's Included in Our Work

• Audit of current image storage and processing system
• Strategy selection: queue or lazy generation
• Implementation of thumbnail generation with required sizes and formats
• Caching setup (CDN, Cache-Control)
• Integration with existing API and storage (S3, cloud server)
• Documentation for use and maintenance

Why Sharp Outperforms Competitors

The Sharp library (based on libvips) performs operations 4–5 times faster than ImageMagick or GD for typical tasks. This is achieved by working with the image in RAM without intermediate files and efficient CPU cache usage. For Node.js projects, Sharp is the de facto standard. For PHP projects, we recommend Intervention Image with queues or Glide for lazy generation.

Formats and Optimization: Comparison

// Format selection based on browser support
const output = sharp(buffer)
  .resize(800)
  .toFormat(supportsAvif ? 'avif' : supportsWebp ? 'webp' : 'jpeg', {
    quality: supportsAvif ? 60 : supportsWebp ? 80 : 85,
  });

AVIF gives up to 50% savings over JPEG at the same quality. WebP is supported by all modern browsers. For maximum compatibility, use <picture> with multiple formats.

Laravel: Intervention Image + Queue

// Model with automatic thumbnail generation
class Image extends Model
{
    const SIZES = [
        'thumb'  => [200, 200],
        'medium' => [600, 400],
        'large'  => [1200, 800],
    ];
}

// Job for asynchronous generation
class GenerateImageThumbnails implements ShouldQueue
{
    use Dispatchable, InteractsWithQueue, Queueable;

    public function __construct(private Image $image) {}

    public function handle(): void
    {
        $originalPath = Storage::disk('s3')->path($this->image->path);
        $img = \Intervention\Image\Facades\Image::make($originalPath);

        foreach (Image::SIZES as $size => [$width, $height]) {
            $resized = clone $img;
            $resized->fit($width, $height);  // center crop

            $thumbPath = str_replace('original/', "{$size}/", $this->image->path);
            Storage::disk('s3')->put($thumbPath, $resized->encode('webp', 85)->__toString());
        }

        $this->image->update(['processed' => true]);
    }
}

// Upload controller
public function store(Request $request): JsonResponse
{
    $path = Storage::disk('s3')->putFile('original', $request->file('image'));

    $image = Image::create([
        'path'       => $path,
        'user_id'    => auth()->id(),
        'processed'  => false,
    ]);

    GenerateImageThumbnails::dispatch($image);

    return response()->json(['id' => $image->id]);
}

Node.js: Sharp

Sharp is the fastest Node.js library for image processing (based on libvips).

import sharp from 'sharp';
import { S3Client, GetObjectCommand, PutObjectCommand } from '@aws-sdk/client-s3';

const SIZES = {
  thumb:  { width: 200, height: 200 },
  medium: { width: 600, height: 400 },
  large:  { width: 1200, height: 800 },
} as const;

async function generateThumbnails(s3Key: string): Promise<Record<string, string>> {
  const s3 = new S3Client({ region: 'eu-west-1' });

  // Download original
  const { Body } = await s3.send(new GetObjectCommand({
    Bucket: process.env.S3_BUCKET!,
    Key: s3Key,
  }));

  const buffer = Buffer.from(await (Body as any).transformToByteArray());

  const results: Record<string, string> = {};

  await Promise.all(
    Object.entries(SIZES).map(async ([name, { width, height }]) => {
      const thumbnail = await sharp(buffer)
        .resize(width, height, { fit: 'cover', position: 'centre' })
        .webp({ quality: 85 })
        .toBuffer();

      const thumbKey = s3Key.replace('original/', `${name}/`).replace(/\.[^.]+$/, '.webp');

      await s3.send(new PutObjectCommand({
        Bucket: process.env.S3_BUCKET!,
        Key: thumbKey,
        Body: thumbnail,
        ContentType: 'image/webp',
        CacheControl: 'public, max-age=31536000',
      }));

      results[name] = thumbKey;
    })
  );

  return results;
}

Lazy Generation via Glide (PHP)

Glide generates thumbnails on request with a signed URL:

// Route for images
Route::get('/img/{path}', function (Request $request, string $path) {
    $server = League\Glide\ServerFactory::create([
        'source'    => Storage::disk('s3')->getDriver(),
        'cache'     => Storage::disk('local')->getDriver(),
        'cache_path_prefix' => '.cache',
        'base_url'  => '/img',
        'max_image_size' => 2000 * 2000,
    ]);

    // Validate URL signature
    League\Glide\Signatures\SignatureFactory::create(config('app.key'))
        ->validateRequest('/img/' . $path, $request->all());

    return $server->getImageResponse($path, $request->all());
})->where('path', '.*');

// Generate signed URL
$url = (new League\Glide\Urls\UrlBuilderFactory)
    ->create('/img', config('app.key'))
    ->getUrl('uploads/photo.jpg', ['w' => 400, 'h' => 300, 'fit' => 'crop']);

Timeline and Cost

Queue-based thumbnail generation (Laravel Job or BullMQ Worker) with S3 storage: 2–3 days. Lazy generation via Glide with CDN caching: 3–4 days. Complex projects with multiple CMS integrations: up to 5 days. Cost is calculated individually based on complexity and stack. Contact us for a consultation and exact timeline. Order an audit and image optimization – we will select the optimal strategy for your project.

Our engineers have 5+ years of experience optimizing high-load sites. More than 30 projects with similar architecture are successfully running in production. Get a consultation – we will assess your project and propose a turnkey solution, guaranteeing a 30–50% LCP reduction after implementation.

Backend Development Services: Laravel, Node.js, Go, Django, PostgreSQL

On a production server at 3:14 AM, the Laravel Jobs queue stopped processing. 40,000 unprocessed jobs in Redis. Cause: worker crashed due to a memory leak in one of the Jobs (leak via a static variable in an Eloquent observer), supervisor didn't restart it because of misconfigured stopwaitsecs. This is not a hypothetical scenario — it's Tuesday. We analyzed such an incident on a project with 500 RPS load: diagnosis took 4 hours, fix — 20 minutes. So you don't lose money on downtime, we offer backend development services with a focus on production-grade reliability. We'll assess your project in 2 days.

Backend is what works when no one is watching. Or doesn't work. We guarantee you'll have the first option.

How do we ensure production-grade reliability from day one?

What we do correctly from day one

Service Layer over Fat Controllers. Controller receives HTTP request, validates it via Form Request, passes data to Service, returns response. Business logic in Service, not Controller. This sounds trivial, but most legacy projects have controllers with 500 lines and SQL queries inside.

Repository Pattern we use cautiously. If you just wrap Model::where(...) in a repository method — that's boilerplate without benefit. Repository is justified when: you need to abstract from the data source (DB + cache + external API) or when query logic is complex enough to isolate.

Jobs, Events, Listeners. Everything that can be async — make async. Sending email, PDF generation, external API sync, aggregate recalculation — into Queue. Laravel Horizon for queue monitoring in Redis: see throughput, failed jobs, processing time per queue.

How Octane handles high load

Laravel Octane with RoadRunner or Swoole keeps the app in memory between requests — removes bootstrap overhead (config loading, class autoloading) on each HTTP request. Gain: 3–8x on synthetic benchmarks, 2–4x on real applications. Important: no state between requests in static variables — that leads to exactly the incidents from the beginning. We use this in projects with >1000 RPS.

What to do about N+1 queries

N+1 is the most common cause of slow pages in Laravel apps. Standard story: page worked fine on dev with 10 records, on production with 10,000 — 8-second load.

Laravel Debugbar in dev environment shows the number of queries per page. More than 20 queries per page — signal for audit.

Model::preventLazyLoading(! app()->isProduction());

Telescope for profiling in staging: logs all queries, jobs, mail, notifications with time detail. Numbers: after implementing eager loading, page load time drops from 8s to 0.3s — 27 times faster.

PostgreSQL: indexes that are actually needed

PostgreSQL 14+ is the primary DB on all projects. We use PgBouncer + PostgreSQL combination. 10+ years experience, more than 50 backend projects, 5 years on the market.

How PostgreSQL helps avoid slow queries

Composite indexes for frequent WHERE + ORDER BY. If you have WHERE user_id = ? AND status = ? ORDER BY created_at DESC — you need (user_id, status, created_at DESC). A separate index on (user_id) doesn't help much with sorting.

Partial indexes. If 95% of queries go with WHERE status = 'active':

CREATE INDEX idx_orders_active ON orders (created_at DESC)
WHERE status = 'active';

The index is small, fast, covers the main load.

GIN indexes for JSONB and arrays. @> operator without GIN index — seq scan. With index — fast even on millions of rows.

GIN for full-text search. to_tsvector + GIN instead of LIKE '%query%'. LIKE without index is always seq scan. With pg_trgm extension and gin_trgm_ops — supports LIKE with index, useful for CRM search by partial match.

Connection pooling: why it's more important than it seems

Rails, Laravel, Django open a new connection to PostgreSQL for each PHP/Python process. With 100 workers — 100 connections. PostgreSQL starts degrading from 200–300 active connections — overhead on connection management becomes significant.

PgBouncer — connection pooler in front of PostgreSQL. Transaction pooling mode: connection to PostgreSQL is occupied only during a transaction, returned to pool between requests. 1000 application workers → 20–50 actual connections to PostgreSQL. This reduces latency by 40% and hosting costs by 30%.

Node.js with Fastify: when it's better than Laravel

Node.js is justified for:

• Realtime: WebSocket servers, Server-Sent Events, chat, live updates
• Streaming: large files, video, streaming data
• High I/O concurrency: many parallel requests to external APIs without heavy business logic
• Serverless: Lambda/Cloud Functions — Node.js starts faster than PHP

Fastify over Express: 2–3 times faster on benchmarks, built-in JSON Schema validation, better TypeScript support, plugin architecture.

Typical realtime architecture: Laravel — core business logic and REST API. Node.js + Socket.io or ws — WebSocket server. Laravel publishes events to Redis Pub/Sub, Node.js subscribes and broadcasts to clients. This separation allows scaling the WebSocket server independently of the main app.

Go: microservices and high load

Go we use for:

• High-load microservices (>10,000 RPS)
• Background workers with strict latency requirements
• DevOps tools and CLI
• gRPC services in microservice architecture

Goroutines — thousands of times cheaper than OS threads. 10,000 concurrent connections on Go is normal on one server.

But Go is not a silver bullet. Development is slower than Laravel: more boilerplate, no ORM at Eloquent level, error handling with if err != nil everywhere. Justified only when performance is a real requirement, not an assumption.

Django and Python backend

Django with DRF (Django REST Framework) — for tasks where Python is needed: ML pipelines, data processing, integrations with AI tools.

Celery for background tasks — similar to Laravel Queue but more complex to configure. Celery Beat for cron tasks.

Django ORM vs raw SQL: ORM is convenient for CRUD. For analytical queries with multiple JOINs, window functions, and CTEs — connection.execute() with raw SQL is more readable and predictable.

Redis: not just cache

Redis in our projects plays multiple roles:

Redis Cluster for horizontal scaling. Sentinel for automatic failover on standalone setups.

Deployment and infrastructure

Docker + docker-compose — standard for local development and production. Each service in a container: PHP-FPM/Octane, Nginx, PostgreSQL, Redis, Queue Worker, Scheduler.

CI/CD via GitHub Actions:

1. Run tests (PHPUnit / Pest, Vitest, Playwright)
2. Build Docker image
3. Push to Container Registry
4. Deploy: docker pull → docker-compose up -d on server, or Kubernetes rolling update

Zero-downtime deploy for Laravel: php artisan down --secret=TOKEN is not needed with proper configuration. Strategy: new container starts next to the old one, Nginx switches traffic after health check, old container stops.

Monitoring: Sentry for exception tracking with alerting in Slack/Telegram. Grafana + Prometheus (or Grafana Cloud) for metrics: CPU, memory, request rate, queue depth, database connection count. Alerts on: error rate > 1%, p99 latency > 2s, queue depth > 1000 jobs.

What's included in turnkey work

• Architecture design (API documentation, DB schema, service diagram)
• Implementation according to agreed specification with code review
• CI/CD, monitoring, alerting setup
• Load testing (k6, wrk) with report
• Handover of source code, access, deployment instructions
• Training of customer's team (2-3 sessions)
• Warranty support for 1 month after delivery

Timeline benchmarks

Pricing is calculated individually after analyzing load, integrations, and business logic. Contact us for a free audit of your current backend — get an optimization plan in 2 days. Request a consultation.