Skip to main content Skip to content
furyhost Get started
Joniel Rosales, full-stack WordPress developer and hosting specialist
Author profile

Joniel Rosales

Full-stack WordPress developer, SEO practitioner and hosting specialist. Everything on the FuryHost blog is written by me.

  • 15+ years web development
  • 10+ years SEO
  • ~10 years hosting & servers
  • Cebu City, Philippines

I build custom WordPress and I run the servers it sits on. That combination is the reason this blog exists: most WordPress advice online is written by someone who only ever sees one half of the problem, and the half they cannot see is usually where the actual fault is. A theme developer blames the host. A host blames the theme. Somebody who has done both can usually tell you which it is in about ten minutes.

What I actually do

I write code rather than assemble plugins. Custom themes and plugins, hooks and filters, custom post types, and modular theme architecture built on ACF flexible content — so an editor can lay out a page without a developer and without a page builder's markup. I work across Elementor, Divi, WPBakery and WooCommerce when a project already lives there, which is often.

WordPress development

  • Custom themes and plugins from scratch
  • Hooks, filters, custom post types
  • Modular architecture on ACF flexible content
  • Elementor, Divi, WPBakery, WooCommerce

Performance

  • Core Web Vitals — LCP, INP, CLS
  • Page and object caching strategy
  • Image optimisation and next-gen formats
  • Lazy loading, CDN, cutting plugin bloat

Hosting & DevOps

  • Linux administration and bash scripting
  • Site and email migrations
  • DNS, SSL, cPanel, Plesk, Cloudflare, Git
  • Staging to production, backups, rollback

Integrations & tracking

  • Webhooks and API work
  • Form-to-CRM: HubSpot, Pipedrive
  • Google Tag Manager, Meta Pixel
  • Zapier, Airtable

SEO

  • Technical SEO and site architecture
  • Schema and structured data
  • Internal linking strategy
  • GEO — optimising for AI search

Measurement

  • GA4 and Google Search Console
  • Ahrefs and SEMrush
  • Field data over lab scores
  • Before-and-after on real sites

Editorial standards

Every article on this site is written to four rules. They are published here so you can hold the content to them.

1
Nothing is stated from memoryWordPress, PHP and plugin behaviour drift every month. Version numbers, thresholds, pricing and plugin capabilities are checked against primary sources — WordPress.org, developer.wordpress.org, web.dev, Google Search Central, PHP.net and first-party vendor documentation — on the day an article is written or updated.
2
No invented benchmarksIf you see a before-and-after figure here, it was measured and the conditions are stated. Illustrative examples are labelled illustrative. A performance number without a methodology is decoration, and this industry has far too much of it.
3
The advice says what it applies toSteps differ between the block editor, classic editor, full site editing and a page builder. A tutorial that does not say which one it means is wasting your afternoon. Minimum PHP and WordPress versions are stated too.
4
Corrections are made in publicHow-to and troubleshooting articles carry the date they were last checked. When something here turns out to be wrong it gets fixed on the page rather than quietly deleted, and the correction is credited to whoever caught it.

What I do not write about

Scope limits are an authority signal, not a weakness. I do not cover topics I would only be summarising someone else's work on: headless and JavaScript-framework front ends, multisite at scale, enterprise WordPress VIP, or the marketing side of SEO such as outreach and link building. If a question here lands outside WordPress, performance, hosting or technical SEO, I will say so and point you somewhere better rather than write filler.

On the commercial side, plainly: FuryHost sells managed WordPress hosting, and I write the blog. I would rather tell you a problem is in your theme — where hosting cannot help — than sell you a migration that will not fix it. Where a FuryHost product is genuinely the answer I will say so and label it as an offer. Where it is not, I will say that too. No article here is a ranking that has been sold, and no comparison invents a competitor flaw.

Opinions I will defend

Most sites run too many plugins, and the fix is deleting rather than optimising. A Lighthouse score of 100 tells you almost nothing about whether real people can use your site. Nulled themes and plugins are never worth it, at any price, for reasons that show up as malware six months later. Auto-updating everything on a store that takes orders is not a time-saver, it is deferred risk. And a backup nobody has ever restored is a hypothesis, not a safety net.

Articles I have written

More are in progress — the full list of what is being written is on the guides page, and everything published appears on the blog.

Get in touch

If something here is wrong, out of date, or contradicted by your own testing, I want to know — write to joniel@furyhost.com and the correction gets made on the page with credit. Technical questions about a FuryHost site go to support, where they reach an engineer rather than a script. My public profile is on Gravatar.

Built with Oxygen