News sites are some of the hardest WordPress sites to make fast. Every article page carries a featured image, ads, share buttons, related posts, and a pile of plugin CSS and JavaScript — and readers on slow mobile connections in Pakistan bounce the moment the page feels heavy. When I rebuilt a small news site's performance setup, I set one rule for myself: no JavaScript delay tricks. Delaying scripts until user interaction inflates lab scores while breaking real functionality, and on a news site that means broken share buttons, dead comment forms, and menus that only wake up after a tap. The goal was a genuinely fast page, not a fast-looking lab report.
The first real win was unused CSS. WordPress themes and plugins ship stylesheets written for every possible layout, and a single article page typically uses a fraction of them. I turned on Perfmatters' "Remove Unused CSS" feature in its local mode — no external processing service, no cloud queue. It generates a small used-CSS file per page type and drops the rest. The important detail: this only works if you verify every template afterward. A homepage, an article page, a category archive, and a tool page all use different components, so I checked each one visually after enabling it. One missed selector and a layout breaks silently for readers who never report it.
The second win was the hero image. On article pages the featured image is the largest contentful paint element, so it has to be discovered early. Perfmatters already preloads the first image and serves it as WebP, so I did not add a second preload — duplicate preloads are a classic self-inflicted wound that shows up as wasted bytes in every audit. What mattered more was making sure the image dimensions were set, so the browser reserves the space and the page does not jump while loading. Layout shift is the metric readers feel even when they cannot name it.
The third decision was what NOT to enable. Perfmatters offers a JavaScript delay feature that would have pushed the score higher on paper. I left it off deliberately. On this site the interactive elements — search, menus, comment forms, tool widgets — need to work on first tap, not after a delay script decides the user has interacted enough. The same reasoning applied to other aggressive options: I enabled exactly one CSS optimization and verified it, rather than stacking five features and debugging the interaction between them.
The result, measured on mobile: a PageSpeed score of 96, largest contentful paint around 2.5 seconds, zero milliseconds of render-blocking time, and zero kilobytes of unused CSS reported. No script delay, no deferred interactivity, no broken widgets. The lesson generalizes beyond news sites: pick one optimization at a time, verify it on every template, and resist features that trade real functionality for lab points. A fast site that works is worth more than a faster-looking site that does not.
TimelyUps is a Pakistan news site covering breaking news, government schemes, and everyday guides — and its free tools section includes bill checkers, calculators, and study resources. Read more at
Top comments (0)