Something on the page scrolls sideways. A sticky header stops sticking. A button\nwill not take a click. Frontend Doctor looks at the page as your browser has\nactually laid it out, and shows you the element responsible.<\/p>\n\n
It runs entirely in your browser, on the page you are already looking at.\nNothing is uploaded, nothing is stored, and nothing is sent anywhere. There is\nno scan history, no dashboard of scores, and no database table - close the panel\nand the plugin has left no trace but the file it was installed from.<\/p>\n\n
Five checks<\/strong><\/p>\n\n Built to stay out of the way<\/strong><\/p>\n\n Only administrators see it. A logged-out visitor loads none of it - not a byte,\nnot a tag, not a request. An administrator browsing their own site carries a\nlauncher of well under two kilobytes, and the diagnostic engine is fetched only\nwhen they ask for it.<\/p>\n\n The two files in With Node.js 18 or newer, in the plugin directory:<\/p>\n\n That rewrites The human-readable JavaScript source is in No. The scan runs in your browser. The plugin makes no network request of its\nown, has no REST route, no admin-ajax endpoint, and no analytics.<\/p><\/dd>\n No. It creates no options, no transients, no user meta and no database tables.<\/p><\/dd>\n No. It requires the No. It reads the page and draws on top of it. It never writes to your content,\nnever applies a fix, and never modifies the layout it is measuring.<\/p><\/dd>\n\n<\/dl>\n\n\n\n
Rebuilding the compiled JavaScript<\/h3>\n\n
assets\/js<\/code> are compiled. Everything they are compiled from\nships beside them, in assets\/src<\/code>, along with the script that compiles them.<\/p>\n\n\n
npm install<\/code> - installs one dependency, the esbuild bundler.<\/li>\nnpm run build<\/code><\/li>\n<\/ol>\n\nassets\/js\/khfd-launcher.js<\/code> and assets\/js\/khfd-runtime.js<\/code> from\n assets\/src. The build is deterministic: on an unmodified copy of the plugin it\nreproduces the two shipped files byte for byte.<\/p>\n\nassets\/src<\/code>, and scripts\/build.js<\/code>\nrebuilds the two compiled bundles from it; both ship in this package. The\npublic source repository contains the same source and the build material needed\nto rebuild the distributed JavaScript. The internal test suites, linters and\nrelease tooling are not part of this package or of the public source\nrepository.<\/p>\n\n\n\n
\/wp-content\/plugins\/<\/code>, or install it through the\nPlugins screen.<\/li>\n\n
Does anything leave my site?<\/h3><\/dt>\n
Does it store anything?<\/h3><\/dt>\n
Can editors use it?<\/h3><\/dt>\n
manage_options<\/code> capability, which in practice means\nadministrators.<\/p><\/dd>\nWill it change my site?<\/h3><\/dt>\n
1.0.0<\/h4>\n\n
\n