Troubleshooting
WordPress Not Displaying Correctly: A Simple Guide

Short answer
WordPress usually displays incorrectly when stylesheets fail to load, a cache serves old files, an update causes a plugin or theme conflict, or site URLs are wrong after a move. Check a private window, clear every cache and test with optimization turned off.
Key takeaways
- Plain unstyled pages mean the CSS files are not loading.
- Clear plugin, host, CDN and browser caches in that order.
- Minify and combine settings are a frequent cause of broken layouts.
- Wrong site URLs and mixed content often follow a migration.
- The browser console and network tab show what failed to load.
Why is WordPress not displaying correctly?
WordPress usually displays incorrectly because stylesheets fail to load, a cache serves old or broken files, a plugin or theme update causes a conflict, or the site URL settings are wrong after a move.
A site that looks broken can mean many things. The page may show plain text with no styling, a layout that is out of place, missing images, or a design that only breaks on one device or browser.
The good news is that your content is almost never lost. The problem is nearly always in how the page is put together, not in the posts and pages themselves.
Start with the quick checks, then use the table to find the cause that matches what you see. Each section below explains one cause and its fix.
| What you see | Likely cause | First thing to try |
|---|---|---|
| Plain text, no styling at all | CSS files not loading | Check site URL and https settings |
| Old design after making changes | Browser, plugin or CDN cache | Clear every cache layer |
| Layout broken after an update | Theme or plugin conflict | Roll back or test with plugins paused |
| Broken only after a speed change | Minify or combine settings | Turn optimization off and retest |
| Page builder layout scrambled | Builder CSS needs regenerating | Regenerate builder CSS files |
| Fine on desktop, broken on phone | Responsive settings or mobile cache | Check mobile views and mobile cache |
| Images missing, padlock warning | Mixed http and https content | Update URLs to https |
What should you check first?
First, open the site in a private window and a second browser, because a page that looks fine there means the problem is your own browser cache rather than the site.
Private windows load the page without your stored cookies and cached files. If the site looks right there, clear your browser cache and the problem is solved.
Next, check whether the issue affects every page or just one. A single broken page points to that page's content or builder layout, while a site-wide problem points to theme, plugin or settings issues.
Finally, think about what changed. An update, a new plugin, a migration or a speed setting change in the last day or two is the most likely cause.
Are your CSS files failing to load?
If the page shows plain text, blue links and no layout, the browser could not load your theme's CSS files, often because of a wrong URL, an https mismatch or a blocked request.
Open your browser's developer tools and check the network tab for red, failed requests. The Chrome DevTools documentation shows how to inspect them.
A 404 on CSS files usually means the file path is wrong. A 403 means the server refused it, which can come from file permissions or a security rule.
Check Settings → General. The WordPress Address and Site Address must match the domain and protocol your site really uses, including https and www or non-www.
If permissions are the cause, our guide on setting correct file permissions in WordPress shows the usual values.
Is a cache showing an old or broken version?
Yes, caching is one of the most common causes, because your browser, a caching plugin, your host and a CDN can each keep an old copy of the page or its styles.
Clear each layer in order. Start with your caching plugin, then your host's cache, then your CDN, and finally your browser.
A mismatch between layers causes strange results. The page may use new HTML but old CSS, which scrambles the layout.
Our guide on how to clear cache in WordPress covers every layer.
If design changes still do not show, see fixing CSS changes not showing.
Did a speed optimization setting break the layout?
Minify, combine and delay features in caching and speed plugins often break layouts, because they change the order or content of CSS and JavaScript files.
Turn off CSS and JavaScript optimization in your speed plugin, clear the cache and reload. If the layout returns, one of those features caused it.
Turn the features back on one at a time. When the layout breaks again, you have found the setting that needs an exclusion.
Features that remove unused CSS are especially risky. They can strip styles that load only after a click, such as menus and pop-ups.
Did a theme or plugin update cause it?
If the site broke right after an update, the new version of a theme or plugin probably conflicts with your setup, and rolling back or testing with plugins paused will confirm it.
Pause all plugins and switch to a default theme on a staging copy. If the display returns to normal, turn things back on one by one until it breaks.
The Health Check and Troubleshooting plugin does this safely on a live site. It only changes what you see while you are logged in.
Our guide on fixing plugin conflicts walks through the testing process step by step.
If the theme is the cause, see our guide on fixing a theme that broke the site after an update.
Is the page builder layout scrambled?
Page builders such as Elementor store layout styles in generated CSS files, and when those files are outdated or missing, the page loses its spacing, columns and colours.
Most builders have a tool to rebuild these files. In Elementor, look for the option to regenerate CSS and data in its tools settings.
After regenerating, clear every cache. The builder's new files will not appear if a cache still serves the old ones.
Check that the builder and its add-ons are up to date and match each other. An add-on built for an older version can break layouts after the main builder updates.
Did the site break after a migration or domain change?
After a migration, display problems usually come from old URLs still stored in the database, so pages try to load styles, images and scripts from the old domain or over http.
Run a search and replace on the database to update the old URL to the new one. Use a tool that handles serialized data, or changes can corrupt your settings.
Check the site URLs in Settings → General too. If you cannot reach the dashboard, the values can be set in wp-config.php.
Our guide on fixing broken links after migration explains the full search and replace process.
Is mixed content breaking the display?
Mixed content happens when a secure https page loads files over plain http, and browsers block those files, leaving missing styles, images or scripts.
Look for a warning next to the padlock in the address bar, or check the browser console for mixed content messages. MDN explains the rules in its page on mixed content.
Update the site URL to https and replace old http links in the database. Hard-coded links in theme files or widgets need fixing by hand.
Our guide on fixing mixed content warnings covers the tools and steps.
Is the site only broken on mobile?
If the site looks right on desktop but broken on phones, the cause is usually responsive settings in the theme or builder, a separate mobile cache, or content that is wider than the screen.
Page builders let you set different spacing and sizes per device. A value set only for desktop can look wrong on a phone.
Some caching plugins keep a separate mobile cache. Clear it after design changes, or the phone keeps showing the old layout.
Wide images, tables and embedded content can push the page sideways. Our guide on how to fix WordPress mobile view covers these problems.
Is your child theme stylesheet loading?
If you use a child theme and your custom styles are missing, the child stylesheet may not be enqueued correctly, or the parent theme's styles may load after it and override your changes.
Check the page source for the child theme's style.css file. If it is missing, the functions file in the child theme needs to enqueue it.
The WordPress guide to including CSS and JavaScript shows the correct method. Our guide on child theme style.css not working covers the common mistakes.
How do you find the cause when nothing obvious stands out?
Turn on debugging, check the browser console for errors, and compare the broken page with a backup or staging copy, because a JavaScript error or PHP warning often explains the display problem.
A single JavaScript error can stop sliders, menus and tabs from working, which makes the page look broken. The console shows the file that caused it.
PHP warnings printed on the page can also push the layout out of place. Logging them to a file, rather than showing them, keeps the page clean while you fix the cause.
If you are still stuck, restore a recent backup to a staging site and compare. The difference between the working and broken copies usually points straight to the cause.
Frequently asked questions
Why does my WordPress site look different in another browser?
Different browsers may hold different cached versions, or one may block files that another allows. Open the site in a private window in each browser to compare. If only one browser shows the problem, clear its cache and check its console for blocked files or errors.
Will clearing the cache delete my content?
No. Caches only store temporary copies of pages and files to make the site faster. Your posts, pages, settings and media stay in the database and uploads folder. The cache rebuilds itself as visitors load pages again.
Why does my site look broken only when I am logged out?
Logged-out visitors usually see cached pages, while logged-in users often bypass the cache. If the site breaks only when logged out, a page cache or optimization setting is the likely cause. Clear the cache and retest with optimization features turned off.
Can a WordPress update break my site's display?
Yes. A core, theme or plugin update can introduce a conflict or change styles. Test with plugins paused and a default theme to find the cause, roll back the update if needed, and check for a fixed version from the developer.
Sources
- Health Check & Troubleshooting WordPress.org Plugins
- Including CSS & JavaScript WordPress Developer Resources
- Mixed content MDN Web Docs
- Chrome DevTools Chrome for Developers
Is your product missing, or something out of date?
Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.
Thanks — we review requests within 3 business days.
Related guides
About the editors
Researched from the primary sources listed above and checked against our editorial rules before publishing.


