![]() ![]() ![]() |
|
richms: Don't blame the cache for the broken plugin process. There are well established best practice processes for versioning the filename for these things so that it doesnt happen. If the script authors are stupid enough to update a file and keep the name the same then stuff like that happens.
Same files will get cached with the same expiration on corporate proxies and also browser cache. Its a plugin/theme issue.
timmmay: Cloudflare can make a HUGE difference even just for with basic caching for a very lightly loaded website, if you set it up properly. For example I have an image heavy website hosted in the USA, it used to take 12 seconds to load - super slow. Once I put it onto Cloudflare AND set the headers up to allow caching of images, css, and js the load time dropped to 3 seconds - they have a POP in Auckland. I set static resources to basically never expire, you can manually purge their cache if required. I can drop that even lower by setting headers to cache pages - I can achieve around 1 second website load times, at the expense of some pages being stale. You of course only cache pages that rarely change - product pages, but not ordering or shopping cart pages.
Putting CloudFlare in is only step one - configuration is really important. I do this for a lot of my customers. I have a pretty decent sized set of techniques in this area.
boland:
Just looked into HTML caching and our homepage now loads bloody fast :) Check it out: eurodress .co.nz
Google Pagespeed Insights doesn't use it though. Server response time: 3.3 seconds :( :(
mattwnz:boland:
Just looked into HTML caching and our homepage now loads bloody fast :) Check it out: eurodress .co.nz
Google Pagespeed Insights doesn't use it though. Server response time: 3.3 seconds :( :(
It seem to load slowly for me, so I would hate to see how slow it was before that.
You probably should ask any host you are looking at how many websites they allow per server, and gets stats for server loads and uptime stats.
timmmay: Homepage isn't bad, but generally the website feels pretty slow. I'll have a look later, but I suspect it's more around processing time than static resources. I do think there's a chance your host is correct that you need to look at the code and database for optimisation. I spent a year as a performance engineer and have a business that does a fair bit of SEO and performance work, with a background in development. I could potentially help speed things up.
mattwnz: I am now getting an error as below. I see that it is redirecting to https, I wonder if that could be part of the reason for the slowness.
Unable to complete secure transaction
You tried to access the address http://www.eurodress.co.nz/, which is currently unavailable. Please make sure that the web address (URL) is correctly spelled and punctuated, then try reloading the page.
Secure connection: fatal error (80) from server.
https:// eurodress .co.nz/
boland:mattwnz: I am now getting an error as below. I see that it is redirecting to https, I wonder if that could be part of the reason for the slowness.
Unable to complete secure transaction
You tried to access the address http://www.eurodress.co.nz/, which is currently unavailable. Please make sure that the web address (URL) is correctly spelled and punctuated, then try reloading the page.
Secure connection: fatal error (80) from server.
https:// eurodress .co.nz/
I haven't seen this error before? Everything is working fine.
ANd yes, you are correct, I force SSL everywhere in the site. Didn't notice a big difference at that time, and read some articles that SSL-enabled site receive a slightly higher ranking in Google.
May be I turn that off.
mattwnz:boland:mattwnz: I am now getting an error as below. I see that it is redirecting to https, I wonder if that could be part of the reason for the slowness.
Unable to complete secure transaction
You tried to access the address http://www.eurodress.co.nz/, which is currently unavailable. Please make sure that the web address (URL) is correctly spelled and punctuated, then try reloading the page.
Secure connection: fatal error (80) from server.
https:// eurodress .co.nz/
I haven't seen this error before? Everything is working fine.
ANd yes, you are correct, I force SSL everywhere in the site. Didn't notice a big difference at that time, and read some articles that SSL-enabled site receive a slightly higher ranking in Google.
May be I turn that off.
I am still getting it, I am using the Opera browser. Maybe there is something going on at the server side.
timmmay: Tests say your home page is pretty good now - see here. Feels much faster than before you started playing with Cloudflare. Just be careful not to cache things you shouldn't. If you want to force https create a pagerule, make it the first rule.
|
![]() ![]() ![]() |