Aurelia’s source uses generated delivery assets and context-specific media. Check the files actually served on the target site rather than assuming source CSS, a manifest label or an earlier performance budget proves current delivery.
Preserve the asset pipeline
The parent owns its runtime files and manifest; child styles extend presentation through the supported order. Use the owning build tools after source changes and verify generated files, references and cache versions together. Do not edit a compiled asset alone and leave its source/manifest inconsistent.
Inspect only the route-relevant theme assets and the browser’s delivered versions. Theme-owned local assets do not mean the entire booking journey has no external requests: Pro payment SDKs and configured integrations are separate owners.
Review image composition and loading
Use suitable source dimensions and the supported responsive media/focal-point controls. Inspect selected srcset/sizes and the actual phone/tablet/desktop result. A frame can intentionally crop a photo; use the full-photo viewer where supported rather than assuming one object-fit value satisfies every context.
Hero priority, content image loading and layout dimensions have different roles. Avoid adding competing eager images or oversized child-theme assets without checking network and layout effects. Keep image rights/attribution with the actual supplied media source.
Measure the actual journey
Test Homepage, Rooms/Search, Room Detail, Book Now and result/account surfaces separately. Inspect image decode/layout shifts, typography, responsive calendar width and main-thread behavior with realistic content. Compare cold/warm cache and logged-out output; an administrator toolbar can change geometry.
Use reproducible browser/device conditions for timing and performance metrics. Static source checks or a ZIP matching its inventory do not establish LCP/CLS budgets, mobile usability or cross-browser image behavior.
If delivery is stale, verify the installed package, generated asset identity and relevant cache/worker before changing design settings. Preserve business form hooks and Core/Pro logic while repairing styling or assets.
See layout/cache diagnosis and Customizer media.
