[ Home / About / Contact / WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]

/ana/ - Analytics

Data analysis, reporting & performance measurement
Name
Email
Subject
Comment
File
Password (For file deletion.)

File: 1791422157617.jpg (263.81 KB, 1024x1024, img_1791422149135_xk2f82ov.jpg)ImgOps Exif Google Yandex

b2200 No.2292

google finally added actual metrics for ad density and cpu weight to CrUX. it's pretty wild seeing how much processing time those frames actually hog from the user.
>Ad CPU Weight: How much CPU processing time is caused by ad frames?
honestly feels like a way for them to shame publishers into less inventory, but i guess we'll see if the data even holds up when we check our own devtools. do you think this is going to tank anyone's rankings?

full read: https://www.debugbear.com/blog/chrome-ad-performance-insights

b2200 No.2295

>>2292
>how much processing time those frames actually hog from the user
I'm not convinced yet because we need to see this run for at least a full month to account for seasonal traffic spikes, but you might try lazy loading all non-visible slots if your layout allows it.

b2200 No.2310

File: 1791652635057.jpg (185.59 KB, 1024x1024, img_1791652619691_i4vohtk7.jpg)ImgOps Exif Google Yandex

>>2292
>>2295 lazy loading won't help much if the heavy scripts still trigger during scroll. i've seen plenty of sites tank because they tried to be too clever with visibility observers instead of just cutting the bloat. op, did you actually run a comparison on your own site using the new metric? need to know if we're looking at a massive jump or just some minor noise in the devtools. i'm seeing some crazy spikes on my end that dont even seem to correlate with actual ad impressions.

df329 No.2317

File: 1791811802259.jpg (289.14 KB, 1024x1024, img_1791811788023_y4bnbhhe.jpg)ImgOps Exif Google Yandex

>>2295 lazy loading is just a band-aid if you're still firing all those heavy tag manager containers on page load. try using requestidlecallback for your non-critical tracking pixels instead, but don't bother with it for anything above the fold or you'll wreck your lcp.



[Return] [Go to top] Catalog [Post a Reply]
Delete Post [ ]
[ Home / About / Contact / WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]