Google Is Not God of The Web
Tags: webdev, ux
Published: 2020-11-06 17:13:22

Almost exactly two years ago, [I warned that Google was on track to replace God](https://bilge.world/google-soul-ledger-dont-be-evil) of us all. Last month, *The Verge*'s Dieter Bohn reported that [Google plans to begin accounting for "page experience" in its search rankings](https://www.theverge.com/2020/5/28/21272543/google-search-results-page-experience-load-time-contentfu-paint-layout-shift-top-stories-amp) beginning in 2021, later explaining in a [subsequent episode of *The Vergecast*](https://www.theverge.com/21274502/vergecast-podcast-407-trump-executive-order-social-media-hbo-max-launch): 

> Here is another example of the Chrome team coming up with a bunch of web standards and then the Search team making a bunch of incentives based on those standards.

It was news to me that in May, Google [launched](https://blog.chromium.org/2020/05/introducing-web-vitals-essential-metrics.html) a page called "Web Vitals" on its [**web.dev**](https://web.dev/vitals/) domain (which they've [apparently owned since November 2018](http://web.archive.org/web/20180415000000*/web.dev).) The company measures "page experience" based on three main criteria:

> - [**Largest Contentful Paint**](https://web.dev/lcp/) measures perceived load speed and marks the point in the page load timeline when the page's main content has likely loaded.
> - [**First Input Delay**](https://web.dev/fid/) measures responsiveness and quantifies the experience users feel when trying to first interact with the page.
> - [**Cumulative Layout Shift**](https://web.dev/cls/) measures visual stability and quantifies the amount of unexpected layout shift of visible page content.

[CoStar](https://www.costarastrology.com/neoyokel) just sent an oddly topical (and honestly, encouraging) notification:

![Costar Notification](https://i.snap.as/1Lo8JrN.jpeg)

I'm not a "real" web developer - nor do I mean to dictate to a single one - but I know enough theory to note that of this "core web" education operation centered around web.dev is operating on some irritating assumptions:

### 1. Smaller assets are ideal.

The simple assumption that it is always better to have the smallest page possible - that images should be resized and compressed to hell and typography/other elements should be few in number. Instantaneous page loads should be priority over any other standards of measure for a web page - like interesting design, for instance.

### 2. Minimalistic design is necessary.

The reality - for most of the Western world, at least - is that [average network speeds are exponentially increasing](https://www.forbes.com/sites/kevinmurnane/2018/12/11/heres-how-internet-speeds-fared-for-the-worlds-fastest-and-largest-countries-in-2018/#3f3124664976) year-by-year. In 2018:

> World-wide average mobile download speed was 22.82 Mbps (Megabits per second), an increase of 15.2% over 2017. Average upload speed was 9.19 Mbps, an increase of 11.6%. Fixed broadband speeds also increased. Average download speed increased 26.4% to 46.12 Mbps, while average upload speed came in at 22.44 Mbps, a 26.5% increase.

I may be a yokel, but these averages are still absolutely *inconceivable* to me. Our phones have as much RAM as my "studio" work desktop, now. 22.82 Mbps will reliably download *very* complex web pages nearly instantaneously. There is a very reasonable argument for essential services like search engines and news websites to conform to/adopt standards like AMP, but for the rest of The Open Web, ingenuity and risktaking should be *encouraged*, not discouraged, for the true good of all Peoplekind.

A term I haven't seen for a good while describes this ideology: "the **mobile web**," and it completely sucking ass is not a new concept. I've before referenced [an old complaint](https://www.theverge.com/2015/7/20/9002721/the-mobile-web-sucks) from 2015 by *The Verge*'s Editor-in-Chief, Nilay Patel (which the original article also links in different context in its last line):

> The entire point of the web was to democratize and simplify publishing using standards that anyone could build on, and it has been a raging, massively disruptive success for decades now. But the iPhone's depressing combination of [dominant mobile web marketshare](https://www.netmarketshare.com/browser-market-share.aspx?qprid=0&qpcustomd=1) and shitbox performance means we're all sort of ready to throw that progress away.

### 3. Google has the right to dictate "Best Practices."

The Mobile Web as a utility has its place, but it's certainly not a necessary or desirable ideal for the entirety of The Web, yet Google has the audacity to presume it can dictate what is and is not optimal web design. The URL in and of itself is extremely presumptuous - Google technically has every right to own web.dev, sure, but *should* it? The Accelerated Mobile Pages (AMP) program has already had an annoying effect on day-to-day browsing. I despise AMP links more than most things in life, just as I despise the name of the website *Search Engine Land* (which sounds like actual hell) who [also reported on this](https://searchengineland.com/the-google-page-experience-update-user-experience-to-become-a-google-ranking-factor-335252):

> If you have AMP, the good news is that the majority of AMP pages do extremely well in terms of page experience metrics, [Google Project Manager] Rudy Galfi said. It doesn’t mean that all AMP pages will have top page experience metrics, but AMP is built in a way to help with this.

Recently, I discovered an incredibly refreshing/affirming essay wrapped in a hand-build web experience called "[Rediscovering the Small Web](https://neustadt.fr/essays/the-small-web/)" by designer [Parimal Satyal](https://twitter.com/parimalsatyal), arguing for a different variety of Web presence:

> Modern web design principles are very rarely directed at regular people looking to make a website on something they are interested in. Instead, the focus is on creating websites that perform well:
> *Don't use too many colours. Write short, catchy headlines. Don't let content be too long. Optimise for SEO. Produce video content, attention span is decreasing. Have a an obvious call to action. Push your newsletter. Keep important information above the fold. Don't make users think. Follow conventions.*

I realize that the majority of Web utilization cannot "revert" to hand-coded plain HTML web pages hosted on Neocities, but there's something to be learned (or remembered, in my case) from Satyal's argument: **The Web's forgotten strength is <u>diversity</u>** (much like my country's, it would seem,) and the majority of users are being pushed by Google's search engine toward a very specific minority of URLs. We have not been *exploring* for a very long time:

> Instead of browsing, the web is for many an endless and often overwhelming stream of content and commentary picked out by algorithms based on what they think you already like and will engage with. It's the opposite of exploration.

"It is worth remembering a website does not have to be a product; it can also be art," argues Satyal. "The web is also a creative and cultural space that **need not confine itself to the conventions defined by commercial product design and marketing**." (Emphasis mine.) It's not just that The Web was *meant* to be more - nostalgia is definitely not my particular trip, if you didn't know - it's that it *can* be so much more. My [list of favorite Open Web projects](https://bilge.world/open) contains just a few examples of what I mean.

It's possible I am being *too* critical of Google. A [Twitter search](https://twitter.com/search?q=%22https%3A%2F%2Fwww.theverge.com%2F2020%2F5%2F28%2F21272543%2Fgoogle-search-results-page-experience-load-time-contentfu-paint-layout-shift-top-stories-amp%22&f=live) for the link to *The Verge*'s article reveals commentary like "[Experience, matters ;)](https://twitter.com/carlosriverao/status/1266051773472608257)," "[Web search moving forward](https://twitter.com/markupgrade/status/1266492831218139137)," and "[Halleluja!](https://twitter.com/reDDakteur/status/1266078587767177219)," so there are clearly users who are more than onboard, and not all of what Google has done for the web recently has been detrimental. It was also announced last month that [Chrome will begin blocking "resource-heavy" advertisements](https://blog.chromium.org/2020/05/resource-heavy-ads-in-chrome.html) by default and that [Google and Microsoft have been working together to improve spellcheck and scrolling in Chromium](https://www.theverge.com/2020/5/28/21273934/microsoft-google-chrome-edge-chromium-spellcheck-improvements). There's not much to feel about these announcements, but - as always - there is a whole lot to feel about Google as a company.

Google has [announced](https://dev.to/chromiumdev/announcing-web-dev-live-a-three-day-digital-event-2640) a three-day live digital event at the end of this month (June 30th-July 2nd) in which viewers will "celebrate our community's actions, learn modern web techniques and connect with each other." "Over three days, we'll share quick tips on aspects of modern web development," explains the company on its [web.dev/live page](https://web.dev/live/). I am planning to attend and bitch as much as I am allowed. [Stay tuned](https://bilge.world/subscribe) to hear a chronicle.