WordPress history, from 4.9 to the Gutenberg era
WordPress 4.9 was "the calm before the storm." We analyze this pivotal moment in WP history that prepared the ground for the block editor. What changed since? How did the ecosystem evolve?
Hiring WordPress developers in Nottingham usually means weighing a local agency against a freelancer, and sometimes against someone abroad. I run WPPoland by myself from Gdynia, on the Polish coast. No Nottingham office exists. Work happens remotely and in writing, and a reply reaches you inside 48 hours. Poland keeps its clocks an hour ahead of Britain all year, which hardly matters when email and shared documents carry the job.
Use the list below on every candidate you speak to, me included.
Start with a short message through the contact form: the site, its hosting and the problem. You get my first reading of it by email, no later than the second working day. Scope, dates and the fee are then put in writing, and work begins only after you accept.
The build lives on a Git branch and meets a staging copy. I add behaviour through hooks and blocks and leave WordPress core untouched. Before release I click through the enquiry form, the cookie banner, keyboard navigation and the pages your customers land on. Releases avoid your busy weeks and keep a route back. At the end you get written notes.
Since 2006 I have been on wordpress.org, sending patches to WordPress core and keep plugins in the official directory up to date. For the wider list of services, see the WordPress developer overview.
Legal advice is not my job, and you decide what applies to your company. What follows are the points I check on a site, each pinned to the wording of the law.
A limited company must show certain particulars online. Under regulation 25 of the 2015 company disclosure rules, a website carries the UK nation of registration, the company number and the registered office. The registered name is required by regulation 24(2). I place all four in the footer and check them against the Companies House record.
PECR regulation 6 now opens with the words “subject to Schedule A1”. The wording took effect on 5 February 2026 under the 2025 Data (Use and Access) Act. Within Schedule A1, consent is not needed for storage that is strictly necessary to deliver what the visitor requested. Storage used only to count how a site is used, so you can improve it, is exempt too, as long as nothing is passed on for other purposes, visitors are told plainly what happens and can object without paying or jumping through hoops.
My routine: open the site in a fresh browser, note every cookie and script that fires on arrival, and divide them into exempt and not exempt. Consent tooling and tag loading are configured so the second group stays idle until a visitor agrees. Whether a given analytics tool is statistics only is for you and your adviser to decide.
In the UK GDPR, Article 33 sets the clock at 72 hours from the moment you learn of a breach, where feasible, before the regulator must hear of it. A late notice has to explain the delay. A breach unlikely to endanger anyone’s rights and freedoms need not be notified. Every breach still goes into the controller’s own record.
Sites collect enquiries, accounts and sometimes orders, so a compromise puts personal data in play. Logs decide how fast you can answer. My part is technical: where the data lives, which plugins reach it, how long logs survive, and a timeline. Reporting is your decision.
Equality Act 2010 provisions (section 29, subsection 7) extends the duty of reasonable adjustments to anyone providing a service. A site is often the front door to that service. So labels, colour contrast, keyboard paths and clear error messages belong in the build. I test the templates customers use, repair theme-level faults and flag anything caused by third-party plugins.
The WordPress.org UK meetup directory names groups for Birmingham and Sheffield but none for Nottingham, Derby, Leicester or the rest of the East Midlands. I have no local scene to point to, so I do not claim one. Protection comes from how the work is packaged: code in your own Git account, documents you hold and a staging site, which lets any later developer continue without me.
No. I work alone from Gdynia, Poland, one time zone east of the UK. Email and documents carry the job, and each message gets a written answer inside 48 hours.
Not the design itself. Layouts, graphics and wireframes are supplied by you or whoever designs for you, and I implement them as a quick, accessible WordPress theme.
Yes. Regulation 25 asks for the nation of registration, the company number and the registered office address. Regulation 24 asks for the registered name.
Tell me about the site and its host, and say whether a staging copy exists, using the contact form. My written reading follows within two working days.
Examples of my work.
The Dune City website was built for a prestigious apartment complex located on the 10-kilometre spit separating the Baltic ...
The lifetree.pl website is a platform dedicated to personal development, healthy lifestyle, and inspiration from nature. The project was created for users se...
Linkr.pl is an online portal launched in 2007 as an alternative to Wykop.pl, which at that time dominated the Polish “social news” market. The project was in...
Describe your project by e-mail. I reply within 48 hours.
Describe your projectWordPress 4.9 was "the calm before the storm." We analyze this pivotal moment in WP history that prepared the ground for the block editor. What changed since? How did the ecosystem evolve?
Compare the best WordPress plugins in 2026 for security, SEO, cache, backups, and image optimisation, with practical advice on what to install and what to avoid.
Gutenberg blocks, synced patterns, full site editing, custom templates, and block plugins for teams that want a cleaner WordPress editing system.
CrUX field-data audit with per-template LCP, INP, CLS attribution.
Core Web Vitals, caching, and faster delivery.
A free check of your site's public version, results on screen.
Stability, updates, and post-launch support.
Updates checked before release, with a report.
Migration to Astro, Next.js, and headless WordPress.
Audit, hardening, and incident risk reduction.

How to optimize Interaction to Next Paint (INP) on WordPress sites. Practical fixes for the newest Core Web Vital metric that directly impacts Google rankings.

Field versus lab, LCP, INP and CLS for WordPress in 2026. Google's green LCP is still 2.5 s in CrUX. 100/100 in Lighthouse is a lab target. Edge HTML, consent banners, checkout widgets.

How we took a slow WooCommerce site from score 45 to 100. A technical deep dive into Speculation Rules, AVIF, and Critical CSS in 2026.