Performance

· 28 checks — Lighthouse + waterfall + sustainability rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Performance-focused optimization plan with CWV assessment, top offenders, and time estimates

Mobile Desktop

Performance

Accessibility

Best Practices

SEO

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

2.60 s

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

9.49 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

361 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

1.000

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

3.57 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

9.49 s

Page Load Progression

375 ms

750 ms

1.1 s

1.5 s

1.9 s

2.2 s

2.6 s

3.0 s

Checks

14 PASS 6 REVIEW 3 FIX

Third-Party Impact

Action

99% third-party, 0 ms blocking

FIX

99% third-party, 0 ms blocking

Third-party code accounts for 99% of page weight (1.7 MiB of 1.7 MiB)

Third-party blocking time is low (0 ms)

99%

First-party Third-party

JS Execution Cost

Action

2510ms total JS execution

FIX

2510ms total JS execution

https://successstory.com/: 1339ms CPU time

Unattributable: 480ms CPU time

https://www.googletagmanager.com/gtag/js?id=G-0P59...: 431ms CPU time

https://images.successstory.com/js/home.min1.js: 167ms CPU time

https://images.successstory.com/js/jquery-1.10.2.m...: 94ms CPU time

Third-party scripts: 691ms (28% of total)

Main Thread Breakdown

Style & Layout 35% Other 26% Script Evaluation 23% Rendering 9% Script Parsing & Compilation 3%

Script	Total	Scripting	Parse/Compile	Party
https://successstory.com/	1339ms	38ms	5ms	1st
Unattributable	480ms	11ms	0ms	1st
https://www.googletagmanager.com/gtag/js?id=G-0P592KDNGW	431ms	347ms	62ms	3rd
https://images.successstory.com/js/home.min1.js	167ms	113ms	7ms	3rd
https://images.successstory.com/js/jquery-1.10.2.min.js	94ms	71ms	10ms	3rd

Page Weight Inventory

Action

24 resources · 1.7 MB · 80 KB savings available

FIX

24 resources · 1.7 MB · 80 KB savings available

Page weight 1.7 MB exceeds 1 MB target by 756 KB

Got: 1.7 MB Expected: ≤ 1 MB

~80 KB of savings available

23 third-party resources (99% of weight)

1 resources over 200KB

24 resources · 1.7 MiB · 23 third-party 755.8 KiB over 1MB target

Image 69% · 1.2 MiB

JavaScript 13% · 230.7 KiB

CSS 10% · 169.7 KiB

Font 7% · 131.5 KiB

Document 1% · 12.3 KiB

Other 0% · 1.1 KiB

~79.8 KiB of savings available

Remove unused JavaScript: 79.8 KiB

#	Resource	Type	Size	Cache	Unused	3rd party	Issues

24 resources			1.7 MiB

Page Weight Budget

Action

1.7 MB transferred, 24 requests

REVIEW

1.7 MB transferred, 24 requests

Page weighs 2.4 MB (1.7 MB transferred)

Images are 1.2 MB — compress or use modern formats

Convert images to WebP/AVIF and resize to display dimensions to reduce transfer size.

Got: 1.2 MB

24 HTTP requests

Estimated 0.36 g CO2 per page load

1.7 MB transferred

24 requests

0.36 g CO2 per page load

Images 1.2 MiB 69%

JavaScript 230.7 KiB 13%

CSS 169.7 KiB 10%

Fonts 131.5 KiB 7%

HTML 12.3 KiB 1%

Other 586 B 0%

Other 549 B 0%

Other 0 B 0%

0 2.4 MB 4.9 MB

Approaching limit

Convert images to WebP/AVIF and resize to display dimensions to reduce transfer size.

Why this matters

Image bandwidth is high — modern formats (WebP/AVIF) and resizing typically cut it 50%+.

Source: web.dev

Image Optimization

12 images, 0 KB saveable

REVIEW

12 images, 0 KB saveable

https://images.successstory.com/images/img/logo.sv... is missing width/height — may cause layout shift

Set explicit width and height to prevent CLS.

12 images 1.2 MB

0 oversized -0 KB

12 legacy format

1 missing dimensions CLS risk

Set explicit width and height to prevent CLS.

Why this matters

Image without explicit width/height — browser can't reserve space; CLS jumps when image loads.

Source: web.dev / Core Web Vitals

JS Bundles

3 scripts, 80 KB unused

REVIEW

3 scripts, 80 KB unused

https://www.googletagmanager.com/gtag/js?id=G-0P59...: 80 KB unused (42%)

Consider code splitting or tree shaking to reduce unused code.

Total unused JavaScript: 80 KB

80 KB unused JavaScript

Downloaded but never executed on this page.

Script	Size	Unused	Minified	Party
https://www.googletagmanager.com/gtag/js?id=G-0P592KDNGW	188 KB	80 KB (42%)	✓	3rd
https://images.successstory.com/js/jquery-1.10.2.min.js	32 KB	—	✓	3rd
https://images.successstory.com/js/home.min1.js	11 KB	—	✓	3rd

Consider code splitting or tree shaking to reduce unused code.

Why this matters

This bundle has high unused code — code-split or tree-shake to ship only what executes.

Source: web.dev / Lighthouse coverage

Document Compression

Document response uses gzip; brotli would be ~20% smaller

REVIEW

Document response uses gzip; brotli would be ~20% smaller

Main HTML response uses gzip (brotli would be ~20% smaller)

All current browsers support brotli. Most CDNs (Cloudflare, Fastly, AWS CloudFront, Vercel, Netlify) can switch from gzip to brotli with a single config flag. Origin servers (nginx, Apache) need a brotli module compiled in -- nginx-brotli or Apache mod_brotli.

Main HTML Cache-Control

Action

Main HTML max-age=31536000 (~525600min) is aggressive

REVIEW

Main HTML max-age=31536000 (~525600min) is aggressive

Main HTML cached for 525600 minutes -- risks stale auth / SPA state

Long max-age on the main HTML document means users may see outdated auth state, SPA shells, or A/B variants until the cache expires. Consider Cache-Control: no-cache (or max-age=300) for HTML and let your hashed assets (JS/CSS/images) carry the long cache instead.

Got: public, max-age=31536000, immutable

Server-Timing Observability

No Server-Timing header found

REVIEW

No Server-Timing header found

Server-Timing exposes backend timing breakdowns to browser DevTools (e.g., `db: 45ms; render: 120ms; cache: 2ms`). Useful for diagnosing slow pages without backend log access. Most modern frameworks (Next.js, Cloudflare Workers, Fastly) emit it automatically; absence on a managed platform usually means telemetry headers are stripped at the edge.

A+

Text Compression

All text resources are compressed

PASS

All text resources are compressed

All text resources are properly compressed.

A+

Font Loading

3 fonts (131 KB)

PASS

3 fonts (131 KB)

3 font(s) use font-display: swap (FOUT risk but functional)

Web fonts

131 KB total

Render-blocking

of 3

Dominant font-display

swap

Most common across fonts

Font loading timeline

Transfer FOIT (block) FOUT (swap)

octet-stream;base64,d09... unknown swap

Size 24 KB

Load time 34 ms

Start 573 ms

Risk FOUT — text flashes from fallback to web font

octet-stream;base64,d09... unknown swap

Size 24 KB

Load time 35 ms

Start 575 ms

Risk FOUT — text flashes from fallback to web font

octet-stream;base64,d09... unknown swap

Size 84 KB

Load time 37 ms

Start 576 ms

Risk FOUT — text flashes from fallback to web font

Optimization checklist

Preload critical fonts (priority=high)
Use woff2 format for all fonts
Set font-display to swap, optional, or fallback
Subset large fonts (≤100 KB each)

Fixing the unchecked items could save ~39 KB and ~78 ms

A+

Resource Caching

All resources properly cached

PASS

All resources properly cached

No caching issues found

All static resources have appropriate caching headers.

A+

Critical Rendering Path

No render-blocking resources

PASS

No render-blocking resources

No render-blocking resources detected

A+

Resource Hints

1 hints, 0 missing preconnects

PASS

1 hints, 0 missing preconnects

Page uses 1 resource hint(s)

Current Resource Hints

preconnect

—

preload

—

dns-prefetch

prefetch

—

1 resource hints configured

A+

HTTP/3 (QUIC)

HTTP/3 advertised via Alt-Svc

PASS

HTTP/3 advertised via Alt-Svc

HTTP/3 (QUIC) is supported

First-load mobile users on cellular networks see meaningful latency improvements with HTTP/3. The QUIC transport collapses TLS + TCP handshakes into one and recovers faster from packet loss.

A+

LCP Image Preload

LCP preload audit not available

PASS

LCP preload audit not available

LCP image preload audit not available for this scan

A+

Server Response Intelligence

2 server-response signal(s) detected

PASS

2 server-response signal(s) detected

`Vary` header declared: Accept-Encoding

The page declares a `Vary` header, telling downstream caches which request headers the response varies on. Critical for content-negotiated responses (compression, language, cookies, device class).

No `ETag` or `Last-Modified` -- conditional GET not supported

Without either header, browsers can't issue conditional GETs and refresh always re-downloads the full response body even when nothing changed. Add `ETag: "<hash>"` (or `Last-Modified: <date>`) on cacheable responses; the server returns 304 Not Modified when the client's cached copy is still valid, saving bandwidth.

A+

Render-Blocking Resources

No render-blocking resources detected

PASS

No render-blocking resources detected

No render-blocking resources detected in <head>

A+

Third-Party Resources

No third-party resources detected

PASS

No third-party resources detected

A+

JavaScript Blocking

No render-blocking JS or document.write usage detected

PASS

No render-blocking JS or document.write usage detected

No JavaScript blocking issues detected

A+

CSS Performance Depth

No CSS performance depth issues detected

PASS

No CSS performance depth issues detected

A+

Green Hosting

Whether the site is served from green-energy infrastructure

PASS

Green Hosting

This site is hosted on green energy infrastructure

Provider: Google Cloud

HTTP Caching

max-age=31536000 (52 weeks)

PASS

max-age=31536000 (52 weeks)

Cache-Control header is set

Got: public, max-age=31536000, immutable

Effective TTL: 52 weeks (max-age=31536000)

No ETag or Last-Modified header

Conditional requests (304 Not Modified) are not possible without validators.

Cache-Control

public, max-age=31536000, immutable

Directive	Value	Meaning
public	—	Any cache may store this response
max-age	31536000	Cache for 52 weeks
immutable	—	Content will never change

Effective TTL: 31536000 seconds

Asset Compression

No text asset hosts to measure

INFO

No text asset hosts to measure

No third-party or subdomain host served enough text assets to measure

Asset compression is measured per host, from one HEAD request against a sampled resource. Pages that serve all their JS and CSS from the document's own origin are covered by the document compression check instead.

Network Waterfall

24 requests over 643ms

INFO

HTML JavaScript CSS Images Fonts XHR/Fetch Other

Third-Party Script Cost

Per-script blocking time, transfer cost, and cache headers

INFO

28% of JavaScript execution is third-party

First-party Third-party 691ms · 231KB · €8/mo

Script	Category	Execution	Transfer	Unused	Monthly Cost	Verdict
Google Tag Manager www.googletagmanager.com	Tag Manager	431ms	188 KB	42%	€5/mo	Costly
images.successstory.com images.successstory.com	Other	167ms	11 KB	—	€2/mo	Optional
images.successstory.com images.successstory.com	Other	94ms	32 KB	—	€1/mo	Optional

Google Tag Manager

Tag Manager

Costly

Execution 431ms

Transfer 188 KB

Unused 42%

Monthly Cost €5/mo

images.successstory.com

Other

Optional

Execution 167ms

Transfer 11 KB

Monthly Cost €2/mo

images.successstory.com

Other

Optional

Execution 94ms

Transfer 32 KB

Monthly Cost €1/mo

These scripts may cost more than they're worth

Google Tag Manager adds 431ms and costs ~€5/month

Google Tag Manager takes 431ms of CPU time. Consider loading it asynchronously or replacing it with a lighter alternative.

Why this matters

This script has high main-thread execution time — optimize hot paths or defer.

Source: web.dev

How third-party costs are calculated

Real-User Performance (CrUX)

Field metrics from the Chrome User Experience Report

INFO

Chrome User Experience (CrUX)

Real-user metrics from the Chrome UX Report (2026-09-04 — 2026-10-01)

LCP (p75)

1947 ms

84% good

INP (p75)

117 ms

90% good

CLS (p75)

1.000

53% good

FCP (p75)

1480 ms

TTFB (p75)

1168 ms

Image Optimization

1 images, 0 KB total, 0 KB wasted

INFO

Image Optimization Audit

Total Images

Total Size

0 KB

1 missing dimensions

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.