16 September 2026
Network roundup — across the board: — @HookConfessions — Real stories of scripts that flopped and hooks that exploded — the… — @CacheCatch — The best caching reads, tools, and configs from around the web,… — @SmartlinkOp…
@CoreVitals101
15 September 2026
Find Which Element Is Your LCP LCP — Largest Contentful Paint — is the moment your biggest visible thing (usually a banner image or headline) finishes loading. Before you can speed it up, you need to know exactly which e…
@CoreVitals101
14 September 2026
The filmstrip vs the LCP number The LCP number tells you 'biggest element loaded at 3.2 seconds'. The filmstrip (a row of screenshots over time, in WebPageTest or DevTools) shows you what the visitor actually saw at each…
@CoreVitals101
13 September 2026
Inlining critical CSS vs deferring the rest CSS in your page head is render-blocking: the browser won't paint until it loads, which delays FCP and LCP. Two tactics tame this. Inlining critical CSS puts the few styles for…
@CoreVitals101
12 September 2026
Image CDN vs resizing images by hand Both shrink oversized images that bloat LCP (Largest Contentful Paint). Resizing by hand means you export each image at the right size yourself. An image CDN (a service that resizes o…
@CoreVitals101
11 September 2026
A CDN vs caching: which fixes slow TTFB? When your server is slow to answer, TTFB (Time To First Byte — the wait before anything arrives) climbs, and that drags LCP with it. Two tools help, differently. A CDN (Content De…
@CoreVitals101
10 September 2026
PageSpeed Insights vs Search Console for vitals Both pull from the same real-visitor data (CrUX), but serve different purposes. PageSpeed Insights checks one URL deeply. The Core Web Vitals report in Search Console group…
@CoreVitals101
09 September 2026
TBT in the lab vs INP in the field These two measure the same kind of problem, your page being busy and unresponsive, but from different seats. TBT (Total Blocking Time) is a lab number from one test run. INP (Interactio…
@CoreVitals101
08 September 2026
Why tools show the 75th percentile, not the average When you read a Core Web Vitals score, it's the 75th percentile (the value 75% of visits stay under), not the average. Averages hide pain: a few super-fast loads can ma…
@CoreVitals101
07 September 2026
Which network throttle should you test on? Throttling fakes a slower connection so you see what real visitors feel. DevTools offers 'Fast 4G', 'Slow 4G', and custom. Picking too fast hides problems; too slow scares you f…
@CoreVitals101
06 September 2026
Crossover rec A bit outside our lane, but if you run Programmatic / DSP too, @BidstreamLab is the one to follow. Deep dives into programmatic and DSP mechanics: auction dynamics, bid-shading,……
@CoreVitals101
05 September 2026
Debugging INP: which tool catches the lag? INP (Interaction to Next Paint) measures the delay between a tap and the screen responding. Two tools help, but at different moments. The web-vitals JavaScript library logs the …
@CoreVitals101
04 September 2026
Self-hosting fonts vs loading from Google Both give you nice type, but the loading path differs. Google Fonts adds a hop to another server first. Self-hosting means the font lives on your own domain, so the browser fetch…
@CoreVitals101
03 September 2026
defer vs async on your scripts Both keep a script from blocking your page, which protects FCP and LCP (how fast text and images appear). The difference is timing. async runs each script the instant it arrives, in any ord…
@CoreVitals101
02 September 2026
Preload vs preconnect: two early hints Both are <link> tags that warm things up before the browser asks. But they do different jobs. Preconnect opens an early handshake with another server (like a font host). Prelo…
@CoreVitals101
01 September 2026
Lazy loading vs priority hints: opposite tools These two settings pull in opposite directions, and that's the point. loading="lazy" tells the browser to wait on an image until it's almost on screen. A priority hint (fetc…
@CoreVitals101
31 August 2026
WebP vs AVIF: which image format to ship Both shrink images well and both help LCP (Largest Contentful Paint — when the biggest thing on screen finishes loading). AVIF squeezes a bit smaller, often 20-30% under WebP. But…
@CoreVitals101
30 August 2026
Finding bloat: Coverage tab vs Lighthouse treemap Both tools tell you which code is too heavy, but in different shapes. The Coverage tab (in Chrome DevTools) shows what percent of each file went unused on this page. Ligh…
@CoreVitals101
29 August 2026
CrUX vs your own speed tracking (RUM) CrUX (Chrome User Experience Report) is Google's free field data, but it only counts Chrome users, updates monthly, and rolls 28 days together. RUM (Real User Monitoring — a script y…
@CoreVitals101
28 August 2026
CrUX dashboard vs checking pages one by one CrUX (Chrome User Experience Report) is Google's database of real-visitor speed. You can read it one page at a time in PageSpeed Insights, or see your whole site at once. Check…
@CoreVitals101
27 August 2026
A few channels in the SEO & search space worth your feed: — @LinkEquityHeat — Strong, unfiltered opinions on internal linking — why your 'related… — @SitemapSOP — Repeatable checklists and standard procedures for XML sit…
@CoreVitals101
26 August 2026
Field data vs lab data: which one decides? Lab data comes from a single test on a borrowed machine. Field data is real visits from real people over the last 28 days. Think of lab data like rehearsing a song alone, and fi…
@CoreVitals101
25 August 2026
The mistake: assuming a fix worked The last trap is the trickiest: you make a change, the lab score in Lighthouse jumps to green, and you celebrate. But field data — real-visitor numbers — updates slowly, over a rolling …
@CoreVitals101
24 August 2026
The mistake: stacking up redirects Over the years a URL might redirect from http to https, then to www, then to a new path — a chain of hops. Each hop is a round trip before the real page even starts loading. That delays…
@CoreVitals101
23 August 2026
The mistake: letting the browser guess priorities By default, the browser guesses which resources matter most — and it often guesses wrong, treating a tiny footer icon the same as your main hero image. That confusion can…
@CoreVitals101
22 August 2026
The mistake: a heavy autoplay video up top A big background video at the top of the page looks impressive, but it can wreck both LCP and load time. The browser fights to download that heavy file early, delaying the text …
@CoreVitals101
21 August 2026
The mistake: pasting one huge CSS file Many sites load one enormous stylesheet covering the entire website on every single page. The browser must download and read all of it before showing anything — that's a render-bloc…
@CoreVitals101
20 August 2026
The mistake: sending uncompressed files An easy-to-miss issue: your HTML, CSS, and JavaScript travel to visitors uncompressed. Text files squeeze down beautifully — often 70 percent smaller — but only if your server turn…
@CoreVitals101
19 August 2026
The mistake: a page with too many elements Sometimes a page is slow to respond not because of one big script, but because it has thousands of HTML elements. Every interaction makes the browser re-check that huge structur…
@CoreVitals101
18 August 2026
The mistake: checking desktop, ignoring mobile A quiet trap: you test on your fast laptop and everything looks great. But Google primarily uses the mobile experience for Core Web Vitals, and most field data comes from ph…
@CoreVitals101
