Tastemedia - faster mobile publishing for media-heavy content
A media-heavy site was slow on the phones most of its audience used, which is where a publisher loses readers.
What we changed
- 1
Rebuilt the experience mobile-first, since that is where the audience actually is.
- 2
Made heavy images and video load only when needed rather than all at once.
- 3
Reworked search and recommendations so readers land on something relevant.
Qualitative evidence
What changed operationally
- Pages become usable quickly on a phone on a normal connection.
- Rich media no longer costs the reader the first few seconds of every page.
- Readers move from one piece of content to the next without hunting.
Evidence standard: These are delivered workflow and operating-state changes supported by the project record. They are qualitative results, not estimated percentages or modelled savings.
What Devntech continued to own
- Front-end maintenance
- Performance work
- Hosting
This is what we mean by
Internal applicationsGot a workflow like Tastemedia’s?
Describe the process. We come back with what it costs today, what could be automated and what we would build first.
- For businesses with $5M to $30M in revenue
- No long-term commitment
- Start with one workflow
- Keep ownership of everything we build