Performance optimisation
Asset size, lazy loading and motion cost.
Performance optimisation
VELORYZ Studio · Quality, accessibility, performance and security Audience: QA, security reviewers and release owners Guide type: Practical Studio operations guide
Purpose
Performance optimisation should be treated as an end-to-end responsibility, not an isolated button. Start by defining what will change, who can approve it and how success will be checked. Asset size, lazy loading and motion cost.
This guide covers asset size, lazy loading and motion cost. Use it as an actionable practical studio operations guide: verify the current UI and any provider configuration before relying on a control in production.
Availability and responsibility
This section is a release checklist and technical reference, not proof of external certification or zero defects. Security reviews depend on real implementation, runtime configuration and deployment tests.
Before committing time or budget, confirm who operates this workflow: the visitor, the client portal user, a Studio owner, or the delivery team. A feature described in design documentation is not automatically a public account entitlement.
Before you begin
- A test matrix of browsers, devices, viewport sizes and assistive technology
- High-impact user journeys and a recorded set of expected outcomes
- A staging build, analytics diagnostics and a secure issue-reporting channel
- A short list of measurable success criteria specifically for performance optimisation.
- A recovery plan if the proposed change creates a regression.
Recommended procedure
- Locate the relevant area or public route. For new projects, establish the brief at /create/; for owner-only content changes, use authenticated Studio Control at /admin. Do not assume a missing feature exists.
- Define the specific work item for Performance optimisation: capture the initial state, user intent, relevant data, permissions, expected output and what must not change.
- Follow the design and operating decisions listed below. Work in a draft, staging or reviewed project handoff where available; avoid editing live customer data experimentally.
- Review the effect with real content and realistic viewport sizes. Record any exception and obtain the appropriate approval before a public change.
- After the change, verify the public outcome rather than relying on a success message alone; preserve a reference to the reviewed version.
Topic-specific operating procedure
These steps apply to Performance optimisation. The implementation must be verified against the current Studio permissions, deployed provider connections and approved project scope.
- Measure real page weight, layout shift, interaction latency and largest contentful paint.
- Compress imagery and video, avoid unnecessary third-party scripts and minimize blocking resources.
- Prefer opacity/transform animations and controlled observers instead of per-scroll reflows.
- Retest the production experience on a realistic mobile network after optimisation.
Evidence to retain
- The original input or situation, and a clear before/after comparison.
- The reviewed version, responsible owner and acceptance record.
- Any limitation, follow-up decision, or safely reversible workaround.
Configuration and decision points
- Test critical paths: navigation, forms, project creator, admin authorization, client portal and documentation search.
- Run keyboard, screen-reader, zoom, focus-visibility and reduced-motion checks.
- Review content, link destinations, file handling, authentication and server-side validation.
- Measure actual performance and errors; prioritise fixes by severity and affected users.
When more than one implementation is possible, prefer the simplest approach that remains accessible, maintainable and compatible with the current source. Note any cost, licensing, privacy, ownership and performance implications before approval.
Verification checklist
- No critical unhandled errors or inaccessible essential workflows remain.
- Private data is accessible only through correct server-side permissions.
- Responsive layouts work at mobile widths without horizontal overflow.
- Every critical issue has a reproducible report and verified resolution.
Also confirm that the result addresses the original objective: Asset size, lazy loading and motion cost.. Review the customer-visible language, error states, navigation paths and the relevant device widths. A green build or a successful save does not by itself establish a correct production outcome.
Troubleshooting and recovery
- If a critical security issue is suspected, limit access and notify the responsible operator securely.
- If a deployment fails QA, do not ship the affected feature until it is addressed.
- For intermittent issues, record exact environment, timestamps and user actions.
When asking for assistance, include the exact public URL or project reference, a concise reproduction path, the expected behaviour, actual behaviour, relevant timestamps and a redacted screenshot if useful. Never include passwords, access tokens or private customer records.
Related reading
- [Quality assurance workflow](/docs/studio/quality/overview/)
- [Accessibility checklist](/docs/studio/quality/accessibility/)
- [Browser and device testing](/docs/studio/quality/browser-testing/)
- [All VELORYZ documentation](/docs/)
- [Studio documentation](/docs/studio/)
- [Help Centre](/help/studio/)
- [/contact/](/contact/)
- [/docs/troubleshooting/](/docs/troubleshooting/)
Operational note
This article describes the Studio workflow and its acceptance criteria. Where a self-service control is not available, the action is coordinated with the Studio team rather than silently represented as automated.
