Optimize Performance and Security for MorphoClarity.com

WordPress Website Speed Optimization & Security Fix — MorphoClarity.com OVERVIEW We need an experienced WordPress performance specialist to improve the loading speed, mobile experience, and security of our existing live website — without changing the current design, functionality, payment system, or booking system. The site is built on WordPress + Elementor. Over time, as pages, features and integrations have been added, load performance has degraded — particularly on mobile. This is an optimization project, not a redesign or rebuild. CURRENT ISSUE - Noticeable page load and reload-speed issues, especially on mobile - Heavier-than-ideal loading experience across the site as a whole (not just 1–2 pages) - Some known security issues in the current setup that also need to be resolved CURRENT PERFORMANCE BENCHMARK (from PageSpeed Insights) These are real, current numbers pulled directly from PageSpeed Insights on our own pages — not estimates. Your final deliverable must be benchmarked against these same metrics, tested with the same tool, so we can directly compare before vs. after. Homepage (Mobile) - Performance Score: Current 61 → Target 90+ - First Contentful Paint (FCP): Current 3.0s → Target ≤ 1.8s - Largest Contentful Paint (LCP): Current 12.6s → Target ≤ 2.5s - Total Blocking Time (TBT): Current 280ms → Target ≤ 200ms - Cumulative Layout Shift (CLS): Current 0 → Target ≤ 0.1 (maintain) - Speed Index: Current 4.6s → Target < 3s Service Pages (Mobile) - Performance Score: Current 54 → Target 90+ - First Contentful Paint (FCP): Current 2.3s → Target ≤ 1.8s - Largest Contentful Paint (LCP): Current 11.7s → Target ≤ 2.5s - Total Blocking Time (TBT): Current 490ms → Target ≤ 200ms - Cumulative Layout Shift (CLS): Current 0.001 → Target ≤ 0.1 (maintain) - Speed Index: Current 6.8s → Target < 3s Desktop Benchmark — Sample of 4 Service Pages + Homepage - Service Page A: Score 73 | FCP 0.6s | LCP 2.3s | TBT 250ms | CLS 0.006 | Speed Index 2.4s - Service Page B: Score 57 | FCP 0.6s | LCP 2.7s | TBT 490ms | CLS 0.006 | Speed Index 3.1s - Service Page C: Score 77 | FCP 0.6s | LCP 2.3s | TBT 240ms | CLS 0.006 | Speed Index 1.6s - Service Page D: Score 83 | FCP 0.6s | LCP 2.3s | TBT 100ms | CLS 0.006 | Speed Index 2.2s - Homepage: Score 70 | FCP 0.4s | LCP 2.4s | TBT 320ms | CLS 0.002 | Speed Index 2.2s - Average: Score ~72 | FCP ~0.56s | LCP ~2.4s | TBT ~280ms | CLS ~0.005 | Speed Index ~2.3s Desktop Target: 95+ Performance Score on every customer-facing page (Desktop naturally scores higher than mobile, so we're holding it to a tighter bar), with: - LCP ≤ 2.0s - TBT ≤ 150ms - FCP ≤ 1.0s - Speed Index < 2s - CLS maintained ≤ 0.1 Secondary Sanity-Check Metric (Optional, supports the above — not the primary KRA) - GTmetrix "Fully Loaded Time" — Desktop: Target < 2s - GTmetrix "Fully Loaded Time" — Mobile: Target < 2s PageSpeed Insights (Lighthouse) scores above remain the primary pass/fail benchmark. GTmetrix's Fully Loaded Time is a simpler, easy-to-verify real-world check we may also glance at, but it is not the contractual target. NOTE: Before starting work, please run and share a baseline PageSpeed Insights (Mobile + Desktop) audit for every customer-facing page type listed below, so we have an agreed "before" snapshot for every page category, not just the samples above. SCOPE — PAGES TO BE OPTIMIZED (ALL CUSTOMER-FACING FRONTEND PAGES) This must be reviewed holistically across the whole live site — not just the homepage or a handful of pages. This includes: - Homepage - Service pages - Service/payment-related pages - Booking-related customer-facing pages - Information and content pages - Existing landing pages - Any other publicly accessible customer-facing frontend pages - New lightweight ad-traffic landing pages (initial testing shows these need full optimization too — see benchmark below, not just fine-tuning) WHAT MUST NOT BE COMPROMISED - Current design and visual quality - Existing functionality - User experience - Payment and booking systems (Razorpay, Google Calendar booking flow, etc.) - Overall appearance and layout of the site AREAS TO REVIEW - Caching and server-side optimization - JavaScript and CSS loading (render-blocking resources, minification, deferring) - Fonts and external resources - Images and other media (compression, lazy loading, next-gen formats) - Plugins and unnecessary resources/bloat - Elementor and Astra-specific performance tuning - Page loading and rendering behavior (especially the 10s+ LCP issue seen above) - Mobile-specific performance (top priority) - Any other technical factors contributing to slow load times SECURITY - Identify and resolve existing security vulnerabilities - Payment functionality must continue working after fixes - Booking functionality must remain unaffected - No breakage to core features - Site must remain fully stable post-changes DELIVERABLES & KRAs (KEY RESULT AREAS) 1. Performance Score 90+ on Mobile, 95+ on Desktop on all customer-facing pages, verified via PageSpeed Insights 2. LCP ≤ 2.5s on all pages (down from the 10s+ currently seen on sampled pages) 3. TBT ≤ 200ms on all pages 4. FCP ≤ 1.8s on all pages 5. Speed Index < 3s on all pages 6. CLS maintained at ≤ 0.1 (currently good — must not regress) 7. Zero breakage to payment, booking, or existing functionality — confirmed via test transactions/bookings post-optimization 8. Security issues identified and resolved, with no disruption to live site stability 9. Landing pages reviewed and fine-tuned (design/structure untouched) with speed maintained or improved 10. Before/after PageSpeed Insights report (Mobile + Desktop) for every page category, shared as proof of work HANDOVER & DOCUMENTATION (REQUIRED AT PROJECT COMPLETION) A written handover document covering: - Main performance issues identified - Key optimizations implemented - Important settings/configurations changed - Security issues addressed and how they were resolved - Things we should be careful about going forward - B