Page speed depends on the published page, network, device, browser, third-party services, and test location. Measure the actual public URL on both mobile and desktop, then optimize the largest controllable costs first.
Start with a repeatable baseline
- Test the same public URL more than once and compare the median result.
- Test a clean browser session and a representative mobile connection.
- Separate Ion platform resources from page content and third-party scripts before deciding what to change.
Images and animation
- Resize images near their rendered dimensions and compress them before upload.
- Use the format that best fits the asset: WebP or AVIF when your delivery workflow supports it, JPEG/WebP for photographs, PNG only when lossless detail or transparency is needed, and SVG for suitable simple graphics.
- Avoid oversized background images. Load below-the-fold media only when needed and do not use animation where a static image communicates the same information.
- Prefer an efficient video format over a large animated GIF when motion is necessary.
Page structure and interactive content
- Keep the first page focused. Remove empty containers, unused elements, duplicate widgets, and unnecessary nested structure.
- Use interactive components deliberately; every component adds markup, styling, scripts, or media that the browser must process.
- Check for horizontal overflow, layout shifts, hidden desktop-only assets still being downloaded on mobile, and large content above the fold.
Scripts, fonts, and external services
- Remove unused third-party scripts and tags. Ask the provider for an asynchronous or deferred version when available.
- Avoid placing nonessential blocking code in the page head. Load code at the latest safe point without breaking consent, analytics, or experience behavior.
- Limit font families, weights, external CSS, embeds, and network calls. A slow third-party service can delay an otherwise fast Ion page.
Optimize safely
Change one category at a time, publish to a controlled URL, and remeasure. Confirm that forms, rules, integrations, consent, analytics, accessibility, and responsive behavior still work after each optimization.
Some resources are required by Ion and should not be removed from customer pages. Focus first on page media, page structure, custom code, fonts, and third-party services that you control.
For the built-in workflow, see Page Speed Scores.
