manda-ia.com performance optimization

A score alone is not an audit. The Lighthouse snapshot records the URL, date, mobile or desktop profile and the metrics composing the result. Lab data reproduces a controlled scenario; it remains distinct from field Core Web Vitals collected from real visitors.

Desktop reaches 99/100 with a 0.5-second LCP and 30-millisecond TBT. Mobile remains at 80/100 with 680-millisecond TBT. This gap prevents an artificial conclusion: initial rendering is strong, while the main thread still runs too much JavaScript under simulated mobile conditions.

The CSS audit inspects what actually reaches the browser: transferred size, unused rules, stylesheet order, fonts, critical styles and the team's ability to maintain components. Tailwind can ship compact CSS when compiled correctly, but it does not remove the need to inspect dependencies, variants and accumulating conventions.

Benchmarking another CSS approach only makes sense with the same screens, content and test conditions. I compare weight, render blocking, rule repetition and migration cost before recommending Tailwind, CSS Modules, modern native CSS or a targeted combination.

The Supabase database held about 25 MB, yet the organization exceeded 5.5 GB of egress. Stored volume did not explain the transfer. Public pages were dynamically rendered and re-read the CMS, fallbacks and some data on every request, including crawler visits.

Public content was pre-rendered, Payload became optional in production and frequent reads were replaced with shared caching. The visitor dashboard keeps a maximum freshness delay of 30 seconds while returning a lightweight response without a direct Supabase read for every browser.

The order of changes matters as much as their nature. I begin with high-impact, low-risk corrections: static rendering for editorial content, appropriate caching, removal of duplicated calls, deferred third-party scripts and correctly sized images. Deeper changes only follow when measurements justify them.

Each correction is checked against real journeys, network failures, localized pages and mobile behaviour. This method improves an existing production site without turning the audit into a forced rebuild.

Business websites use this method from the design stage: render statically where possible, load media for the actual viewport, minimize client components and measure the deployed build. Performance becomes an architecture constraint rather than a cosmetic task before delivery.

For hotels, restaurants, travel agencies or rental companies, that speed directly protects mobile conversion. The page must remain light when a visitor compares an offer, reads a menu, checks availability or completes an enquiry.