Case study · Local service · bookings

WemeSports: a local football-pitch website found by area, with a measurable booking funnel

An artificial-turf football venue in Dĩ An. A 25-page site built around area queries, homepage images cut by about two thirds, and a booking funnel measured since 27 September 2026.

WemeSports – Local service · bookings

Business

  • WemeSports is an artificial-turf football venue in Đông Hòa, Dĩ An (Ho Chi Minh City) with five 5-a-side pitches and one 7-a-side pitch, rented by the hour and available for tournaments.
  • It is a project inside the Weme ecosystem: Weme builds and runs the website itself; it is not an outside client.

Website objective

  • People looking for a pitch nearby must find the site on Google and be able to book, call or message on Zalo straight from their phone.
  • The owner must be able to measure the booking funnel: how many people tap to book and how many bookings are confirmed.

Initial state

  • Searches reaching the site were mostly for the brand name, meaning people who already knew the venue.
  • Homepage images weighed 1,517 KB, the largest one alone 565 KB.
  • On mobile, 13 text areas were covered.
  • The code fired booking events, but none reached the analytics tool, so there was no funnel data before 27 September 2026.

Architecture

  • 25 pages, each answering one need: home, pricing, on-site facilities, news.
  • 7 pages by area and pitch type (for example "pitch near the University Village", "pitch near Sóng Thần industrial park", "7-a-side pitch in Dĩ An"), created only where real queries exist.
  • 4 tournament pages by area and audience (companies, unions, students).
  • 10 guides based on what people booking ask: rental prices, how to get prime-time slots, what happens when it rains.

Build

  • WordPress on a LiteSpeed server.
  • Homepage images cut from 1,517 KB to 494 KB; the largest one is now 133 KB.
  • The mobile layout fixed so that no text area is covered any more.

SEO

  • The homepage carries 7 structured-data types: SportsActivityLocation, LocalBusiness, FAQPage, HowTo, Organization, WebSite, WebPage.
  • The sitemap lists 25 URLs; all 25 are indexed by Google (Search Console, September 2026).
  • All 25 pages have a unique title, a description and a canonical URL (read live on 2 October 2026).

Conversion

  • The homepage has 4 call links and 16 Zalo links (counted on 2 October 2026).
  • Two booking-funnel events are measured: click_book (tap to book) and booking_confirmed (booking confirmed).
  • Customers' phone numbers are never sent to analytics.

Evidence

MetricBeforeAfterSource · date
Homepage image weight1.517 KB494 KBChange log SPORT-CHG-002 · Sep 2026
Largest homepage image (LCP)565 KB133 KBChange log SPORT-CHG-002 · Sep 2026
Text areas covered on mobile130Change log SPORT-CHG-002 · Sep 2026
Booking events reaching analytics0click_book · booking_confirmedMeasurement check · 27 Sep 2026
Sitemap URLs indexed by Google—25 / 25Search Console · Sep 2026
Structured-data types on the homepage—7Read from the live site · 2 Oct 2026

Outcome

  • Traffic, bookings and revenue are not published yet: the funnel has only been measured since 27 September 2026, which is not enough data for a before / after comparison.
  • What is certain: the site is lighter, no longer covers content on mobile, is fully indexed and has a measurable booking funnel.

Improvements

  • Track non-brand searches for the 7 area pages.
  • Link bookings to customer records so returning customers can be recognised.
  • Report monthly on confirmed bookings.

Lessons returned to Weme Core

  • The "local service with bookings" pattern: every area page answers a real query; never create a page just because a keyword exists.
  • Nothing may cover text on mobile: check it by counting covered areas, not by feel.
  • Name events once and keep them; always test that events actually reach the analytics tool.
  • Never send phone numbers to analytics.

WemeWebsite · updated 2 Oct 2026

Where does your website stand against these cases?

Run a free website check for a score, issues and priorities.