Technical insights on web performance, automatic optimization, and the engineering behind ModPageSpeed 2.0 and mod_pagespeed 1.1.
40% of the top 1,000 sites serve almost nothing to AI crawlers that do not run JavaScript — ChatGPT, Perplexity, and Claude see an empty page. Here is the data, the method, and how to fix it.
Read post →mod_pagespeed 1.1.0 ships 765 first-parent merges since 1.13.35.2 — image-decoder hardening, a full sanitizer matrix, a current dependency graph, and the IIS port folded into the C++ tree.
Read post →ModPageSpeed 2.0 as ASP.NET Core middleware via NuGet. Same optimization pipeline — images, CSS, JS, critical CSS — integrated with two lines of C#. No nginx required.
Read post →Serve WebP and AVIF from ASP.NET Core with no controller changes. WeAmp.PageSpeed middleware does content negotiation, viewport sizing, and LCP preload.
Read post →How to fix INP on ASP.NET Core: Razor + jQuery responds well to bundling and the WeAmp.PageSpeed middleware; Blazor Server INP is architectural and needs WASM.
Read post →Google's dl-ssl.google.com URL historically served the 2020 mod_pagespeed .deb. Years later, it's a no-longer-maintained build. Here's where to get a maintained build.
Read post →Yes, mod_pagespeed is deprecated. The 1.13.35.2 binaries still run but have not received security updates in years. Here's what to use instead on Apache, nginx, IIS, and ASP.NET Core.
Read post →A working docker-compose.yml for ModPageSpeed 2.0 on nginx: worker + module + shared Cyclone cache volume. Verify with curl, apply a license, done.
Read post →Generate and inline critical CSS at the nginx layer for any backend (PHP, Rails, Django, ASP.NET, Go). No WordPress plugin. No headless browser.
Read post →How to fix CLS on ASP.NET Core: pre-size async view components, persist image dimensions, reserve banner space, rewrite img tags via middleware.
Read post →How to fix LCP on ASP.NET Core: async view components, cached static files, and the WeAmp.PageSpeed middleware. Practical steps for Razor Pages and MVC in 2026.
Read post →How to fix INP on nginx: a CMS-agnostic guide. Server-layer JS minification helps if your JS is bloated; if your stack is already lean, the wins are upstream.
Read post →How to fix CLS on nginx: rewrite img tags to add width/height, reserve container space, use aspect-ratio, ship dimensions at build time.
Read post →How to fix LCP on nginx: HTTP/2, gzip_static, TLS resumption, and the ModPageSpeed rewriter. Stack-agnostic LCP fixes that work behind any backend in 2026.
Read post →How to fix INP on Magento: the high-leverage fix is theme architecture (Hyvä), not a server-layer rewriter. What ModPageSpeed can do, and what it cannot.
Read post →How to fix CLS on Magento: tame Fotorama gallery jumps, pre-size mini-cart and private-content blocks, rewrite img dimensions at the server layer.
Read post →How to fix LCP on Magento: tame the RequireJS waterfall, regenerate catalog images, inline critical CSS at the server. Step-by-step for Magento 2 in 2026.
Read post →How to fix INP on WooCommerce: server-layer JS minification reduces the parse cost, but cart and variation handlers are architectural. The plan inside.
Read post →How to fix CLS on WooCommerce: stop the gallery shift, lock variation swap dimensions, reserve cross-sell space, and rewrite img tags at the server.
Read post →How to fix LCP on WooCommerce: shrink the product gallery, kill cart-fragments on non-shop pages, and rewrite images at the server. Practical steps for 2026.
Read post →How to fix INP on WordPress: diagnose the responsible interaction, defer non-critical JS at the server layer, then trim plugin handlers and jQuery.
Read post →How to fix CLS on WordPress: diagnose the shifts, set width/height on every image at the server layer, lock down fonts, reserve banner space.
Read post →How to fix LCP on WordPress: diagnose the hero, inline critical CSS at the server, convert JPEG to WebP, and verify in Search Console. Step-by-step, 2026.
Read post →Google mod_pagespeed and ngx_pagespeed are no longer actively developed. Two actively developed successors exist — here is how to choose.
Read post →Step-by-step guide for migrating from mod_pagespeed 1.x or ngx_pagespeed to ModPageSpeed 2.0. Configuration mapping, Docker Compose setup, and verification checklist.
Read post →Extract critical CSS without Puppeteer, Penthouse, or headless Chrome. ModPageSpeed uses heuristics in under 5ms per page — no Node.js required.
Read post →Cost model for image optimization at 100K to 10M monthly requests. CDN pricing scales linearly; self-hosted is flat. Break-even sits around 300K requests/month.
Read post →How ModPageSpeed 2.0 respects the Save-Data HTTP header to serve lighter image variants. Typical 30-50% additional bandwidth reduction on top of format and viewport optimization.
Read post →ModPageSpeed 2.0 benchmarks across e-commerce, blog, news, and portfolio sites. Real LCP, FCP, and Lighthouse improvements on 3G, 4G, and broadband — methodology included.
Read post →Serve images in modern formats on nginx automatically. ModPageSpeed 2.0 transcodes to WebP and AVIF in one decode pass — up to 37 variants per image.
Read post →The story behind ModPageSpeed 2.0 — why mod_pagespeed is no longer actively developed, what was kept from PSOL, and how a new architecture replaced the RewriteDriver.
Read post →