Why I avoid carousels on my portfolio

A carousel turns a visitor’s first impression into a timed performance. Slides advance, gestures become required, and meaningful work can remain hidden behind a dot, arrow, or swipe. The result feels active, yet it makes visitors manage the interface before they can understand what the person behind the work can do. That extra effort has no obvious reward.

That is why I keep my portfolio still. I want a visitor to see the work, read the context, and decide what deserves attention without learning a set of controls. Restraint gives typography, whitespace, colour, and photography room to do their jobs. A page can feel considered through composition and hierarchy rather than movement.

Visibility beats novelty

The job of a portfolio opening is not to prove that a website can animate. It is to make the visitor quickly recognise the kind of problems I solve and the quality of the result. A clear statement, a strong project image, and a visible path into selected work create a more useful first impression than several slides competing for attention.

A static hero followed by a project grid lets the page reveal depth progressively. The visitor chooses whether to continue, so the sequence responds to intent rather than a timer. This approach also makes every project discoverable in the document, which helps someone arriving from a search result, a referral, or a direct message on a phone.

That restrained approach is visible on my personal site, where the visual system supports the content instead of becoming the content. In Australia’s competitive market for independent designers, photographers, and developers, this kind of clarity is particularly valuable. Clients and recruiters often scan a small portfolio between meetings or while travelling, and a calm page is easier to assess than an interface full of prompts. For paid work, statements about services or results can also fall within the Australian Consumer Law, making accurate claims as important as clear presentation.

Motion creates hidden costs

Even a well-made carousel carries costs that are easy to overlook. It needs state management, controls, animation rules, responsive behaviour, and often a library to coordinate them. Every extra dependency increases the chance of a small defect on an unfamiliar device. What looks simple in a design file becomes a set of engineering decisions in the browser.

The familiar swipe gesture also changes how people search. Some visitors swipe without reading; others do not realise the panel moves at all. A row of small indicators can provide orientation, but it often says only that there are more items, not whether those items are cases, services, or decorative variants. After one accidental swipe, the visitor may lose the image that made them stop.

Autoplay adds another layer. It can interrupt reading, shift focus, and make a shared page feel unstable when it reloads on a different screen. Respecting a reduced-motion preference helps some people, but the deeper issue is attention: a portfolio should not compete with the person trying to read it. Letting the visitor initiate change keeps the page predictable and gives control back to the user.

Speed follows local habits

Australia makes speed and resilience a practical portfolio concern. A visitor may open work on a phone while waiting for a train in Sydney, riding a tram in Melbourne, or moving between meetings in Brisbane. Mobile coverage can be inconsistent in tunnels, lifts, and crowded stations, so a page that waits for a carousel script or a large media bundle may not appear when the visitor is ready.

Static content gives the browser much less to negotiate. Semantic headings and links are available as soon as the document arrives, while images can be sized, compressed, and loaded lazily. This supports Core Web Vitals, including Largest Contentful Paint and Interaction to Next Paint, because the main visual does not depend on a sequence of transitions completing first. It also works better on the widely used combination of mobile and fixed-line broadband at home.

Performance is part of hospitality. Someone in Perth or a regional town should not need a perfect connection to inspect a project, and someone on a capped mobile plan should not download an entire slideshow before reading the brief. A fast page respects both time and data. The design remains legible on an inexpensive phone, an old laptop, or a public computer, which matters when the audience for creative work extends well beyond major city studios.

Accessibility must include behaviour

A carousel can be built accessibly, but many are not. Keyboard users need a logical focus order and visible focus around previous and next controls. Screen-reader users need slide status, meaningful labels, and a way to understand whether changing the panel changes the page content. People with motor impairments may struggle with small targets or gestures, while vestibular conditions make automatic movement uncomfortable or disorienting.

The relevant accessibility guidance is behavioural rather than visual. WCAG 2.2 asks sites and software to provide keyboard access, support reflow at narrow widths, expose names and roles to assistive technology, and let users pause automatic moving content that lasts longer than five seconds. A decorative fade may pass a contrast check while still failing to communicate its movement or state. Testing with a keyboard and a screen reader often reveals problems that a visual review misses.

The legal setting in Australia is worth stating precisely. Private portfolios are not automatically required to meet a universal federal web accessibility standard, and WCAG does not replace advice about duties under disability-discrimination laws. Even so, WCAG is a strong baseline for professional practice, especially when agencies, government suppliers, or large clients include accessibility expectations in procurement. Clear, stable pages are easier for every visitor, not only those who disclose a disability.

A project deserves a narrative

Portfolio work is rarely one image. A project may begin with a problem, move through research and decisions, and end with a result that needs qualification. A carousel can show fragments, but it tends to flatten that story into equal visual moments. A dedicated case-study page gives each part room, allowing the visitor to move between an overview, process, outcome, and relevant details without compressing the work into a fixed number of panels.

A good example is my daily mood tracking review, where the value comes from the sequence of observation and reflection rather than the number of images. A reader can scan the headings, follow the argument, and revisit the section they need. That is more useful than a timed sequence that asks for equal attention on every frame.

Personal content also deserves careful handling. If a mood form or analytics flow records identifiable information, the Privacy Act 1988 and Australian Privacy Principles may apply, including stricter treatment of sensitive health information. A restrained interface can collect less, explain what it stores, and avoid unnecessary tracking. This is a design benefit as much as a compliance concern: a portfolio that does not gather data it does not need asks less of its visitors.

Exceptions need a clear reason

A carousel is not automatically a poor choice. A bounded set of variants, a temporary campaign, or a sequence designed to preserve an established relationship between items can justify horizontal movement. The reason should be functional rather than fashionable. If separate pages would make the comparison harder, a carousel may help, provided every state remains visible and understandable.

When I encounter that situation, I would require manual controls, no autoplay, clear item counts, and a design that does not strand keyboard focus. Each slide would need a stable URL or another direct route, and essential information could not exist only in a moving panel. Those conditions turn motion into a tool with a defined job rather than the default structure of the whole site.

For this portfolio, the balance is straightforward. The work, writing, and images benefit from a stable reading order, and the restraint supports the visual language I want to maintain. I will keep the interface still unless a future project offers a genuine reason to change, and even then the movement will serve the content rather than distract from it.