x

Are you having issues with FTP and Overall Performance due to Cache?

Recently Weebly decided to cancel the orange to orange (O2O) DNS Setup, we contacted Cloudflare to find out about this and they confirmed this.

 

Cloudflare's support said that Weebly no longer supports the O2O (orange to orange) DNS setup with Cloudflare. It means that Cloudflare no longer can control the cache behavior, this was helping to reduce the FTP time and improve over 30 points the overall performance measured by https://pagespeed.web.dev, now it's only up to Weebly to control it.

 

(as Weebly said, Weebly is now a "closed platform", but for years in a row they connected well with Cloudflare) 😞

 

The problem is that Weebly does NOT offer any cache control features ! So there's no replacement for the features we've lost.

 

For example, we used to have a "cache all" policy with Cloudflare, including the HTML file which is not cached by default.

 

Then we used the "purge cache" to decide when exactly we want to refresh the cache, achieving fine control over the cache. 

 

This is a common speed optimization technique, used in millions of websites over many platforms, but Weebly just can't do it !

 

Now we can't control the cache behavior, so the HTML file won't be cached, which greatly reduces the page speed. 

 

For comparison, WordPress has cache control, so their websites perform much better than Weebly's current state. 

 

Previously we could compete with Wordpress with our speed results, but currently it's not even close 😞 

 

Is anyone having this same issues? Any idea on how to solve this?

Thank you.

Ivan Ratkovich
134 Views
Message 1 of 1
Report
0 REPLIES 0