The settings screen is a single script that draws every section after the page loads. If you see only the heading and the line “If the controls do not appear, reload this page,” the script did not run. Reload once. If it happens again, something on the page or in the browser is stopping it, and the list below finds it in a few minutes.
Reload, then try a clean browser
A slow connection can leave the page half loaded; one reload fixes most reports. If the controls are still missing, open the same page in a private window or another browser. Content blockers and privacy extensions sometimes block scripts on admin pages, and a private window usually runs without them. If the controls appear there, allow your site’s admin in the extension.
Look at the browser console
Open the browser’s developer tools (F12 in most browsers) and select the Console tab, then reload the settings page. A red error names the script that failed. If it comes from another plugin’s file, that plugin is breaking the page before WP Visibility’s script runs; deactivate it briefly to confirm. If the error mentions a blocked request, continue below.
Optimization and security plugins
Plugins that combine, defer or minify scripts sometimes do so on admin pages too, and the settings screen’s script must load in order and unmodified. Exclude wp-admin from optimization, or exclude the handle wpvis-settings.
Saving settings goes through the WordPress REST API at /wp-json/wpvis/v1/. A firewall or security plugin that blocks REST requests lets the screen draw but stops every save with an error. Allow that path for logged-in administrators.
Permissions
The menu and the screen are for administrators. A user without the manage_options capability sees neither. If you reached the page by URL as a lower role, that is why.
If none of that is it
Write to support@wpvisibility.com with your WordPress and plugin versions, the browser, and the first error line from the console. Those four facts usually settle it in one reply.