Google adjusts results per user.
The kind of improvements tech support gaiz can make to site speed won't help enough. The biggest problem with speed is vB5 and the way its code is rendered in browsers. It chews the everliving fuck out of my CPU. It's a fad (though I'm afraid it's here to stay) to make HTML "responsive" so that you write a one-size-fits-all version instead of a mobile version and a desktop version. Responsive code is supposed to deal with different screen sizes/shapes, different input methods, etc all on the fly. So you get this huge, bloated, javascript-infested pile of shit that places a huge burden on the client, whose job used to be merely a matter of displaying stuff but now must write a whole page to display and constantly watch for changes that might cause a need to rewrite it.
Not all responsive sites are that bad. Combine really sleek code written by really smart folks with simple, efficient design and things work tolerably. However, most web developers really aren't that good, and few designers give a damn about efficiency.
vB3 (what we're using here) predates "responsive" techniques. For each page there's a regular desktop version, maybe there's a mobile version optimized for small screens, and there's FUCKING TAPATALK FOR FUCK'S SAKE because extensive use of a forum is one case where an app (or actually multiple apps using the Tapatalk back-end) really is better than just using a web browser.
I prefer desktop usage but if they'd hook that shit up to Tapatalk or ForumRunner I'd just use the app most of the time, only occasionally dropping into a web browser, just so I could avoid that clusterfuck.
Responsive crap is not something you can put in a ticket for and they can change, it's something where they're going to need to see a major loss of customers before they'll accept that they have to do something about it. Tapatalk/ForumRunner won't be fixed from a single ticket, but if they are flooded with enough tickets from all of their customers they'll probably do it.
|