Newspaper Theme Speed: Ad Slots, Composer Pages and Heavy Archives

Where tagDiv hides the speed controls

The ThemeForest listing calls Newspaper blazing fast, which is a sales line, and says its JavaScript files are combined and minified automatically, which is a fact about the build. Everything else is spread across the Theme Panel, tagDiv Composer and a separate mobile plugin. The current release is 12.7.9. The panel names below come from tagDiv's guides and its support staff's answers on the tagDiv forum, so check them against your own Theme Panel before changing anything.

tagDiv's own speed guide adds outside tools on top: WP Super Cache for page caching, Autoptimize, Cloudflare as a CDN and EWWW Image Optimizer for WebP. That is a sensible kit and a frank admission that a news site's speed is decided outside the theme. Our theme speed test guide shows how to measure before you install any of it.

Ad slots: the layout shift you are paid to cause

An ad network decides what to show after the page has started drawing. If nothing reserves the space, the ad pushes everything below it down when it arrives. That is Cumulative Layout Shift, and on a news site it repeats in every slot on every article. Google measures it from real visitors, so the shift your readers see is the shift that counts.

tagDiv's support staff give the standard fix: wrap each ad code in a container with a fixed width and height that match a size your ad provider actually serves, such as 300 by 250. That applies to ads placed in Theme Panel > Ads and to Ad Box elements in Composer, where the element's CSS tab takes a width and height. Responsive units need a reserved minimum height for each screen size. In one forum thread staff could not fully cure shifts that appeared while scrolling, and suggested inline ads or a standard post style from the tagDiv Standard pack instead of a Cloud Library template.

For the general mechanism behind jumping pages, see theme layout shift and CLS on WordPress versus Next.js.

Sliders, Composer blocks and the front page that does everything

Newspaper's prebuilt sites open with motion: a featured slider, a ticker, several category blocks, a video row. Each Composer block that pulls stories by category is a database query and a set of thumbnails. A front page with fifteen of them is fifteen queries and dozens of images before the reader sees a headline, which is why page caching matters more on this theme than on most.

The changelog also shows two heavyweight third-party plugins riding along: Revolution Slider, updated to 7.2.0 in 12.7.9, and WPBakery, updated to 9.0.1 in 12.7.8. Whether every license includes both is not something the pages we read confirm. If yours are active and unused, deactivate them on staging and measure the difference. If a slider is the first thing on the page, it is probably your Largest Contentful Paint element, and it cannot show its first slide until its script runs.

• Replace the homepage slider with a single lead story and a correctly sized image.
• Cut category blocks to the sections readers actually click; your analytics will tell you which.
• Keep Composer for layout and let reporters write in the normal post editor.
• Check that nothing loads WPBakery or Revolution Slider assets on article pages that do not use them.

If Composer itself will not open while you work, see tagDiv Composer not loading. If a removed block leaves a script error behind, Newspaper JavaScript errors walks the console checks.

The CSS Analyzer: a beta tool with a narrow job

The tagDiv CSS Analyzer generates critical CSS for the first screen and removes unused CSS per page. On paper it is exactly what a heavy builder theme needs. In practice tagDiv's own staff describe it as a beta, recommend it only for pages with a few blocks and standard styling, and, when it misbehaved, told one user to remove the CSS it had generated because it was interfering with styles. Users also found it works on pages, not posts.

That last limit is the important one for a publisher. Search and social traffic lands on articles, and articles are posts. So the tool tagDiv built for speed does not touch the template that carries most of your audience. Use it, if at all, on a simple landing page, and check the result on a phone. Never run it alongside a cache plugin's own critical CSS or unused-CSS feature: two tools rewriting the same styles is how layouts scramble. When styles go missing afterwards, start with Newspaper CSS not loading.

The speed tool tagDiv built works on pages. Your readers arrive on posts.

Image-heavy archives: categories, tags and endless thumbnails

A news site's archive pages are thumbnail walls. Every category, tag and author page lists twenty or more stories, each with an image, and a busy site has thousands of these pages. They are often the slowest URLs on the site and the least watched.

• Some modules draw images as backgrounds. Staff note that certain blocks place images as CSS backgrounds in span elements, while standard blocks 1 to 25 use image tags. The browser finds background images later, which hurts LCP on the first row.
• Lazy loading is a single switch. Use Loading Animation Image applies site-wide, and staff say the theme cannot set conditions. If the lead image on articles waits behind a placeholder, test with the switch off and rely on WordPress's own native lazy loading.
• Thumbnail sizes drift. Images uploaded at camera size and squeezed into small cards waste bandwidth. Regenerate thumbnails after changing layouts, and serve WebP through EWWW or Cloudflare as tagDiv's guide suggests.
• Thin tag pages multiply. Thousands of tag archives with one or two stories cost crawl budget and server time. Decide which deserve to exist before you optimize them.

Our slow LCP checklist covers the image mechanics, and LCP on WordPress versus Next.js shows how a framework finds the lead image early by design.

Tuning a Newspaper site, ten steps in order

Work on a staging copy and change one thing at a time. Measure the article template first, because that is where readers land, then the homepage, a category page and the mobile layout.

1. 1

   Measure the article template

   Run several articles through PageSpeed Insights and check Search Console's Core Web Vitals report, which groups similar URLs. Our guide to reading PageSpeed Insights for a theme explains what each number means.

2. 2

   Check PHP, then update

   Release 12.6 required PHP 8.0 or later and left some sites blank. Confirm your PHP version on staging, update to the current release, and click through an article, the homepage and a category. Newspaper update problems covers the recovery.

3. 3

   Add one page cache and a CDN

   tagDiv's guide uses WP Super Cache and Cloudflare. Any single, well-configured page cache works; two do not.

4. 4

   Fix every ad slot's size

   Wrap each ad in a container of fixed width and height, in Theme Panel > Ads and in every Ad Box.

5. 5

   Trim fonts

   Cut Google Fonts to two families, or switch off Use Google Fonts on Mobile and test system fonts on phones.

6. 6

   Decide on lazy loading

   Check whether the lead image waits behind the loading animation. If it does, test the site with the Theme Panel switch off.

7. 7

   Simplify the homepage

   Replace the slider with a lead story, cut unused category blocks and deactivate unused bundled plugins.

8. 8

   Pick one CSS optimizer

   Either the Theme Panel's Minify and Aggregate inline CSS options or a cache plugin's CSS features, not both. Keep the CSS Analyzer to simple pages.

9. 9

   Test the Mobile Theme both ways

   Measure phones with the tagDiv Mobile Theme on and off. Keep whichever passes, and remember a second layout means second testing.

10. 10

    Retest and keep watching

    Field data runs on a 28-day window, so recheck next month. Then set a monthly check on the article template.

What the Theme Panel cannot reach

• The ad stack. Networks, bidders and their scripts are the heaviest code on most news pages, and the theme does not control them.
• Uncached traffic. Logged-in editors, paywalled readers and comment submissions bypass the page cache and hit PHP and the database.
• Database load from a large archive. Thousands of posts and tag pages need hosting sized for them.
• Composer's markup. Blocks render the wrappers they render; fewer blocks is the only real reduction.
• Bundled plugin weight. Revolution Slider and WPBakery load their own assets where they are active.
• Embeds. Social posts, videos and newsletter forms pull code from other servers into every story that uses them.

When you reach these limits, tuning has done its job. Our theme speed optimization service handles the tuning on a fixed quote, the Newspaper slow website guide is the repair route for a site already in trouble, and the Newspaper repair hub gathers every other fix. For a broader view of how themes compare on vitals, see themes for Core Web Vitals.

When a publication outgrows the theme

A local news startup or niche magazine can make Newspaper fast enough with the steps above, and should. The case for a rebuild is a publisher whose income rides on article pages: ad revenue that drops when Core Web Vitals fail, search traffic at volume, or a paywall that needs real member levels. At that point the limits above are the business, not a footnote.

A Next.js build prerenders articles and serves them from a CDN, reserves the exact height of every ad slot in code, loads ad tags after the story is readable, and sizes every image with next/image. It costs more up front and needs a developer for structural change. Newspaper vs Next.js weighs that trade for newsrooms, and Newspaper to Next.js shows how an archive moves with every article, tag and author URL kept or redirected.

Editors work in Athena CMS, with plain fields, a real preview, every version kept and membership areas with Stripe subscription billing. Argus flags templates that slow down. Start with a free site audit, or browse the other WordPress theme reviews first.