Image pipeline -Reduce Image Size and Speed Up Previews, Uploads, and Page Loading with Caching

READ: https://www.debug.school/rakeshdevcotocus_468/laravel-microservices-performance-optimization-a-priority-wise-plan-to-speed-up-holidaylandmark-2o9l

Resize, stable previews, efficient uploads, asset caching
======================Expected impact:====================================
Image-heavy pages aur uploads par major benefit; agar yahi main complaint hai toh P4 tak lao.
Make Image Uploads and Pages Faster
Reduce Image Size and Upload Time
Improve Image Previews, Uploads, and Loading
Upload Images Faster and Reuse Cached Images
Fix Slow Image Uploads and Heavy Pages
==============================prompt===========================================
Act as a senior Laravel, Livewire, and image-upload performance engineer. Audit only the image pipeline in HolidayLandmark to identify slow previews, oversized uploads, unnecessary buffering, sequential transfers, and ineffective asset caching.

Enter Plan Mode first. Do not change code, configuration, storage, or server processes until I review and explicitly approve your proposed approach.

Read the project’s AGENTS.md and CLAUDE.md. Verify the installed Laravel and Livewire versions, upload architecture, file-service API contracts, storage backend, and asset-serving configuration.

Inspect these six areas separately:

1. Resize in the browser:
   - Trace image selection, validation, resizing, and upload.
   - Evaluate browser-side resizing with suitable dimensions, quality, and size limits for each image use.
   - Preserve orientation, aspect ratio, transparency, and acceptable visual quality.
   - Handle animated images and unsupported formats explicitly; avoid silently flattening animations.
   - Keep server-side validation authoritative. Explain fallback behavior when browser processing fails.

2. Stable createObjectURL previews:
   - Identify repeated object URL creation, base64 previews, unnecessary rerenders, and memory leaks.
   - Propose creating one preview URL per selected file and reusing it until replacement or removal.
   - Revoke URLs when no longer needed, including component cleanup, without breaking visible previews.
   - Preserve existing images, multiple-image ordering, removal, validation errors, and retry behavior.

3. Pooled, streamed uploads:
   - Inspect browser-to-application and application-to-file-service transfers separately.
   - Identify sequential independent uploads, full-file buffering, repeated reads, and base64 conversion.
   - Evaluate version-compatible streamed multipart uploads and bounded concurrency.
   - Verify stream lifetime, retries, file-service capacity, and memory usage.
   - Preserve authentication, tenant isolation, file order, response mapping, and partial-failure handling.
   - Prevent duplicate files during retries and explain cleanup of orphaned uploads if saving fails.

4. Asset caching:
   - Inspect responses from /file/assets-storage and all applicable web-server, proxy, and storage layers.
   - Propose Cache-Control: public, max-age=31536000, immutable only for genuinely public assets with unique, versioned URLs whose contents never change at the same URL.
   - Identify overwritten URLs and propose versioning before enabling immutable caching.
   - Preserve private-file authorization and use appropriate private or no-store policies for sensitive assets.
   - Explain how image replacement, deletion, and cache invalidation will behave.

5. Save button and submission state:
   - Inspect upload, processing, and save states.
   - Disable submission while required uploads or saving are in progress using version-compatible behavior.
   - Preserve loading feedback, validation messages, and recovery after failure.
   - Prevent repeated submissions without leaving the form permanently disabled.
   - Retain server-side protection against duplicate mutations where needed.

6. Later phase:
   - Evaluate direct signed uploads with short-lived, scoped permissions, file limits, upload completion verification, and orphan cleanup.
   - Preserve server-side ownership checks and file validation before attaching uploads to records.
   - Evaluate queued WebP variants with explicit dimensions and quality, preserving originals where required.
   - Define pending, successful, and failed conversion behavior, fallback URLs, retries, and versioned variant URLs.
   - Keep these changes separate from immediate improvements.

For every finding, show:

- Affected page and user action.
- Exact file paths and current line numbers.
- Existing code or configuration snippet.
- Current preview, upload, save, and delivery flow.
- Why it adds latency, transferred bytes, memory usage, or duplicate work.
- Whether the issue is confirmed or needs measurement.
- Recommended approach and exact locations to change.
- Clearly labelled proposed before/after code or configuration—do not apply it.
- Risks, focused validation, and rollback steps.

Include validation for single and multiple images, large files, transparency, orientation, animated formats, replacement, removal, failed uploads, retries, failed saves, private assets, and repeated submission.

Propose comparable before/after measurements for original and uploaded file sizes, preview time, upload duration, save response time, request count, browser/server memory, and asset cache headers. Compare cold and warm asset loads separately. Do not invent improvement percentages.

Finish with a prioritized implementation plan separating immediate fixes from direct signed uploads and queued WebP variants. Explain the proposed fixes clearly enough for me to review and recommend adjustments.

Stop and wait for my approval. After approval, implement only the agreed changes, preserve existing functionality, and report changed files, line numbers, validation results, and measured improvements. Avoid unrelated refactoring.