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.

2.09 s

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

3.57 s

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

110 ms

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

0.026

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

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

6.74 s

Page Load Progression

1.0 s

2.0 s

3.1 s

4.1 s

5.1 s

6.1 s

7.2 s

8.2 s

Checks

5 PASS 3 REVIEW 5 FIX

Page Weight Budget

Action

13.9 MB transferred, 178 requests

FIX

13.9 MB transferred, 178 requests

Page weighs 21.2 MB (13.9 MB transferred)

Images are 5.4 MB — compress or use modern formats

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

Got: 5.4 MB

JavaScript is 1.7 MB — consider code splitting or lazy loading

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

Got: 1.7 MB

CSS is 498 KB — consider purging unused styles

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

Got: 498 KB

178 HTTP requests — consider bundling or reducing

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

Estimated 2.9 g CO2 per page load

13.9 MB transferred

178 requests

2.9 g CO2 per page load

Other 6.0 MiB 43%

Images 5.4 MiB 39%

JavaScript 1.7 MiB 12%

CSS 498.4 KiB 3%

Fonts 192.6 KiB 1%

HTML 105.2 KiB 1%

Other 5.7 KiB 0%

Other 3.0 KiB 0%

Other 1.9 KiB 0%

Other 683 B 0%

Other 0 B 0%

0 2.4 MB 4.9 MB

Over budget

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

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

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

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 (13.9 MiB of 13.9 MiB)

Third-party blocking time is low (0 ms)

100%

First-party Third-party

JS Bundles

Action

69 scripts, 384 KB unused

FIX

69 scripts, 384 KB unused

https://www.cuny.edu/wp-content/plugins/revslider/...: 105 KB unused (97%)