Brotli and Gzip Compression: Turn It On and Verify It
Turn on Brotli or gzip for HTML, CSS and JavaScript, choose the right file types and levels, and verify the Content-Encoding and Vary headers with curl.
Practical, step-by-step website launch and SEO health guides.
Showing 1 to 24 of 25 guides in Performance (page 1 of 2)
Turn on Brotli or gzip for HTML, CSS and JavaScript, choose the right file types and levels, and verify the Content-Encoding and Vary headers with curl.
Set Cache-Control headers so browsers and CDNs reuse static files, keep HTML fresh, avoid stale CSS and personal pages in shared caches, and verify the result.
Set up a CDN for speed, choose what to cache, keep Googlebot and Bingbot able to crawl, and verify cache headers, status codes and bot access afterwards.
Learn what the three Core Web Vitals measure, the good and poor thresholds, why field and lab numbers differ, and how to read your results and plan fixes.
Understand how the Search Console Core Web Vitals report groups URLs, why it shows no data, and how to rank fixes and track them over a 28-day window.
Learn when critical CSS is worth the effort, how to extract above-the-fold styles, inline them in the head, load the rest later and test for flashes.
Compare Lighthouse lab results with Chrome UX Report field data, understand why they differ metric by metric and decide which one to act on.
Identify your page's LCP element, then fix slow server response, late discovery and oversized images, and retest in lab and field data on mobile.
Choose the right font-display value, preload key fonts, subset to WOFF2 and match fallback sizes so web fonts load fast without text jumping on screen.
See what HTTP/2 and HTTP/3 change, check which protocol your site uses with DevTools and curl, turn them on safely and know what they will not fix.
Find which clicks, taps and keystrokes feel slow, trace the long JavaScript tasks behind them, shorten the work and recheck INP on real devices.
Set a repeatable Lighthouse baseline, find the main bottleneck, make small safe fixes and compare repeated runs without breaking your site.
Defer YouTube video and map iframes with loading=lazy, reserve space to avoid layout shift, add a click-to-load facade and test what Google can see.
Lazy-load below-the-fold images with the native loading attribute, keep above-the-fold and LCP images eager, and test that Google still sees them.
Set up Lighthouse CI in your build, write a lighthouserc file with assertions and size budgets, and fail pull requests that slow the site down.
Learn why the mobile Lighthouse score is usually lower than desktop, then compare like-for-like runs and fix oversized images, scripts and slow requests.
Set the viewport meta tag, size and space tap targets, stop horizontal scrolling and keep text readable and zoomable, with tests you can run on a phone.
Check that your mobile pages carry the same content, links, structured data and robots rules as desktop, and test them with Search Console and DevTools.
Find what makes your page jump while it loads, then reserve space for images, embeds, banners and fonts and retest CLS on mobile and desktop.
Find what fills your JavaScript bundle, remove unused code, split by route with dynamic import, and check the result with Lighthouse and DevTools.
Identify the CSS and scripts that delay first paint, split critical from optional code, apply defer or async where safe and test menus and forms.
Write srcset and sizes correctly, use picture for art direction and formats, set width and height, and verify that phones download smaller files.
List every third-party tag, chat widget and ad script, measure what each costs your page, then remove, delay or isolate the ones that slow it down.
Measure time to first byte, split it into redirect, connection and server time, then cut each part with caching, fewer redirects and faster back-end work.