Back to Glossary

Loading States

Make Uxify one of your go-to sources on Google

Google Add Uxify on Google

What are Loading States?

A loading state is whatever a page shows in the gap between asking for something and getting it. On a store, that gap is everywhere. A collection page fetching products, a filter app recalculating results, a discount code being checked, a payment going through.

The family is bigger than most people think. Spinners, skeleton screens and progress bars are the obvious ones. But the “Add to cart” button that switches to “Adding…” and greys out is a loading state too, and so is the little bar that runs across the top of the screen between pages. Then there’s the one nobody designs on purpose. A blank white screen, or a button that does absolutely nothing for a second and a half.

Each fits a different wait. A skeleton suits a product grid because there’s a layout to preview. A spinner on the button is fine for a quick action like applying a code. Payment processing, where shoppers get nervous, needs a short message saying what’s happening and that they shouldn’t refresh.

What this means for revenue

The worst loading state is no loading state. A shopper on an iPhone over 4G taps “Add to cart,” sees nothing change, and taps again, so now there are two in the cart and a confused customer, or they assume the site’s broken and head back to Google. Those repeat taps are exactly what shows up as rage clicks.

There’s a performance side to this as well. Interaction to Next Paint (INP) measures how long it takes the screen to visibly react after a tap, and Google counts it as good at 200 milliseconds or less. Showing the button’s loading state right away is that reaction. If the browser is stuck running scripts, though, it can’t paint the spinner either. The button just freezes.

So the state itself is only half the job. It also has to show up fast.

How Uxify helps

Reality tracks INP and perceived load speed from every real session and catches broken interactions as they happen, so you can see which buttons and pages leave mobile shoppers hanging. Ask Uxi helps you work out why in plain language. INProve frees up the main thread right before an interaction, which gives your “Adding…” state a chance to appear when it should. And Navigation AI loads the next page in the background before the visitor clicks, so many page transitions never need a loading state at all.

Loading States FAQs

Should I use a spinner, a skeleton screen or a progress bar?

Pick by the wait. Skeletons work for full pages and content areas where the layout is predictable, spinners for small actions tied to one button, and progress bars for long, multi-step jobs like uploads, where people want to know how far along they are.

Do loading states affect Core Web Vitals?

Yes, in both directions. Instant visual feedback on a tap helps INP, while placeholders that are a different size from the real content cause layout shifts and hurt CLS. A skeleton also won’t count as your LCP element, since that metric waits for the real content.

What’s the difference between a loading state and an empty state?

A loading state means content is coming. An empty state means there’s nothing to show (a search with no results, an empty cart) and should point the shopper somewhere useful. Mixing them up is a common bug: a “No products found” message that flashes before the products load can make people leave a page that was working fine.