Current time: 08-23-2017, 02:21 PM Hello There, Guest! (LoginRegister)

Post Reply 
 
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Slow load after settng up CloudFlare
06-23-2017, 12:14 AM
Post: #1
Slow load after settng up CloudFlare
Hi,

I have a VPS where I run some sites.

2 of the sites is set up with Cloudflare and both of them loads slower than the others without Cloudflare.

Example ;

http://bestillefisk.no/ - with cloudflare (Load is slow)
http://dennorskefiskebilen.no/ - technically the same site on the same server, but without Cloudflare (Load is ok)

I have also run 2 tests. 1 via Cloudlare and one directly to the server/sites IP.
The result showed that Cloadflare was a bit faster... Huh

Links to results;
https://www.webpagetest.org/result/170622_57_19T1/
https://www.webpagetest.org/result/170622_ST_1A5P/

Have anyone experianced similar? Any tips?
Find all posts by this user
Quote this message in a reply
06-25-2017, 12:24 AM
Post: #2
RE: Slow load after settng up CloudFlare
You've answered your own question.

CloudFlare is great for fixing very slow + poorly tuned LAMP Stack sites.

For well tuned sites, avoid CloudFlare or any other tech which stands between your site + your visitors.

Like help speeding up your site? Skype me @ ID davidfavor for a quote. Be sure to include your site name in your Skype Add Contact request.
Find all posts by this user
Quote this message in a reply
06-25-2017, 04:52 AM
Post: #3
RE: Slow load after settng up CloudFlare
(06-23-2017 12:14 AM)Altberger Wrote:  2 of the sites is set up with Cloudflare and both of them loads slower than the others without Cloudflare.

I have also run 2 tests. 1 via Cloudlare and one directly to the server/sites IP.
The result showed that Cloadflare was a bit faster... Huh

Links to results;
https://www.webpagetest.org/result/170622_57_19T1/
https://www.webpagetest.org/result/170622_ST_1A5P/

My experience with Cloudflare is long but generally good when setup properly. My own impatience has sometimes led me into error when initiating CF. When transferring nameservers to CF I know I'll have to wait until they resolve and CF Dashboard shows 'Active'.

'Active' can be misleading. It took an additional 12-18 hours beyond DNS resolution for CF's CDN servers to begin delivering content to WPT, and to other testing tools! So be certain that you are more patient than I am before drawing your download speed conclusions.

Time To First Byte on both tests are very long. My first action would be to find better hosting, and to make sure that 'Keep-Alive' is enabled on their server. A host that won't supply that feature at a minimum is not one you should use.

Best of luck!
Find all posts by this user
Quote this message in a reply
06-26-2017, 09:10 AM
Post: #4
RE: Slow load after settng up CloudFlare
Those two sites are quite different. One is 2MB, the other one is 1.7MB. One has 5 fonts, the other one just 4. One has more JS, more images etc. than the other one. That's enough to explain any performance difference between them.

The two tests you presented show almost exactly the same performance when you discard initial redirect from this test:
https://www.webpagetest.org/result/170622_ST_1A5P/
(substract 2230 from SpeedIndex and other appropriate values).

And now for "why" it seems slower with CF:
- this is slow http://www.webpagetest.org/result/170625...dbd2f2c77/
- and this is slow as hell http://www.webpagetest.org/result/170625...544bb02c7/

Why the first one is just slow and the second one is slow as hell? Because in the second one you make a request to JS that either doesn't exist and it triggers long running 404 handler or is processed by PHP and times out. Or it's infinite redirect loop to very slow resource. Or dozen other reasons. Either way JS blocks page rendering until it times out and hence the difference.

Actually I ran:
:~$ curl -H "Host: bestillefisk.no" "http://91.225.60.234/wp-content/plugins/woocommerce/assets/js/frontend/woocommerce.min.js?ver=2.6.14"

And it hasn't responded with either content nor error code for five minutes. At this point you can pretty much clear CF out and focus on why your server takes so much time to respond to this request.
Find all posts by this user
Quote this message in a reply
06-29-2017, 12:27 AM
Post: #5
RE: Slow load after settng up CloudFlare
As datadiggers said, focus on your site speed.

Trying to debug CloudFlare problems tends to suck massive amounts of time + rarely produce useful results.

Remove CloudFlare + fix your site speed (hire someone if required) + then determine your next steps.

Like help speeding up your site? Skype me @ ID davidfavor for a quote. Be sure to include your site name in your Skype Add Contact request.
Find all posts by this user
Quote this message in a reply
07-29-2017, 07:57 AM
Post: #6
RE: Slow load after settng up CloudFlare
What about international websites. Is it not better to use a service like CF to deliver some static content nearby the location of the user directly by cache?

I think this might be helpful. That's why I setup Cloudflare for my webprog24 website. The performance did not change and I asked people from all over the world (Mexico, India, USA) about the loading speed. They all say that the first time hit is better on this website. But that's it.
Find all posts by this user
Quote this message in a reply
08-01-2017, 12:27 PM (This post was last modified: 08-01-2017 12:30 PM by GreenGecko.)
Post: #7
RE: Slow load after settng up CloudFlare
(07-29-2017 07:57 AM)webprog24 Wrote:  What about international websites. Is it not better to use a service like CF to deliver some static content nearby the location of the user directly by cache?

I think this might be helpful. That's why I setup Cloudflare for my webprog24 website. The performance did not change and I asked people from all over the world (Mexico, India, USA) about the loading speed. They all say that the first time hit is better on this website. But that's it.

Use an oldschool CDN then. If you want it to be geo-aware, remember that you may well need a geo-aware DNS service to run it.

Because CF attempts to dumb everything right down, it has to proxy your web page, and that will always make it slower.

A CDN ( in the original meaning of the word? ) will - once set up - deliver static resources from a local source. Combine this with decent expires headers for them, and you should both lower the stress on your web server, and improve performance for the customer.

Once you've set that up, you need to size and configure your web server to deliver in a performant manner - but at least you don't have to tune it to deliver static content at the same time.

EDIT: I see you're running drupal. Don't forget to install a full page cache at application level too.
Find all posts by this user
Quote this message in a reply
Post Reply 


Forum Jump:


User(s) browsing this thread: 1 Guest(s)