Browse & Analyze

Browse recent website audits and performance trends

Explore technology stacks detected across the web

Side-by-side technology comparisons and market share

Curated technology stacks and the sites that use them

Editorial deep-dives on the state of web performance

Browse and download favicons from analyzed websites

Learn

Common questions about BeaverCheck scores and checks

How we calculate scores across 100+ checks

The story behind BeaverCheck and the team

Practical guides to fix common web performance issues

Migration Guides

Step-by-step guides for moving between web technologies

Definitions for performance, SEO, and web platform terms

Contrast Checker

Check WCAG color contrast ratios between any two colors

Inspect HTTP response headers for any URL

Analyze SSL/TLS certificate details and chain

Look up DNS records for any domain

Redirect Checker

Trace the full redirect chain for any URL

Real-user INP and Core Web Vitals from Google's Chrome UX Report.

RESTful API for programmatic website audits

Embed an auto-updating health score badge on your site

https://www.thousandsmiles.uk/veneer-prices/

Performance

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

SCORE

81

GRADE

B

FIX

5

REVIEW

5

PASS

13

INFO

5

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

76

Performance

93

Accessibility

96

Best Practices

100

SEO

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

1.01 s

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

6.34 s

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

154 ms

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

0.032

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

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

11.42 s

Page Load Progression

378 ms

756 ms

1.1 s

1.5 s

1.9 s

2.3 s

2.6 s

3.0 s

Checks

28

13 PASS 5 REVIEW 5 FIX

D

Third-Party Impact

Action

72% third-party, 0 ms blocking

FIX

72% third-party, 0 ms blocking

Third-party code accounts for 72% of page weight (1.1 MiB of 1.6 MiB)

Third-party blocking time is low (0 ms)

28%

72%

First-party Third-party

D

JS Execution Cost

Action

2061ms total JS execution

FIX

2061ms total JS execution

https://www.thousandsmiles.uk/veneer-prices/: 824ms CPU time

https://www.gstatic.com/recaptcha/releases/NhfdZHz...: 815ms CPU time

Unattributable: 301ms CPU time

https://static.botsrv2.com/website/js/widget2.js: 120ms CPU time

Third-party scripts: 936ms (45% of total)

Main Thread Breakdown

Script Evaluation 42% Other 27% Style & Layout 16% Rendering 5% Parse HTML & CSS 5% Script Parsing & Compilation 4%

Script	Total	Scripting	Parse/Compile	Party
https://www.thousandsmiles.uk/veneer-prices/	824ms	34ms	8ms	1st
https://www.gstatic.com/recaptcha/releases/NhfdZHzre166o-vFZrWsq3yu/recaptcha__en.js	815ms	698ms	74ms	3rd
Unattributable	301ms	7ms	0ms	1st
https://static.botsrv2.com/website/js/widget2.js	120ms	84ms	11ms	3rd

F

JS Bundles

Action

6 scripts, 576 KB unused

FIX

6 scripts, 576 KB unused

https://www.gstatic.com/recaptcha/releases/NhfdZHz...: 185 KB unused (53%)

Consider code splitting or tree shaking to reduce unused code.

https://www.gstatic.com/recaptcha/releases/NhfdZHz...: 185 KB unused (53%)

Consider code splitting or tree shaking to reduce unused code.

https://www.gstatic.com/recaptcha/releases/NhfdZHz...: 185 KB unused (53%)

Consider code splitting or tree shaking to reduce unused code.

https://static.botsrv2.com/website/js/widget2.js: 21 KB unused (56%)

Consider code splitting or tree shaking to reduce unused code.

Total unused JavaScript: 576 KB

576 KB unused JavaScript

Downloaded but never executed on this page.

Script	Size	Unused	Minified	Party
https://www.gstatic.com/recaptcha/releases/NhfdZHzre166o-vFZrWsq3yu/recaptcha__en.js	351 KB	185 KB (53%)	✓	3rd
https://www.gstatic.com/recaptcha/releases/NhfdZHzre166o-vFZrWsq3yu/recaptcha__en.js	350 KB	185 KB (53%)	✓	3rd
https://www.gstatic.com/recaptcha/releases/NhfdZHzre166o-vFZrWsq3yu/recaptcha__en.js	0 KB	185 KB (53%)	✓	3rd
https://static.botsrv2.com/website/js/widget2.js	37 KB	21 KB (56%)	✓	3rd
https://www.google.com/recaptcha/api.js?render=6Lc03agkAAAAADsmmwNIIj1r-OVSvmkhuZrm5Cva&ver=3.0	1 KB	—	✓	3rd
https://www.google.com/recaptcha/api2/webworker.js?hl=en&v=NhfdZHzre166o-vFZrWsq3yu	0 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

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

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

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

F

Page Weight Inventory

Action

55 resources · 1.6 MB · 576 KB savings available

FIX

55 resources · 1.6 MB · 576 KB savings available

Page weight 1.6 MB exceeds 1 MB target by 594 KB

Got: 1.6 MB Expected: ≤ 1 MB

~576 KB of savings available

21 third-party resources (72% of weight)

2 resources over 200KB

55 resources · 1.6 MiB · 21 third-party 594.2 KiB over 1MB target

JavaScript 46% · 739.7 KiB

Font 21% · 337.5 KiB

CSS 15% · 248.9 KiB

Image 13% · 218.4 KiB

Document 4% · 64.1 KiB

Other 1% · 9.7 KiB

~576.4 KiB of savings available

Remove unused JavaScript: 576.4 KiB

#	Resource	Type	Size	Cache	Unused	3rd party	Issues

55 resources			1.6 MiB

F

HTTP Caching

Action

No cache headers

FIX

No cache headers

No Cache-Control header found

Browsers will use heuristic caching, which can be unpredictable. Set explicit cache headers.

No Cache-Control header

Adding a Cache-Control header can significantly improve repeat-visit performance.

C

Page Weight Budget

Action

1.6 MB transferred, 55 requests

REVIEW

1.6 MB transferred, 55 requests

Page weighs 4.5 MB (1.6 MB transferred)

JavaScript is 740 KB — consider code splitting or lazy loading

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

Got: 740 KB

Fonts are 337 KB — consider subsetting or using system fonts

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

Got: 337 KB

CSS is 249 KB — consider purging unused styles

Remove unused CSS rules with tools like PurgeCSS to reduce stylesheet size.

Got: 249 KB

55 HTTP requests

Estimated 0.33 g CO2 per page load

1.6 MB transferred

55 requests

0.33 g CO2 per page load

JavaScript 739.7 KiB 46%

Fonts 337.5 KiB 21%

CSS 248.9 KiB 15%

Images 214.5 KiB 13%

HTML 64.1 KiB 4%

Other 9.7 KiB 1%

Other 3.9 KiB 0%

Other 0 B 0%

0 2.4 MB 4.9 MB

Approaching limit

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

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

Remove unused CSS rules with tools like PurgeCSS to reduce stylesheet size.

Why this matters

CSS bundle is large — purge unused styles (PurgeCSS, Tailwind JIT) to reduce CSS payload.

Source: web.dev

B

Image Optimization

11 images, 0 KB saveable

REVIEW

11 images, 0 KB saveable

https://www.thousandsmiles.uk/wp-content/themes/th... is missing width/height — may cause layout shift

Set explicit width and height to prevent CLS.

https://www.thousandsmiles.uk/wp-content/themes/th... is missing width/height — may cause layout shift

Set explicit width and height to prevent CLS.

data:image/gif;base64,R0lGODdhAQABAPAAAMPDwwAAACwA... is missing width/height — may cause layout shift

Set explicit width and height to prevent CLS.

11 images 214 KB

0 oversized -0 KB

3 legacy format

3 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

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

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

B

Main HTML Cache-Control

No Cache-Control header on main HTML response

REVIEW

No Cache-Control header on main HTML response

Main HTML response has no Cache-Control header

Without an explicit Cache-Control, browsers fall back to heuristic caching (~10% of Last-Modified age). Set `Cache-Control: no-cache` or `max-age=300` for HTML to control freshness explicitly -- prevents stale auth state and SPA shell drift.

B

Server-Timing Observability

No Server-Timing header found

REVIEW

No Server-Timing header found

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.

B

JavaScript Blocking

1 JS blocking issue(s) detected

REVIEW

1 JS blocking issue(s) detected

9 render-blocking <script src> tag(s) without async/defer

Each `<script src=...>` without `async`, `defer`, or `type="module"` blocks HTML parsing while the browser fetches and executes it. The block lasts the entire round-trip + execution time -- on slow networks this translates directly into LCP delay. Add `defer` (executes after parse, in source order) for scripts that interact with the DOM, or `async` (executes whenever ready) for analytics / independent scripts. Module scripts (`type="module"`) are deferred by default.

A+

Text Compression

All text resources are compressed

PASS

All text resources are compressed

All text resources are compressed

All text resources are properly compressed.

A+

Font Loading

7 fonts (337 KB)

PASS

7 fonts (337 KB)

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

Web fonts

7

337 KB total

Render-blocking

0

of 7

Dominant font-display

swap

Most common across fonts

Font loading timeline

Transfer FOIT (block) FOUT (swap)

pxiEyp8kv8JHgFVrFJM.woff woff swap

Size 65 KB

Load time 208 ms

Start 277 ms

Risk FOUT — text flashes from fallback to web font

Convert to woff2 for ~30% smaller file size

pxiByp8kv8JHgFVrLCz7V1g... woff swap

Size 64 KB

Load time 203 ms

Start 278 ms

Risk FOUT — text flashes from fallback to web font

Convert to woff2 for ~30% smaller file size

pxiByp8kv8JHgFVrLEj6V1g... woff swap

Size 65 KB

Load time 202 ms

Start 280 ms

Risk FOUT — text flashes from fallback to web font

Convert to woff2 for ~30% smaller file size

x-font-woff;charset=utf... woff swap

Size 31 KB

Load time 9 ms

Start 297 ms

Risk FOUT — text flashes from fallback to web font

Convert to woff2 for ~30% smaller file size

fontawesome-webfont.woff2 woff2 swap

Size 76 KB

Load time 90 ms

Start 307 ms

Risk FOUT — text flashes from fallback to web font

wpxpress.woff woff swap

Size 3 KB

Load time 34 ms

Start 308 ms

Risk FOUT — text flashes from fallback to web font

Convert to woff2 for ~30% smaller file size

KFO7CnqEu92Fr1ME7kSn66a... woff2 swap

Size 34 KB

Load time 110 ms

Start 994 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 ~68 KB and ~136 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

15 hints, 0 missing preconnects

PASS

15 hints, 0 missing preconnects

Page uses 15 resource hint(s)

Current Resource Hints

preconnect

—

preload

+5

15

dns-prefetch

—

prefetch

—

15 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+

Document Compression

Document response uses brotli

PASS

Document response uses brotli

Main HTML response uses brotli (Content-Encoding: br)

Brotli is the best text-compression algorithm for general use, ~20% smaller than gzip on average (40% on smaller files). Modern browsers all support it.

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

CSS Performance Depth

1 CSS depth issue(s) detected

PASS

1 CSS depth issue(s) detected

12 render-blocking stylesheet(s) -- recommended: <=3

Each `<link rel="stylesheet">` without a non-blocking `media` attribute holds up the first paint. Browsers download all of them before painting any content. Consolidate into 1-2 critical-path stylesheets; defer non-critical CSS via `<link rel="stylesheet" media="print" onload="this.media='all'">` or via the loadCSS pattern; inline above-the-fold CSS in `<style>` to short-circuit the request entirely.

A+

Green Hosting

Whether the site is served from green-energy infrastructure

PASS

Green Hosting

This site is hosted on green energy infrastructure

Provider: Cloudflare

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

55 requests over 2524ms

INFO

HTML JavaScript CSS Images Fonts XHR/Fetch Other

Third-Party Script Cost

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

INFO

45% of JavaScript execution is third-party

First-party Third-party 936ms · 37KB · £10/mo

Script	Category	Execution	Transfer	Unused	Monthly Cost	Verdict
www.gstatic.com www.gstatic.com	Other	815ms	0 KB	53%	£8/mo	Costly
static.botsrv2.com static.botsrv2.com	Other	120ms	37 KB	56%	£1/mo	Optional

www.gstatic.com

Other

Costly

Execution 815ms

Transfer 0 KB

Unused 53%

Monthly Cost £8/mo

static.botsrv2.com

Other

Optional

Execution 120ms

Transfer 37 KB

Unused 56%

Monthly Cost £1/mo

These scripts may cost more than they're worth

www.gstatic.com adds 815ms and costs ~£8/month

45% of JavaScript execution time comes from third-party scripts.

Why this matters

Third-party scripts (analytics, ads, social, A/B testing) often dominate execution time — every one is a perf-and-privacy tax.

Learn more ▾

Each third-party script is a black box: you don't control when it loads, what it executes, or how much it grows. They often account for a major share of total blocking time on average sites (HTTP Archive's Web Almanac documents the trend). Audit which ones you actually need, defer the rest, and use facade patterns (lite-youtube, lite-vimeo) for embedded media.

Source: web.dev / HTTP Archive Web Almanac

www.gstatic.com takes 815ms 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

53% of www.gstatic.com's code is unused. The script may be loading features you don't use.

Why this matters

Bundle has high unused-code ratio — tree-shaking and route-splitting recover the wasted bytes.

Source: web.dev

56% of static.botsrv2.com's code is unused. The script may be loading features you don't use.

Why this matters

Bundle has high unused-code ratio — tree-shaking and route-splitting recover the wasted bytes.

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-10-02 — 2026-10-29)

LCP (p75)

1019 ms

95% good

INP (p75)

69 ms

96% good

CLS (p75)

0.170

60% good

FCP (p75)

682 ms

TTFB (p75)

566 ms

Image Optimization

10 images, 204 KB total, 119 KB wasted

INFO

Image Optimization Audit

Total Images

10

Total Size

204 KB

Oversized

2

Wasted

119 KB

10 missing dimensions 7 missing lazy loading

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

Send Feedback