Performance

· 15 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.

1.24 s

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

1.51 s

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

91 ms

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

0.023

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

3.43 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.

4.05 s

Page Load Progression

592 ms

1.2 s

1.8 s

2.4 s

3.0 s

3.5 s

4.1 s

4.7 s

Checks

5 PASS 3 REVIEW 5 FIX

Page Weight Budget

Action

3.2 MB transferred, 176 requests

FIX

3.2 MB transferred, 176 requests

Page weighs 8.4 MB (3.2 MB transferred)

JavaScript is 1.2 MB — consider code splitting or lazy loading

Large JavaScript bundles delay interactivity. Split code by route or defer non-critical scripts.

Got: 1.2 MB

Images are 1.0 MB — compress or use modern formats

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

Got: 1.0 MB

Fonts are 279 KB — consider subsetting or using system fonts

Subset fonts to include only used characters, or switch to system font stacks.

Got: 279 KB

176 HTTP requests — consider bundling or reducing

Each request adds latency. Bundle small files, use sprites, or eliminate unnecessary requests.

Estimated 0.67 g CO2 per page load

3.2 MB transferred

176 requests

0.67 g CO2 per page load

JavaScript 1.2 MiB 39%

Images 1.0 MiB 32%

HTML 529.6 KiB 16%

Fonts 279.1 KiB 9%

CSS 98.5 KiB 3%

Other 38.9 KiB 1%

Other 2.9 KiB 0%

Other 1.6 KiB 0%

Other 550 B 0%

Other 0 B 0%

0 2.4 MB 4.9 MB

Over budget

Large JavaScript bundles delay interactivity. Split code by route or defer non-critical scripts.

Why this matters

JavaScript bundle is large — code-split routes and lazy-load off-screen components to defer.

Source: web.dev

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

Subset fonts to include only used characters, or switch to system font stacks.

Why this matters

Font payload is large — subset to used glyphs only, or fall back to system fonts (zero load time).

Source: web.dev font loading

Each request adds latency. Bundle small files, use sprites, or eliminate unnecessary requests.

Why this matters

High HTTP request count — bundling, sprite-ing, and HTTP/2 server push can reduce per-request overhead.

Source: web.dev

Third-Party Impact

Action

100% third-party, 0 ms blocking

FIX

100% third-party, 0 ms blocking

Third-party code accounts for 100% of page weight (3.2 MiB of 3.2 MiB)

Third-party blocking time is low (0 ms)

100%

First-party Third-party

JS Bundles

Action

27 scripts, 459 KB unused

FIX

27 scripts, 459 KB unused

https://www.swissinfo.ch/eng/wp-content/themes/swi...: 188 KB unused (87%)