Book a call
Max Tymoshyn, founder of Norml Studio
Max TymoshynFounder, Norml Studio

WordPress websites for races and sports events, with live updates during the event

We build WordPress websites for races and other sports events that need a live view: positions, split times, results or scores that change while visitors watch, on phones and desktops. Your team publishes event pages, news and announcements in the WordPress admin. The live data comes from your timing or scoring source through a separate connection, and the whole setup is tested with recorded data and expected traffic before the first event.

A few clients we’ve worked with

99Legal / Kremenchuker Law GroupAstraZenecaCoxitDiet vs DiseaseFlorida seal — Regional Counsel projectMetroplex HomebuyersNasdaq Private MarketOffice of Criminal Conflict and Civil Regional Counsel, Second Region of Florida — Ita M. NeymotinPolaclubThe Farm Soho

What we do

Norml designs and builds the WordPress site, the live view and the connection that reads your data source, then tests how they behave with late data and event-day traffic. The data, the timing equipment and the rights to publish results stay with you and your provider.

What a live event website involves

We plan the site around what your data source publishes and how often, so reading its documentation comes before any design.

Solution
Websites
Platforms
WordPress
  • Event pages your team editsSchedules, entry lists, course or venue maps, news and sponsor sections are built as WordPress templates with a field for each part of the page. Your team publishes them in the admin without touching code.
    01
  • A live view built around your dataWhat it shows depends on the data: participants on a course map when the source reports tracker positions, split times when it reports checkpoints, standings or scores for matches. New data appears without reloading the page.
    02
  • A data connection kept apart from WordPressA separate connection reads your source, checks each update and serves the latest data from a cache. Visitors refreshing during the event do not each reach the source or the WordPress database, and a change in the source format is handled in one place.
    03
  • Update times, labels and correctionsEvery update is stamped with the time it arrived, and the view shows that time. Provisional and official results are labelled, and a correction replaces the earlier value everywhere it appears. What the view does when updates stop is agreed during the data review.
    04
  • Messages and controls for the event teamFrom the WordPress admin, your team posts announcements such as a delayed start or a course change, marks results official and pauses the live view when needed, without developer help.
    05
  • Phone layouts firstThe live view and event pages are designed for phones first, then for desktops and screens at the venue. Wide result tables become rows that stay readable on a small screen. We test at phone, tablet and desktop widths and on a slowed mobile connection.
    06
  • Load testing before the eventOn the staging copy, we run recorded data through the connection while a load test simulates the audience you expect. Caching and hosting settings are adjusted where the test shows strain, and you receive the results with the changes made.
    07
Josiah BallCo-Founder & CEO, HOMEEC

“Norml Studio's professionalism and responsiveness were impressive.”

Clutch review
Lucas SeyhunCEO, The Farm Soho

“They were proactive in suggesting improvements we hadn't considered.”

Clutch review
Gaius CooperDirector, Streamline Pump Solutions

“They delivered what they said they would, on time.”

Clutch review
Emma EstefaClient Success Manager, Metroplex Homebuyers

“They focused on how to make our daily operations easier, not just on building features for the sake of it.”

Clutch review
Bret MillerManager, Door Knock Pro

“They understood that the app needed to be practical for someone sitting in a car, not just look good on a desktop.”

Clutch review
Saima AhmedFounder, GoPetZen

“Their level of dedication to the success of the project and GoPetZen's business as a whole is unique.”

Clutch review

What we need from you

  • Your data source and its documentationDocumentation for the timing system, scoring service or other source that supplies the data, plus recorded data from a past event. Test access is issued to our team as an invitation or a separate key, never as a shared password.
    01
  • Permission to publish the dataConfirmation that you may show the data publicly, including participants' names, under any agreement with your data provider. Those terms stay between you and the provider, and the site is built within them.
    02
  • Access to WordPress and hostingAn administrator account and access to the hosting or staging copy, set up as invitations to your accounts. For a new site, the hosting choice is made with the load test in mind.
    03
  • Event dates and expected audienceThe dates of the events the site has to cover and your estimate of how many people follow each one, so the load test uses realistic numbers.
    04
  • Brand and event materialLogos, sponsor assets, course or venue maps, and any existing pages or designs that set the visual direction.
    05
  • Someone who owns the data on your sideOne person from the event or timing team who can confirm what each value should be, approve results as official and decide what the page says when data is late.
    06

How a live event build runs

  1. [Data review]

    We read the source documentation and run recorded data from a past event through a test connection. You receive a written summary of what the source supports, a proposed live view and the open questions.

    Step 01
  2. [Design review in Figma]

    You review the live view and event pages as Figma designs, phone layouts before desktop. Approved designs become the components of the WordPress theme.

    Step 02
  3. [Build on staging]

    We build the theme and the data connection on a staging copy and replay a past event through it, so you can follow the replay on your own phone and computer.

    Step 03
  4. [Failure and load tests]

    We stop the data partway through a replay, send corrections and run the load test, then fix whatever these checks expose before launch.

    Step 04
  5. [Launch and practice run]

    We launch before the first event and run a practice session in which your team uses each control on the live site. Written steps for each task are part of the handover.

    Step 05

The people who do this work.

Meet the whole team

No account layer between you and them. These are the Norml specialists this work runs through.

Max Tymoshyn, founder of Norml Studio

Let's chat

“I've spent 10 years working across development and marketing. I started as a developer, but design, SEO and advertising were already part of the job. That taught me to treat a website as one system: the business, the content, the design and the code have to work together. At Norml, I lead the architecture behind our work and stay involved wherever strategy, design, development and search meet.”

Max TymoshynFounder & Architect

From the Norml blog.

Questions

Where does the live data come from?
From a source you already use: a timing system, a scoring service or your own records. We connect to it and do not supply the data. The data review checks how the source publishes updates, because that decides what the live view can show.
Can the live view run inside our current WordPress site?
Usually, yes. The live view sits on WordPress pages like any other section, and the data connection runs beside the site. We check the theme, plugins and hosting first and list anything that has to change before the live part is added.
How current will the data on the page be?
As current as your source allows. Some sources publish each change as it happens; others publish at set intervals or only when a participant passes a checkpoint. We agree a target with you once the data review shows which kind you have.
What do visitors see if the data stops during the event?
By default, the last confirmed data stays on screen with its time, next to a message that updates are paused. When the source resumes, the newest data takes its place. Your event team approves the wording of that message before launch.
How many visitors can the site handle?
We give a number only after measuring it in a load test on staging. The test shows where the setup starts to slow down, and the hosting plan is chosen or changed with that result in mind.
Will the live view work at the venue, where the signal is weak?
We keep each update small and test the view on a slowed mobile connection. If a phone loses signal, the view marks the data on screen as not current until the connection returns.
Should the tools for officials be built in WordPress too?
Not always. WordPress suits the public site: event pages, news and results your team publishes. Tools for officials, with logins and controls for entering or correcting times, can work better as a separate web application that feeds the public site. We recommend an approach after the data review and explain why.
Can the same site cover our next event?
Yes. The event templates and the data connection are reused, so your team sets up the next event in the admin. If the source changes its data format, the connection needs development work before that event.
Can we start with the data review alone?
Yes. The data review can run as a separate first piece of work, and its summary and proposed live view are yours to keep whether or not a build follows.
What falls outside this work?
Timing equipment and trackers, the timing or scoring service itself, video streaming, ticketing and mobile apps. Each comes from its own provider or needs its own discovery, and the site can link to or embed them where their terms allow.
Can you keep working on the site after launch?
Yes. New features continue as development work, and a monthly maintenance plan covers updates, backups, monitoring and fixes. Cover during each event is agreed before it starts.

See more of our work

Each case study covers the starting point, what we built and what changed after launch.

See all case studies