The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
1.1s (winhost) vs 14.7s (sMaRtErAsP.nEt). From: PA, USA.
SmarterASP one is not doing HTTPS
This shouldn't matter unless they're using decade+ old servers; anything newer has hardware acceleration in the CPU and should see something like a 1% performance impact from HTTPS.
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, weighing all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
I didn't time it exactly but, it took WinHost quite a long time. I could see the image being rendered block-by-block. At least 6-7 seconds. The SmarterASP site was less than a second, hardly noticeable. I'm in South Carolina, USA.
3. If you care about speed, reliability and security (incl. ddos-protection) you should really serve everything from a CDN edge-cache like Cloudflare or AWS CloudFront.
Even if your content isn't cacheable.. just using a CF endpoint as a "proxy" will have huge benefits for short-circuiting roundtrips from browser-to-server. (Just establishing a single HTTPS connection requires several sequential TCP roundtrips.)
Thanks for trying it out. And, I do believe that it does matter where you are physically located in relation to where my web server is located. It's a very odd thing actually & I've learned a bit about it but it is still quite confusing.
Most people saw WinHost 2x - 10x slower. But I did notice that if you are "closer" to the WinHost one it could resolve just as fast.
Differences could be network performance, disk performance, or caching. Edge versus Chrome variation might be at related to caching connection information or caching at the web host (where the first connection, Edge established the connection information and caused the host cache to load, then Chrome used it).
A CDN would help with both performance and DDOS attacks for static content. Larger, more established providers, often have built in DDOS defenses and CDNs, but optimizing costs may require a little more creativity.
Actually, I have now switched (and the DNS seems to have propagated through) to amazingly fast InterServer.net web host. I believe your test (newlibre.com) probably hit the new site ip address 126.96.36.199.
WinHost: 2.556 seconds elapsed during load.
SmarterASP: 2.812 seconds elapsed during load.
WinHost: 0.122 seconds elapsed during load.
SmarterASP: 0.173 seconds elapsed during load.
Near Toronto, EST.
- The index and js pages appear to be different sizes on each site (larger on the second), and the favicon was not found on the first site.
- Firefox gave me a warning about loading the newlibre site.
- Be sure to optimize your images if actually using any.
I just had to login to a website and my password expired (password expiry is bad practice, according to the pros).
When I tried to reset my password I got an error that my new password looked too much like the previous.
To my knowledge, they can't possibly know that unless they store it as plain text as even a single letter difference should generate a completely different hash.
Am I right to not trust these guys with my password?
Not that I really have a choice in the matter, but I'd at least give them a call about their (mal)practices...
I'm giving these guys my old password as part of the password renewing process...
Must be a Monday
Did they not ask you to enter the previous password before setting the new password?
If you're entering the old and new password at the same time, then it's trivial to check.
If you've entered the old one and been told that it has expired, they may be storing the old password that you entered in memory to compare to the new one. It wouldn't be great, but it doesn't necessarily mean they're storing your password insecurely.
Alternatively, they may store the salt and hash for one or more previous passwords, apply simple variations to your new password, and see if the modified password produces the same hash as a previous password.
Without seeing their code, you can't be certain that they're not doing the wrong thing; but you can't be certain that they are doing the wrong thing either.
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
Last Visit: 31-Dec-99 18:00 Last Update: 20-May-22 11:25