Nginx can improve the parts of a PageSpeed or Lighthouse result that depend on delivery: compressing text, reusing cacheable responses, and serving static files efficiently. It cannot compensate for oversized images, render-blocking JavaScript, third-party code, or slow application queries. Measure the page first, change only the Nginx layer that matches a failing audit, validate the configuration, and run the same audit again.
Need a server to try this on? Antihost offers Linux VPS plans with NVMe storage, full root access and a 14-day free trial.
The practical objective is not a perfect number. Lighthouse classifies 90–100 as Good, 50–89 as Needs Improvement, and 0–49 as Poor; its documentation also says a score of 100 is extremely challenging and not an expected universal target.
As an Amazon Associate I earn from qualifying purchases.
Recommended Free Tools
What a PageSpeed score actually measures
PageSpeed Insights presents two kinds of evidence. Lighthouse runs a controlled lab audit against the URL and reports performance audits, opportunities, and diagnostics. PageSpeed Insights also uses real-user Chrome UX Report data when enough field data exists for the page or origin. Lab results are useful for reproducing a change; field data reflects the devices, networks, and locations your visitors actually use.
Use the individual failing audits as your work list rather than treating the headline score as a diagnosis. An Nginx change is relevant when the report points to transfer size, compression, cache reuse, connection delivery, or a slow response that the reverse proxy can improve. An Nginx change is not a substitute for fixing the page itself.
#1 Best Overall
- [Ultra-Lightweight Ear Buds Designed for Small Ears] Each earbud weighs only 3.7g and features a compact, ergonomic in-ear design made especially for small ears. Secure, low-profile, and comfortable for workouts, all-day wear or overnight sleeping.The ultra-slim profile sits flush in your ear with no hard edges poking or rubbing, so you can even sleep on your side without discomfort.
- [Immersive Stereo Sound with TOZO OrigX Technology] TOZO OrigX tuning delivers clear vocals, balanced mids, and natural stereo sound for music, podcasts, and videos.
- [Long Battery Life for Daily Use] Get up to 7 hours of playtime on a single charge, with up to 32 hours total using the charging case—ideal for workdays, commuting, and extended listening sessions.
- [Bluetooth 5.3 & Stable Connection] Bluetooth 5.3 provides fast pairing, stable wireless performance, and reduced dropouts as you move around home or office.
- [Deep Bass with Clear Vocals] High-performance drivers produce punchy bass while keeping vocals clean and detailed for everyday listening.
| Lighthouse band | Score | How to use it |
|---|---|---|
| Poor | 0–49 | Find the largest blocking or transfer-costing problems first; a small delivery improvement may be hidden by larger page issues. |
| Needs Improvement | 50–89 | Prioritize the specific opportunities with the largest estimated savings, then retest after each material change. |
| Good | 90–100 | Look at field data and consistency rather than chasing a few additional lab points. |
The bands and the warning about a perfect score come from Chrome for Developers’ Lighthouse scoring guidance. A score is an output of a measurement setup, not a permanent property of a server.
Establish a baseline before editing Nginx
Run repeatable tests
- Run the production URL through PageSpeed Insights or Lighthouse and save the report date, tested URL, device category, and location.
- Record the failing audits, especially those mentioning text compression, cache policy, transfer size, server response time, or static-resource delivery.
- Repeat the test at least once under the same conditions. Lab scores vary with load and network simulation, so one run is not a reliable before value.
- Check field data separately when it is available. A lab pass does not prove that real visitors have good Core Web Vitals.
Inspect what the server sends
Use your browser’s Network panel or an equivalent header inspection tool to confirm the response status, Content-Type, Content-Encoding, Cache-Control, and timing for HTML, CSS, JavaScript, fonts, and images. Look at the actual response, not only the Nginx file: another proxy, a CDN, or an application framework may overwrite headers.
Keep a change record
Write down the directive changed, its context (http, server, or location), the expected effect, and the test result. This makes it possible to revert a change that improves one URL while harming authenticated traffic or another server block.
Compress text responses selectively
Compression reduces bytes sent over the network. Nginx’s documented pattern enables gzip, lists the MIME types that should be compressed, sets a minimum response size, and optionally controls which proxied responses may be compressed. Runtime compression uses CPU, so applying it indiscriminately can move the bottleneck from the network to the server.
A conservative gzip configuration
gzip on;
gzip_types text/plain text/css application/javascript application/json application/xml image/svg+xml;
gzip_min_length 1000;
gzip_proxied no-cache no-store private expired auth;These directives may be placed in http, server, or location context according to Nginx’s documentation. The MIME list targets text-like payloads such as CSS, JavaScript, JSON, XML, and SVG. The 1,000-byte threshold avoids spending CPU on tiny responses; choose a value that matches your traffic rather than assuming every response benefits.
Rank #2
- 【IP68 Waterproof Multifunctinal Smart Watch】Torjalph fitness activity tracker smart watch is IP68 waterproof technology ,you can wear it when swimming,handwashing,it's rain-proof which means that you perform multiple exercise modes outside without worrying about sweat or rain corroding your fitness smart watch,and this watch equipped with a 230 mAh large capacity battery magnetic charging ,and this sports activity tracker watch can be used 5-7 days If fully charged.
- 【Larger 1.83'' Full Screen Watch & Multi-dial Selection】1.83 inch full HD color touch screen smart watch for men / women provides excellent 240*284 resolution image quality ,This Bluetooth smart watch offers a better touch experience and remarkable immersion and ,more than 200 watch faces for you to choose from App"Da Fit ", you can change the dial style according to your mood to wear keeping the world on your wrist
- 【Accurate Activity Tracker Smart Watch 】sports watch activity tracker uses sweat and dust resistant breathable silicone strap, our Fitness Tracker Smart Watch for Android iOS Phones supports 12 sports modes,walking,running,bicycle,swimming,badminton,basketball,football,rope skipping. This bluetooth calls smart watch for men women is lightweight and stylish, bringing more convenient and relaxing sports experience while also providing more protection.
- 【Your 24 Hour Personal Daily Health Monitor】Fitness watch for women men full touch screen IP67 waterproof bluetooth smartwatch for Android iOS Phones with heart rate blood pressure monitor multifunction Andriod smart watch with steps counter sleep monitor sports fitness watch, monitoring blood oxygen saturation allows you to understand your physical condition in real time to track fitness progress ,to know your health status in time.
- 【More Functions Bluetooth Call Smart Watch】This fitness activity smart watch full screen for iPhone and Android phones includes a bunch of new features including:The bluetooth smart watch can hang up the phone, receive and display WhatsAPP /Text /Facebook /Twitter /Messenger reminder.Support sedentary reminder, alarm clock, stopwatch, timer,weather information,music control, remote camera control compatible with Android 5.0 and above or iOS 9.0 and above smartphones.
Understand the proxy rule
gzip_proxied determines when Nginx compresses a response that came from an upstream proxy. The example allows compression when the upstream response is marked no-cache, no-store, private, expired, or requires authorization. Review that choice with the application team: compression is normally safe for public text, but response handling must still respect your security and caching policy.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Do not recompress already compressed formats
JPEG, WebP, AVIF, ZIP files, and most video formats are already compressed. Adding them to gzip_types increases CPU work with little or no transfer saving. Images should be resized and encoded for the target device instead of being sent through a general-purpose text compressor.
Serve precompressed files when your build creates them
gzip_static on;gzip_static tells Nginx to look for a matching .gz file and serve it when the client accepts gzip. It does not perform runtime compression. The compressed artifact must exist beside the original file and must be regenerated whenever the source changes. Verify that deployment publishes both files and that content types and cache headers remain correct.
Verify that gzip is working
- Request a CSS or JavaScript file with an
Accept-Encoding: gzipheader. - Confirm the response includes
Content-Encoding: gzipand a suitableVary: Accept-Encodingbehavior from your complete proxy chain. - Compare the transferred size and server CPU before and after enabling compression.
- Check a client that does not advertise gzip; it must still receive a valid uncompressed response.
Cache safe reverse-proxy responses
Reverse-proxy caching can prevent repeated origin work and shorten the wait for public responses. It is also the easiest Nginx optimization to make unsafe: a cache can serve one user’s personalized or authenticated response to another user if the cache key and bypass rules are wrong.
Basic cache layout
http {
proxy_cache_path /data/nginx/cache keys_zone=mycache:10m max_size=1g inactive=60m;
server {
location / {
proxy_cache mycache;
proxy_cache_valid 200 302 10m;
proxy_cache_valid 404 1m;
proxy_cache_bypass $cookie_nocache $arg_nocache;
proxy_no_cache $http_pragma $http_authorization;
proxy_pass http://backend;
}
}
}The cache zone is declared in http; the proxy_cache policy is selected in the relevant server or location. The example keeps successful and redirect responses for 10 minutes and a 404 for 1 minute, but those durations are policy decisions, not universal recommendations. The official Nginx content-caching guide describes GET and HEAD responses as the default cacheable methods when proxy caching is enabled.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errorsRank #3
- [Low Noise High Fidelity] New bee guitar cord with 22AWG oxygen-free-copper center conductors provides enhanced signal transfer, the PVC insulation material and the high-density stranded copper double shield provide noise rejection for quiet operation
- [Ideal for Choice] New bee 1/4 straight and right angle metal connectors, ensures a secure connection in any instrument, pedal, or amp jack. L shape great fro on stage guitar stands
- [Wide Compatible] Suitable for mixer, power amplifier, microphone, effector, decoder, equalizer, electoronic organ, electric guitar, electric bass and other electronic equipments. Widely used in the installation of smart home, karaoke speaker, professional stage audio, etc
- [Easy Disassemble] Making incidental repairs quick and easy! Very nice, flexible cable
- [Dont Hesite to Order] 24 hours customer services and professional technology team are standing by
Set the safety boundary first
- Cache only responses that are identical for every eligible visitor, or explicitly include the dimensions that make them different.
- Bypass the cache when a request carries a session cookie or a deliberate opt-out argument.
- Do not cache responses carrying authorization unless you have a tested, user-specific cache design.
- Review upstream
Cache-Control,Set-Cookie, andVaryheaders; an application may intentionally prohibit sharing. - Keep account pages, checkout flows, dashboards, and other personalized locations outside the public cache.
Plan expiry and invalidation
A cached response can remain fast but stale. Choose proxy_cache_valid values according to how quickly each content type changes. When publishing an urgent correction, purge or bypass the affected keys rather than waiting for normal expiry. The cache directory also consumes disk space; monitor its size, hit ratio, and eviction behavior.
Prove cache behavior with headers and logs
Inspect a first request and a repeated request. Add a temporary diagnostic header or log field that shows a cache hit, miss, bypass, or expired entry in your environment. Confirm that a logged-in request cannot receive a public user’s cached body and that an opt-out request reaches the upstream application.
Serve static files efficiently
Use sendfile and tcp_nopush where they fit
sendfile on;
tcp_nopush on;sendfile on; lets the operating system copy file data directly between file descriptors instead of first copying it into an intermediate Nginx buffer. tcp_nopush on; works with sendfile so response headers and the beginning of a file can be sent in one packet. These settings affect the file-transfer path; they do not resize an image or make application-generated HTML faster. Test them on the operating system and storage used by your server, particularly when files are on network-mounted storage.
Resolve files before invoking the application
location / {
try_files $uri $uri/ @backend;
}
location @backend {
proxy_pass http://backend;
}try_files checks for a file or directory and routes a miss to the named backend location. This avoids sending every request for an existing asset through the application. Adjust the fallback to your framework’s actual entry point and verify that directory handling, trailing slashes, and error pages remain correct.
Free tools Windows power users keep installed
One-click scans. No signup required.
Protect the static path
- Confirm that the Nginx worker can read the asset directory but cannot write to it unless your deployment requires that capability.
- Return the correct
Content-Typefor fonts, JavaScript modules, CSS, and SVG. - Use versioned filenames for assets that should be cached for a long time; otherwise, a long TTL can preserve an old file after deployment.
- Test missing files and directory requests so that a typo does not become an expensive application request or an unintended directory listing.
Consider ngx_pagespeed only as an optional module
The ngx_pagespeed project provides an Nginx module that can rewrite and generate optimized resources. Its documented setup includes pagespeed on;, a writable pagespeed FileCachePath, and location handlers for the generated resources. A response can be checked for an X-Page-Speed header to verify that the module is active.
Rank #4
- Digital Family Calendar: BSIMB digital calendar wall touch screen puts an end to your chaotic life. Designed for busy families, the digital calendar keeps you organised and in step with your family. Assign different colours and tasks to each family member to make family scheduling easier and more intuitive.
- Easy Setup and Auto-Sync: Plug in, connect to WLAN and auto-syn your electric calendar in minutes. Digital wall calendar compatible with Google calendar, iCloud calendar, Outlook calendar, Cozi calendar and Yahoo calendar. Add events directly on the device or through the ecalendar app. Electronic calendar stays current whether you're at work or traveling—no manual updates needed.
- All-In-One Home Assistant: Smart calendar builds habits and encourage independence with personalised chores. Display daily meal plan to reduce the daily ‘What's for dinner?’ stress. To-do lists keep track of everything you want. Turning chores into valuable achievements with stars and rewards, making life easier and more enjoyable.
- Manage Anytime Anywhere: BSIMB electronic calendar for family stay connected with the powerful ecalendar app. Access and manage your digital wall calendar anytime, anywhere with free features like stars & rewards, photo screensaver, chore charts, meals plans, to-do lists etc. Electronic planner paid features like Magic Import tailor advanced tools for users with special needs.
- Stay in Touch with Loved Ones: Share photos or videos from your phone to electronic wall calendar with app, instantly update your life moment, and keep in touch with your family, especially those who are far away; you can also surprise your smart calendar digital wall by sending him a wish card; it's also great for keeping tech-illiterate elders in touch with the youngsters.
pagespeed on;
pagespeed FileCachePath /var/cache/pagespeed;
location /ngx_pagespeed_beacon {
pagespeed on;
}
location ~ ".pagespeed.[^.]+.[^.]+$" {
add_header Vary "Accept-Encoding";
}Treat this as a module decision, not a default switch. Before production use, verify how the module was built, whether it is compatible with your Nginx version and operating system, how its file cache is secured and sized, and whether the project’s maintenance status meets your risk requirements. Generated resources introduce another cache and invalidation layer. Test HTML, CSS, JavaScript, images, and error responses separately; an optimization that rewrites one page can break a script or produce stale output on another.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Fix the problems Nginx cannot solve
Images
Google notes that images often account for a large share of downloaded bytes. Choose the format, quality, pixel dimensions, and responsive variant for each asset and device. A smaller source image delivered at the display size usually saves more than compressing the surrounding HTML. Use width and height information so the browser can reserve layout space, and verify that mobile visitors are not downloading a desktop-sized image.
Render-blocking application code
Minify and split CSS and JavaScript, remove unused code, and defer noncritical scripts in the application build. Nginx can transfer the resulting files efficiently, but it cannot determine which code a page needs to render or safely reorder application dependencies.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Backend latency
Slow database queries, external API calls, template rendering, and cold application workers appear as a delayed initial response. Measure upstream timing and profile the application. A proxy cache can hide repeated work for public pages, but it should not be used to conceal a backend that must respond uniquely for each request.
Third-party resources
Analytics, advertising, embedded media, and remote fonts can add DNS, connection, JavaScript, and main-thread cost outside your Nginx process. Remove unnecessary vendors, load them later, or self-host where licensing and operational requirements allow.
A safe Nginx-to-Lighthouse improvement loop
- Capture the baseline. Save lab and available field results, the tested URL, and the exact failing audits.
- Map the audit to a layer. Use gzip for eligible text bytes, proxy caching for reusable public responses, sendfile and
try_filesfor static delivery, and application or asset work for everything else. - Change one related group. For example, enable gzip and set its MIME list together, but do not simultaneously change caching, image encoding, and JavaScript delivery if you want to know which change mattered.
- Validate syntax. Run
nginx -twith the same configuration that production will load. Resolve warnings as well as fatal errors. - Reload without dropping existing connections. Use your platform’s supported Nginx reload procedure, then check the error log and a representative public, authenticated, missing, and static URL.
- Inspect the wire result. Confirm headers, status codes, compressed sizes, cache state, and upstream timing. A higher score with a broken cache policy is not an improvement.
- Re-run the same audit. Compare the relevant audit and diagnostic, not just the headline score. Keep the change only when it improves the intended metric without violating correctness.
- Watch field behavior. Lab gains may take time to appear in real-user data, and a field regression can reveal device or network conditions that the lab did not model.
Choose the intervention by bottleneck
| Observed problem | Nginx option | What changes | Main cost or risk |
|---|---|---|---|
| Large CSS, JavaScript, JSON, XML, or SVG transfer | Runtime gzip or precompressed files with gzip_static |
Bytes sent over the network | Runtime CPU, or build and deployment complexity for precompressed artifacts |
| Repeated public requests perform the same origin work | proxy_cache with explicit validity and bypass rules |
Origin work and response time for cache hits | Stale or cross-user content if personalization and invalidation are mishandled; disk usage |
| Static files take an inefficient transfer path | sendfile, tcp_nopush, and try_files |
File handling and routing | Platform-specific behavior and incorrect fallbacks if not tested |
| Generated resources need automatic rewriting | Optional ngx_pagespeed module | Generated or transformed resources | Module compatibility, maintenance, extra cache, and operational complexity |
| Images, blocking scripts, or slow queries dominate | Application, build, image, or backend changes | Payload composition or work performed before delivery | Cannot be fixed by Nginx directives alone |
Troubleshoot common regressions
The score did not move after enabling gzip
Check that the tested response is text, exceeds gzip_min_length, and is not already compressed. Verify Content-Encoding at the public endpoint rather than only at the origin. If the audit’s largest opportunity is an image or third-party script, gzip is addressing the wrong payload.
Users see stale or private content
Disable the affected cache location, purge its entries, and inspect cookies, authorization headers, Set-Cookie, and Vary. Add an explicit bypass or no-cache rule for personalized requests before re-enabling public caching.
Static files return the application’s HTML
Check the order and scope of try_files, the named fallback, filesystem permissions, and the active server block. Request a known existing file and a known missing file separately; the first should be served directly and the second should follow the intended application route.
CPU or latency increased
Runtime compression may be consuming worker CPU, while an oversized cache or slow storage may be affecting I/O. Compare CPU, upstream timing, cache hit ratio, and transferred bytes. Narrow the gzip MIME list, lower compression work for small responses, or revert the change if the end-to-end result is worse.
ngx_pagespeed output is missing or broken
Confirm that the running binary contains the module, the file cache path is writable, the generated-resource locations are reachable, and the response includes the expected X-Page-Speed header. If compatibility or invalidation cannot be demonstrated, remove the module rather than leaving an unverified transformation layer in production.
What success looks like
A useful result is a measurable improvement in the failing audit and, where available, better real-user experience without compromised caching or correctness. Keep the configuration that matches the bottleneck: compress eligible text, cache only safely shareable responses, serve existing files directly, and leave image, code, third-party, and backend problems to the systems that control them. Re-test after meaningful changes instead of treating one PageSpeed number as a permanent verdict.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
