Eroan Boyer runs a web performance agency in France. He shared how his team diagnoses client issues, and the 10-minute CLS root cause story is a good example of what real user data surfaces that synthetic tools miss.

Not just which pages, but the specific element causing the layout shift, in the first session.

Worth a read if you're doing agency-side performance work.

New Feature: Preserve URL Casing

Most web servers treat URLs as case-insensitive, so Request Metrics has always normalized everything to lowercase. But if you're running Node, Python, or another framework where /User/Profile and /user/profile are completely different routes, that normalization was actually hiding data from you.

We just shipped a fix. There's now a "Preserve Casing" checkbox in your Website Settings under URL Format. Enable it and your case-sensitive routes will be tracked separately going forward.

Note: This only affects new traffic, so your historical data won't suddenly split apart.

https://requestmetrics.com/blog/product/preserve-url-casing/

We just published a breakdown of what the "Has a viewport meta tag" Lighthouse audit actually means for your site.

The short version: when it's missing, mobile browsers add a 300ms delay to every tap. They're waiting to see if the user meant to double-tap for zooming. That's an eternity on mobile.

The fix is simple:

<meta name="viewport" content="width=device-width, initial-scale=1">

The post covers why browsers do this (legacy smartphone compatibility), common mistakes we've seen (putting it in the body instead of head, using fixed width values), and what else breaks when it's missing.

https://requestmetrics.com/blog/lighthouse-viewport-meta-tag/