Boncer’s own website · Project review
Making Boncer easier to explore and measure.
A practical website project connecting service discovery, enquiry preparation, technical SEO and privacy choices.
Project checks recorded 16 October 2026 (UTC). This is our own agency website, not a client testimonial or an independent audit.

The starting problem
Visitors needed a clearer path from a service overview to its details and then to a project enquiry. Large introductory areas made some destinations less obvious after navigation. The website also needed distinct, crawlable service pages and a reliable way to distinguish a prepared email from a confirmed lead.
What changed
- Retained the hero imagery, slideshow and light/dark themes, while simplifying the visible controls.
- Kept click-to-flip service summaries and added dedicated pages with scope, preparation, deliverables and related guides.
- Connected menus, breadcrumbs, related services and project CTAs to clear destinations, with compact introductions on contact and about pages.
- Added page metadata, canonical URLs, structured data, an XML sitemap and optimized image assets.
- Made optional analytics a visitor choice, with a preference panel and privacy policy explaining the email-draft workflow.
- Measured page visits and prepared enquiries explicitly, without putting enquiry field values in custom analytics events.
What we verified
| Check | Observed result | What it establishes |
|---|---|---|
| Public-page crawl | 23 pages, 772 internal links, 12 image references; 460 checks passed. | Rendered metadata, canonical URLs, authored internal destinations, image references and structured-data syntax passed the audit. |
| Mobile PageSpeed | 94 performance; 100 SEO, accessibility and best practices. | A homepage lab snapshot, not a site-wide score or a guarantee of real-user experience. |
| Tracking receipt | GA4 Realtime received page_view and lead_request_prepared. | A test visit and synthetic enquiry draft were measured. No test email was sent. |
| Privacy choice | Google tag absent after rejection and reload; loaded after opt-in. | The visitor’s analytics choice affected tag loading. |
| Mobile layout | Contact navigation and cookie preferences checked at a 390-pixel browser setting. | The tested views fit without horizontal page overflow. |
| Sitemap | Google read the 23-URL sitemap with no reported errors or warnings. | The sitemap was processed. This does not establish that all pages were indexed. |
View the recorded mobile PageSpeed report ↗
How to interpret the measurements
The recorded mobile lab run reported largest contentful paint of 2.9 seconds, total blocking time of 30 milliseconds and cumulative layout shift of 0. These figures describe one test under simulated mobile conditions. They do not establish field Core Web Vitals, and no comparable before-test was recorded.
The project established a website and measurement foundation. We are not claiming an increase in revenue, conversion rate, qualified leads, rankings or organic traffic. Search performance needs real queries and sufficient data over time; preparing an email is not a completed enquiry.
What this means for a similar project
Start with the decisions visitors need to make: understand the service, review the scope and choose a next action. Then check that search engines can access the pages and that reporting measures the actions the website actually supports. Keep visual character while removing friction from those steps.
Explore our website and landing page design, brand identity work and marketing planning guides.
Discuss your website project →