Newspaper CSS Not Loading: Missing Styles, Scrambled Blocks and the Tools That Cause Them

Where a Newspaper page gets its styles

Owners expect a theme's styles to live in the theme folder. On Newspaper, most of them do not. When we loaded tagDiv's public Newspaper Pro demo in October 2026 (running 12.6.7), it requested four stylesheets: the theme's own style.css, a multi-purpose stylesheet and a file called td_legacy_main.css from the tagDiv Composer plugin, and tdb_main.css from tagDiv Cloud Library. Then came a long run of inline styles printed into the page itself.

Those inline styles are the part people miss. A tagDiv staff member explained in 2023 that every element on a Composer page carries its own CSS, because the same element can appear many times on one page with a different layout each time. So a single homepage carries dozens of small style blocks, one per element, written by Composer when the page renders. That design is what makes the Newspaper theme flexible, and it is also what optimizers love to grab, merge and move.

Read the damage before you touch a setting

The shape of the breakage tells you which layer failed. Look at a page and a post side by side, logged out, in a private window.

Then confirm with the browser. Press F12, open the Network tab, tick Disable cache, filter to CSS and reload. Any stylesheet that is not a plain 200 is your lead, and its address says who wrote it: a path under td-composer or td-cloud-library is tagDiv's plugin, a path under a cache folder is an optimizer bundle. The general method is in WordPress theme CSS not loading.

Minify inline CSS and Aggregate inline CSS: two switches with a warning label

Version 12.6, released in September 2023, added Theme Panel options for minifying and aggregating block inline CSS, in the changelog's words. A tagDiv staff member named their home in a 2023 forum answer as Theme Panel > Block Settings, with the labels Minify inline CSS and Aggregate inline CSS, and added a plain warning: if you use WP Rocket, they can cause problems, so do not use them. Another staff answer that month said the same of any extra cache or CSS optimization plugin.

The reason is mechanical. Aggregating collects all those per-element style blocks into one. A cache plugin's own CSS features then try to minify, combine, defer or strip the same styles. Two programs rewriting one stylesheet rarely agree on what the other has done. Version 12.6.5 even shipped a fix for a lazy-loaded video on mobile whose inline CSS clashed with the aggregate option, so the feature has edges tagDiv itself is still sanding.

The 2023 case in the lede is instructive. After 12.6, an owner running Cloudflare, WP Super Cache, EWWW, SWIS Performance and Autoptimize saw misaligned blocks and missing featured images. The owner rolled back to 12.5.1, which fixed it; when staff then asked about the inline CSS options, the owner could not find them. Whatever the exact trigger, five tools touching one stylesheet is the pattern to remove. Option names can move between releases, so check them against your own Theme Panel before you rely on this page.

The CSS Analyzer leaves its CSS behind

tagDiv's CSS Analyzer runs from the admin bar on the front end. It removes CSS a page does not use, generates critical CSS for the first screen, and, since version 11, moves non-critical CSS to the footer. Forum answers describe a Remove button and a Generate critical CSS button on pages, with only generation available on templates. It works on pages, including mobile pages, but not on posts, post templates or the Mobile Theme.

tagDiv staff have called it a beta several times, most bluntly in 2023: it interferes with the style, so remove the CSS it generated. A 2021 staff answer pointed users to a button labeled Remove generated CSS. One owner later found that button disabled on his install, and staff replied that nothing was wrong if the feature was not active. So check whether a page has generated CSS at all before you blame it.

The pages-but-not-posts limit makes it easy to spot. If landing pages and the homepage lost their styling and articles did not, the Analyzer is the first suspect. A forum user's step-by-step guide says to switch off your cache plugin while the Analyzer runs, and staff troubleshooting advice says the same. Our Newspaper speed guide covers when it is worth using at all.

The tool that removes unused CSS can only judge what it saw, and it never saw your posts.

Putting Newspaper's styles back, in order

1. 1

   Copy the site first

   Take a backup or work on a staging copy. CSS fixes involve purging and regenerating, and you want a way back.

2. 2

   Confirm tagDiv's plugins are active

   On the Newspaper plugins screen, check that tagDiv Composer and tagDiv Cloud Library are active and current. Their stylesheets carry much of the layout.

3. 3

   Pick one CSS optimizer

   Either the Theme Panel's Minify inline CSS and Aggregate inline CSS, or your cache plugin's CSS minify, combine and unused-CSS features. Switch the other side off completely.

4. 4

   Remove Analyzer output on broken pages

   If only pages are affected, open one with the CSS Analyzer and remove the generated CSS. Do this with the cache plugin off.

5. 5

   Purge every layer

   Clear the optimizer's cache, the page cache, the host's cache and the CDN, in that order. Cached HTML that names deleted bundles is the classic cause of 404 stylesheets.

6. 6

   Check the CDN rules

   Open each stylesheet address directly. If the CDN returns an error or an old file, exclude that file from the CDN or fix the rule, then purge again.

7. 7

   Test pages, posts and phones

   Check the homepage, a landing page, an article and a category page, logged out, on a desktop and a real phone. If the Mobile Theme is active, make sure your cache keeps a separate mobile copy, as tagDiv's Mobile Theme guide requires for cache plugins other than WP Super Cache.

If the styles load but your changes do not appear, that is a different problem with a different fix: see CSS changes not showing. If the layout breaks only after a plugin update, our plugin conflict guide walks the isolation test.

Rules that keep the styles where they belong

• One owner for CSS optimization. Write down which tool it is and switch the equivalent features off everywhere else.
• Keep the CSS Analyzer to a few simple pages, as staff advise, and keep a list of which pages have generated CSS.
• Purge every cache layer after a theme update, a Composer template change or an optimizer setting change, not just one.
• After each update, compare a page and a post logged out. The pages-versus-posts split catches Analyzer trouble early.
• Keep tagDiv's plugins updated in the same session as the theme, so the stylesheets and the markup that expects them match.

A broken menu often turns out to be a styling fault in disguise, which is why Newspaper mobile menu not working checks stylesheets too. Script failures that leave blocks half-drawn belong to Newspaper JavaScript errors, and the wider set of known faults is in the Newspaper repair hub.

Five tools and one stylesheet

Newspaper's styling is split between the theme, two plugins and inline blocks written per element. tagDiv then offers two ways to optimize it, its own speed guide recommends adding Autoptimize and Cloudflare, and most owners add a cache plugin with CSS features of its own. Every one of those tools is sensible. None of them was tested against the others on your site.

A Next.js build compiles its CSS once, at build time, into files named after their contents, and ships the HTML and CSS of a release together. Nothing on the live server rewrites them later. It costs more to build and needs a developer for layout changes, which is the honest trade. Newspaper vs Next.js lays it out for publishers, Newspaper to Next.js covers the move, and Athena CMS keeps the editing simple afterwards. To keep Newspaper running cleanly instead, our theme repair service fixes the stack on a fixed quote, and more fixes live in WordPress troubleshooting.