Astra Telematics

Astra Telematics makes IoT telematics hardware and provides platform and data SIM services, and its WordPress site is where fleet and asset-owner buyers read the product range. It had seven reported problems: a messy blog, a contact form that was not reliably sending, a menu with mismatched text, slow pages, product filters that reloaded the whole page, an Applications page with empty tabs, and a backlog of updates. Reidify took it on as a paid one-week pilot, 21 to 27 October 2026. The rule for the week was simple: back up first, change one thing at a time, check it as a visitor sees it, and write every change down with a way back.

WordPress was rebuilding every page for every visitor, which took two to three seconds before it sent anything. Page caching now keeps a ready copy. Measured as time to first byte, the median of five runs for a visitor who is not logged in, every key page fell from between 2.6 and 4.3 seconds to about half a second: the home page from 3.05 seconds to 0.55, the product listing from 4.32 to 0.52. That is between 4.6 and 8.3 times faster to first byte, across six pages. The caveats below belong to every one of those figures.

Fixed: the blog layout, where previews no longer repeat the title and the stray category label is gone; the dropdown menu, which now matches the main menu's font and size; the product filters, which reloaded the page on every tick because the filter plugin looked for the standard product list while that page uses a different one, and which now update the products at once; and the Applications page, rebuilt from the client's own text in their order, with an image on every tab and three empty tabs filled. Improved, not closed: the contact form, where a lost Microsoft 365 permission in the mail plugin was reconnected and every enquiry is saved, though delivery to the client's own inbox is not confirmed from their side; speed, covered above, with full page loads still to do; and updates, where 12 plugins were updated after a fresh full backup and checked after every batch, three plugins were removed, one that had never been set up was switched off, and the larger updates were held for testing on a copy.

Pages are not yet fast to load in full: that is the next stage of speed work and it is not done. The larger update project, the page builder, the theme and WordPress itself, is still to be tested on a copy before it touches the live site. And whether the contact form's notifications reach the client's own inbox is still to be confirmed from their side. None of this is tucked into a footnote: it is the work that is still ahead.

The client asked to continue, and the work is continuing as a monthly plan: tested updates with a backup first, an off-server backup copy, a weekly check that contact-form enquiries arrive, the larger upgrade done on a copy first, one speed improvement a month, and day-to-day requests. Month one also covers making the site easier for search engines and AI tools to read: page titles and headings, product data on product pages, company data on the homepage, and Google's indexing notices. That is agreed scope, not a result. No search or AI-readability figure appears on this page because none has been measured.