This is amazing @mohammed-ahmed7

Thanks for sharing your tech stack here. Could you also share what steps you took and some challenges you faced when improving the performance? This will be so beneficial for fellow community members.

Biggest wins came from four areas:

1. Rendering strategy – kept the landing page server-rendered with ISR so Strapi content streams fast while published pages stay cached at the edge.

2. Media & UI diet – every hero/portfolio image goes through next/image (AVIF/WebP, responsive sizing, lazy loading) and the rest of the UI leans on gradients/SVGs to keep the JS bundle tiny.

3. Request hygiene – the contact endpoint runs behind an LRU rate limiter plus a honeypot so bots can’t blow up cold caches or SMTP quota.

4. Crawler guidance – tuned metadata, sitemap/robots, and IndexNow hooks so bots stick to prerendered routes and don’t hammer dynamic APIs.

Hardest parts: adapting our Strapi mapper to the new documents API (Blocks content, optional media, draft/live toggles), keeping preview mode from disabling cache for everyone else, and getting rich-text rendering + SMTP deliverability reliable on serverless and there’s still more fine‑tuning behind the scenes, but those were the biggest levers.

I suggest adding a headless CMS to the project for long-term benefits.

A headless CMS provides superior flexibility, omnichannel delivery, and developer freedom. It allows content to be managed in one central location and delivered via API to any device, including websites, apps, and IoT devices. By decoupling content management from presentation, a headless CMS enhances performance, scalability, and security through microservices while facilitating easier integration with modern frameworks, thereby future-proofing digital experiences.

Hey Chintan, thanks for jumping in! The site you’re looking at is already powered by a headless stack—content is managed centrally in Strapi and delivered via API, while the front end on Vercel just consumes that data and renders it. That setup gives us the flexibility, omnichannel reuse, and performance benefits you mentioned, so we’re already enjoying the perks of a headless CMS here.

Okay, Noted.

I checked tech stack using wappalyzer, Strapi CMS is not there.

Thanks for confirming. enjoy