Back to Top Start Free Trial

Turbulence Report

/

banyantreerestaurant.com could see a 6+ improvement in page speed by adopting Turbulence.

banyantreerestaurant.com — For banyantreerestaurant.com, Google's performance score goes from 64 to 70 (+6). Turbulence does this with a DNS change — no code updates.

  • Higher scores mean fewer visitors leaving before your page loads.
  • Content appears sooner: 5.4 s → 3.9 s.
  • 2.0 MB less data per visit — faster on mobile networks.

Performance

Lab data — simulated mobile
Before

Lab metrics

Metric Before With Turbulence
Speed Index SI Before: 5.4 s After: 3.9 s -27%
First Contentful Paint FCP Before: 2.4 s After: 2.0 s -18%
Largest Contentful Paint LCP Before: 16 s After: 6.9 s -56%
Cumulative Layout Shift CLS Before: 0.020 After: 0.002 -90%
Total Blocking Time TBT Before: 207 ms After: 182 ms -12%

What changed (10)

  • picperf-banner Improves page load speed and visitor experience.
  • Speculation rules prefetching Browser prefetches likely navigation targets for instant loads
  • Resource hints injected Browser knows what to fetch early
  • Render-blocking resources deferred Page paints before stylesheets finish
  • Images re-encoded to AVIF/WebP Smaller image files that look the same
  • Images re-encoded to AVIF/WebP Smaller image files that look the same
  • Off-screen images lazy-loaded Images load as they scroll into view
  • Image dimensions explicitly set Explicit dimensions prevent layout shifts
  • CSS and JavaScript minified and edge-cached Stylesheets and scripts load faster with smaller, cached files
  • Font display swap + DNS preconnect Text shows up while fonts load

How we measured this

  1. 1. We fetched your page and scored it with PageSpeed Insights (mobile, lab data).
  2. 2. We re-fetched it through a Turbulence preview environment that applies our transformation pipeline.
  3. 3. We scored the result with PageSpeed Insights again.
  4. 4. The deltas above are the difference — a directional estimate, not a forecast. First visits, geographic location, network conditions, and JS-rendered content all affect real-world results.