I always view the source of websites like this and this is one of the worst I’ve seen. 217 lines of code (including inline Javascript?!) and a Google tag for some reason, all to put the word YES in green on black.
Oh man. One of my old companies, the Devs would always blame the network. Even after we spent a year upgrading and removing all SPOFs. They’d blame the network……
“Your application is somehow producing 2 billion packets per second and your SQL queries are returning 5GB of data”…. “See! The network is too slow and it has problems”
So it is always DNS
https://isitdns.com/
I always view the source of websites like this and this is one of the worst I’ve seen. 217 lines of code (including inline Javascript?!) and a Google tag for some reason, all to put the word YES in green on black.
Agreed, could be static HTML and a GIF.
Thanks, I won’t click that link.
Did not think of doing that.
I guess i never expected anyone to have a fcking JavaScript on a simple page as that
How else would you center a div??
can confirm, its always DNS. Even when it looks like a network issue, its DNS
Spotted the Network guy
Oh man. One of my old companies, the Devs would always blame the network. Even after we spent a year upgrading and removing all SPOFs. They’d blame the network……
“Your application is somehow producing 2 billion packets per second and your SQL queries are returning 5GB of data”…. “See! The network is too slow and it has problems”
Dev: My app’s getting a 400 hitting the server. Your firewall changes broke it.
Me: You’re getting to the server, it’s giving you back a malformed request error. Most likely it’s a problem in your client.
Dev: it worked fine until you made that change in QA.
Me: Your server is in production.
After that, I just get too busy to look at it for a while… They figure it out eventually.