--- title: "#pagespeed articles | Hashnode" description: "Explore 67 articles tagged #pagespeed on Hashnode. Tutorials, guides, and how-tos from the community." url: "https://hashnode.com/tag/pagespeed" --- Tag # #pagespeed 67 posts · 3 followers [Apogee Watcher](https://hashnode.com/@apogeewatcher) · [7h ago](https://hashnode.com/posts/partial-page-loads-crux-what-field-data-quietly-drops/6af81f5389b3ba1d6b73e8a1) ### [Partial page loads and CrUX: what field data quietly drops](https://devlog.apogeewatcher.com/partial-page-loads-crux-what-field-data-quietly-drops?utm_source=hashnode&utm_medium=feed) Chrome UX Report percentiles are not a slower Lighthouse run. Incomplete visits, background starts, and navigation types quietly reshape what agencies can claim after a green lab score. 7 min read · [devlog.apogeewatcher.com](https://devlog.apogeewatcher.com/partial-page-loads-crux-what-field-data-quietly-drops?utm_source=hashnode&utm_medium=feed) [2](https://hashnode.com/posts/partial-page-loads-crux-what-field-data-quietly-drops/6af81f5389b3ba1d6b73e8a1) [Apogee Watcher](https://hashnode.com/@apogeewatcher) · [3d ago](https://hashnode.com/posts/wordpress-speculation-rules-when-prerender-makes-lcp-worse/6af3fd7941f3d234483ad042) ### [WordPress Speculation Rules: When Prerender Makes LCP Worse](https://devlog.apogeewatcher.com/wordpress-speculation-rules-when-prerender-makes-lcp-worse?utm_source=hashnode&utm_medium=feed) Core 6.8 and Speculative Loading can make the next click feel instant. Here is why the page you are already on can get slower, and how to measure before you roll settings back. 8 min read · [devlog.apogeewatcher.com](https://devlog.apogeewatcher.com/wordpress-speculation-rules-when-prerender-makes-lcp-worse?utm_source=hashnode&utm_medium=feed) [1](https://hashnode.com/posts/wordpress-speculation-rules-when-prerender-makes-lcp-worse/6af3fd7941f3d234483ad042) [Apogee Watcher](https://hashnode.com/@apogeewatcher) · [5d ago](https://hashnode.com/posts/lighthouse-used-to-punish-useful-preloads-framer-spent-a-year-fixing-that/6af15a6b27166d7fca35586e) ### [Lighthouse used to punish useful preloads. Framer spent a year fixing that.](https://devlog.apogeewatcher.com/lighthouse-used-to-punish-useful-preloads-framer-spent-a-year-fixing-that?utm_source=hashnode&utm_medium=feed) Lantern treated high-priority modulepreloads and fonts as if they blocked paint. Lighthouse 13.6 reads Chrome’s render-blocking signal instead. Here is what agencies should stop undoing. 9 min read · [devlog.apogeewatcher.com](https://devlog.apogeewatcher.com/lighthouse-used-to-punish-useful-preloads-framer-spent-a-year-fixing-that?utm_source=hashnode&utm_medium=feed) [Apogee Watcher](https://hashnode.com/@apogeewatcher) · [Nov 6](https://hashnode.com/posts/google-remove-crux-pagespeed-insights-api-how-to-prepare/6aed660b904bff15ffb2cc37) ### [Google to remove CrUX from PageSpeed Insights API; How to prepare](https://devlog.apogeewatcher.com/google-remove-crux-pagespeed-insights-api-how-to-prepare?utm_source=hashnode&utm_medium=feed) Google plans to stop returning CrUX field data from the PageSpeed Insights API. Lab Lighthouse results stay. Here is what to change in your integration before the keys go empty. 8 min read · [devlog.apogeewatcher.com](https://devlog.apogeewatcher.com/google-remove-crux-pagespeed-insights-api-how-to-prepare?utm_source=hashnode&utm_medium=feed) [Apogee Watcher](https://hashnode.com/@apogeewatcher) · [Nov 4](https://hashnode.com/posts/why-pagespeed-insights-jumped-overnight-lighthouse-13-6/6aeafb305ac11928f6281ae6) ### [Why did PageSpeed Insights jump overnight? (Lighthouse 13.6, site unchanged)](https://devlog.apogeewatcher.com/why-pagespeed-insights-jumped-overnight-lighthouse-13-6?utm_source=hashnode&utm_medium=feed) Lighthouse 13.6 changed how PageSpeed Insights simulates FCP and LCP. A higher lab Performance score can appear when the HTML did not move. Here is a short check. 6 min read · [devlog.apogeewatcher.com](https://devlog.apogeewatcher.com/why-pagespeed-insights-jumped-overnight-lighthouse-13-6?utm_source=hashnode&utm_medium=feed) [Apogee Watcher](https://hashnode.com/@apogeewatcher) · [Nov 2](https://hashnode.com/posts/why-does-crux-say-no-data-for-my-client-site/6ae8fc13dc52ada64aa57444) ### [Why does CrUX say no data for my client site?](https://devlog.apogeewatcher.com/why-does-crux-say-no-data-for-my-client-site?utm_source=hashnode&utm_medium=feed) A blank field block on PageSpeed Insights is usually eligibility, not a broken lab run. The useful debug path comes before the client email. 7 min read · [devlog.apogeewatcher.com](https://devlog.apogeewatcher.com/why-does-crux-say-no-data-for-my-client-site?utm_source=hashnode&utm_medium=feed) [Apogee Watcher](https://hashnode.com/@apogeewatcher) · [Oct 30](https://hashnode.com/posts/launch-checklist-vs-retainer-checklist-ai-built-websites/6ae454928c461181e13d7d1e) ### [Launch checklist vs retainer checklist for AI-built websites](https://devlog.apogeewatcher.com/launch-checklist-vs-retainer-checklist-ai-built-websites?utm_source=hashnode&utm_medium=feed) One afternoon of QA gets the padlock live. A weekly lab and CrUX loop is what keeps Core Web Vitals honest after the next prompt. 7 min read · [devlog.apogeewatcher.com](https://devlog.apogeewatcher.com/launch-checklist-vs-retainer-checklist-ai-built-websites?utm_source=hashnode&utm_medium=feed) [4](https://hashnode.com/posts/launch-checklist-vs-retainer-checklist-ai-built-websites/6ae454928c461181e13d7d1e) [Apogee Watcher](https://hashnode.com/@apogeewatcher) · [Oct 28](https://hashnode.com/posts/agency-to-product-pagespeed-monitoring/6ae1bcc382d85f90e46a2ff1) ### [We Sold PageSpeed Retainers for Years. Here Is Why We Productised Monitoring Instead of Another Audit PDF](https://devlog.apogeewatcher.com/agency-to-product-pagespeed-monitoring?utm_source=hashnode&utm_medium=feed) Productise the calendar, not the PDF: how we turned a PageSpeed retainer continuity problem into multi-tenant monitoring. 10 min read · [devlog.apogeewatcher.com](https://devlog.apogeewatcher.com/agency-to-product-pagespeed-monitoring?utm_source=hashnode&utm_medium=feed) [Apogee Watcher](https://hashnode.com/@apogeewatcher) · [Oct 28](https://hashnode.com/posts/ai-built-sites-core-web-vitals-regressions-after-the-padlock/6ae1bb42e9eeb5870f1cdfa6) ### [AI-built sites: the Core Web Vitals regressions that show up after the padlock](https://devlog.apogeewatcher.com/ai-built-sites-core-web-vitals-regressions-after-the-padlock?utm_source=hashnode&utm_medium=feed) HTTPS and a green launch check are not a monitoring plan. Hero swaps, chat widgets, cookie banners, and redesign prompts are how AI-built sites get slow after go-live. 7 min read · [devlog.apogeewatcher.com](https://devlog.apogeewatcher.com/ai-built-sites-core-web-vitals-regressions-after-the-padlock?utm_source=hashnode&utm_medium=feed) [Apogee Watcher](https://hashnode.com/@apogeewatcher) · [Oct 26](https://hashnode.com/posts/is-pagespeed-insights-reliable/6adf1048566f74eca2f1803a) ### [Is PageSpeed Insights Reliable?](https://devlog.apogeewatcher.com/is-pagespeed-insights-reliable?utm_source=hashnode&utm_medium=feed) Yes for diagnostics and CrUX when samples exist. No as a once-a-week screenshot that proves every client site is fine. Here is how agencies keep the two clocks honest. 6 min read · [devlog.apogeewatcher.com](https://devlog.apogeewatcher.com/is-pagespeed-insights-reliable?utm_source=hashnode&utm_medium=feed)