FRENVersion française

Feedback

Skeleton screen

Squelette de chargement

Demo

Loading demo…

A grey mock-up of the content to come, shown while it loads: bars for text, circles for avatars. It reveals the shape of the page before the data arrives and makes the wait feel shorter.

Story

Did you know

Luke Wroblewski coined the term in 2013 for his app Polar. His point: a spinner draws the eye to the wait, a skeleton draws it to what is coming, so time feels shorter.

Timeline

  1. 2013Luke Wroblewski names "skeleton screens" while building the Polar app.
  2. 2014+Facebook adopts it for its feed and the pattern spreads.
  3. 2020sFrameworks (Suspense, loading.tsx) make it a standard loading state.

Vocabulary

Names

FR
Squelette de chargement, écran squelette, placeholder de contenu
EN
Skeleton screen, skeleton, skeleton loader, content placeholder, ghost elements, shimmer

Common uses

  • Lists and feeds loading from an API
  • Product cards while fetching
  • First render of a client-side page

Often paired with

The components it usually sits with, by page type, in reading order.

Code

<article class="card" aria-busy="true">
  <div class="skeleton line" aria-hidden="true"></div>
  <div class="skeleton line short" aria-hidden="true"></div>
</article>

<style>
.skeleton {
  background: linear-gradient(90deg, #eee 25%, #ddd 50%, #eee 75%);
  background-size: 200% 100%;
  animation: shimmer 1.2s linear infinite;
}
@keyframes shimmer { from { background-position: 200% 0; } to { background-position: -200% 0; } }
@media (prefers-reduced-motion: reduce) {
  .skeleton { animation: none; }
}
</style>

<script>
const card = document.querySelector('.card')
fetch('/api/user').then(r => r.json()).then(user => {
  const name = Object.assign(document.createElement('h3'), { textContent: user.name })
  const bio = Object.assign(document.createElement('p'), { textContent: user.bio })
  card.replaceChildren(name, bio)
  card.removeAttribute('aria-busy')
})
</script>

Good to know

  • The skeleton must match the real shape of the content. Otherwise the layout shift (CLS) comes back when the data lands.
  • Under ~300 ms, show nothing: a flashing skeleton is worse than a short delay.
  • Animating background-position triggers a repaint every frame. With many blocks, animate a transform on an ::after instead.
  • With SSR, render the real content straight away. Skeletons are for data fetched on the client, for example as a <Suspense> fallback.

Accessibility

Must have

  • aria-busy="true" on the container while loading, removed once loaded.
  • Hide the grey blocks with aria-hidden="true": they mean nothing to a screen reader. Add visually hidden text such as "Loading comments" instead.

Often forgotten

  • aria-busy alone doesn't announce the end, and screen reader support varies. Announce the arrival in a role="status" region ("12 results loaded").
  • If the focused element vanishes when the skeleton is replaced, focus falls back to <body>. Keep focus on a stable element.
  • Turn off the shimmer under prefers-reduced-motion: static blocks are enough.

Nice to have

  • If loading fails, replace the skeleton with an error message: an endless shimmer suggests it is still loading.

Who uses it