14 ms·
The Ethics of Web Performance
- thethirdone 7y ago> When you stop to consider all the implications of poor performance, it’s hard not to come to the conclusion that poor performance is an ethical issue. I don't think its clear cut and the article does not make a good argument that "poor performance is an ethical issue" The two supporting points are roughly: 1. Poor performance will make sites unusable for people without good CPUs / internet 2. Poor performance will waster energy and lifespan of devices Point #2 is very weak, because the alternative to slow sites is spending time optimizing them which may waste human time. Its not obvious what the optimal ratio is to minimize total waste. In order for #1 to be an ethical issue, I would require it to only or disproportionately affect those without high speed devices. However, web performance seems to scale decently so improving a sites performance on high end machines by 2 probably also improves it on low end machines by ~2.
- Arbalest 7y agoYour point about #1 doesn't make much sense. Sure the performance might scale the same on both low and high end devices, but two things come to mind. There is absolute thresholds of usability, that doubling the performance might not mean much for the high end user, but it might mean the difference between something tolerable and intolerable on a low end device. That's all well and good if we're only measuring CPU time. If memory becomes an issue, excessive memory usage will lead either to: 1. Complete failure of the website or 2. going into paging/swap, which would very much give you the disproportionate effect you were asking for.
- thethirdone 7y ago> There is absolute thresholds of usability, I don't think this is true, for slow websites (taking >6 seconds to load) the effect is mostly linear. For faster sites going from 1s to 0.5s will be less impactful than going from 6s to 3s. So there are non-linear effects from a psychological perspective, but I think those are mostly relevant at faster timescales. > difference between something tolerable and intolerable on a low end device. The only case where I have had things reach intolerable is when the network cannot actually send the data without faulting. Loading for 3 minutes is not actually intolerable. > If memory becomes an issue, excessive memory usage will lead either to: I don't think most single webpages will overload a low end systems RAM. I think the lowest system RAM you can have is ~0.5 gb usable and most sites fit within that.
- Arbalest 7y ago> For faster sites going from 1s to 0.5s will be less impactful than going from 6s to 3s. So there are non-linear effects from a psychological perspective, but I think those are mostly relevant at faster timescales. I don't see how you can dismiss the psychological perspective. These are real people using the websites. If it wasn't the premise wouldn't be raised in the first place. > The only case where I have had things reach intolerable is when the network cannot actually send the data without faulting. Loading for 3 minutes is not actually intolerable. What you've had? What perspective is this being raised from? What about SPAs where you aren't loading the whole website because of lazy loading, but that lazy loading has overheads that don't include network time. > I don't think most single webpages will overload a low end systems RAM. I think the lowest system RAM you can have is ~0.5 gb usable and most sites fit within that. Could you please clarify whether you mean 0.5GB total system ram, or 0.5GB left over after system overheads. Consider this: https://gadgets.ndtv.com/jio-phone-4255 https://gadgets.ndtv.com/jio-phone-4255 or https://en.wikipedia.org/wiki/Nokia_8110_4G https://en.wikipedia.org/wiki/Nokia_8110_4G Both have 0.5GB system ram, and I can say with high confidence, having the latter, that the main system is slow, I don't believe for a second that that is somehow only bogging CPU and not using RAM. In the developing world mobile systems are often the only computing device people have, which is why there is even a market for such a lackluster phone in the jio phone. The issue, as other commenters have pointed out, is not the core website, but rather the addons that are thrown in because every marketing department and their dog needs to have their own code run on the site. No matter how simply the site is built, optimised for UI, these things will cause problems.
- okaleniuk 7y agoWriting code with performance in mind will get you there without any optimizations whatsoever. It's not about 12% speed up anymore, we're not living in the 70s. It's about not wasting orders of magnitude because of poor design choices.
- t34543 7y agoUntil there are clear and real incentives for performant code I think we are largely in a academic exercise.
- okaleniuk 7y agoYes, that's true. There are clear and real incentives they are just more visible in the cloud where you pay for your hardware. Or in traditional workstation software where there's also market competition: "do that 10 times faster than the competitors and we'll talk". It's true that with the Web the incentives are week. Sure, you'll lose some 10% of your potential visitors to frustration, but who cares if the traffic grows expectations are exponential.
- TeMPOraL 7y ago> There are clear and real incentives they are just more visible in the cloud where you pay for your hardware. Unfortunately not clear enough. Compute is cheap enough that company can easily run 10 or 100x less efficiently than it could with little extra work, because the cost barely registers when compared to revenue or salaries. (Even working in a small company I've seen situations like someone asking, "are you folks still using the XYZ VM, because it's burned a kilodollar this month", and we're all like "a what machine? sure, shut it down". It was needed once, then forgotten about, and it took a while before anyone noticed.)
- nullwasamistake 7y ago> Point #2 is very weak, because the alternative to slow sites is spending time optimizing them which may waste human time. Ehhh the easiest way to get fast sites is combining a fast language and framework. There's like 3 orders of magnitude difference in performance between something like Django and Vert.x I've seen code slow enough (PHP, 10 req/second) that running enough capacity consumed like 15% of the engineering budget. That could have easily been .1%. Since developers dont care about hosting cost most of the time, they keep using horrifically inefficient frameworks. I rarely see super slow code because people get called out in code reviews for doing really stupid stuff. It's always the slowness of frameworks that's been a problem IMO.
- C1sc0cat 7y agoDon't know why your downvoted - what people need to do is embrace statically rendered sites which pull from a more traditional back end.
- nullwasamistake 7y agoNot everyone agrees with that. A lot of people think the efficiency of writing code in favorite language X makes up for the added hosting cost. I just don't believe it with how many choices are available now. Maybe that was true 5-10 years ago. Now we have a good 5 languages with maybe 40 frameworks that run less than 3x slower than C. That's really really fast. Enough that you could run anything under top 500 sites with a single machine. Static CDN hosted react/angular SPA with a speedy backend can serve a stupid amount of traffic even on AWS free tier.
- C1sc0cat 7y agoAs an Enterprise SEO with over 15 years experience I don't really give any F&%!'s about your favourite language What I need is something that is faster than the competition, is properly built to minimise usage of our crawl budget and is flexible enough to add new content quickly can properly handle site migrations can implement hreflang for say a dozen locales.
- zucker42 7y agoThis is a pretty poor refutation to the thesis that web performance is an ethical issue. Your argument is that both points in the article are unimportant or outweighed by other factors. However, by making that argument, you are already tacitly accepting the ethical framework the author laid out.
- TeMPOraL 7y agoPoint #2 isn't weak, because it scales with the number of users. Slow sites waste not only energy and money (through electricity bills and device wear) × number of users, but also user's time, again, × number of users. If you want to count human time, then that extra second or three your thousands of users have to spend waiting for your site to load easily adds up to justify getting an engineer to muck around your site with a profiler for couple of hours and identify hot spots, and then more hours (over next days) to fix them.
- xamuel 7y agoI wish the "human time" ethical cost was factored in elsewhere besides just software. Things like: redundant forms at the doctor's office; useless fences that prevent you walking the shortest distance; time-consuming preambles when you call any customer service number. Imagine if the amount of time wasted was instead converted to a single number, divided by the average lifespan, and the corresponding number of people struck dead.
- thethirdone 7y agoThe argument for users time is a good point, but I don't think the author was intending that. My point was just that it was not sufficiently argued to be obvious. However, even that does not make the case that web performance is an ethical issue. It would only do so when the number of users is much greater than the amount of effort it takes to make a site. If I make a site that I expect 1000 people to look at, then the performance of that site isn't really significant. And not an ethical issue.
- TeMPOraL 7y agoThere's a categorical imperative aspect to this: a site with 1000 daily visitors (not necessarily unique) is not big enough to make its performance a significant issue. But if all such sites think like this, then it suddenly becomes an issue.
- pacaro 7y agoSimilar logic applies server side too. If your backend is inefficient then you may well be consuming orders of magnitude more power per query. While I take these numbers with more than a pinch of salt, I've seen comparisons that suggest that a backend written in ruby/python/php may be over 10x less efficient than one written in Java/C++
- sieabahlpark 7y agoWhen you can be just as productive as a web developer in c++ let me know.
- pacaro 7y agoIndeed, there are many factors to consider here. In a sense that is what makes discussions like this interesting! I suspect that in some respects that we already optimize for this as an industry, we might have application logic in python, but the database is presumably written in a systems programming language.
- luckylion 7y agoFair point. I believe productivity is a major factor in most performance issues. Write highly optimized code that's very fast and as small as possible or pull in jquery and a dozen libraries? It's pretty obvious which one will get the job done more quickly. And once the job is done, optimization often is off the table, because the next features await. I work for clients that are making lots of money with their sites, and not even then are they willing to spend pennies on the dollar to optimize those pages. Maybe the highest impact you can get is working on most-used parts. Make Wordpress run 3% more efficiently and you'll have an enormous global impact. Make your own site run 3% more efficiently and it won't register globally, unless you're Google, FB etc.
- de_watcher 7y agoIt's just good developers are hard to find. Web gurus will tell you that web is slow because the specific sites are written badly. While Linus has told that C keeps bad developers away from the kernel.
- okaleniuk 7y agoI'm really glad that's becoming a part of public discourse. Of course, poor performance is an ethical and economical issue. As the latter, we've been largely ignoring it in PC era (as a software guy, you don't pay for the hardware you're wasting so why should you care?) and now it's starting to be a concern with the cloud.
- buttholesurfer 7y agoThere are far greater things to be worried about.
- guggle 7y agoThe article seems to put the burden of performance on the developers... but I've been in situations where no matter what I did in favor of performance, the efforts were always negated by the installation of third party marketing tools. Things like retargetting platforms, tracking scripts or even recommandation systems. And let's not talk about the unreasonable client expectations about features per page...
- okaleniuk 7y agoThis is so true. You can maneuver within client expectations, and you certainly can optimize every particular features but marketing tools are often non-negotiable. From the user's stand point - they are pure overhead, too. For my own project, I decided to ditch them completely. Including the analytics. Well, it would have been nice seeing all the nice plots but at the end of the day they just show vanity metrics. The real impact is immeasurable.
- Cthulhu_ 7y agoThere should be analytics solutions that don't put the burden on the client, server-side products. Or lightweight ones that mainly track button clicks and navigation, instead of e.g. recording all mouse and keyboard interactions. I want to think basic analytics has a very low impact on performance. Ads, on the other hand... Which all inject their own analytics as well.
- Moru 7y agoThere are analytic tools that run on the log files. If that is to high load on the server I'm sure they can be run offline by downloading the logs to your local machine.
- vast 7y agoHe actually says that devs try to do their best but the business models make it hard. I can very well resonate with that. With decent effort we could make out site respond in a tenth of the current time. But no one ever asks for it nor will give you the opportunity. Even performance centric companies like Google are now doing an insanely bad job. Business applications perform bad even on modern desktops. They will probably try to keep the user facing parts of the ad machine fast, but everything else is not what I expect from a company with such mindset. They of course never did anything to improve the state of ad tech.
- pflenker 7y agoI know it's comparing Apples and Oranges, but: "War and Peace" by Tolstoi is 1.9 MB. A Twitter profile page is 2.5 MB, and that is already optimized (Posts below the fold are not loaded). Websites are bloated - so I am glad the ethical aspect is getting more and more into the focus.
- okaleniuk 7y agoI have a rule of keeping every page on wordsandbuttons.online under 64KB. And no dependencies so, apart from occasional pictures from wikimedia, no other hidden costs for the visitor. The number is of course arbitrary, but surprisingly it's usually quite enough for a short tutorial or an interactive explanation of something. And I don't even compress the code or the data. Every page source is human-readable. So it is possible to have leaner Web. it just requires a little bit of effort.
- Nyandalized 7y agoWith the help of transport compression like gzip, the total size can still be reduced by almost the same amount even if you don't minimize it.
- mr__y 7y agoThat's obviously true, however a minimized version will require less memory and slightly less cpu-cycles* to compress and, on the client side, it requires slightly less resources as well I do realize how insignificant difference that would be * then again not much of a difference since the DOM tree itself would consume orders o magnitude more mem.
- hinkley 7y agoProbably not less memory. zlib is based on a design that dates back to an era where you might only have 250-350 kilobytes (not a typo) of RAM to work with, and it was never really extended beyond that. It has a window it keeps in memory and if your file is longer than that window, you hit peak memory and stay there (you might actually hit that window immediately. I've forgotten how that part works, but some chunks of memory are pre-allocated).
- Nyandalized 7y agoAnything that becomes 19 seconds to become interactive on a flagship phone should be classified as faulty. It's not just unethical for people, but the environment. It's badly written code that is basically turning your cpu into a space heater.
- ajsnigrutin 7y agoNot just that. Anything that takes 19 seconds, will probably be refreshed after 10 and closed after 15 seconds.
- cameronbrown 7y agoThat's being incredibly generous too. Google: "53% of mobile users abandon sites that take over 3 seconds to load" https://www.thinkwithgoogle.com/marketing-resources/data-measurement/mobile-page-speed-new-industry-benchmarks/ https://www.thinkwithgoogle.com/marketing-resources/data-mea...
- Nyandalized 7y agoThere are lots of other problems piled on web development that is strictly not their fault. The aging network infrastructure hasn't seen updates in sometimes decades, despite billions and billions of tax money poured into it. You really should be able to get more than 3mbit/s in 2019. Pictures should be allowed to be more than a handful kilobytes in size. Datacaps are a ginormous moneygrab with no basis on technology. Abolishing corrupt corporate brotherhoods would do much more good than inventing yet another band-aid compression/surveillance point to the mix.
- vbezhenar 7y agoYou can't easily improve the latency. My latency to EU is 100 ms, my latency to US is 250 ms, so request-answer is 500 ms. Make two request-answer cycles and that's already 1 second. And TCP already have some cycles. Yes, I have 100 megabits (which is not easy to utilize, because of TCP algorithm), but that does not help. And that's not only about size.
- def_true_false 7y agoThe number reported by tools like ping is round trip time -- it already includes the return trip.
- KaiserPro 7y agoYou can make a rich, animated, and engaging website for less than 200kb. Most devs have big stonking macbook pros, with decent network connections. So having a 4.5 meg wedge of JS is a perfectly acceptable tradeoff. Much as US infrastructure is crumbling, You can't just say "Nahh, I'm not going to sacrafice my time to make things fast for the end user. I need these 1400 modules and full motion video."
- Nyandalized 7y agoYou definitely can, and that is being done at the moment. I'm reasoning that you could be doing so much more with much less effort and cost if you didn't have as stringent requirements. We should progress in all fronts, and not simply pile everything on one.
- lewiscollard 7y agoI think this is a very thoughtful article. As web devs we are much more likely to be developing and testing on beefy machines and beefy Internet connections than the general population is. Let's remember that we're building this stuff for other people, not just for us. :) I'll take one issue with one thing in the article (emphasis added): > The cost of that data itself can be a barrier, making the web prohibitively expensive to use for many without the assistance of some sort of proxy technology to reduce the data size for them—an increasingly difficult task in a web that has moved to HTTPS everywhere. But: HTTP/2! It's only available over HTTPS, gives really significant performance improvements and is supported on Chrome on those low-end Android devices the article mentions (and basically everything browser other than IE11 on Windows < 10 and Opera Mini).
- vast 7y agoI would argue if you make a well designed low end website h2 wouldn't make as much difference.
- pjc50 7y agoThe "proxy technology" sounds more like Opera: it's not simply compressing the existing stream, it does things like aggressively recompress your images at lower quality or even size. HTTP/2 will deliver your 2MB hero image using 2MB of data. A compressing proxy will deliver a slightly uglier 100kb version. Oh, and save a lot of data by never downloading the ads.
- Crinus 7y agoI remember many years ago when i had a 3G internet connection (which sometimes even had to work via 2G networks) for my laptop, the service would automatically recompress images to lower bandwidth and speed up times. To enable the connection i had to use a custom tool (it was essentially a fancy terminal - AFAIK it communicated with the 3G dongle using AT commands) which also had an option to adjust the (ISP-side) compression (i could disable it, leave it at default or make everything look like garbage but load fast...ish :-P).
- Nyandalized 7y ago
- bem94 7y agoI recently emailed the Guardian (UK newspaper) to tell them that an element of their website caused one of my CPU cores to spike to 100% utilisation while it was in view. It happened on my laptop, work desktop and phone. If you're a visitor, it was the graphic next to the podcast banner which looked like a sound wave. They've removed the element now and sent a very nice message saying they'd investigate. I really think/hope that the next "big thing" in software engineering will be energy efficiency in some form or another.
- YawningAngel 7y agoOh praise be. That's been screwing with me for months and I couldn't find a bug report page. Thank you anonymous Internet person!
- barrkel 7y agoYup, that thing completely killed scrolling perf in Android Firefox.
- JetSpiegel 7y ago> I really think/hope that the next "big thing" in software engineering will be energy efficiency in some form or another. The future is here, and it's called uBlock Origin.
- baalimago 7y agoThis is not an ethical issue, this is a capitalistic opportunity. The company who starts writing effective, clean and fast websites will gain more traffic = more money. There's nothing more frustrating than waiting for a website to load, only to have the button you know you want to press suddenly get pushed down 5 cm by some interactively loaded DOM element.
- kmlx 7y agodisagree with the premise of the article. performance is a technical issue, not a moral or ethical one. the experience that is derived out of poor performance might be classified as a moral/ethical issue (emphasis on might - a lot of apps use 100% of cpu, but your experience isn't affected, so it doesn't matter - in other cases your experience is affected so it matters), but poor performance by itself i think not. i might be wrong on this, but i didn't find the article compelling enough to change my mind. any other opinions that might change my mind?
- KaiserPro 7y agoThe ethics come from exclusion. If a reasonable device(ie cheap & modern) is unable to load said website, then they are stopped from using that site. If you are "poor" to use a term, then it might be that your phone is your only way of interacting with said service. (libraries and other places are not an option due to cost of getting there, or lack of time.) You are effectively saying that you must be this rich to use our stuff. Now, if you're bently, rolex or similar thats basically your whole way of life. But if you're a utility that provides a monopoly, then its morally dubious. Especially as things like paying bills over the phone, or by post incurs an extra cost.
- kmlx 7y agomy argument is that performance doesn't matter if user experience isn't affected. if it is, then sure, performance becomes a moral issue. but if there is no effect, then poor performance simply becomes a technical issue.
- kdmccormick 7y agoSure, but the entire article is about how experience is widely being affected by poor performance. I'm not sure what point you're trying to make outside of pedantics.
- kmlx 7y agopoor performance is not a pre-requisite of bad experience. in reality it's a combination of UI & UX that contributes the most to bad experiences. not poor performance. so don't focus on poor performance when there is no effect. and even when there is a marginal effect, UI & UX matter a lot more and could even negate the poor performance aspect. so my point: UI&UX > performance. almost every single time. all of this is based on various analysis i have done for a whole slew of clients dating back to 10 years ago.
- KaiserPro 7y agoI think positioning this as an ethics issue will not have the impact that I think it should. We should really be making the argument on a capitalistic basis. (stay with me here.) I was at the FT when we were re-designing the site. The page was lighter than the dailymail (but then most things are) but not as fast as skynews. (it loaded within a second with pictures on a slow desktop) The marketing team really wanted more tracking, and the advertisers also were insisting on inserting _another_ three tracking systems. So the developers (and product owners) pushed back. The writeup is here: https://medium.com/ft-product-technology/a-faster-ft-com-10e7c077dc1c https://medium.com/ft-product-technology/a-faster-ft-com-10e... There was a clear correlation between load time and dwell time. Which lead to the undeniable conclusion that tracking stuff cost the business more money than the extra info brought in. The take away from this is when ever you are making a case for business change, you have to argue that _your_ change will make the business better, using the metrics that the business understands. The skill is making your moral choice look and smell like a money making/target hitting opportunity.
- commandlinefan 7y agoThank God _somebody_ is talking about this instead of shutting down every suggestion of speeding things up with (their misunderstanding of) Knuth's famous "performance optimization is the root of all evil" quote.
- anilgulecha 7y agoThe cost numbers are suspect. The paper states: > Our major finding is that the Internet uses an average of about 5 kWh to support the utilization of every GB of data, which equates to about $0.51 of energy costs. Which I read as equating what's on storage -- A GB of data in a datacenter. Somehow the articles runs with this as a GB downloaded by a user, which is so bad, it's hilarious.
- waylandsmithers 7y agoI get it and I agree, but my assumption has always been that we're all trying to write the most efficient code anyway right? (Maybe with a few exceptions, like intentionally slowing down auth to prevent brute forcing passwords). But this article is saying that if I don't, I'm not just a bad programmer, I'm a bad _person_ too. Hm.
- tkadlec 7y agoHopefully that's not the way it comes off! The entire last section of the article is my attempt to make it clear that this _doesn't_ happen because we're bad people. > So clearly, folks who have built a heavy site are bad, unethical people, right? > Here’s the thing. I have never in my career met a single person who set out to make a site perform poorly. Not once. > People want to do good work. But a lot of folks are in situations where that’s very difficult. > The business models that support much of the content on the web don’t favor better performance. Nor does the culture of many organizations who end up prioritizing the next feature over improving things like performance or accessibility or security.
- jmull 7y agoIt seems weird to me to belabor this point. The arguments make sense, but these are little teacup arguments when we already have multiple barrel-sized arguments in favor of good performance. (I mean generally -- there could be specific situations with different dynamics -- but we're talking generally here.)
- chrisdone 7y agoI think that the lumbering hogs we call publication web sites these days are making sure that you as a reader are paying a cost to use their otherwise free web site; paying a subscription is better, but no one will do that. People on mobiles pay a tax that people on desktops don't, and people on bad connections in poor areas pay a tax that people in rich fibre-wonderlands don't, and yet energy and money is wasted on transferring garbage that nobody wants. I seem to get dismissed whenever I suggest this, but these web sites could instead try another approach: remove all the garbage, have a beautiful, clean web site, and implement artificial rate limiting on all connections to it. If you want a super fast experience, pay a subscription! What are the upsides? * Less bandwidth and energy and mobile phone battery is wasted. * The site will still load in the same time that people are normally used to anyway. * Rich people and poor people get the same experience; you don't pay a poor people tax if you are poor. Equity! * Mobile phone users don't pay a tax, either. * Meanwhile, Rich people have disposable income; they should be spending money on magazines and newspapers that people are producing anyway, to show their support, but they don't, so here's an incentive. They also indirectly support the poor people with news/media, who can't afford to pay a subscription (or wouldn't benefit anyway). Isn't anyone trying this model?
- leetcrew 7y agoif you make the website simple enough that it loads quickly on a bad connection and it loads the same content on a fast connection, why would anyone pay extra for it to be even faster?
- dodobirdlord 7y agoI think the idea suggested is that the website could load quickly but doesn't, instead artificially loading very slowly regardless of connection speed.
- deleted 7y ago[deleted]
- sooheon 7y agoFor this to be a tax someone has to collect--as it is, it's just a straight up degraded product to nobody's benefit. At least taxes get used for something.
- dangerface 7y ago> 17.6 million kWh of energy to use the web every single day. 17 million sounds like a lot but it's nothing. In Ireland there are 2,878 wind turbines producing 30% of our electric, 47 million kWh of energy every single day more than enough to power the worlds internet even if you use the larger numbers in this article. This "Wasted energy" is a non issue.
- wazoox 7y agoOr, for our specific purposes, why would I need an expensive device with higher-powered CPU if the sites and applications run well on a lower-powered device? Precisely that. We need more human work (optimizing code) and less brainless energy spending, i.e. more jobs and less consumption of non-renewable resources.
- NohatCoder 7y agoOverall a good article, but please note that the 5 kWh/GB figure is plain wrong. The source attributes all power consumption of all connected devices to data transfer, and it simply makes up the base figures. Actual marginal power cost of data transfer is probably around 1/1000 the cited figure. Still doesn't mean wasting data is a good idea.
- donohoe 7y agoThe state of web page performance is pretty bad and could be so much better. In 275 tests of 75 news articles the average page size was 3.6MB, made 345 requests, and took 46 seconds to load (on a ‘3G’ connection using WebPageTest.org) More info and date: https://webperf.xyz/ https://webperf.xyz/ Some publishers can load in seconds (with advertising etc) so there is little excuse. We know how to fix this.
- pradn 7y agoInvestopedia, the fastest site profiled at webperf.xyz, still places at least image 4 banner ads. So it's possible to support yourself with web advertising and still be fast.
- tempodox 7y agoPutting the words “Ethics” and “Web” in the same sentence would already make for a perfect April's fool joke but also adding “Performance” is really overdoing it. If I had what the author smoked for breakfast, I might actually die laughing.
- miki123211 7y agoPerformance is part of accessibility. I haven't realized this earlier, but now it's clear to me. I think accessibility is much more than what we believe it to be. It's about allowing as many people as possible to access our services. This, in my opinion, is a moral issue, and I think not doing that is just plain unethical. Making a website that's not WCAG compliant, i.e. doesn't work well for disabled people, one that is not available in specific countries or for specific age groups is bad, but making website that wastes resources is bad too. If you're doing one kind of accessibility because moral issues, you should be doing the other kinds too.