In Fight View and on the Triage Page, every winner card and loser row shows a source line: where that CSS rule came from. It’s written in real human terms, not in stylesheet paths or technical identifiers. Here’s what each label means and what it tells you about where to go to fix the problem.
Your theme’s stylesheet #
The rule came from your active WordPress theme’s CSS files. The fix is usually one of two things: a more specific rule added to your theme’s custom CSS area, or a setting change in the theme’s customizer if the theme exposes that option through its own UI.
Page Builder (Elementor, Divi, etc.) #
The rule was generated by your Page Builder. These can be compiled stylesheets or inline styles set per-widget. The fix is usually in the Page Builder’s own settings for that element: the Style tab on the widget, the section settings, or the global style settings depending on what’s overriding what.
Plugin stylesheet #
The rule came from a WordPress plugin. The stylesheet filename usually contains the plugin’s name and appears in the full capture file. Fixes for plugin-origin conflicts usually mean either adding a more specific override in your custom CSS or, if it’s a bug, contacting the plugin’s support.
WPCode snippet #
The rule came from a code snippet plugin like WPCode. That means someone (probably you, at some point) added it as a custom snippet. Find it in your snippet plugin and update or remove it there.
Inline Style #
The rule is set directly on the element’s style attribute rather than through a stylesheet. If it’s set by a Page Builder UI, look in the Page Builder’s settings for that widget and clear the inline value there. If it’s set by JavaScript at runtime, Lens routes to developer handoff, because changing a JavaScript-set Inline Style requires changing the JavaScript that sets it.
JavaScript-injected style #
The rule was added by JavaScript after the page loaded. It’s not in any stylesheet. There’s no CSS rule you can add that will reliably beat it in all situations. Lens routes these directly to developer handoff. Your developer needs to find the JavaScript setting it and either remove or change it at the source.
Browser default #
The rule is the browser’s built-in baseline styling. These are filtered out of the computed styles panel in Stage 1 since they’re rarely the cause of a visual conflict. If you see this in Fight View, it means no other rule is setting that property, and the browser’s default is winning by default. The fix is to add a rule that sets the property to what you want.