Newspaper Theme fix
Newspaper Theme Site Slow? Ads, Blocks and Images Come First
A Newspaper site is rarely slow because of one thing. It is slow because the front page runs a query for every block, prints dozens of thumbnails and then hands the browser to several ad networks. Speeding it up is mostly subtraction, done in order of what costs the most.
What you are seeing
- The front page shows its header, then waits before any headline appears
- Articles jump around as ads and images arrive late
- PageSpeed Insights blames third-party code and oversized images
- The site slows sharply when a story gets shared widely
- Load more buttons and block filters take a second or two to answer
Why it happens on Newspaper Theme
Most common first.
- 1
A query for every block on the page
Each post block asks the database for its own list of articles. Twenty blocks mean twenty queries before the page can be assembled, and blocks sorted by popularity or at random cost more than blocks sorted by date. Without caching, every visitor pays for all of them.
- 2
Images larger than the cards they sit in
Flex blocks let an editor choose the image size block by block, and the Theme Panel decides which sizes get generated at all. Pick a large size for a small card, or switch off the size a block expects, and the browser downloads far more than it displays. Multiply that by sixty thumbnails on a front page.
- 3
An ad stack that outweighs the page
The Theme Panel's ad spots make it easy to fill the header, the sidebar and several positions inside each article. Every network brings scripts that fetch more scripts, run auctions and resize their slots after load. Much of the processing time and most of the layout shift come from there.
- 4
Block Ajax that goes around the page cache
Load more, next and previous arrows and the category filters on blocks fetch their results through WordPress's admin-ajax endpoint. A page cache does not serve those requests, so each click runs PHP and the database in full. Infinite loading on a busy page turns readers into a steady stream of uncached requests.
- 5
Extras the demo brought and nobody removed
A demo front page is built to show everything the theme can do at once, which is not what a reader needs. Sliders, a ticker, social counters, weather widgets and several font families stay on. So does tagDiv Standard Pack, which loads the classic headers and templates whether or not the site still uses them.
How to fix it, in order
Least invasive first. Stop at the step that fixes it.
- 1
Measure an article and the front page separately
Run both through PageSpeed Insights on mobile and note three readings for each: server response time, the largest element and the third-party total. Articles and front pages are slow for different reasons, and the split tells you where to begin.
- 2
Cut and simplify blocks in tagDiv Composer
With a backup taken, open the front page in the Composer and remove blocks below the point readers stop scrolling. Lower the post count on the rest. Change random and popularity sorting to latest wherever the difference is not editorial, and swap infinite loading for ordinary pagination.
- 3
Turn on the cache inside the blocks that remain
Flex blocks have a cache option in their settings that stores the block's query result for a set time, from a minute to a week. Use it on blocks that change slowly. It does not clear when a new post is published, so give breaking-news blocks a short time or none. The stored data can be cleared from Newspaper, System Status.
- 4
Correct the image sizes
In each block's settings choose an image size close to what the layout displays. In the Theme Panel's block settings, make sure the thumbnail sizes those blocks use are switched on, then regenerate thumbnails with a plugin made for the job so older posts get the right files. On a large archive, run it in batches during quiet hours.
- 5
Audit the ad spots
Go to Newspaper, Theme Panel, Ads and list every spot in use. Drop the networks that earn little, keep the count above the fold low on phones and reserve a fixed height for each slot so the article stops shifting. Ask your ad provider about lazy loading for slots further down.
- 6
Set up page caching the way this theme needs
Use one page cache and confirm it serves hits. If the tagDiv Mobile Theme plugin is active, phones receive a different theme, so the cache must keep separate mobile and desktop copies. Enable Newspaper, Theme Panel, Post Settings, Ajax view count so views still register on cached pages. On staging, deactivate tagDiv plugins the site does not use and test whether it still needs Standard Pack. The general method is in our WordPress speed guide.
Keep it from coming back
- Give the front page a block budget and remove one whenever you add one
- Decide image sizes per block once and write them down for editors
- Review ad and tracking scripts every quarter and drop what does not pay
- Re-test on a phone after every theme update and every new ad partner
The permanent fix
A faster Next.js build, with a CMS made for your business
If the site is still slow on phones after the blocks are cut, the images are right and the ad stack is lean, what remains is the theme's own baseline and WordPress assembling pages on request. That is the point where a rebuild pays. A Next.js front end serves every article as a prebuilt static file and sizes each image for the slot it fills, while editors publish from a custom CMS with no block builder between them and the story.
| On Newspaper Theme today | On Next.js with a custom CMS | |
|---|---|---|
| What you keep updated | WordPress, the theme, its builder and every bundled plugin, all in step | Nothing on a schedule. There is no theme or plugin stack to fall out of step |
| How a page is served | Built from the database on each visit, through the theme and its builder | Built ahead of time and served as finished files from servers near the visitor |
| How you edit it | A general-purpose builder with every option the theme ships | A CMS built around what your business actually changes: services, prices, photos, posts |
| What can break it | An update to any one of those parts, or a license that lapses | A change someone makes on purpose, tested before it goes live |
Your content, your addresses and your rankings come with you: every page is moved, every old address is redirected, and you get a login to an editor that only shows what you need. A repair is still the right call for many sites, and we will say so when it is.
Want this fixed on your Newspaper Theme site?
Tell us what you are seeing. We look at the site, tell you plainly what is wrong and what it takes, and quote a fixed price before any work starts.
Which of these sounds like you? (pick any)
Frequently asked
Any well-configured page cache works. Three things need care: separate mobile and desktop copies if the tagDiv Mobile Theme plugin is active, script optimization kept away from logged-in editors so tagDiv Composer still opens and the Ajax view count switched on in the Theme Panel. Block pagination will still reach the server, since those requests skip the page cache.
There is no fixed number, and anyone who quotes one is guessing. The useful test is behavioral: see how far readers scroll and question every block past that point. Many front pages carry blocks no reader reaches, and removing those costs nothing editorially.
Often, yes. Open PageSpeed Insights and compare the third-party total with what your own domain serves. On ad-supported news sites the outside scripts commonly take the larger share of processing time. Changing themes does not change that, which is worth knowing before you pay for a redesign.
It can help, since it serves phones a simpler theme. The costs are a second design to maintain, a Mobile Theme tab in the Theme Panel with its own ad and menu settings and a cache that must tell phones from desktops. Trim the main responsive design first. If you do enable it, check ads and analytics on the mobile version separately.
Keep reading
- ServiceWordPress Speed & OptimizationA slow site loses customers before they read a word. We tune WordPress for speed, stability, and search — measured, not guessed.
- ServiceSite Speed & Core Web VitalsA slow site loses the customer before they see your offer. We fix what makes pages crawl — heavy images, bloated scripts, blocked rendering — and prove it with numbers.
- ServiceWebsite Hosting & Maintenance PlansThe watching after launch: managed hosting, tested updates, backups that restore, security and uptime monitoring, and small edits done within a day, month to month.