chillimanis.com.sg — Halal Buffet Catering Singapore
Performance · Accessibility · UX · Technology Stack
// website audit — may 2026
Website Audit &
Revamp Proposal.
Revamp Proposal.
Prepared for Chilli Manis
May 2026
// current state
The site,
as it stands.
as it stands.
chillimanis.com.sg
WordPress + Elementor + Apache
WordPress + Elementor + Apache
The baseline before the revamp.
Desktop — 1440px viewport
Tablet — 768px viewport
Mobile — 390px viewport
Screenshot capture — May 2026
61
// overview
C+
Overall Score — 61 / 100
3 critical issues · 4 warnings · 2 minor findings
Critical work required before growth investment.
Full technical, accessibility, UX, and SEO audit — May 2026 · Google Lighthouse + WCAG 2.1 AA
2 scores below 50 — Performance & Accessibility need structural changes, not patches
SEO at 92 is the one real asset — must be protected through any migration
Root cause is architectural — the tech stack explains all three failing scores
Performance
D+
45 / 100
Accessibility
D+
46 / 100
SEO
A+
92 / 100
UX Best Practices
C
58 / 100
Security
B−
67 / 100
45
// performance
52.1 Seconds.
Users Don't Wait.
Users Don't Wait.
Largest Contentful Paint measured at 52.1 s. Google's benchmark is under 2.5 s.
That is a 20× gap — users abandon pages after 3 s.
Largest Contentful Paint (LCP)
52.1 s
Target: < 2.5 s · Gap: 20×
Lighthouse Performance Score
45
/100
Best Practices: 57/100
Root Cause
WordPress + Elementor page builder
· No CDN · 60 unoptimised images
· No CDN · 60 unoptimised images
Every 1 s improvement in page speed delivers a 7%+ lift in conversion rate. (Google / Deloitte)
// accessibility & ux
Failing Users. On Two Fronts.
46
/ 100 Accessibility
WCAG 2.1 AA evaluation · 8 violations
Critical violations
2
Serious violations
3
Moderate violations
3
Missing alt text · unlabelled buttons · broken link text · heading disorder
58
/ 100 UX Score
4 critical UX patterns missing
No search functionality
No breadcrumb navigation
No cookie / privacy consent banner
11 H1 headings on one page (should be 1)
Contact form: 13 fields, no input validation
10 font families — visual fragmentation
35% of 60 images carry alt text. 39 images are invisible to screen readers and search engines.
92
// strengths
One Bright Spot.
92
SEO Score — A+
Organic visibility is strong. Protect this during any revamp.
Meta & Canonical
51-character title, rich meta description, canonical URL, and correct lang attribute. SEO foundations are solid.
Technical SEO
robots.txt, sitemap.xml, HTTPS with HSTS, structured headings (H2–H5), and indexable content.
Content Depth
1,527 words across 125 paragraphs. 84 internal links. Menu taxonomy is rich and crawlable.
Analytics
Google Tag Manager and Facebook Pixel in place. Conversion tracking infrastructure is ready to use.
A structured SEO migration plan is non-negotiable — a revamp must preserve current organic rankings.
// root cause
The Stack Is
the Problem.
the Problem.
CMS
WordPress + Elementor 4.0
JavaScript
jQuery (legacy)
Server
Apache · no CDN
Analytics
GTM + Facebook Pixel
Typography
10 font families
Why This Matters.
Page Builder Bloat
Elementor generates hundreds of unused CSS classes and render-blocking scripts, directly inflating LCP and page weight beyond what any plugin can fix.
No Content Delivery Network
Every visitor hits the origin Apache server directly. No edge caching means high latency for all Singapore and international users.
Design Fragmentation
Poppins, Cinzel, Rosela, and seven more families — each adds HTTP requests and creates visual inconsistency that undermines brand trust.
// verdict
90% confidence
Full revamp recommended
Patch Fixes Won't
Solve This.
Solve This.
01
Performance
A 52.1 s LCP is an architectural problem. Page-builder rendering cannot be optimised with plugins — the frontend must be rebuilt.
02
Design System
10 font families and fragmented layout cannot be reconciled inside Elementor. A new design system requires clean HTML structure.
03
Accessibility
8 WCAG violations — 2 critical — require semantic HTML and ARIA changes that Elementor cannot reliably produce or maintain.
// recommendation
Laravel + Inertia
+ React.
+ React.
A single, cohesive PHP framework handles backend logic, routing, and data — while InertiaJS bridges to a React frontend with no separate API contract. Modern, maintainable, fast to ship.
One codebase. Laravel ergonomics. React UI components. Vite builds.
Current Stack
WordPress + Elementor 4.0
Page builder overhead · legacy rendering · locked-in template system
jQuery · Apache · No CDN
Legacy JS library · origin-only serving · no edge caching
Recommended Stack
Laravel 11 + InertiaJS
Full-stack MVC framework · Eloquent ORM · built-in auth and API scaffolding
React + Vite + CDN Edge
SPA-like routing without a separate API · React component architecture · Vite build tooling
// impact forecast
Measurable Business Outcomes.
Projections based on audit data and published industry benchmarks.
15–25%
Bounce Rate Reduction
Closing the LCP gap from 52.1 s to under 2.5 s. Users who abandoned before load will complete their visit.
7%+
Conversion Lift per Second Saved
Industry-validated benchmark. Each second of LCP improvement compounds across catering enquiries and bookings.
8–12
Weeks to Launch
Full revamp delivery estimate: design system, development, SEO migration, QA, and go-live handoff.
Source: Google Core Web Vitals, Deloitte Digital Consumer Study (2020), audit-specific LCP delta analysis.
// next steps
Let's Revamp.
01
Discovery Workshop
Align on user journeys, booking conversion flow, content structure, and brand direction. Define information architecture and wireframes.
02
Design & Architecture
New design system and component library. Laravel + InertiaJS application setup. React component architecture. WCAG AA compliance target.
03
Build, Migrate & Launch
Iterative development, SEO-safe content migration, load-time QA, GTM reconfiguration, and live deployment with monitoring.
techcanvasstudio.com