IISpeed has a new home — and your license comes with you
IISpeed's PageSpeed optimization for IIS is continuing under a new name: mod_pagespeed 1.1. It uses the same PageSpeed Automatic library, now maintained as part of a broader release. Your existing license transfers at no cost — nothing to repurchase, nothing to lose.
What this means for you
- 1. Your license transfers at no cost. Existing IISpeed licenses are valid for mod_pagespeed 1.1 (IIS port). No repurchase needed.
- 2. Same PageSpeed Automatic library. mod_pagespeed 1.1 uses the same PageSpeed Automatic library you already rely on, with continued updates.
- 3. No hard cutoff. IISpeed continues to work — there's no forced cutoff — but new features, bug fixes, and security patches land in 1.1 going forward.
- 4. Path to 2.0. When you're ready, ModPageSpeed 2.0 is a ground-up rewrite — same philosophy, modern C++23 codebase.
PageSpeed for IIS in 2026
Core Web Vitals optimization for IIS and ASP.NET shops
Most Core Web Vitals advice for .NET shops stops at "enable compression and ship a CDN." That moves the needle, but it leaves the work that actually shifts Largest Contentful Paint and Cumulative Layout Shift — image optimization, critical CSS, lazy loading, content negotiation — to a build step that classic ASP.NET, WebForms, and SharePoint sites rarely have. IISpeed was built to do that work at the server, transparent to the application. That library is now maintained as mod_pagespeed 1.1 for IIS and, for ASP.NET Core, as the WeAmp.PageSpeed.AspNetCore NuGet middleware.
Classic IIS, ASP.NET, WebForms, SharePoint
mod_pagespeed 1.1 ships a native IIS module — the direct continuation of the IISpeed codebase. Install it on Windows Server, point IIS at it, and the module rewrites responses as they leave the worker process. No application changes; no rebuilds; no CDN tier required.
mod_pagespeed 1.1 for IISASP.NET Core (.NET 8 / .NET 9)
WeAmp.PageSpeed.AspNetCore
wraps the same PageSpeed Automatic library, packaged as ASP.NET Core middleware
(Preview). One app.UsePageSpeed()
call in Program.cs
— no separate web server, no IIS dependency. Runs equally well behind
Kestrel, in containers, or on IIS as a reverse proxy.
What mod_pagespeed 1.1 does on an IIS site
Four categories of work, all applied at response time without modifying the underlying application:
-
Image optimization
JPEG and PNG recompression, WebP and AVIF variants served via content negotiation, automatic resizing to rendered dimensions. The image work alone often moves Largest Contentful Paint by seconds on image-heavy classic ASP.NET pages.
-
Critical CSS
Above-the-fold CSS is extracted and inlined; the rest is deferred. First paint stops blocking on a CSS round trip — a measurable LCP improvement on the slow Windows-shared-hosting tail.
-
Lazy loading and deferred JavaScript
Off-screen images and iframes load on demand; non-critical JavaScript moves to the end of the document. Cumulative Layout Shift and Interaction to Next Paint improve in step.
-
Content negotiation and cache
One source asset produces multiple variants (WebP/AVIF, mobile-resized, recompressed) keyed off Accept and Viewport headers. The optimized variants are cached server-side; downstream CDNs see ordinary HTTP responses.
Want the full checklist?
We wrote up the IIS Core Web Vitals workflow — what to measure, which filters move which metric, and the migration path from classic ASP.NET to ASP.NET Core middleware — as a separate article.
Read the IIS Core Web Vitals 2026 guideGet a license
New to PageSpeed optimization on IIS? Here are your options.
mod_pagespeed 1.1 — IIS
The direct successor to IISpeed. Native IIS module with the same PageSpeed Automatic library, actively maintained. The right choice if you run IIS natively on Windows Server.
Download at modpagespeed.comModPageSpeed 2.0
Ground-up rewrite in modern C++23. Supports nginx today via a Docker reverse proxy or bare-metal module. For .NET environments, the same optimization technology ships as native ASP.NET Core middleware (Preview).
See what's in 2.0Already have an IISpeed license? Contact us to transfer it to mod_pagespeed 1.1 at no cost. Customers of the legacy mod_pagespeed open-source builds can also read our open-source transition note.
Prefer to move to ModPageSpeed 2.0 instead? Claim your free ModPageSpeed 2.0 license — also at no cost.
Frequently asked questions
Do I need to buy a new license?
No. Your existing IISpeed license transfers to mod_pagespeed 1.1 at no cost. Email info@we-amp.com with your license key and we'll send your new license — license transfers are handled manually, usually within a business day or two.
Will my IISpeed configuration still work?
mod_pagespeed 1.1 uses the same configuration directives. Most configurations will work with minimal changes. The documentation covers any differences.
When will IISpeed stop receiving updates?
There is no hard cutoff date. IISpeed continues to work, but new features and security patches are developed for mod_pagespeed 1.1 going forward. We recommend migrating when convenient.
What about ModPageSpeed 2.0?
ModPageSpeed 2.0 is a ground-up rewrite in modern C++23. It runs on nginx today (as a Docker reverse proxy or bare-metal module). For .NET environments, the same optimization technology ships as native ASP.NET Core middleware (Preview) — no web server dependency required. You can also stay on 1.1.
Have a technical question? See the full FAQ for troubleshooting and configuration help.