See every front-end request — from the WordPress admin bar.
Templates, assets, shortcodes & blocks, optional database insight.
LinkWeb LayerLens — by LinkWeb, for developers & theme authors.
Open the overlay on the real front end: resolved template, hierarchy candidates, enqueued scripts & styles, shortcodes and blocks in content, and optional query stats. Built for debugging workflows — not another “feature plugin” for editors.
Free · Open source (GPLv2+) · No separate dashboard — lives in the admin bar on the page you are debugging.
From context switching to one overlay
LayerLens is a workflow tool: it reduces back-and-forth between Query Monitor, theme files, and browser DevTools when you only need to know what WordPress actually loaded for this request.
| What developers often juggle | Friction | With LayerLens |
|---|---|---|
| Query Monitor + theme files + browser DevTools | Constant context switching | One overlay on the real page you are debugging |
| Guessing template hierarchy with page builders | Time lost on wrong files | Resolved template, candidates, and query context (post type, taxonomies, conditional tags) |
| Hunting scripts and styles by handle | Searching stacks and sources | All enqueued assets with dependencies, versions, and header/footer placement |
Core capabilities
Everything below is read from the current front-end request — no separate “profiler dashboard” screen.
Template
Resolved template, hierarchy candidates, and query context (post type, taxonomies, is_front_page, and similar flags).
Assets
Scripts and styles: handle, dependencies, version, header vs footer, and media types where available.
Content
Shortcodes and block types present in main content, with counts so you can spot surprises quickly.
Database (optional)
Query count, total time, and slowest queries when enabled. Requires SAVEQUERIES in wp-config.php and the setting in Settings → LayerLens.
Deep template detection (optional)
For non-standard loaders and some page-builder setups; may add a small runtime cost. Use when the default detection is not enough.
Capabilities & multisite
Shown only to users with the right capability (e.g. manage_options / edit_theme_options). Optional restriction to super admins on multisite.
Privacy-minded by design
No permanent storage of profiler snapshots in the database; insight is computed per request for eligible admins.
How it works
- Install from WordPress.org and activate.
- Visit the front end while logged in as an admin.
- Click LayerLens in the admin bar to open the overlay.
- Explore tabs and adjust Settings → LayerLens as needed.
USP: No separate dashboard app — insight is tied to the live page and the current request.
Who it is for
A great fit
- Theme developers shipping custom templates
- Plugin authors debugging hooks, assets, and content
- Agencies working with WooCommerce, builders, or hybrid stacks
Less of a fit
Pure content editors without a debugging need. The admin bar entry is only visible to accounts with the appropriate capabilities.
Trust & transparency
- WordPress.org — official listing, updates, and community reviews.
- License — GPLv2 or later, consistent with the plugin readme.
- Optional external request — a site administrator may voluntarily submit deactivation feedback to LinkWeb; nothing is sent unless you submit that form. Details: Privacy policy · Terms of use.
Frequently asked questions
Why don't I see LayerLens in the admin bar?
You must be logged in with a role that passes the plugin capability checks (for example manage_options or edit_theme_options, depending on configuration). Open a front-end page, not wp-admin. On multisite, access can be limited to super admins when that setting is enabled.
Why is the Database tab empty?
Enable Database Query Insights under Settings → LayerLens and add define( 'SAVEQUERIES', true ); to wp-config.php (above the stop-editing line). Without SAVEQUERIES, WordPress does not collect per-query data for the tab to show.
Does it work with page builders?
Yes. LayerLens inspects the rendered front end. Optional deep template detection helps when loaders or builders do not follow a classic template hierarchy; it can have a small performance cost, so use it when needed.
Does the plugin send data off-site?
Normal use does not phone home. The only outbound call documented in the plugin is optional deactivation feedback if an administrator submits the form on the Plugins screen. See the Privacy policy.
Does LayerLens slow down the front end?
For visitors who are not eligible admins, the plugin should not add meaningful overhead. For administrators who open the overlay, work is done on demand for that request. Optional features (database insights, deep detection) can add cost when enabled — use them when debugging, and disable when you are done.
LinkWeb LayerLens
Front-end insight for WordPress professionals
LinkWeb LayerLens
Built for performance, designed for developers.
Youri Boesberg
Bongerdplein 6, 8162 AW Epe
T. 06 34 85 36 54
E. yboesberg@hotmail.com
© 2026 LinkWeb. WordPress.org · lweb.nl · Privacy · Terms