What plugins does this website use?
Paste a URL and check which plugins a site is running. A plugin is what actually decides how a page behaves — the page builder that renders it, the SEO tool that writes its meta tags, the cache layer that serves it, the forms and feeds that add requests to it. When you are asked to fix or rebuild a site, the plugin list is the first thing worth knowing: it tells you what is editable in a UI, what is baked into code, and what is quietly slowing the page down.
Plugins are visible from the outside — if you know where to look
Most CMS installs publish their plugin assets at predictable paths. A page that loads /wp-content/plugins/elementor/assets/... is telling you, in plain URL text, that Elementor is installed. Nothing private is required: the browser has to download those files to render the page, so their paths appear in the HTML you already received.
This is why plugin detection works on a live site without a login. It reads the same asset URLs a visitor's browser reads, groups them by plugin directory, and reports what it found together with how many times each clue appeared.
The same reading works beyond WordPress. Shopify apps ship under /cdn/shopify.com/ app paths, Joomla modules under /modules/, Drupal modules under /sites/all/modules/, and a custom build often exposes bundled libraries and third-party widgets by name. Because this reads whatever folders the page actually publishes, it also names plugins that no signature database has catalogued yet — a plugin only appears in a database after someone adds it, but it still has to load a file with its own folder name.
A path hit is evidence; a brand name in the copy is not
Plenty of pages mention WordPress, Shopify or Elementor in prose — an article about a migration, a comparison post, a client logo wall. That is not an install. A real signature is a structural one: a script or stylesheet URL served from the vendor's own asset path, a generator meta tag, or a vendor-owned host in the response.
Every result on this site carries its evidence and a confidence note. A dashed ``likely'' badge means only a brand keyword matched and no structural signature was found — treat it as a lead to check, not a conclusion.
- Elementor— The most common WordPress page builder — it owns the layout markup and often the bulk of the page weight.
- Ultimate Elementor / ElementsKit— Add-on widget packs that load their own CSS and JS on every page.
- WooCommerce— Turns the site into a shop: cart, checkout, product templates and its own scripts.
- WooCommerce Bookings— Turns products into bookable slots, days or resources.
- Contact Form 7— The classic contact form plugin; a common source of unstyled or blocking markup.
- WPForms— Drag-and-drop form builder, often loaded site-wide for a form used on one page.
- Advanced Custom Fields— Stores custom fields for editors; what is editable in the CMS often comes from here.
- Yoast SEO— Owns titles, meta descriptions, canonical tags and schema output.
- Rank Math— An alternative SEO plugin doing the same job as Yoast — never run both.
- Site Kit by Google— Google's own dashboard plugin for Search Console and Analytics data.
- MonsterInsights— Wires Google Analytics into WordPress; check it is not loading a second tracking stack.
- PixelYourSite— Injects tracking pixels — usually visible as third-party cookies in a scan.
- Jetpack— Bundles stats, CDN images, security and social features — a frequent performance question mark.
- WP Rocket— A paid caching/optimisation plugin — if it is installed, check that the win is actually switched on.
- LiteSpeed Cache— Cache and optimisation plugin; only fully effective on a LiteSpeed server.
- Autoptimize— Aggregates and minifies CSS/JS — a direct answer to render-blocking requests.
- Wordfence— Security scanner; useful, but its live scans can add server load.
- UpdraftPlus— Backup plugin — front-end invisible when it works properly.
- Redirection— Manages 301s and 404 logs; a common cause of unexpected redirect chains.
- WPML— Multilingual plugin — it changes hreflang, URLs and often adds weight.
- Polylang— A lighter multilingual alternative to WPML.
- Mailchimp for WP— Email signup integration; forms can be a layout and accessibility weak point.
- Smash Balloon social feeds— Whenever a site shows an Instagram or YouTube feed, this is usually why.
What the plugin list tells you about the work
The builder plugin decides whether you can change a layout in a UI or have to touch code. The SEO plugin decides whether titles and schema come from settings or from the theme. A cache and optimisation plugin decides whether your CSS and JS are combined and deferred, or shipped raw on every request.
That is why the same visual problem can be a ten-minute settings change on one site and a template rewrite on another. Read the plugin list before you estimate the job.
If nothing is detected: that is a finding too
No plugin directories, no CMS fingerprints, no builder assets usually means a custom-built site — hand-written HTML/CSS/JS, or a site generated by a framework without an exposed plugin layer. The detector says so explicitly rather than reporting an empty result, because ``custom-built'' changes both the fix and the estimate.
Custom builds can still be identified in shape: which front-end framework renders them, which host serves them, which third-party scripts they call. Those are separate detectors on this site.
Pick the plugin that matters most to your question. If you do not know where to start, run a full check on the homepage — it lists every detected plugin directory at once, then come back here for the one you care about.
Optimization help is available
Tell me your URL and what you want fixed — you get a clear scope, price and timeline.
To：[email protected] | Cc：[email protected]
