How to Boost Thorium’s Web Performance with Lighthouse: Testing Steps and Optimization Tips

Introduction

Thorium is a Chromium‑based browser branch that adds compiler optimizations and privacy features. To evaluate its web‑page performance, Lighthouse is used to measure performance, accessibility, best practices, and SEO.

1. Thorium Performance Testing

1.1 Test Tool Preparation

Lighthouse can be run in Thorium via two methods:

# Method 1: CLI
npm install -g lighthouse

# Method 2: Thorium DevTools
# 1. Open Thorium
# 2. Press F12
# 3. Switch to the "Lighthouse" tab

1.2 Test Environment Setup

Clone the Thorium source and build an optimized binary with the following GN flags:

# Clone Thorium repository
git clone https://gitcode.com/GitHub_Trending/th/thorium
cd thorium
./setup.sh
./autobuild.sh

# Key GN parameters (args.gn)
is_official_build = true
enable_thin_lto = true
v8_enable_maglev = true
v8_enable_turbofan = true
chrome_pgo_phase = 2
gn

2. Lighthouse Core Metrics

2.1 Performance Score Dimensions

Lighthouse evaluates five core metrics, each with a different weight.

2.2 Test Procedure and Baselines

Disable all extensions.

Enable incognito mode (Ctrl+Shift+N).

Run Lighthouse three times and average the results.

Test URLs:

Static content: https://example.com

Dynamic app: https://jsbench.me

Media content: https://www.youtube.com/tv

Baseline scores for an official Thorium build are:

Overall performance: 85‑90/100

LCP: 1.8‑2.2 s

FID: 60‑80 ms

CLS: 0.05‑0.08

INP: 120‑180 ms

3. Thorium‑Specific Optimization Strategies

3.1 Compiler and Build Flags

Key GN options that improve Lighthouse scores:

# Basic performance
is_official_build = true
symbol_level = 0
enable_stripping = true

# Linker optimizations
use_lld = true
use_icf = true
use_thin_lto = true
thin_lto_enable_optimizations = true

# V8 engine tweaks
v8_symbol_level = 0
v8_enable_maglev = true
v8_enable_turbofan = true
v8_enable_builtins_optimization = true
v8_enable_wasm_simd256_revec = true

3.2 Media Performance

Enable proprietary codecs and hardware acceleration for better Largest Contentful Paint (LCP):

proprietary_codecs = true   # enable proprietary codecs
ffmpeg_branding = "Chrome" # set FFmpeg brand
enable_ffmpeg_video_decoders = true
is_component_ffmpeg = true
use_vaapi = true           # enable VAAPI on Linux
gn
# Apply AC‑3 audio patch
./patch_ac3.sh
# Build optimized FFmpeg
./build_ffmpeg.sh

3.3 JavaScript Engine Tuning

Adjust V8 settings to lower First Input Delay (FID) and Interaction‑to‑Next‑Paint (INP):

# V8 tuning
v8_target_cpu = target_cpu
v8_enable_fast_torque = true
v8_use_context_snapshot = true
v8_enable_embedded_builtins = true
if (target_cpu == "x64") {
  v8_enable_avx2 = true
} else if (target_cpu == "arm64") {
  v8_enable_neon = true
}
gn

4. Lighthouse Test Walk‑through and Result Analysis

4.1 Test Command and Report Generation

# Simple CLI test
lighthouse https://example.com --view --preset=perf

# Advanced options
lighthouse https://example.com \
  --view \
  --preset=perf \
  --chrome-flags="--headless=new --disable-extensions" \
  --throttling.cpuSlowdownMultiplier=4

4.2 Typical Bottlenecks and Fixes

Scenario 1: Low LCP (<60)

Cause: Large images or slow‑loading fonts.

# Enable WebUI optimizations
optimize_webui = true
# Enable JPEG‑XL support
enable_jxl = true
gn

Web‑page recommendation (modern image formats):

<!-- Use modern image formats -->
<picture>
  <source srcset="image.jxl" type="image/jxl">
  <source srcset="image.webp" type="image/webp">
  <img src="image.jpg" alt="Optimized image" loading="lazy">
</picture>

Scenario 2: Low INP (<70)

Cause: Long JavaScript execution and main‑thread blocking.

# V8 performance flags
v8_enable_maglev = true
v8_enable_turbofan = true
v8_enable_wasm_simd256_revec = true
# PGO settings
chrome_pgo_phase = 2
pgo_data_path = "path/to/profile.profdata"
gn

Web‑page recommendation (use Web Workers):

// Offload heavy work to a worker
const worker = new Worker('data-processor.js');
worker.postMessage(largeDataset);
worker.onmessage = (e) => {
  updateUI(e.data.result);
};

5. Best‑Practice Checklist

Enable official build (is_official_build=true)

Configure PGO (chrome_pgo_phase=2)

Turn on ThinLTO and ICF (use_thin_lto=true, use_icf=true)

Apply V8 flags (v8_enable_maglev=true, v8_enable_turbofan=true)

Activate media hardware acceleration (use_vaapi=true, proprietary_codecs=true)

5.1 Automated Performance Testing

Integrate Lighthouse into the Thorium build pipeline:

# In autobuild.sh
npm install -g lighthouse
lighthouse https://example.com --output=json --output-path=thorium-performance-report.json

5.2 Ongoing Optimization Strategy

Monitor trends: run Lighthouse regularly and track changes.

Baseline comparison: benchmark against the stable Chrome release.

Targeted tuning: adjust GN flags per deployment scenario (e.g., is_debug=true for development, proprietary_codecs for media‑heavy use, is_raspi=true for low‑end devices).

6. Future Directions

Potential evolution includes AI‑driven PGO profile generation, deeper WebAssembly SIMD enhancements, green‑computing trade‑offs, and adding mobile‑centric metrics such as battery‑usage efficiency.