SEO & website optimization for iroco.com

Phase 1: fix search, clear minor bugs, improve structured data, run a bounded whole-site validation, and push PageSpeed scores to 100 on iroco.com (Drupal + Drupal Commerce) — following the same approach used to take woodstock.co to 100 across all PageSpeed metrics.

Background

From our meeting, the immediate scope for iroco.com is clear: search and filters need fixing, there are a handful of minor bugs, mobile PageSpeed sits in the ~60s. This first engagement keeps scope tight and low-risk — it also doubles as discovery, getting hands on the code so I understand the architecture before we scope any larger restructuring work (navigation, clarity, "moving things around") as discussed.

Scope

• Fix search / search-filter issues
• Resolve minor bugs surfaced during the pass
• Review and improve structured data across reusable site templates, then validate representative page types and bilingual variants
• Run a whole-site crawl covering indexability, structured data, metadata, redirects, broken links, sitemap coverage, and Search Console checks
• Get all PageSpeed scores to 100; performance 90–100 depending on what the Drupal stack allows
• Scan all images for further optimization and serve smaller, appropriately sized images on mobile for higher speeds
• Ensure Japanese pages are indexable (the JP version was just recently indexed, checking this is effective on all pages)
• Before/after PageSpeed validation

What comes next (as discussed in the meeting)

After this introduction project, based on our talk: review the information hierarchy on the site, make small redesigns proposals of the site, and — depending on complexity (i havenet seen the code) — a proposal to change parts of the stack to achieve higher fidelity.

I also recommend an analytics handover / alignment talk where we decide which metrics matter most: retention, user journeys, engagement time, homepage → services → product drop-off, and inquiry / signup conversion. We can use GA if you prefer to stay with the existing setup, but I recommend PostHog for deeper journey and retention analysis.

For that redesign work, I'd build real components in code (reusable, on-brand) and render them into Figma — with both Japanese and English copy — so you can judge genuine look and feel before anything ships. It's the same component-first approach used on woodstock.co; here's an example file of design in 2 languages and for responsiveness:

https://www.figma.com/design/ylK3Cp0YXRAIvA8PG5fTSs/Woodstock-UI?node-id=0-1&p=f&t=yg5qlSoasnWjy4qb-11

Pricing