perf: upgrade website and docs images to WebP

[imrja8]

video.mp4

While the Dokploy website is already fast, images can sometimes lag behind the text on slower connections. Video demonstrating Dokploy website image slow load even with a 200mbps connection.

What does this PR do?

This PR optimizes the website and documentation by converting .png visual assets to .webp and updating the corresponding codebase references.

Images were converted using cwebp with maximum lossless compression (-lossless -z 9) to ensure 99.9% pixel-perfect original quality with zero visual degradation.

Using WebP cuts the image payload significantly, ensuring visuals load much closer to the speed of the content. At Dokploy's scale, this also noticeably reduces server egress bandwidth, improves the Largest Contentful Paint (LCP), and prevents layout shifts.

Size Reductions

Overall, this permanently removes ~12.6 MB from the codebase.

/apps/website/public

• Before: ~6.7 MB
• After: ~3.3 MB
• Savings: ~3.4 MB (~51% reduction)
• Converted: 41 images

/apps/docs/public

• Before: ~16.3 MB
• After: ~7.1 MB
• Savings: ~9.2 MB (~56% reduction)
• Converted: 93 images

Note: Comparision file sizes are calculated using macOS Base-10 metric, where 1 MB = 1,000,000 bytes. There may be slight differences in reported megabyte sizes depending on OS and file size calculation system, these numbers were calculated on Mac Air M3. The percentage comparison serve as a more universally accurate metric.

Additional Details

• Hardcoded URLs: Updated Hero.tsx and pricing-legacy.tsx to use a relative path (/banner.webp) instead of the absolute URL (https://dokploy.com/banner.png) so the hero banner resolves properly when testing locally or on preview deployments.
• Ignored Metadata: Safely skipped SEO and favicon assets (og.png, apple-touch-icon.png, favicon.png) to keep platform fallback compatibility intact.

Testing & Verification

Because there are over 130 images changed, I couldn't check every single page manually. Here is how I verified the changes:

• Ran a project-wide search to make sure no old .png references were accidentally left behind in any .mdx or .tsx files.
• Double-checked that the og.png and favicon files were correctly ignored by the replacement script.
• Booted up both pnpm run website:dev and pnpm run docs:dev and clicked through a few main pages to make sure everything loads correctly and there are no broken image links.

[imrja8]

@narcisonunez This pr is ready for review.