A JavaScript error is breaking your page

First, open Developer Tools to see the failing file

If you checked your domain on kortaga.com/check, our check tests whether your home page's scripts and stylesheets actually load; otherwise you can see both missing files and runtime script crashes in your browser's Developer Tools.

1. Test your page in a private or incognito window (or in a second browser) first, so a browser extension such as an ad blocker or privacy tool is not what blocked the script.
2. Open Developer Tools on your page: in Chrome, Edge, or Opera press F12 (or Ctrl+Shift+I on Windows and Linux, or Cmd+Option+I on a Mac) and select the Console tab; in Firefox press F12 (or Ctrl+Shift+K / Cmd+Option+K) and select Console; in Safari open Settings → Advanced, enable Show Develop menu (or Show features for web developers), and choose Develop → Show JavaScript Console (or press Cmd+Option+I).
3. Reload the page while Developer Tools is open. Some errors and network requests only appear during page load, and the Network panel only records activity while DevTools is open.

If a script or stylesheet failed to download (Network tab)

When a <script src> or <link rel="stylesheet" href> points to a file that was deleted, moved, or hosted on a third-party widget domain that expired, any code on your page that waits for that file stops working.

1. In Developer Tools, click the Network tab and reload the page so the Network Log records every file the page requests.
2. Look at the Status column (the HTTP response code) and the Initiator column (what caused the resource to be requested). A row with status 404, 410, or 500, or a failed DNS lookup, is a file the browser could not load.
3. Hover over the file's cell in the Name column to see its full URL, or click the link in the Initiator column to jump straight to the line of HTML or script that requested it.
4. If the missing file belongs to an old chat widget, booking tool, or analytics snippet you no longer use, remove that <script> tag from your site's header or footer. If it belongs to an active theme or plugin, reinstall or update that theme or plugin so the missing file is restored.

If a script crashed while running (Console tab)

Each JavaScript error in the Console tab has a name (the type of error), a message, and on the right side the file name and line number where it occurred (for example, jquery.js:2). Expanding the error shows the full stack trace.

1. Read the error type and file path

1. Three error types account for most broken menus, sliders, and forms on small-business sites:ReferenceError: "x" is not defined TypeError: "x" is not a function TypeError: null/undefined has no properties
2. Look at the file path on the right side of the red error line. In WordPress, a path containing /wp-content/plugins/plugin-name/ or /wp-content/themes/theme-name/ tells you which plugin or theme threw the error.
3. A ReferenceError (such as jQuery is not defined) usually means a script ran before the library it depends on was loaded, often because a caching or optimization plugin reordered, deferred, or combined your JavaScript files. Turn off JavaScript concatenation or deferral in your caching plugin and reload the page.

2. In WordPress, test with SCRIPT_DEBUG enabled

1. WordPress loads minified JavaScript and CSS files by default. If the error points to a minified core file, enabling SCRIPT_DEBUG in wp-config.php forces WordPress to load the full, uncompressed versions of core CSS and JavaScript files instead:define( 'SCRIPT_DEBUG', true );
2. Place that line in wp-config.php before the comment /* That's all, stop editing! Happy blogging. */, reload your site, and check whether the error disappears or shows a clearer line number.
3. When you finish diagnosing the issue, set SCRIPT_DEBUG back to false (or remove the line) and update, replace, or deactivate the plugin or theme named in the stack trace.

These steps follow the WordPress Developer Handbook's guides on Using Your Browser to Diagnose JavaScript Errors and Debugging in WordPress (SCRIPT_DEBUG), MDN's JavaScript error reference, and Chrome DevTools' guides to the Network panel and Console messages, all read 27 October 2026.

If you would rather we write it for you

If you would rather we repair the site or build a clean one-page site on your own domain, it is USD 150, live within 7 days of the day you approve the draft or every dollar back, first year of hosting included. Terms at kortaga.com/sites.