Performance
· 15 checks — Lighthouse + waterfall + sustainability rolled into one auditable list.Performance-focused optimization plan with CWV assessment, top offenders, and time estimates
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
1.11 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
2.19 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
10 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.001
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
1.46 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.
2.36 s
Page Load Progression
568 ms
1.1 s
1.7 s 2.3 s
2.8 s
3.4 s 4.0 s
4.5 sFPage Weight BudgetAction2.9 MB transferred, 111 requestsFIX
Large JavaScript bundles delay interactivity. Split code by route or defer non-critical scripts.
JavaScript bundle is large — code-split routes and lazy-load off-screen components to defer.
Source: web.dev
Each request adds latency. Bundle small files, use sprites, or eliminate unnecessary requests.
High HTTP request count — bundling, sprite-ing, and HTTP/2 server push can reduce per-request overhead.
Source: web.dev
DThird-Party ImpactAction100% third-party, 0 ms blockingFIX
DJS BundlesAction55 scripts, 254 KB unusedFIX
Downloaded but never executed on this page.
| Script | Size | Unused | Minified | Party |
|---|---|---|---|---|
| https://www.googletagmanager.com/gtag/js?id=G-23ZQ6638VM&cx=c>m=4e64h1 | 165 KB | 65 KB (40%) | ✓ | 3rd |
| https://www.googletagmanager.com/gtm.js?id=GTM-TZT2564 | 152 KB | 63 KB (42%) | ✓ | 3rd |
| https://connect.facebook.net/he_IL/all.js?hash=ae379714d8a1c020fb3b2a93b5602751 | 83 KB | 58 KB (70%) | ✓ | 3rd |
| https://www.tau.ac.il/sites/all/libraries/jquery/jquery.js?v=3.5.1 | 83 KB | 34 KB (42%) | ✗ | 3rd |
| https://connect.facebook.net/en_US/fbevents.js | 97 KB | 33 KB (34%) | ✓ | 3rd |
| https://www.tau.ac.il/sites/default/files/languages/he_E_3KTcpOLu5vno0W_-SMVEBhtISCeNwzMu26gWX4lVY.js?tdudf9 | 2 KB | — | ✓ | 3rd |
| https://www.tau.ac.il/sites/all/modules/custom/skiplinks/js/skiplinks.js?tdudf9 | 1 KB | — | ✓ | 3rd |
| https://www.tau.ac.il/misc/drupal.js?tdudf9 | 7 KB | — | ✗ | 3rd |
| https://www.tau.ac.il/sites/all/modules/custom/feature/feature_jquery_update/js/jquery-fix.js?tdudf9 | 1 KB | — | ✓ | 3rd |
| https://www.tau.ac.il/sites/all/modules/custom/feature/feature_jquery_update/js/jquery-migrate-fix.js?tdudf9 | 0 KB | — | ✓ | 3rd |
Consider code splitting or tree shaking to reduce unused code.
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.
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.
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.
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.
This bundle has high unused code — code-split or tree-shake to ship only what executes.
Source: web.dev / Lighthouse coverage
DPage Weight InventoryAction111 resources · 2.9 MB · 254 KB savings availableFIX
~253.8 KiB of savings available
| # | Resource | Type | Size | Cache | Unused | 3rd party | Issues |
|---|---|---|---|---|---|---|---|
| — | — | ||||||
| 111 resources | 2.9 MiB | ||||||
FHTTP CachingActionNo cache headersFIX
No Cache-Control header
Adding a Cache-Control header can significantly improve repeat-visit performance.
BImage Optimization21 images, 0 KB saveableREVIEW
CGreen HostingActionWhether the site is served from green-energy infrastructureREVIEW
Green Hosting
No green hosting detected
A+Text CompressionAll text resources are compressedPASS
A+JS Execution Cost377ms total JS executionPASS
Main Thread Breakdown
| Script | Total | Scripting | Parse/Compile | Party |
|---|---|---|---|---|
| Unattributable | 111ms | 4ms | 0ms | 3rd |
| https://www.tau.ac.il/ | 80ms | 6ms | 1ms | 3rd |
| https://www.googletagmanager.com/gtag/js?id=G-23ZQ6638VM&cx=c>m=4e64h1 | 72ms | 60ms | 11ms | 3rd |
| https://www.googletagmanager.com/gtm.js?id=GTM-TZT2564 | 60ms | 50ms | 10ms | 3rd |
| https://cdn.appdynamics.com/adrum/adrum-23.8.0.4309.js | 54ms | 50ms | 2ms | 3rd |
A+Font Loading3 fonts (33 KB)PASS
Web fonts
3
33 KB total
Render-blocking
0
of 3
Dominant font-display
swap
Most common across fonts
Font loading timeline
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)
A+Resource CachingAll resources properly cachedPASS
A+Critical Rendering PathNo render-blocking resourcesPASS
A+Resource HintsNo optimization neededPASS
Network Waterfall111 requests over 2808msINFO
Third-Party Script CostPer-script blocking time, transfer cost, and cache headersINFO
| Script | Category | Execution | Transfer | Unused | Monthly Cost | Verdict |
|---|---|---|---|---|---|---|
Unattributable Unattributable | Other | 111ms | 0 KB | — | ₪4/mo | Optional |
www.tau.ac.il www.tau.ac.il | Other | 80ms | 93 KB | — | ₪3/mo | Optional |
Google Tag Manager www.googletagmanager.com | Tag Manager | 72ms | 165 KB | 40% | ₪3/mo | Optional |
Google Tag Manager www.googletagmanager.com | Tag Manager | 60ms | 152 KB | 42% | ₪2/mo | Optional |
cdn.appdynamics.com cdn.appdynamics.com | Other | 54ms | 33 KB | — | ₪2/mo | Optional |
100% of JavaScript execution time is spent on third-party scripts. Consider auditing which scripts are essential.
When third-party JS execution time exceeds your own, performance gains from frontend work are capped by code you don't own.
Learn more ▾ ▴
Every millisecond of third-party JS competes with your own for main-thread time. If their share is bigger than yours, optimization on your code base barely moves the needle. Audit, defer, or remove third-parties before further frontend optimization. Use Lighthouse's third-party audit to identify the worst offenders.
Source: web.dev