Enjin

The outlined brand mark is a continuous silhouette, avoiding the small seams that overlapping rotated shapes can produce. Drafting scales add degree markings, construction guides and a sweeping measuring arm. The Work entries use a mathematical drawing compass, with a hinged pencil arm, a needle, a calibration ring and fine orange details.

The components share colours and drawing conventions, while their movement and composition respond to their role. A wordmark needs a different visual weight from a large cropped hero illustration.

We animate individual groups where that makes visual sense: a platform lifts, a measuring arm sweeps, a pencil adjusts its angle. CSS transforms keep that movement separate from the surrounding document layout.

Browser testing matters even with small animations. During development, the testimonial treatment was revised to animate an HTML wrapper around a static SVG after stepped movement was reported in Firefox. The visual intention stayed the same; the rendering approach changed.

The Enjin preview combines a lossless WebP capture of the real homepage with the original animated SVG instruments placed at measured coordinates. The screenshot and instruments scale together, including the small mark beside the logo.

It is one self-contained SVG image: no embedded copy of WordPress, no video player and no external animation library. The rotating cogs and sweeping arms are real vector artwork. A conventional static image remains available for sharing metadata and as the configured fallback.

The theme conditionally loads journal styles for editorial views, journal interaction code for individual articles, and case-study styles for projects with chapters. Contact resources are discovered from visible ACF contact sections; their Gravity Forms assets are enqueued where the form is actually present.

The theme also removes the standard block-style bundles it does not use. This is a decision about this implementation’s templates, not a general recommendation to dequeue WordPress styles without checking what renders on the page.

Portfolio screenshots have WebP derivatives at widths suited to their placements. Their sizes descriptions account for the container width, card insets, alternating Work layout and two-card desktop rail. WordPress can then offer the browser an appropriate candidate through srcset.

Below-the-fold imagery uses native lazy loading. A project’s lead image is requested eagerly with high fetch priority. Image dimensions and container aspect ratios establish space before the asset finishes loading.

The hero diagrams are inline vector geometry, coloured through shared tokens and animated with CSS. The interaction layer uses native browser APIs for the menu, project rail and active case-study chapter. There is no separate slider or animation plugin powering those components.

The animated Enjin screenshot illustrates the same principle. Its 57,717-byte file contains its raster base and moving vectors, with no additional asset requests required to render the image. That measured file size says something useful about this technique without pretending to be a whole-site benchmark.

Replaced theme styles, scripts and PHP implementations were removed from the active child theme rather than left beneath newer overrides. Reusable helpers keep the project imagery, decorative framing and illustration families consistent across their different placements.

Database hygiene receives the same attention to ownership. A read-only options audit identified entries for review; deciding what is safe to remove requires tracing their consumers and retaining an appropriate recovery path.

File weight, request count, rendering behaviour and user-perceived responsiveness describe different parts of performance. A small file does not automatically mean a fast interaction, just as an attractive laboratory score does not explain every visitor’s experience.

We distinguish an asset measurement from a page-load test and examine the context behind a result: the URL, device, connection, cache state and third-party services. That keeps optimisation focused on the actual work being done.