Salient fix
Salient Site Slow? Nectar Slider, Animations and What to Keep
Salient is built to move. Full-screen Nectar Sliders, parallax rows, animated columns and page transitions are the reason people buy it, and each one is code and media a phone has to download before the page settles. Speeding up a Salient site is mostly deciding which of those effects still earns its keep.
What you are seeing
- The first screen stays blank, then the slider fades in late
- PageSpeed Insights names a slide image or video as the largest element
- Scrolling stutters on phones where rows animate into view
- Clicking a link plays a loading animation before the next page appears
- A caching plugin is installed and mobile scores barely moved
Why it happens on Salient
Most common first.
- 1
A full-screen Nectar Slider opens the page
The slider is the first thing on the page and the largest. Several full-width images, or a background video, have to download, and the slider's script has to run before the first slide appears. Google measures how long that largest element takes. A full-screen video of coffee being poured is a heavy way to introduce an accounting firm.
- 2
Entrance animations on every row and column
Salient lets each column, image and heading animate into view. Animated content is hidden until the script that reveals it has loaded, so text that could have appeared at once waits its turn. Parallax backgrounds add work on every scroll, which a phone shows as stutter.
- 3
Animated transitions between pages
The Page Transitions setting plays a loading effect when a visitor moves from one page to the next. It looks polished on a fast connection. On a slow one it is a deliberate pause placed in front of content that was ready to show.
- 4
A font family for every heading level
Salient's Typography panel accepts a different font for the navigation, each heading size, the body text and more. Every family and weight chosen there is another file to download before text is drawn in its final form. Icon sets work the same way: the whole set loads to display three icons.
- 5
Plugins and demo leftovers loading everywhere
Salient plugins for features the site never used, a second slider plugin and a store plugin from an imported shop demo all add scripts and styles to pages that do not need them. Slow hosting and a missing page cache make each of these worse, though they are a separate problem with a separate fix.
How to fix it, in order
Least invasive first. Stop at the step that fixes it.
- 1
Measure the page the way a phone sees it
Test the home page on mobile in PageSpeed Insights and write down the element it flags as the Largest Contentful Paint; on Salient it is usually a Nectar Slider or a full-screen row. On most Salient sites it is a slide. Make changes on a staging copy so you can compare before and after.
- 2
Fix the opening slider first
Open Nectar Slider in the dashboard and look at what the first slider holds. Cut it to one slide, or replace it with a single row and a still image. Resize the images to the size they are displayed at, and give phones a still image where desktop gets video.
- 3
Turn on Salient's performance settings
Recent Salient releases have a Performance section in the options panel, under General Settings, covering image lazy loading and how scripts are loaded. Enable one option at a time and check the slider and the menu after each. If your panel has no such section, the theme is several releases behind and updating comes first.
- 4
Remove the motion nobody would miss
Switch off animated transitions under Page Transitions in the Salient options panel. Then edit your main pages in the builder and clear the entrance animation from anything visible without scrolling. Keep parallax for one section, not six.
- 5
Trim fonts, icons and unused Salient plugins
In the Typography panel, bring the site down to two families and the weights you use. Under Plugins, deactivate Salient plugins whose features appear nowhere on the site, checking on staging that no page shows a bracketed shortcode afterward.
- 6
Add one page cache, and only one
With the page itself lighter, a single caching plugin or the host's own cache handles the server side. Do not let it repeat jobs Salient already does, such as lazy loading or delaying scripts. The general WordPress speed guide covers hosting, PHP and the database.
Keep it from coming back
- Choose one hero image over a five-slide slider on the home page
- Add an animation only where it explains something
- Re-test mobile speed after each new plugin or demo section
- Keep one tool in charge of lazy loading and script delay
The permanent fix
A faster Next.js build, with a CMS made for your business
If the site is still slow after the slider is cut down and the animations are pared back, what remains is the floor: the builder's markup and the scripts Salient needs on every page. A Next.js build with a custom CMS serves pages as static files and ships only the code each page uses, so the same design can keep its motion where it matters and still load quickly on a phone. That is the point where further tuning costs more than it returns.
| On Salient today | On Next.js with a custom CMS | |
|---|---|---|
| What you keep updated | WordPress, the theme, its builder and every bundled plugin, all in step | Nothing on a schedule. There is no theme or plugin stack to fall out of step |
| How a page is served | Built from the database on each visit, through the theme and its builder | Built ahead of time and served as finished files from servers near the visitor |
| How you edit it | A general-purpose builder with every option the theme ships | A CMS built around what your business actually changes: services, prices, photos, posts |
| What can break it | An update to any one of those parts, or a license that lapses | A change someone makes on purpose, tested before it goes live |
Your content, your addresses and your rankings come with you: every page is moved, every old address is redirected, and you get a login to an editor that only shows what you need. A repair is still the right call for many sites, and we will say so when it is.
Want this fixed on your Salient site?
Tell us what you are seeing. We look at the site, tell you plainly what is wrong and what it takes, and quote a fixed price before any work starts.
Which of these sounds like you? (pick any)
Frequently asked
Not inherently. A Salient page built with one hero image, restrained animation and the performance settings on can pass. The sites that fail are usually running a video slider, a dozen animated rows and plugins left from a demo, which would weigh down any theme.
On the home page, usually yes. Few visitors wait for a second slide, and a single well-sized image appears sooner than any slider can. Keep the slider further down a page or on a portfolio piece, where it is not the first thing a phone must load.
They can when both try to do the same job. Two tools lazy loading the same images or delaying the same scripts produce blank sliders and menus that will not open. Decide which tool owns each task and switch the duplicate off in the other.
The layout, colors and type stay exactly as they are. Content simply appears in place instead of sliding or fading in. Most owners keep one or two animations where they draw attention to something that matters and do not miss the rest.
Keep reading
- ServiceWordPress Speed & OptimizationA slow site loses customers before they read a word. We tune WordPress for speed, stability, and search — measured, not guessed.
- ServiceSite Speed & Core Web VitalsA slow site loses the customer before they see your offer. We fix what makes pages crawl — heavy images, bloated scripts, blocked rendering — and prove it with numbers.