You want me to set up an optimise a wordpress site just for the sake of proving something to you?
I don't want you to do anything, but if you're trying to back up what're saying or try to get your point across better then maybe it's in your interest to do so. Even if you put a default WordPress install using the default theme on a sub-domain hosted on a setup you think loads a website faster, then that'd do for the test. I'm sure I could get it to load more quickly with the setup/optimisation that I do. If not, then I stand corrected, but at least I'm willing to back up what I'm saying. You're just saying such and such is such and such and mostly giving apples to oranges comparisons.
It's probably best not to say anything if you aren't willing to back up what you're saying. Posting lots of links to static HTML sites is not saying Apache is faster than LiteSpeed or dismissing what I was getting at in my initial post.
You can't expect me to cover the topic 100% with a paragraph or two just as I wouldn't expect you to cover the topic 100% with only a paragraph or two. It's a very complex topic.
I gave information in my initial post that will help. I never said it was the bee all and end all haha. If someone would like further information on how to make a site faster, then they are free to ask for more information.
Also, this was about the webserver, but then the discussion changed to how fast the website loads depending on the code.
Nothing you posted backed up what you were saying. Saying some static websites nearly loaded as fast as a dynamic site isn't saying Apache is faster than LiteSpeed. If it were a static website on Apache and Litespeed, then LiteSpeed would have loaded the content even faster than it did with dynamic content.
Coding aside, out of the box LiteSpeed with LScache will load a website faster without having to tweak Apache or Nginx to death. If you prefer to to go about it the long way for each site to get the same or similar result, then that's up to you, but that takes a lot more time and is more for someone who knows how to do such tweaking.
A lot of individuals or businesses haven't got time to do that or even know how to do it. When hosting on a setup with LiteSpeed/LSCache it's already optimised, and it's possible to tweak things even further if needed. Each to their own.
LScache is very advanced. LiteSpeed is faster than Apache and Nginx by default, even faster if you tweak LiteSpeed. Nginx plugins for cPanel mostly proxy only, so nowhere near as good as LiteSpeed. LiteSpeed is a drop-in-replacement and makes websites faster out of the box regardless of how poor or good the coding is. LiteSpeed also fully supports .htacces, whereas not the case with Nginx.
My point to you was to say LiteSpeed is faster than Apache out of the box i.e no tweaking necessary.
Maybe, so are a lot of other options.
But not Apache vs what I put. The things I said that make a difference, and they do make a difference. You said they were too generic. I also said NVMe helps and with the test I provided, the site is hosted on SSD, not NVMe. So likely even faster if hosted on NVMe.
It is a different thing, and usually much more important.
I agree with this, and at any point did I said it wasn't important. Nor did I say only the hardware/network/software plays a role. You're right; the coding is usually much more important. But from the start, I've said a site with the same content would load faster on LiteSpeed than Apache. LiteSpeed would also handle concurrent connections a lot better than Apache would, i.e. handles massive traffic much better without server running out of resources, or worse, crashing altogether. There are many tests which show Litespeed handles traffic better than Nginx, too.
If people want a faster site they do not care whether it is achieved by optimising the design, or optimising database queries, or changing the web server - but for most sites the problem is the design, the code or the database (most often in that order).
Again, I agree with that, as mentioned in my previous comment. I never said that wasn't true. I was merely saying that out of the box LiteSpeed is faster than Apache and that it depends on storage being used as well as the resources limits that a provider offers to their customers, i.e. if a cron is running in WordPress and the account has 1MB/s Disk IO it would take a lot longer for it to complete than on an account that has 50MB/s. When a resource is being throttled due to a cron running, it can slow down the website for other visitors visiting the site at the same time.
As I said, one could write many pages on how to get the site to load as fast as possible, but the ones I mentioned in my initial post can make a huge difference regardless of how good or bad the coding is in the website.
I'm well aware the website should be optimised first, and only then put it on the best network/hardware/software and optimise further.
Upvote
0