How to make your responsive mobile website hurt my heart
elsyms.com
elsyms.com
I’ll add this too, using uBlock, within seconds of loading the page, it’s already blocked some 500 requests.
Either that or they should have been required to write the thing while allowing us to set their scroll wheel speed.
/rant
Why do you make mobile sites that can't be zoomed? This is so annoying. Then sometimes zooming is possible but the sticky headers/footers also zoom and hide the actual content.
Designers are really in love with using literally any font that's not a system font and will throw a fit if they can't do that. It's all because branding, or something.
As a user I hate that crap. Quit wasting my disk and bandwidth with your cutesy garbage and just use system fonts. As a developer I hate that crap, because it's one more thing to worry about.
But the designers/marketers have won this one—they're willing to fight really hard for their special snowflake fonts and have sold it to the people who make decisions as being vital for branding, which is Super Important™.
Add allowing custom, downloaded fonts to the list of things the web is worse for supporting.
Though to be fair, as an ad block user, I can't actually be totally sure that the font wouldn't have a positive effect on my ad engagement.
You're obviously in the 5% which values function over form, but surely you can understand most people want things to look pretty, plus the company wants to have a cohesive brand.
I used to be a function-over-form advocate but was converted somewhere along the line after working with some awesome designers, doing lots of a/b testing and talking with the end user.
Both form and function are equally as important as each other.
any stats? I'd say it's the opposite. It would seem to me people want things to work, first and foremost.
Both form and function are equally as important
This contradicts the previous statement, if your userbase is your first priority.
It is important to test these kind of assumptions. That's the reason why A/B testing and other analytics tools are used(not to mention communicating with the end user).
/s
I think a large part of the push for icons is awareness that not everybody reads English.
I remove sticky elements with the dev console on anything I actually want to read that's longer than a few lines of text—though I can't do that on mobile, so it's worse there.
> Old-school sticky sidebars (as in old frame layouts, for example) were totally fine on desktop, but are out of fashion now because they don't translate well to mobile.
What we need is the ability to focus on a div.
My other one to re-enable proper scroll and zoom: javascript:document.queryselector('meta%5bname=viewport%5d').setattribute('content','width=device-width,initial-scale=1.0,maximum-scale=10.0,user-scalable=1');
These two can fix a lot of broken "responsive" garbage the front-end web dev community seems to really enjoy.
If you do use lazy-loading, please be sure to do so in a way which works without JavaScript enabled (sadly, this is very uncommon). Mobile users are free to use browsers which load images on demand (indeed, I remember that approach from the 1990s), or perhaps browsers could agree on a standard for different resolutions of images, but breaking the Internet (which is what requiring JavaScript to view content is) to save some people some bandwidth is IMHO a bad idea.
https://www.robinosborne.co.uk/2016/05/16/lazy-loading-image... looks like a nice technique.
> Render as much server-side content as you can.
> Reduce/remove the third party dependencies you have on your pages.
> Lazy load images whilst maintaining page layout.
> Stop hacking fixes for your mistakes with Javascript.
All good advice, particularly the last bit.