Tessera
Folgen

Dave Smart

@tamethebots.com

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

874 Posts965 Follower298 Folgt
Dave Smart@tamethebots.com · 3w ago

This is a really cool addition! I have added these new metrics to my free CWV tool here: tamethebots.com/tools/cwv-hi...

Visualise Data from the Chrome UX Report History API

See charts from the Chrome UX Report History API

tamethebots.com

Barry Pollard@tunetheweb.com · 3w ago

We just launched experimental ad metrics in the Chrome User Experience Report (CrUX): - Ad Count - Ad Density - Ad Weight: Network - Ad Weight: CPU These metrics are a set of ad-related measurements that provide transparency into sites' ad experiences. developer.chrome.com/blog/crux-ad... 1/8 🧵

Joan León@nucliweb.net · 2mo ago

In my audits, the question I hear most after a deploy is "why hasn't CrUX moved yet?" The window is always 28 days; daily, weekly and monthly are just cadences over the same data. And p75 resists change by design I explain it with two interactive demos joanleon.dev/en/crux-28-d... #WebPerf #CrUX

The CrUX 28-day rolling window | Joan León

How the CrUX 28-day rolling window actually works, what each source publishes, and why p75 takes so long to move even though the data is only two days old.

joanleon.dev

Myriam Jessier@myriam.dopamine.builders · 2mo ago

Swipe through 3 places prompt injection already sits inside your GEO funnel. None of them require a breach...There are even more. Full breakdown and the checklist in the article. Link landing in comments.

Slide 1 of 5, titled "Your help center." Explains that hidden instructions in support pages can make an AI summarizer surface a fake account alert and a malicious QR code inside a chat window, with no blocklist stopping it. Source credited to Permiso's ChatGPhish research.Slide 2 of 5, titled "The comparison content you don't control." Explains that a competitor's comparison article can hide a paragraph that reads as normal prose to a person but as a command to an AI browsing agent. Source credited to Promptfoo.Slide 3 of 5, titled "Your podcast, video, and voice content (multimodal GEO)." Explains that instructions can hide in images and in audio at frequencies people can't hear, and that a voice's tone alone can bypass AI safety filters with no code. Sources credited to i10X and StyleBreak research.Slide 4 of 5, titled "Your customer support agent." Explains that an AI agent holding both an untrusted input and a privileged tool can be manipulated through that input, referencing the June 2026 hijacking of Instagram accounts through Meta's AI assistant. Source credited to TechCrunch.
Dave Smart@tamethebots.com · 2mo 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 · 3mo ago

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 · 3mo ago

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.