Skip to content
https://www.ifttt.com

Performance

· 14 checks — Lighthouse + waterfall + sustainability rolled into one auditable list.
SCORE
84
GRADE
B
FIX
2
REVIEW
4
PASS
6
INFO
2

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

Mobile Desktop
90
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
93
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
96
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
100
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

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

1.41 s

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

1.41 s

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

12 ms

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

0.020

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

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

1.95 s

Page Load Progression

466 ms
932 ms
1.4 s
1.9 s
2.3 s
2.8 s
3.3 s
3.7 s
Checks
14
6 PASS 4 REVIEW 2 FIX
D
Third-Party Impact
Action
100% third-party, 0 ms blocking
FIX
100% third-party, 0 ms blocking
Warning::
Third-party code accounts for 100% of page weight (1.5 MiB of 1.5 MiB)
Info::
Third-party blocking time is low (0 ms)
100%
First-party Third-party
F
HTTP Caching
Action
No cache headers
FIX
No cache headers
Warning::
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.

B
Page Weight Budget
1.5 MB transferred, 74 requests
REVIEW
1.5 MB transferred, 74 requests
Info::
Page weighs 4.3 MB (1.5 MB transferred)
Warning::
JavaScript is 509 KB — consider code splitting or lazy loading
Large JavaScript bundles delay interactivity. Split code by route or defer non-critical scripts.
Got: 509 KB
Info::
74 HTTP requests
Info::
Estimated 0.31 g CO2 per page load
1.5 MB / 2.4 MB budget
1.5 MB transferred
74 requests
0.31 g CO2 per page load
Other 678.8 KiB 44%
JavaScript 508.8 KiB 33%
Images 144.6 KiB 9%
Fonts 93.7 KiB 6%
HTML 72.2 KiB 5%
CSS 26.3 KiB 2%
Other 1.8 KiB 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

B
JS Execution Cost
895ms total JS execution
REVIEW
895ms total JS execution
Warning::
https://ifttt.com/: 328ms CPU time
Info::
Unattributable: 227ms CPU time
Info::
https://web-assets.ifttt.com/builds/assets/header-...: 198ms CPU time
Info::
https://www.googletagmanager.com/gtag/js?id=G-LW9T...: 74ms CPU time
Info::
https://www.googletagmanager.com/gtm.js?id=GTM-NNB...: 69ms CPU time
Warning::
Third-party scripts: 895ms (100% of total)

Main Thread Breakdown

Other 35% Script Evaluation 34% Style & Layout 22% Parse HTML & CSS 3%
ScriptTotalScriptingParse/CompileParty
https://ifttt.com/328ms23ms1ms3rd
Unattributable227ms30ms0ms3rd
https://web-assets.ifttt.com/builds/assets/header-BL1JXuXM.js198ms124ms0ms3rd
https://www.googletagmanager.com/gtag/js?id=G-LW9TEDF6M2&cx=c&gtm=4e646074ms60ms12ms3rd
https://www.googletagmanager.com/gtm.js?id=GTM-NNB6HCT69ms56ms13ms3rd
C
JS Bundles
Action
17 scripts, 200 KB unused
REVIEW
17 scripts, 200 KB unused
Warning::
https://www.googletagmanager.com/gtm.js?id=GTM-NNB...: 82 KB unused (56%)
Consider code splitting or tree shaking to reduce unused code.
Warning::
https://www.googletagmanager.com/gtag/js?id=G-LW9T...: 71 KB unused (41%)
Consider code splitting or tree shaking to reduce unused code.
Warning::
https://web-assets.ifttt.com/builds/assets/header-...: 48 KB unused (49%)
Consider code splitting or tree shaking to reduce unused code.
Info::
Total unused JavaScript: 200 KB
200 KB unused JavaScript

Downloaded but never executed on this page.

ScriptSizeUnusedMinifiedParty
https://www.googletagmanager.com/gtm.js?id=GTM-NNB6HCT146 KB82 KB (56%)✓3rd
https://www.googletagmanager.com/gtag/js?id=G-LW9TEDF6M2&cx=c&gtm=4e6460175 KB71 KB (41%)✓3rd
https://web-assets.ifttt.com/builds/assets/header-BL1JXuXM.js99 KB48 KB (49%)✓3rd
https://web-assets.ifttt.com/builds/assets/setup_unified_header_dropdown-BvRXZELe.js1 KB—✓3rd
https://ifttt.com/lib.min.js32 KB—✓3rd
https://web-assets.ifttt.com/builds/assets/prosumer_home-BCHwP4z9.js2 KB—✓3rd
https://web-assets.ifttt.com/builds/assets/setup_unified_mobile_menu-BPXGQfFZ.js1 KB—✓3rd
https://web-assets.ifttt.com/builds/assets/shared_vanilla_setup-C9jVuncL.js2 KB—✓3rd
https://web-assets.ifttt.com/builds/assets/customer-ZmgQMiqW.js3 KB—✓3rd
https://web-assets.ifttt.com/builds/assets/preload-helper-BJPIp3l8.js3 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

C
Green Hosting
Action
Whether the site is served from green-energy infrastructure
REVIEW

Green Hosting

No green hosting detected

A+
Text Compression
All text resources are compressed
PASS
All text resources are compressed
Info::
All text resources are compressed
All text resources are properly compressed.
A
Image Optimization
37 images, 0 KB saveable
PASS
37 images, 0 KB saveable
Info::
All images are well-optimized
37 images 145 KB
0 oversized -0 KB
2 legacy format
0 missing dimensions CLS risk
A+
Font Loading
4 fonts (94 KB)
PASS
4 fonts (94 KB)
Info::
4 font(s) use font-display: swap (FOUT risk but functional)

Web fonts

4

94 KB total

Render-blocking

0

of 4

Dominant font-display

swap

Most common across fonts

Font loading timeline
Transfer FOIT (block) FOUT (swap)
0 ms 500 ms 1.0 s FCP 1.4 s LCP 1.4 shttps://web-assets.ifttt.com/builds/assets/avenir_next-heavy-CgodJsf-.woff2avenir_next-heavy-CgodJ... https://web-assets.ifttt.com/builds/assets/avenir_next-heavy-CgodJsf-.woff2 — 36.3 KiB — 0 ms — font-display: swaphttps://web-assets.ifttt.com/builds/assets/avenir_next-bold-ZNsI5KX4.woff2avenir_next-bold-ZNsI5K... https://web-assets.ifttt.com/builds/assets/avenir_next-bold-ZNsI5KX4.woff2 — 19.3 KiB — 0 ms — font-display: swaphttps://web-assets.ifttt.com/builds/assets/avenir_next-demi-DaV_O9Wc.woff2avenir_next-demi-DaV_O9... https://web-assets.ifttt.com/builds/assets/avenir_next-demi-DaV_O9Wc.woff2 — 19.0 KiB — 0 ms — font-display: swaphttps://web-assets.ifttt.com/builds/assets/avenir_next-medium-DSUCEw9K.woff2avenir_next-medium-DSUC... https://web-assets.ifttt.com/builds/assets/avenir_next-medium-DSUCEw9K.woff2 — 19.1 KiB — 0 ms — font-display: swap
avenir_next-heavy-CgodJ... woff2 swap
Size 36 KB
Load time 0 ms
Start 0 ms
Risk FOUT — text flashes from fallback to web font
avenir_next-bold-ZNsI5K... woff2 swap
Size 19 KB
Load time 0 ms
Start 0 ms
Risk FOUT — text flashes from fallback to web font
avenir_next-demi-DaV_O9... woff2 swap
Size 19 KB
Load time 0 ms
Start 0 ms
Risk FOUT — text flashes from fallback to web font
avenir_next-medium-DSUC... woff2 swap
Size 19 KB
Load time 0 ms
Start 0 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)
A+
Resource Caching
All resources properly cached
PASS
All resources properly cached
Info::
No caching issues found
All static resources have appropriate caching headers.
A+
Critical Rendering Path
No render-blocking resources
PASS
No render-blocking resources
Info::
No render-blocking resources detected
A+
Resource Hints
No optimization needed
PASS
No optimization needed
Info::
No resource hint issues
Network Waterfall
74 requests over 0ms
INFO

Performance analysis not available for this result.

Third-Party Script Cost
Per-script blocking time, transfer cost, and cache headers
INFO
100% of JavaScript execution is third-party
First-party Third-party 895ms · 492KB · €14/mo
ifttt.com
Other
Costly
Execution 328ms
Transfer 72 KB
Monthly Cost €5/mo
Unattributable
Other
Costly
Execution 227ms
Transfer 0 KB
Monthly Cost €4/mo
web-assets.ifttt.com
Other
Optional
Execution 198ms
Transfer 99 KB
Unused 49%
Monthly Cost €3/mo
Google Tag Manager
Tag Manager
Optional
Execution 74ms
Transfer 175 KB
Unused 41%
Monthly Cost €1/mo
Google Tag Manager
Tag Manager
Optional
Execution 69ms
Transfer 146 KB
Unused 56%
Monthly Cost €1/mo

These scripts may cost more than they're worth

  • ifttt.com adds 328ms and costs ~€5/month
  • Unattributable adds 227ms and costs ~€4/month

100% of JavaScript execution time is spent on third-party scripts. Consider auditing which scripts are essential.

Why this matters

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

ifttt.com takes 328ms 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

Unattributable takes 227ms 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

56% of Google Tag Manager'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

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

Send Feedback