What Is a Preloader (Loading Screen)?
Updated 4 November 2026
Jump to section
A preloader is a loading screen or animation shown while a web page and its assets finish loading, usually a spinner, a progress bar, or a branded splash. Most business sites do not need one. Nielsen Norman Group's research on wait times shows that a delay under one second keeps a visitor's flow of thought. Hiding a fast page behind an animation adds a wait rather than filling one.
What a preloader is for
A preloader's job is to fill a genuine wait, so the visitor sees feedback instead of a blank screen. It matters most when something really does take time, like a heavy web app booting or a large media gallery loading.
For an ordinary marketing page that loads in a second or two, a preloader fills a wait that barely exists. Worse, it can delay the content the visitor actually came for.
What the research says about waiting
Research on response times sets three limits worth designing around. Jakob Nielsen's long-standing thresholds (Nielsen Norman Group, 1993) name three. A delay of 0.1 second feels instant, one second keeps your flow of thought, and ten seconds is the limit for holding attention.
| Wait | What the visitor feels |
|---|---|
| Under 0.1s | Feels instant; no special feedback needed |
| Up to 1s | Delay noticed, but flow of thought holds |
| 2 to 10s | Show a looped animation, such as a spinner |
| Over 10s | Show a percent-done indicator; attention drifts to other tasks |
Source: Nielsen Norman Group, "Response Times: The 3 Important Limits" (1993) and "Progress Indicators Make a Slow System Less Insufferable" (2014), both linked in this section.
A separate Nielsen Norman Group guide on progress indicators is more specific. Show an indicator for any action over about one second.
Use a simple looped animation for waits of two to ten seconds, and a percent-done bar once a wait passes ten seconds.
Preloader, spinner, or skeleton screen
The three common patterns solve the same problem in different ways. A spinner says only that something is happening. A percent-done bar says how much is left. A skeleton screen shows a gray outline of the page as it fills in.
Skeleton screens have become popular because they create the illusion of a shorter wait. That is the honest claim: they shape perception, not real speed.
Nielsen Norman Group (2023) is direct about the limit: skeleton screens "do not replace performance-optimization efforts". They are one extra tool for the wait, not a fix for a slow page. If your page is genuinely fast, none of the three is needed.
When a preloader hurts more than helps
A preloader hurts when it delays a page that was already fast. A forced two-second splash on a one-second page just doubles the wait, and every visitor pays it on arrival.
A pattern we see is owners judging a site by how it looks rather than what it does for a visitor. A branded loading animation is that instinct at its purest: polished, and standing between the visitor and the content they came for. The better fix is almost always a faster page, not a nicer way to wait.
If the real problem is speed, a preloader hides the symptom. Improving Core Web Vitals, especially Largest Contentful Paint, and trimming heavy assets above the fold does more than any spinner.
Heavy visual effects add to the same problem. Parallax scrolling moves layers of a page at different speeds as the visitor scrolls, and it can slow loading and cause motion discomfort, so use it sparingly.
Frequently asked questions
Do I need a preloader on my website?
Usually not, if your pages load in a second or two. At that speed a preloader adds a wait instead of covering one, and it stands between the visitor and your content. Preloaders earn their place on genuinely slow-to-start experiences, like a web app or a heavy interactive tool. For a standard brochure site or store, a fast page beats any loading screen.
Do preloaders slow down a website?
They do not make it faster, and a forced-duration one makes the perceived wait longer. A preloader is a cover for loading time, not a way to reduce it. If it is set to run for a fixed few seconds, it adds delay on top of the real load. The honest fix for a slow site is to make it lighter, not to decorate the wait.
Are skeleton screens better than spinners?
For longer waits, often yes, because a skeleton screen hints at the layout to come and feels less blank. The gain is in perception, though, not measured speed. Nielsen Norman Group frames skeleton screens as shaping the wait, not shortening it. For a very short wait, neither is worth the effort; for a long one, a percent-done bar tells the visitor the most.
Do preloaders affect SEO?
Indirectly, and only if they get in the way. A preloader that delays your main content can push out your Core Web Vitals, which search engines weigh. It does not help rankings on its own. If it hides a genuinely slow page, the underlying slowness is the SEO problem, and the loading screen just masks it from you, not from Google.
When should a website show a loading indicator?
For any wait longer than about one second, so the visitor knows the site is working. Use a simple looped animation for waits of a few seconds, and a percent-done bar once a process passes ten seconds. Below one second, show nothing, because the response already feels instant. The guiding rule is that any feedback beats a frozen, silent screen.
A fast page beats a pretty wait
Storming Solutions builds custom-coded websites for Malaysian businesses from Kuala Lumpur, and runs SEO, AEO, and GEO. We reach for a loading indicator only where a real wait exists, and we would rather cut the wait than dress it up.
Our honest view is that most sites asking for a preloader need a lighter, faster page instead. Wondering whether yours is slower than it should be? Talk to us about web development, and we will tell you where the time is going.