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

Comparison
GitHub Logo

Kafka-Centered Stacks vs. a Single Harper Cluster: Where Real-Time Latency Actually Comes From

End-to-end latency in real-time pipelines comes from coordination across systems, not from any single component. Four common workloads, tested two ways, show where multi-hop architectures compound delays and where collapsing storage, messaging, and compute into one runtime changes the math.
Cache
Comparison
End-to-end latency in real-time pipelines comes from coordination across systems, not from any single component. Four common workloads, tested two ways, show where multi-hop architectures compound delays and where collapsing storage, messaging, and compute into one runtime changes the math.
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
Comparison

Kafka-Centered Stacks vs. a Single Harper Cluster: Where Real-Time Latency Actually Comes From

End-to-end latency in real-time pipelines comes from coordination across systems, not from any single component. Four common workloads, tested two ways, show where multi-hop architectures compound delays and where collapsing storage, messaging, and compute into one runtime changes the math.
Aleks Haugom
Jun 2026
Comparison

Kafka-Centered Stacks vs. a Single Harper Cluster: Where Real-Time Latency Actually Comes From

End-to-end latency in real-time pipelines comes from coordination across systems, not from any single component. Four common workloads, tested two ways, show where multi-hop architectures compound delays and where collapsing storage, messaging, and compute into one runtime changes the math.
Aleks Haugom
Comparison

Kafka-Centered Stacks vs. a Single Harper Cluster: Where Real-Time Latency Actually Comes From

End-to-end latency in real-time pipelines comes from coordination across systems, not from any single component. Four common workloads, tested two ways, show where multi-hop architectures compound delays and where collapsing storage, messaging, and compute into one runtime changes the math.
Aleks Haugom
Tutorial
GitHub Logo

Your API cache is secretly a database

Most teams treat a cache as a black box: URL-keyed blobs with a TTL, useful for speed and nothing else. In Harper, cached data lands in a real table inside the same query engine. That means filtering, joining, real-time subscriptions, and vector search all work against it.
Cache
Tutorial
Most teams treat a cache as a black box: URL-keyed blobs with a TTL, useful for speed and nothing else. In Harper, cached data lands in a real table inside the same query engine. That means filtering, joining, real-time subscriptions, and vector search all work against it.
Person with very short blonde hair wearing a light gray button‑up shirt, standing with arms crossed and smiling outdoors with foliage behind.
Kris Zyp
SVP of Engineering
Tutorial

Your API cache is secretly a database

Most teams treat a cache as a black box: URL-keyed blobs with a TTL, useful for speed and nothing else. In Harper, cached data lands in a real table inside the same query engine. That means filtering, joining, real-time subscriptions, and vector search all work against it.
Kris Zyp
Jun 2026
Tutorial

Your API cache is secretly a database

Most teams treat a cache as a black box: URL-keyed blobs with a TTL, useful for speed and nothing else. In Harper, cached data lands in a real table inside the same query engine. That means filtering, joining, real-time subscriptions, and vector search all work against it.
Kris Zyp
Tutorial

Your API cache is secretly a database

Most teams treat a cache as a black box: URL-keyed blobs with a TTL, useful for speed and nothing else. In Harper, cached data lands in a real table inside the same query engine. That means filtering, joining, real-time subscriptions, and vector search all work against it.
Kris Zyp