What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
A green Lighthouse score does not show whether your single-page app (SPA) releases objects after users navigate, open and close views, or repeat other interactions. Lighthouse audits page quality and performance; diagnosing a memory leak means reproducing a workflow, comparing heap snapshots, and tracing the references that keep objects alive.
Why a green Lighthouse score cannot rule out a memory leak
Lighthouse runs automated audits for performance, accessibility, best practices, and SEO. Its Performance score is generally based on performance metrics, not the separate Opportunities or Diagnostics results. That score does not test whether objects left behind by earlier SPA interactions are eventually released. Lighthouse’s scoring inputs also change by version, so historical metric weights should not be treated as current leak-detection criteria. Chrome’s Lighthouse overview and performance-scoring documentation describe those distinctions.
As an Amazon Associate I earn from qualifying purchases.
Lighthouse documentation also discusses the memory cost of retained JavaScript references in the context of JavaScript execution. The “Reduce JavaScript execution time” audit measures execution time, however; it is not a test of whether objects are released over a long SPA session. The audit documentation should not be read as defining memory-leak thresholds.
What each tool can tell you
| Tool | Useful for | Does not establish by itself |
|---|---|---|
| Lighthouse | Automated page-quality and load-performance audits, including recommendations. | Whether objects from repeated SPA interactions are released. |
| Chrome DevTools Memory | Heap snapshots, allocation profiles, and inspection of detached DOM nodes and retained objects. | A complete accounting of all browser or native memory, or the app’s root cause without interpreting the profile. |
See Lighthouse’s overview, Chrome DevTools’ memory-problem guide, and heap snapshot documentation.
Quick Recap
Rank #4
- CEL Doctor: The ANCEL AD310 is one of the best-selling OBD II scanners on the market and is recommended by Scotty Kilmer, a YouTuber and auto mechanic. It can easily determine the cause of the check engine light coming on. After repairing the vehicle's problems, it can quickly read and clear diagnostic trouble codes of emission system, read live data & hard memory data, view freeze frame, I/M monitor readiness and collect vehicle information
- Sturdy and Compact: Equipped with a 2.5 foot cable made of very thick, flexible insulation. It is important to have a sturdy scanner as it can easily fall to the ground when working in a car. The AD310 OBD2 scanner is a well-constructed mechanic tool with a sleek design. It weighs 12 ounces and measures 8.9 x 6.9 x 1.4 inches. Thanks to its compact design and light weight, transporting the device is not a problem. The buttons are clearly labelled and the screen is large and displays results clearly
- Accurate Fast and Easy to Use: The AD310 scanner can help you or your mechanic understand if your car is in good condition, provides exceptionally accurate and fast results, reads and clears engine trouble emission codes in seconds after you fixed the problem. This device will let you know immediately and fix the problem right away without any car knowledge. No need for batteries or a charger, get power directly from the OBDII Data Link Connector in your vehicle
- OBDII Protocols and Car Compatibility: Many cheap scan tools do not really support all OBD2 protocols. AD310 scanner as it can support all OBDII protocols such as KWP2000, J1850 VPW, ISO9141, J1850 PWM and CAN. This device also has extensive vehicle compatibility with 1996 US-based, 2000 EU-based and Asian cars, light trucks, SUVs, as well as newer OBD2 and CAN vehicles both domestic and foreign. Pls confirm with our customer service whether it is compatible with your vehicle before purchasing
- Home Necessity and Worthy to Own: This is an excellent code reader to travel or home with as it weighs less and it is compact in design. You can easily slide it in your backpack as you head to the garage, or put it on the dashboard, this will be a great fit for you. The AD310 is not only portable, but also accurate and fast in performance. Moreover, it covers various car brands and is suitable for people who just need a code reader to check their car
Rank #3
- 【A MUST-HAVE SCANNER TOOL FOR DIYERS】 - VDIAGTOOL VD10 car code reader is an incredibly useful, handheld obd2 scanner for each car owner or hobbyist, even for those with little to no experience when it comes to vehicle mechanics! Similar to a fixd car diagnostic tool, using this car diagnostic scanner is extremely easy. All you have to do is attach it to your car OBDII port and you can diagnose car problems in seconds! Read Codes (DTCs); Clear Codes; Live Data; View Freeze Frame; I/M Readiness; Vehicle Information.
- 【KEEP ENGINE IN GOOD STATUS】 - VDIAGTOOL check engine code reader brings a fast access to scan, read the car fault code, show its definition on the screen instantly, troubleshooting to find the root causes of problems, erase the engine fault code and turn off the MIL (Malfunction Indicator Light). Similar to a fixd car diagnostic tool, this car code reader helps ensure your engine stays in top condition.
- 【READ/CLEAR CODES & DTC LOOKUP】- No search online & saving your time, this vehicle car code reader retrieves generic (P0, P2, P3, and U0), manufacturer specific (P1, P3, and U1) codes, pending codes and displays DTC definitions based on the built-in database(more than 3000 codes) on the TFT screen, find out the root causes and clear the codes after fixed.
- 【ENHANCED OBD2 SCANNER WITH LIVE DATA & RETRIEVE FREEZE FRAME】 - This diagnostic scan tool for accurate diagnosis enables you to retrieve data from vehicle sensors, such as Engine RPM, Intake air temperature, Short/Long term fuel, Misfire data and etc. The freeze frame is stored in the PCM together with the diagnostic trouble code (DTC) related to the fault. Comparable to a fixd car diagnostic tool, the VD10 car code reader car scanner can be a valuable & practical diagnostic aid and also greatly help when diagnosing intermittent problems.
- 【I/M READINESS for THE S-nn-0-g CHECK】- OBDII vehicle may not pass the annual inspection unless the required monitors since reset are complete. So you should at least read the readiness monitors and make sure they are ready. This car obd2 scanner diagnostic tool is equipped with I/M readiness function to check the operations of the e-m-issi0n system on OBD2 compliant vehicles, run I/M monitor readiness test, checking if the pass vehicle s-m-0-g inspection.
Rank #2
- [Easy to Use—Work Out of the Box] + [FOXWELL 2026 New Version] FOXWELL NT604 Elite scan tool is the 2026 new version from FOXWELL, designed for car owners who want to figure out the cause of issues before fixing car problems by scanning common systems like ABS, SRS, engine, and transmission. The NT604 Elite obd2 scanner diagnostic tool comes with the latest software—no need to waste time downloading software first. Plug the scanner into the OBDII port with OBDII cable to start the diagnosis.
- [Affordable] + [Reliable Car Health Monitor] Will you be confused what happens when the warning light of ABS/SRS/transmission/check engine flashes? Instead of taking your cars to dealership, this FOXWELL scanner will help you do a thorough scanning and detection for your cars and pinpoint the root cause. Note:The device is a diagnostic tool, not a repair tool. To turn off a warning light, you must first physically repair the issue causing it. Only then can the scanner be used to clear the corresponding fault code.
- [5 in 1 Car Diagnostic Scanner] Compared with obd scanners (50-100), NT604 Elite code scanner not only includes their OBDII diagnosis but also serves as ABS/SRS scanner, transmission and check engine code reader. When it’s an odb2 scanner, you can use it to check if your car is ready for annual test through I/M readiness menu. In addition, live data stream, built-in DTC library, data play back and print, all these features are a big plus for it. Note: doesn't support maintenance functions like reset or relearn. For the SRS system, NT604 Elite can read and clear common fault codes not caused by a crash, but crash/collision data cannot be cleared.
- [Fantastic AUTOVIN] + [No extra software fee] Through the AUTOVIN menu, this NT604 Elite car scanner allows you to get your V-IN and vehicle info rapidly, no need to take time to find your V-IN and input one by one. What's more, the NT604 Elite ABS SRS scanner supports 60+ car brands from worldwide (America/Asia/Europe). You don’t need to pay extra software fee. AUTOVIN may not work on some older vehicles or certain vehicle brands. If AUTOVIN fails, please input the vin code manually or go to the Diagnostic Menu to select your vehicle model.
- [Solid protective case KO plastic carrying bag] + [Lifetime update] Almost all same price-level car scanner diagnostic tool only offers plastic bag to hold the scanner.However, NT604 Elite automotive scanner is equipped with solid protective case, preventing your obd2 scanner from damage. Then you don’t need to pay extra money to buy a solid toolbox.
#1 Best Overall
- 【Diagnose Check Engine Light in Seconds – No Mechanic Needed】The FOXWELL NT301 OBD2 scanner instantly reads & clears engine fault codes (DTCs) with one click. Simply plug into the 16-pin DLC port, turn ignition on, and get accurate results within seconds—No prior car knowledge required. Save hundreds on dealership fees by knowing exactly what’s wrong before you visit a shop. The #1 choice car scanner for DIYers and car owners who want to take control of their vehicle’s health
- 【Clear & Reset CEL with Confidence】Unlike cheap code readers that just erase codes temporarily, NT301 works like all professional vehicle code readers: It clears the check engine light only after you’ve fixed the underlying issue. If the problem isn’t fully repaired, the fault code will reappear. So you’ll never get a false pass. Use the foxwell scanner to verify your repair work and drive with peace of mind
- 【Sm-og Check Helper – Know Your Pass/Fail Status Before the Test】With dedicated one-click I/M readiness hotkeys and a simple Red-Yellow-Green LED indicator, you’ll instantly know if your vehicle is ready for annual testing. Built-in speaker provides clear audio feedback. No guesswork—just confidence before you head to the test center. One less thing to worry about when inspection day comes
- 【Advanced OBDII Modes – O- 2 Sensor & EVAP Testing】NT301 go beyond basic code reading with enhanced OBD2 modes. Run an EVAP system check to assess fuel tank condition, and use the O- 2 sensor test to optimize air-fuel ratio, boosting fuel economy, cutting em- issions, and saving you money at the pump. The code reader for cars and trucks is like having a mini em-issions lab in your glove box
- 【Live Data Graphing – Spot Engine Issues in Real Time】View and log live sensor data in easy-to-read graphs with this OBD2 scanner diagnostic tool. Monitor ox- ygen sensors, fuel trims, coolant temperature, RPM, and more to spot suspicious values instantly. This obd scanner gives you professional-grade insight without the pro price tag—a feature you won’t find on basic $20 car code readers
How to investigate a suspected SPA leak
- Define a repeatable journey. Record the starting route and state, then perform the suspected action and its reverse—for example, navigate to a route and back, or open and close a view. Repeat the same bounded sequence with a stable browser and dataset so the results can be compared. Chrome’s profiling guidance recommends checking paired direct and reverse operations for objects that remain. Read the JavaScript memory-profiling guide.
- Watch memory over time for clues. Chrome Task Manager or a Performance recording can show broad trends. Do not treat the operating-system memory footprint and JavaScript heap as interchangeable: the live JavaScript-memory value represents reachable objects, while browser memory includes more than the JavaScript heap. A rising graph is a reason to investigate, not proof of a leak. Chrome explains these memory views and their limits.
- Capture a baseline heap snapshot. In DevTools, open the Memory panel and take a snapshot before the workflow. Heap snapshots trigger garbage collection and show reachable JavaScript objects at that point; they do not account for every kind of browser or native memory. Chrome’s snapshot guide explains the view and comparison workflow.
- Repeat the workflow and compare snapshots. Perform the same actions, return to the starting state, and capture another snapshot after collection. Use the Comparison view to look for objects that persist or accumulate across equivalent cycles rather than drawing conclusions from one raw reading. A large heap may be intentional; unexpected growth after repeated, bounded journeys is more informative.
- Inspect detached DOM nodes and retaining paths. A detached node has been removed from the document tree but remains reachable through JavaScript. Search the snapshot for detached DOM nodes, then follow the retaining path to find the object or closure keeping a node alive. Detached nodes are a recognizable leak pattern, not the only possible one. Chrome’s memory guide covers detached DOM trees and retained objects.
- Profile where allocations happen. Record an Allocation Timeline during the suspect interaction or use allocation sampling to identify where objects are created. Check whether those objects remain after the route or component has been removed; use the retaining path and allocation evidence together.
- Verify the fix with the same scenario. Change the reference lifecycle indicated by the profile, then repeat the identical journey and snapshot comparison. The right code change depends on what the retaining path shows; a profile is needed before attributing the leak to a particular framework, listener, timer, cache, or closure.
How to tell a leak from normal memory movement
- Do not diagnose from one reading. Normal allocation and garbage collection make memory rise and fall, and total browser memory is not the same as the JavaScript heap.
- Compare like with like. Repeat the same actions, return to the same state, and compare snapshots after collection. Persistent growth in equivalent cycles is a stronger signal than a single large heap.
- Follow retained references. A detached DOM node can reveal a problem, but other retained objects may matter too. Use the retaining tree and allocation profile rather than assuming a cause.
- Account for intentional retention. An application may legitimately keep data in memory. The question is whether unexpected objects continue to accumulate after a workflow that should have released them.
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.




