Slow Transition on Live but Faster on Staging

I have a staging site and a live site. Both have the same files, same settings, etc. However, the live site seems to transition in the portfolio extremely slow compared to the staging site. I cannot figure out why there is a difference nor where to look to fix it. I want the faster transition.

Thank you.

Staging:
div class=“portfolio-individual-sec portfolio-individual-sec-1 slick-slide” data-slick-index=“0” aria-hidden=“true” style=“width: 2543px; position: relative; left: 0px; top: 0px; z-index: 998; opacity: 0; height: 1040.39px; transition: opacity 500ms ease 0s;” tabindex=“-1” role=“option” aria-describedby=“slick-slide00”

Live:
div class=“slick-slide” data-slick-index=“2” aria-hidden=“true” style=“width: 2543px; position: relative; left: -5086px; top: 0px; z-index: 998; opacity: 0; transition: opacity 7000ms ease 0s;” tabindex=“-1”

You sure you have the same settings? Cause it looks to me like you dont.

3 Likes

Hello, and thank you for getting back to me.
Yes, all the code is the same. I’m wondering if you’re looking at an old cached version. Refresh your browser and double check.

Considering i’ve never been to your website before today, i’m going to say that no, i’ve not got a cached version of your webpage.

Your webserver is serving a page that has the carousel set to 7 seconds delay. If the WEBSERVER is caching something, that’s between you and your hosting provider.

Well, yes, that would make sense. It just seems odd that the files that control the slick slider are all the same and yet you’re seeing two different speeds. I thank you for pointing the above out, though, and I’ll do some more looking. But it doesn’t make sense if they are all the same.

Well you say they’re all the same, but I see different files on your different sites.


Your sites are calling different versions of the file, for starters… (I called your live site with a dummy query parameter, ?break=1 , to try and break any possible caching)

Note that from this screenshot, it’s your staging site that’s cached. And it’s being cached by WordPress.

I dont know Wordpress very well, so i’m probably reaching the limit of my ability to assist, so someone else chime in here…

Based on the version numbering, it looks like Wordpress is showing you an “in-edit” version of your website (hence the version number being a timestamp) that hasnt been published properly to the main site (which would then become a proper version 1.3, presumably). I dont know how editing wordpress works. Is it possible there’s a “publish changes” button you need to push somewhere?

That actually makes more sense (the delivery of different versions). As for a ‘publish’, no. These sliders run on a ‘slick.min.js’ code within the theme files.

I will say this, I am editing both the live and the staging sites in “New Private Window”. I’m running both of the portfolio pages and see that both the live and the staging are transitioning very slowly. So this proves that both sites are running the same code. However, if I was to test this using regular Chrome, the staging site’s Portfolio page transitions at 500ms.

I can’t really help with the problem but it may help you or someone else narrow down the problem. If I simply blanket copy your html straight into a codepen for the slow site then it runs at 500ms the same as your staging site.

I did make a small mod to a slick file to reflect the correct speed, which is now working. Thanks to @m_hutley suggestion of breaking the cache when I load the live site page, it all seems to be functioning correctly.

Thank you, gents!

2 Likes

This topic was automatically closed 91 days after the last reply. New replies are no longer allowed.