Boost MERN App Loading Speed
Budget: $15 – $25 USD
My production-ready MERN application has grown heavy and first-time loads are now a drag. I need a seasoned MERN performance specialist to dive in, isolate the bottlenecks, and shave seconds off the initial render without altering existing features or the UI.
Here is what I expect:
• A quick diagnostic audit of the current React bundle, Express middleware, and static asset pipeline to pinpoint where the payload and parse time are ballooning.
• Practical optimisations—code-splitting, lazy loading, tree-shaking, gzip/Brotli compression, HTTP/2 where possible, and smart caching rules—implemented directly in the repo (GitHub).
• Clear before-and-after metrics (Lighthouse, WebPageTest, or similar) that prove faster loading speed in real-world conditions, not just synthetic tests.
• A concise report or README addendum explaining each optimisation so the team can maintain the gains going forward.
Stack in use: React 18, Node 18, Express, MongoDB Atlas, Webpack 5, Nginx reverse proxy on Ubuntu. Access will be over a feature branch and staging server.
Acceptance criteria
1. Largest Contentful Paint ≤2.5s on a fresh cache.
2. Bundle size reduced by at least 30 % without breaking functionality.
3. No new security warnings or dependency issues introduced.
If this sounds straightforward to you and you thrive on measurable performance wins, let’s get it done.
Here is what I expect:
• A quick diagnostic audit of the current React bundle, Express middleware, and static asset pipeline to pinpoint where the payload and parse time are ballooning.
• Practical optimisations—code-splitting, lazy loading, tree-shaking, gzip/Brotli compression, HTTP/2 where possible, and smart caching rules—implemented directly in the repo (GitHub).
• Clear before-and-after metrics (Lighthouse, WebPageTest, or similar) that prove faster loading speed in real-world conditions, not just synthetic tests.
• A concise report or README addendum explaining each optimisation so the team can maintain the gains going forward.
Stack in use: React 18, Node 18, Express, MongoDB Atlas, Webpack 5, Nginx reverse proxy on Ubuntu. Access will be over a feature branch and staging server.
Acceptance criteria
1. Largest Contentful Paint ≤2.5s on a fresh cache.
2. Bundle size reduced by at least 30 % without breaking functionality.
3. No new security warnings or dependency issues introduced.
If this sounds straightforward to you and you thrive on measurable performance wins, let’s get it done.