Tessera
Folgen

Dave Smart

@tamethebots.com

(semi) professional goth. Full-time idiot with a computer. Tech SEO & Dev at tamethebots.com #Webdev #TechSEO

853 Posts951 Follower297 Folgt
Dave Smart@tamethebots.com · 2w ago

I heard again the other day about the 5 second render timeout limit in Google's web rendering service. It's not real, but because of how the WRS works, it's understandable where that figure comes from. I did a test case and wrote it up here: tamethebots.com/blog-n-bits/...

There's no 5 second render limit in Google, but I can see why you might think there is.

A fairly common belief is that Google stop rendering pages after 5 seconds, I did some testing to show that's not true, but why your measurements might be lying to you to make you think so, because time in the web rendering service is artificial.

tamethebots.com

John Mueller@johnmu.com · last mo.

A properly made website works well for AI agents ... and search engines, and LLMs, and above all, for actual people. If you're trying to fix accessibility issues by making a separate "agent-friendly" version, you are just building technical debt. You'll have to redo it multiple times. Just fix it.

Stef Walter@stephaniewalter.bsky.social · last mo.

Sad truth: we are making the web accessible for AIs, not for people. Some sites now offer a text version for LLMs, but still skip real accessibility needs like proper heading structure, landmarks that screen reader users need.

Dave Smart@tamethebots.com · last mo.

This is very cool. For those without the time to setup the demo example, I put a version here if you want to see it in action: testing.tamethebots.com/nativestream

Streaming Photo Gallery

testing.tamethebots.com

Barry Pollard@tunetheweb.com · last mo.

The first part of Declarative Partial Updates (`<template for>` out-of-order HTML) is now available, unflagged, in Chrome 150!! developer.chrome.com/release-note... The second part (the new JS setting APIs, include the streaming ones) we're still working on the spec side, but maybe for Chrome 152?

Rowan Merewood@rowan.fyi · last mo.

A while back quite a few of you answered me on your annoyances with web payments. I've collated your responses and it looks like we're still doing forms like it's 1999 out there. More detail in the article, and let me know if there's more of your e-concerns with e-commerce rowan.fyi/posts/web-pa...

Form & autofill failures: 57% Digital wallets & local payment methods: 30% Trust, privacy, and dark patterns: 30% Flaky services: 23% Too many steps: 13%
Barry Pollard@tunetheweb.com · 2mo ago

The Chrome DevTools team are doing a "papercuts" sprint where they try to address lots of small, irritating bugs and annoyances. Reply with crbug.com links (no bug, no fix—that's the deal!) and will see what we can do. No promises though as some may be features/too big/unclear how to solve.

Chromium

crbug.com