Click Below to Get the Code

Browse, clone, and build from real-world templates powered by Harper.
Event
GitHub Logo

Technical SEO 101: Early Hints | On-Demand Webinar

In the latest Harper SEO Series session, experts from SearchSide and Akamai explored how implementing Early Hints (HTTP 103) can dramatically speed up website load times and boost SEO performance. The session showcased a live demo where Akamai EdgeWorkers and Harper worked together to cut Largest Contentful Paint from 2.9s to 2.0s — proving that even fractional improvements in speed can lead to meaningful business gains.
Event

Technical SEO 101: Early Hints | On-Demand Webinar

Jaxon Repp
Field CTO
at Harper
August 13, 2025
Jaxon Repp
Field CTO
at Harper
August 13, 2025
Jaxon Repp
Field CTO
at Harper
August 13, 2025
August 13, 2025
In the latest Harper SEO Series session, experts from SearchSide and Akamai explored how implementing Early Hints (HTTP 103) can dramatically speed up website load times and boost SEO performance. The session showcased a live demo where Akamai EdgeWorkers and Harper worked together to cut Largest Contentful Paint from 2.9s to 2.0s — proving that even fractional improvements in speed can lead to meaningful business gains.
Jaxon Repp
Field CTO

In our latest Harper SEO Series session, I had the privilege of hosting two experts: Martin Spiek (CEO, SearchSide) and Brian Apley (Principal Cloud Architect, Akamai). Together, we unpacked Early Hints (HTTP 103) — what they are, why they matter for SEO and conversions, and how you can implement them quickly for measurable gains.

Why Website Speed is a Competitive Advantage

Performance is table stakes. Your site isn’t just competing on content, it’s competing on speed. Martin put it perfectly: “Milliseconds matter. A faster experience means more time on site, more pages viewed, and more revenue — both immediate and over the customer’s lifetime.”

In other words, if you can shave even fractions of a second off your load times, you can outpace your competition and improve user satisfaction.

What Early Hints Actually Do

Normally, a browser waits for the full HTML (200 OK) before it can start downloading linked assets. Early Hints (HTTP 103) flips that model. By sending a partial response first — a tiny set of instructions for the browser — we can tell it to start fetching critical assets before the rest of the page is ready.

That means your largest image, key CSS, or critical JS is already in place when rendering begins. The result? Better Core Web Vitals and a faster perceived load for your visitors.

How We Implemented It with Harper + Akamai

Here’s the setup we demoed:

  • Harper serves as the dynamic source of Early Hint data for each page.
  • Akamai Edgeworkers intercept requests at the CDN edge, fetch the relevant hints from Harper, and inject them into the HTTP 103 response.

This ensures hints are served from the closest edge location with ultra-low latency, and we can tailor them per page type for maximum impact.

The Demo Results

On harpersystems.dev, a site already optimized by Webflow and CDNs, Early Hints still made a difference:

  • Before: Largest Contentful Paint (LCP) at 2.9s.
  • After Early Hints: LCP dropped to 2.0s — nearly a full second faster.

That’s a big win for such a simple change.

Key Takeaways

  • Be selective — only hint critical render-blocking assets.
  • Keep HTML preload fallbacks for browsers like Safari on iOS.
  • Measure results with both Lighthouse and real user monitoring (RUM).

If you missed the live session, I encourage you to watch the full webinar (embeded above) and see just how easy it is to implement Early Hints for real-world performance gains.

Resources:
Harper Early Hints GitHub Repo

Learn about Harper 

Akamai Edgeworkers Overview

In our latest Harper SEO Series session, I had the privilege of hosting two experts: Martin Spiek (CEO, SearchSide) and Brian Apley (Principal Cloud Architect, Akamai). Together, we unpacked Early Hints (HTTP 103) — what they are, why they matter for SEO and conversions, and how you can implement them quickly for measurable gains.

Why Website Speed is a Competitive Advantage

Performance is table stakes. Your site isn’t just competing on content, it’s competing on speed. Martin put it perfectly: “Milliseconds matter. A faster experience means more time on site, more pages viewed, and more revenue — both immediate and over the customer’s lifetime.”

In other words, if you can shave even fractions of a second off your load times, you can outpace your competition and improve user satisfaction.

What Early Hints Actually Do

Normally, a browser waits for the full HTML (200 OK) before it can start downloading linked assets. Early Hints (HTTP 103) flips that model. By sending a partial response first — a tiny set of instructions for the browser — we can tell it to start fetching critical assets before the rest of the page is ready.

That means your largest image, key CSS, or critical JS is already in place when rendering begins. The result? Better Core Web Vitals and a faster perceived load for your visitors.

How We Implemented It with Harper + Akamai

Here’s the setup we demoed:

  • Harper serves as the dynamic source of Early Hint data for each page.
  • Akamai Edgeworkers intercept requests at the CDN edge, fetch the relevant hints from Harper, and inject them into the HTTP 103 response.

This ensures hints are served from the closest edge location with ultra-low latency, and we can tailor them per page type for maximum impact.

The Demo Results

On harpersystems.dev, a site already optimized by Webflow and CDNs, Early Hints still made a difference:

  • Before: Largest Contentful Paint (LCP) at 2.9s.
  • After Early Hints: LCP dropped to 2.0s — nearly a full second faster.

That’s a big win for such a simple change.

Key Takeaways

  • Be selective — only hint critical render-blocking assets.
  • Keep HTML preload fallbacks for browsers like Safari on iOS.
  • Measure results with both Lighthouse and real user monitoring (RUM).

If you missed the live session, I encourage you to watch the full webinar (embeded above) and see just how easy it is to implement Early Hints for real-world performance gains.

Resources:
Harper Early Hints GitHub Repo

Learn about Harper 

Akamai Edgeworkers Overview

In the latest Harper SEO Series session, experts from SearchSide and Akamai explored how implementing Early Hints (HTTP 103) can dramatically speed up website load times and boost SEO performance. The session showcased a live demo where Akamai EdgeWorkers and Harper worked together to cut Largest Contentful Paint from 2.9s to 2.0s — proving that even fractional improvements in speed can lead to meaningful business gains.

Download

White arrow pointing right
In the latest Harper SEO Series session, experts from SearchSide and Akamai explored how implementing Early Hints (HTTP 103) can dramatically speed up website load times and boost SEO performance. The session showcased a live demo where Akamai EdgeWorkers and Harper worked together to cut Largest Contentful Paint from 2.9s to 2.0s — proving that even fractional improvements in speed can lead to meaningful business gains.

Download

White arrow pointing right
In the latest Harper SEO Series session, experts from SearchSide and Akamai explored how implementing Early Hints (HTTP 103) can dramatically speed up website load times and boost SEO performance. The session showcased a live demo where Akamai EdgeWorkers and Harper worked together to cut Largest Contentful Paint from 2.9s to 2.0s — proving that even fractional improvements in speed can lead to meaningful business gains.

Download

White arrow pointing right

Explore Recent Resources

Blog
GitHub Logo

5 Architectures for Web Personalization

Personalization is a data-delivery problem. Every architectural choice reduces to two distances: compute to user, and compute to fresh data. This piece maps five real architectures against both axes, scored on a concrete retailer workload where stale or slow data breaks the business.
Blog
Personalization is a data-delivery problem. Every architectural choice reduces to two distances: compute to user, and compute to fresh data. This piece maps five real architectures against both axes, scored on a concrete retailer workload where stale or slow data breaks the business.
Person with short dark hair and moustache, wearing a colorful plaid shirt, smiling outdoors in a forested mountain landscape.
Aleks Haugom
Senior Manager of GTM
Blog

5 Architectures for Web Personalization

Personalization is a data-delivery problem. Every architectural choice reduces to two distances: compute to user, and compute to fresh data. This piece maps five real architectures against both axes, scored on a concrete retailer workload where stale or slow data breaks the business.
Aleks Haugom
Jul 2026
Blog

5 Architectures for Web Personalization

Personalization is a data-delivery problem. Every architectural choice reduces to two distances: compute to user, and compute to fresh data. This piece maps five real architectures against both axes, scored on a concrete retailer workload where stale or slow data breaks the business.
Aleks Haugom
Blog

5 Architectures for Web Personalization

Personalization is a data-delivery problem. Every architectural choice reduces to two distances: compute to user, and compute to fresh data. This piece maps five real architectures against both axes, scored on a concrete retailer workload where stale or slow data breaks the business.
Aleks Haugom
Blog
GitHub Logo

Agentic Engineering Needs an Opinion: Why Scale Starts with Architecture

AI coding works in a sandbox because the environment is trivially narrow. Real systems have history, constraints, and blast radius. Coding agents make sound decisions only when the architecture is explicit and shared. Opinion isn't a constraint on agentic engineering, it's what makes it possible at scale.
Select*
Blog
AI coding works in a sandbox because the environment is trivially narrow. Real systems have history, constraints, and blast radius. Coding agents make sound decisions only when the architecture is explicit and shared. Opinion isn't a constraint on agentic engineering, it's what makes it possible at scale.
A smiling man with a beard and salt-and-pepper hair stands outdoors with arms crossed, wearing a white button-down shirt.
Stephen Goldberg
CEO & Co-Founder
Blog

Agentic Engineering Needs an Opinion: Why Scale Starts with Architecture

AI coding works in a sandbox because the environment is trivially narrow. Real systems have history, constraints, and blast radius. Coding agents make sound decisions only when the architecture is explicit and shared. Opinion isn't a constraint on agentic engineering, it's what makes it possible at scale.
Stephen Goldberg
Jun 2026
Blog

Agentic Engineering Needs an Opinion: Why Scale Starts with Architecture

AI coding works in a sandbox because the environment is trivially narrow. Real systems have history, constraints, and blast radius. Coding agents make sound decisions only when the architecture is explicit and shared. Opinion isn't a constraint on agentic engineering, it's what makes it possible at scale.
Stephen Goldberg
Blog

Agentic Engineering Needs an Opinion: Why Scale Starts with Architecture

AI coding works in a sandbox because the environment is trivially narrow. Real systems have history, constraints, and blast radius. Coding agents make sound decisions only when the architecture is explicit and shared. Opinion isn't a constraint on agentic engineering, it's what makes it possible at scale.
Stephen Goldberg
Blog
GitHub Logo

Building a Cozy Sandbox Game on Harper

A nature-restoration game with six biomes, 150 animals, and a real food web — built with a single Harper component as the entire backend. One YAML file wires the database, API, content seeder, and static host. The same binary ships offline on itch.io.
Shell
Blog
A nature-restoration game with six biomes, 150 animals, and a real food web — built with a single Harper component as the entire backend. One YAML file wires the database, API, content seeder, and static host. The same binary ships offline on itch.io.
Person with long wavy brown hair wearing a bright pink shirt with a teal trim, smiling outdoors in soft sunlight with blurred trees in the background.
Bailey Dunning
Forward Deployed Engineer
Blog

Building a Cozy Sandbox Game on Harper

A nature-restoration game with six biomes, 150 animals, and a real food web — built with a single Harper component as the entire backend. One YAML file wires the database, API, content seeder, and static host. The same binary ships offline on itch.io.
Bailey Dunning
Jun 2026
Blog

Building a Cozy Sandbox Game on Harper

A nature-restoration game with six biomes, 150 animals, and a real food web — built with a single Harper component as the entire backend. One YAML file wires the database, API, content seeder, and static host. The same binary ships offline on itch.io.
Bailey Dunning
Blog

Building a Cozy Sandbox Game on Harper

A nature-restoration game with six biomes, 150 animals, and a real food web — built with a single Harper component as the entire backend. One YAML file wires the database, API, content seeder, and static host. The same binary ships offline on itch.io.
Bailey Dunning
Blog
GitHub Logo

Your Website was Built for Humans. AI Needs Something Cleaner.

The web spent a decade optimizing for browsers. JavaScript-heavy rendering, dynamic CMS templates, and client-side hydration made pages beautiful and machines blind. AI answer engines retrieve, parse, and cite content directly. If your best content is trapped behind a render cycle, a cleaner source wins.
A.I.
Blog
The web spent a decade optimizing for browsers. JavaScript-heavy rendering, dynamic CMS templates, and client-side hydration made pages beautiful and machines blind. AI answer engines retrieve, parse, and cite content directly. If your best content is trapped behind a render cycle, a cleaner source wins.
Person with short dark hair and moustache, wearing a colorful plaid shirt, smiling outdoors in a forested mountain landscape.
Aleks Haugom
Senior Manager of GTM
Blog

Your Website was Built for Humans. AI Needs Something Cleaner.

The web spent a decade optimizing for browsers. JavaScript-heavy rendering, dynamic CMS templates, and client-side hydration made pages beautiful and machines blind. AI answer engines retrieve, parse, and cite content directly. If your best content is trapped behind a render cycle, a cleaner source wins.
Aleks Haugom
Jun 2026
Blog

Your Website was Built for Humans. AI Needs Something Cleaner.

The web spent a decade optimizing for browsers. JavaScript-heavy rendering, dynamic CMS templates, and client-side hydration made pages beautiful and machines blind. AI answer engines retrieve, parse, and cite content directly. If your best content is trapped behind a render cycle, a cleaner source wins.
Aleks Haugom
Blog

Your Website was Built for Humans. AI Needs Something Cleaner.

The web spent a decade optimizing for browsers. JavaScript-heavy rendering, dynamic CMS templates, and client-side hydration made pages beautiful and machines blind. AI answer engines retrieve, parse, and cite content directly. If your best content is trapped behind a render cycle, a cleaner source wins.
Aleks Haugom