# Unlighthouse
> Google Lighthouse for your entire site.
Canonical Origin: https://unlighthouse.dev/
**Agent Skills:**
Skills an agent can install from this site. The index at https://unlighthouse.dev/.well-known/agent-skills/index.json carries a sha256 digest for each one.
## LLM Resources
- [Full Content](https://unlighthouse.dev/llms-full.txt): Complete page content in markdown format.
## Agent Skills
- [Agent Skills index](https://unlighthouse.dev/.well-known/agent-skills/index.json): Every published skill and its sha256 digest.
- [unlighthouse](https://unlighthouse.dev/SKILL.md): Run Google Lighthouse on every page of a site with the unlighthouse CLI, and fail CI on low scores with unlighthouse-ci. Use when a task mentions unlighthouse, unlighthouse-ci, site-wide Lighthouse scans, performance budgets in CI, unlighthouse.config.ts, defineUnlighthouseConfig, scanner.exclude, dynamic sampling, the authenticate hook, or a scan that never exits, skips pages, or refuses to clear its output folder.
---
- **Page:** Bulk PageSpeed Test - Lighthouse Performance Scores · Unlighthouse
- **Source:** https://unlighthouse.dev/tools/bulk-pagespeed
- **Description:** Check Lighthouse Performance scores and lab metrics for up to 10 URLs. Compare page results and export measurements.
```yaml
meta:
og:image: https://unlighthouse.dev/_og/s/o_0e5bae702a06bcd4.png
og:image:height: "600"
og:image:type: image/png
og:image:width: "1200"
twitter:image: https://unlighthouse.dev/_og/s/o_0e5bae702a06bcd4.png
```
# **Bulk PageSpeed **Test
Test up to 10 URLs at once with Google's PageSpeed Insights API. Get Lighthouse performance scores, Core Web Vitals, and optimization insights.
**Bulk PageSpeed Test**
**Enter URLs **(one per line, max 10)
0/10 URLs
Device:
Enter URLs to run a bulk PageSpeed test
Test up to 10 URLs at once
## **Frequently Asked Questions **
**01**
### **What is bulk PageSpeed testing?**
Bulk PageSpeed testing lets you analyze multiple URLs simultaneously using the PageSpeed Insights API. Instead of testing pages one at a time, you can submit up to 10 URLs and get Lighthouse Performance scores and lab metrics for all pages at once.
**02**
### **How do I use the PageSpeed Insights API for bulk testing?**
The PageSpeed Insights API (pagespeedonline/v5/runpagespeed) accepts a URL parameter and returns Lighthouse results as JSON. This tool handles the API calls for you, but for programmatic access you can call the API directly with your own API key for higher rate limits.
**03**
### **Is there a limit to bulk PageSpeed testing?**
This free tool allows testing up to 10 URLs at once. The PageSpeed Insights API has rate limits (400 requests per day for anonymous users, 25,000 with an API key). For scanning entire sites with hundreds of pages, use Unlighthouse CLI instead.
**04**
### **What metrics does bulk PageSpeed testing show?**
Each URL gets a full Lighthouse audit including: Performance score (0-100), LCP, CLS, TBT, First Contentful Paint, Speed Index, and score-band counts. Results help identify which pages need optimization.
**05**
### **When should I use bulk testing vs full site scanning?**
Use bulk testing for quick checks of specific pages like landing pages, product pages, or comparing competitor URLs. For comprehensive site-wide analysis with all pages automatically discovered, use Unlighthouse CLI which crawls your sitemap and tests every page.
### **Related Guides **
[**Fix LCP Issues **](https://unlighthouse.dev/learn-lighthouse/lcp) [** Fix CLS Issues **](https://unlighthouse.dev/learn-lighthouse/cls) [** Bulk Testing Guide **](https://unlighthouse.dev/learn-lighthouse/bulk-lighthouse-testing) [** Understand Speed Index **](https://unlighthouse.dev/glossary/speed-index)
### **Need to scan your entire site? **
Unlighthouse automatically discovers and audits hundreds of pages on your site. Get comprehensive performance insights with a single command.
$ npx unlighthouse --site example.com
[**Try Unlighthouse CLI (Free) **](https://unlighthouse.dev/guide/getting-started/installation) [** Automate Audits in CI **](https://unlighthouse.dev/integrations/ci)
```json
{"@context":"https://schema.org","@graph":[{"@id":"https://unlighthouse.dev/#website","@type":"WebSite","description":"Google Lighthouse for your entire site.","name":"Unlighthouse","url":"https://unlighthouse.dev/","publisher":{"@id":"https://unlighthouse.dev/#identity"}},{"@id":"https://unlighthouse.dev/tools/bulk-pagespeed#webpage","@type":"WebPage","description":"Check Lighthouse Performance scores and lab metrics for up to 10 URLs. Compare page results and export measurements.","name":"Bulk PageSpeed Test - Lighthouse Performance Scores","url":"https://unlighthouse.dev/tools/bulk-pagespeed","isPartOf":{"@id":"https://unlighthouse.dev/#website"},"potentialAction":[{"@type":"ReadAction","target":["https://unlighthouse.dev/tools/bulk-pagespeed"]}],"primaryImageOfPage":{"@id":"https://unlighthouse.dev/#logo"}},{"@id":"https://unlighthouse.dev/#identity","@type":"Organization","name":"Unlighthouse","url":"https://unlighthouse.dev","logo":{"@id":"https://unlighthouse.dev/#logo"}},{"@id":"https://unlighthouse.dev/tools/bulk-pagespeed#/schema/web-application/1","@type":"WebApplication","applicationCategory":"DeveloperApplication","description":"Check Lighthouse Performance scores and lab metrics for up to 10 URLs. Compare page results and export measurements.","name":"Bulk PageSpeed Test - Lighthouse Performance Scores","operatingSystem":"Web","url":"https://unlighthouse.dev/tools/bulk-pagespeed","offers":{"@type":"Offer","price":"0","priceCurrency":"USD"}},{"@id":"https://unlighthouse.dev/tools/bulk-pagespeed#/schema/faqpage/1","@type":"FAQPage","mainEntity":[{"@type":"Question","name":"What is bulk PageSpeed testing?","acceptedAnswer":{"@type":"Answer","text":"Bulk PageSpeed testing lets you analyze multiple URLs simultaneously using the PageSpeed Insights API. Instead of testing pages one at a time, you can submit up to 10 URLs and get Lighthouse Performance scores and lab metrics for all pages at once."}},{"@type":"Question","name":"How do I use the PageSpeed Insights API for bulk testing?","acceptedAnswer":{"@type":"Answer","text":"The PageSpeed Insights API (pagespeedonline/v5/runpagespeed) accepts a URL parameter and returns Lighthouse results as JSON. This tool handles the API calls for you, but for programmatic access you can call the API directly with your own API key for higher rate limits."}},{"@type":"Question","name":"Is there a limit to bulk PageSpeed testing?","acceptedAnswer":{"@type":"Answer","text":"This free tool allows testing up to 10 URLs at once. The PageSpeed Insights API has rate limits (400 requests per day for anonymous users, 25,000 with an API key). For scanning entire sites with hundreds of pages, use Unlighthouse CLI instead."}},{"@type":"Question","name":"What metrics does bulk PageSpeed testing show?","acceptedAnswer":{"@type":"Answer","text":"Each URL gets a full Lighthouse audit including: Performance score (0-100), LCP, CLS, TBT, First Contentful Paint, Speed Index, and score-band counts. Results help identify which pages need optimization."}},{"@type":"Question","name":"When should I use bulk testing vs full site scanning?","acceptedAnswer":{"@type":"Answer","text":"Use bulk testing for quick checks of specific pages like landing pages, product pages, or comparing competitor URLs. For comprehensive site-wide analysis with all pages automatically discovered, use Unlighthouse CLI which crawls your sitemap and tests every page."}}]},{"@id":"https://unlighthouse.dev/#logo","@type":"ImageObject","caption":"Unlighthouse","contentUrl":"https://unlighthouse.dev/logo.png","inLanguage":"en","url":"https://unlighthouse.dev/logo.png"}]}
```
---
- **Page:** CLS Debugger - Free Layout Shift Testing Tool · Unlighthouse
- **Source:** https://unlighthouse.dev/tools/cls-debugger
- **Description:** Free CLS testing tool. Enter a URL to find which elements cause Cumulative Layout Shift and get actionable fixes. No signup required.
```yaml
meta:
og:image: https://unlighthouse.dev/_og/s/o_7008eea535662f62.png
og:image:height: "600"
og:image:type: image/png
og:image:width: "1200"
twitter:image: https://unlighthouse.dev/_og/s/o_7008eea535662f62.png
```
# **CLS **Debugger
Find which elements cause layout shifts and fix the jank.
**CLS Analysis**
Enter a URL to debug layout shifts
## **What is Cumulative Layout Shift? **
CLS measures **visual stability**—how much elements move unexpectedly while the page loads. A high CLS score means users experience jarring shifts, like clicking a button that suddenly moves because an ad loaded above it.
Google considers CLS one of the three [Core Web Vitals](https://web.dev/vitals/) that directly affect search rankings. A score of **0.1 or below** is considered good.
### **Layout Shift Example **
Elements moving after render causes poor **user experience** and missed clicks.
## **Common CLS Causes & Fixes **
Most layout shifts come from these common issues
**Unsized Images**
Images without width/height push content when they load.
``
**Font Loading**
Custom fonts can cause text to reflow when they load.
`font-display: optional;`
**Dynamic Content**
Ads, embeds, and async content push existing content.
`Reserve space with min-height`
**CSS Animations**
Avoid animating properties that trigger layout.
`Use transform, not top/left`
**Injected Elements**
Banners, cookie notices, and alerts inserted at the top.
`Use position: fixed or sticky`
**Missing Placeholders**
Async content should have skeleton loaders.
`Show skeleton while loading`
## **Frequently Asked Questions **
**01**
### **What is Cumulative Layout Shift (CLS)?**
Cumulative Layout Shift (CLS) is a Core Web Vital that measures visual stability. It quantifies how much page content unexpectedly shifts during loading. A good CLS score is 0.1 or less, meaning minimal unexpected movement of visible elements.
**02**
### **How do I find layout shift culprits on my page?**
This CLS debugger identifies exactly which elements cause layout shifts by analyzing your page with Lighthouse. It shows you the specific DOM elements, their shift scores, and visual overlays highlighting problem areas. Common culprits include images without dimensions, ads, embeds, and dynamically injected content.
**03**
### **What causes high CLS scores?**
High CLS is typically caused by: images or videos without explicit width/height attributes, ads or embeds that resize after loading, web fonts causing FOUT/FOIT, dynamically injected content above existing content, and animations that trigger layout changes instead of using transform.
**04**
### **How do I fix Cumulative Layout Shift issues?**
To fix CLS: always set width and height on images and video elements, reserve space for ads and embeds with CSS aspect-ratio, use font-display: optional or swap with fallback fonts, avoid inserting content above existing content, and use CSS transforms for animations instead of properties that trigger layout.
**05**
### **What is the difference between CLS in lab data vs field data?**
Lab CLS measures layout shifts during initial page load in a controlled environment. Field CLS (from real users) captures shifts throughout the entire page session, including those from user interactions. Field data often shows higher CLS because it includes shifts from lazy-loaded content and user-triggered changes.
Explore more Core Web Vitals tools
[**LCP Finder **](https://unlighthouse.dev/tools/lcp-finder) [** Full Performance Report **](https://unlighthouse.dev/tools/pagespeed-insights-performance) [** CLS Optimization Guide **](https://unlighthouse.dev/learn-lighthouse/cls)
```json
{"@context":"https://schema.org","@graph":[{"@id":"https://unlighthouse.dev/#website","@type":"WebSite","description":"Google Lighthouse for your entire site.","name":"Unlighthouse","url":"https://unlighthouse.dev/","publisher":{"@id":"https://unlighthouse.dev/#identity"}},{"@id":"https://unlighthouse.dev/tools/cls-debugger#webpage","@type":"WebPage","description":"Free CLS testing tool. Enter a URL to find which elements cause Cumulative Layout Shift and get actionable fixes. No signup required.","name":"CLS Debugger - Free Layout Shift Testing Tool","url":"https://unlighthouse.dev/tools/cls-debugger","isPartOf":{"@id":"https://unlighthouse.dev/#website"},"potentialAction":[{"@type":"ReadAction","target":["https://unlighthouse.dev/tools/cls-debugger"]}],"primaryImageOfPage":{"@id":"https://unlighthouse.dev/#logo"}},{"@id":"https://unlighthouse.dev/#identity","@type":"Organization","name":"Unlighthouse","url":"https://unlighthouse.dev","logo":{"@id":"https://unlighthouse.dev/#logo"}},{"@id":"https://unlighthouse.dev/tools/cls-debugger#/schema/web-application/1","@type":"WebApplication","applicationCategory":"DeveloperApplication","description":"Free CLS testing tool. Enter a URL to find which elements cause Cumulative Layout Shift and get actionable fixes. No signup required.","name":"CLS Debugger - Free Layout Shift Testing Tool","operatingSystem":"Web","url":"https://unlighthouse.dev/tools/cls-debugger","offers":{"@type":"Offer","price":"0","priceCurrency":"USD"}},{"@id":"https://unlighthouse.dev/tools/cls-debugger#/schema/faqpage/1","@type":"FAQPage","mainEntity":[{"@type":"Question","name":"What is Cumulative Layout Shift (CLS)?","acceptedAnswer":{"@type":"Answer","text":"Cumulative Layout Shift (CLS) is a Core Web Vital that measures visual stability. It quantifies how much page content unexpectedly shifts during loading. A good CLS score is 0.1 or less, meaning minimal unexpected movement of visible elements."}},{"@type":"Question","name":"How do I find layout shift culprits on my page?","acceptedAnswer":{"@type":"Answer","text":"This CLS debugger identifies exactly which elements cause layout shifts by analyzing your page with Lighthouse. It shows you the specific DOM elements, their shift scores, and visual overlays highlighting problem areas. Common culprits include images without dimensions, ads, embeds, and dynamically injected content."}},{"@type":"Question","name":"What causes high CLS scores?","acceptedAnswer":{"@type":"Answer","text":"High CLS is typically caused by: images or videos without explicit width/height attributes, ads or embeds that resize after loading, web fonts causing FOUT/FOIT, dynamically injected content above existing content, and animations that trigger layout changes instead of using transform."}},{"@type":"Question","name":"How do I fix Cumulative Layout Shift issues?","acceptedAnswer":{"@type":"Answer","text":"To fix CLS: always set width and height on images and video elements, reserve space for ads and embeds with CSS aspect-ratio, use font-display: optional or swap with fallback fonts, avoid inserting content above existing content, and use CSS transforms for animations instead of properties that trigger layout."}},{"@type":"Question","name":"What is the difference between CLS in lab data vs field data?","acceptedAnswer":{"@type":"Answer","text":"Lab CLS measures layout shifts during initial page load in a controlled environment. Field CLS (from real users) captures shifts throughout the entire page session, including those from user interactions. Field data often shows higher CLS because it includes shifts from lazy-loaded content and user-triggered changes."}}]},{"@id":"https://unlighthouse.dev/#logo","@type":"ImageObject","caption":"Unlighthouse","contentUrl":"https://unlighthouse.dev/logo.png","inLanguage":"en","url":"https://unlighthouse.dev/logo.png"}]}
```
---
- **Page:** Core Web Vitals Test - Free CWV Checker · Unlighthouse
- **Source:** https://unlighthouse.dev/tools/cwv-checker
- **Description:** Check available field Core Web Vitals and inspect Lighthouse lab results. View measurement sources and recommendations.
```yaml
meta:
og:image: https://unlighthouse.dev/_og/s/o_8ebb0742b047a8b2.png
og:image:height: "600"
og:image:type: image/png
og:image:width: "1200"
twitter:image: https://unlighthouse.dev/_og/s/o_8ebb0742b047a8b2.png
```
# **Core Web Vitals **Test
Check available field Core Web Vitals and inspect Lighthouse lab results.
**Core Web Vitals Assessment**
Enter a URL to check Core Web Vitals
## **Frequently Asked Questions **
**01**
### **What are Core Web Vitals?**
Core Web Vitals are three metrics Google uses to measure user experience: LCP (loading speed), CLS (visual stability), and INP (interactivity). They are a confirmed ranking factor in Google Search.
**02**
### **What is a good Core Web Vitals score?**
Good field values are LCP at most 2.5 seconds, CLS at most 0.1, and INP at most 200 milliseconds. The assessment uses eligible field p75 measurements. LCP and CLS are required. If INP is unavailable, those two metrics can still establish the assessment.
**03**
### **What's the difference between Lab and Field data?**
Lab data is collected in a controlled environment (Lighthouse). Field data is from real users via the Chrome User Experience Report (CrUX). Field data is what Google uses for ranking, but lab data helps diagnose issues.
**04**
### **Do Core Web Vitals affect SEO?**
Yes. Core Web Vitals are a confirmed Google ranking factor as part of page experience signals. Pages that pass CWV may have a ranking advantage over those that don't, especially for competitive queries.
### **Optimize Your Core Web Vitals **
[**Fix LCP **](https://unlighthouse.dev/learn-lighthouse/lcp) [** Fix CLS **](https://unlighthouse.dev/learn-lighthouse/cls) [** Fix INP **](https://unlighthouse.dev/learn-lighthouse/inp) [** Full Guide **](https://unlighthouse.dev/learn-lighthouse/core-web-vitals)
```json
{"@context":"https://schema.org","@graph":[{"@id":"https://unlighthouse.dev/#website","@type":"WebSite","description":"Google Lighthouse for your entire site.","name":"Unlighthouse","url":"https://unlighthouse.dev/","publisher":{"@id":"https://unlighthouse.dev/#identity"}},{"@id":"https://unlighthouse.dev/tools/cwv-checker#webpage","@type":"WebPage","description":"Check available field Core Web Vitals and inspect Lighthouse lab results. View measurement sources and recommendations.","name":"Core Web Vitals Test - Free CWV Checker","url":"https://unlighthouse.dev/tools/cwv-checker","isPartOf":{"@id":"https://unlighthouse.dev/#website"},"potentialAction":[{"@type":"ReadAction","target":["https://unlighthouse.dev/tools/cwv-checker"]}],"primaryImageOfPage":{"@id":"https://unlighthouse.dev/#logo"}},{"@id":"https://unlighthouse.dev/#identity","@type":"Organization","name":"Unlighthouse","url":"https://unlighthouse.dev","logo":{"@id":"https://unlighthouse.dev/#logo"}},{"@id":"https://unlighthouse.dev/tools/cwv-checker#/schema/web-application/1","@type":"WebApplication","applicationCategory":"DeveloperApplication","description":"Check available field Core Web Vitals and inspect Lighthouse lab results. View measurement sources and recommendations.","name":"Core Web Vitals Test - Free CWV Checker","operatingSystem":"Web","url":"https://unlighthouse.dev/tools/cwv-checker","offers":{"@type":"Offer","price":"0","priceCurrency":"USD"}},{"@id":"https://unlighthouse.dev/tools/cwv-checker#/schema/faqpage/1","@type":"FAQPage","mainEntity":[{"@type":"Question","name":"What are Core Web Vitals?","acceptedAnswer":{"@type":"Answer","text":"Core Web Vitals are three metrics Google uses to measure user experience: LCP (loading speed), CLS (visual stability), and INP (interactivity). They are a confirmed ranking factor in Google Search."}},{"@type":"Question","name":"What is a good Core Web Vitals score?","acceptedAnswer":{"@type":"Answer","text":"Good field values are LCP at most 2.5 seconds, CLS at most 0.1, and INP at most 200 milliseconds. The assessment uses eligible field p75 measurements. LCP and CLS are required. If INP is unavailable, those two metrics can still establish the assessment."}},{"@type":"Question","name":"What's the difference between Lab and Field data?","acceptedAnswer":{"@type":"Answer","text":"Lab data is collected in a controlled environment (Lighthouse). Field data is from real users via the Chrome User Experience Report (CrUX). Field data is what Google uses for ranking, but lab data helps diagnose issues."}},{"@type":"Question","name":"Do Core Web Vitals affect SEO?","acceptedAnswer":{"@type":"Answer","text":"Yes. Core Web Vitals are a confirmed Google ranking factor as part of page experience signals. Pages that pass CWV may have a ranking advantage over those that don't, especially for competitive queries."}}]},{"@id":"https://unlighthouse.dev/#logo","@type":"ImageObject","caption":"Unlighthouse","contentUrl":"https://unlighthouse.dev/logo.png","inLanguage":"en","url":"https://unlighthouse.dev/logo.png"}]}
```
---
- **Page:** Bulk Core Web Vitals Test - Compare CWV Across Sites · Unlighthouse
- **Source:** https://unlighthouse.dev/tools/cwv-compare
- **Description:** Bulk test and compare Core Web Vitals across multiple websites. See how your LCP, CLS, and INP stack up against competitors with real Chrome user data.
```yaml
meta:
og:image: https://unlighthouse.dev/_og/s/o_19ff2c70fa936e3b.png
og:image:height: "600"
og:image:type: image/png
og:image:width: "1200"
twitter:image: https://unlighthouse.dev/_og/s/o_19ff2c70fa936e3b.png
```
**PERFORMANCE SHOWDOWN **
# **CWV **Compare
**Pit your site against competitors. Real Chrome user data. Clear winners. **
**Core Web Vitals Comparison**• Field data from real Chrome users
**CrUX **
**Enter domains to compare **
Compare 2-4 sites using real Chrome user data
## **Frequently Asked Questions **
**01**
### **What data is being compared?**
This tool compares real user performance data from the Chrome User Experience Report (CrUX). It shows P75 values—the experience of 75% of your users.
**02**
### **Why is there no data for a site?**
Sites need sufficient Chrome traffic to appear in CrUX. New sites, low-traffic sites, or sites blocking data collection won't have field data available.
**03**
### **How is the winner determined?**
For each metric, the site with the lowest (fastest/best) P75 value wins. Overall winner prioritizes the number of good Core Web Vitals metrics, then combined metric performance.
**04**
### **Can I share this comparison?**
Yes! The URL updates as you compare sites. Copy and share the URL to show others the same comparison results.
### **Improve Your Core Web Vitals **
[**Fix LCP **](https://unlighthouse.dev/learn-lighthouse/lcp) [** Fix CLS **](https://unlighthouse.dev/learn-lighthouse/cls) [** Fix INP **](https://unlighthouse.dev/learn-lighthouse/inp) [** Full Guide **](https://unlighthouse.dev/learn-lighthouse/core-web-vitals)
```json
{"@context":"https://schema.org","@graph":[{"@id":"https://unlighthouse.dev/#website","@type":"WebSite","description":"Google Lighthouse for your entire site.","name":"Unlighthouse","url":"https://unlighthouse.dev/","publisher":{"@id":"https://unlighthouse.dev/#identity"}},{"@id":"https://unlighthouse.dev/tools/cwv-compare#webpage","@type":"WebPage","description":"Bulk test and compare Core Web Vitals across multiple websites. See how your LCP, CLS, and INP stack up against competitors with real Chrome user data.","name":"Bulk Core Web Vitals Test - Compare CWV Across Sites","url":"https://unlighthouse.dev/tools/cwv-compare","isPartOf":{"@id":"https://unlighthouse.dev/#website"},"potentialAction":[{"@type":"ReadAction","target":["https://unlighthouse.dev/tools/cwv-compare"]}],"primaryImageOfPage":{"@id":"https://unlighthouse.dev/#logo"}},{"@id":"https://unlighthouse.dev/#identity","@type":"Organization","name":"Unlighthouse","url":"https://unlighthouse.dev","logo":{"@id":"https://unlighthouse.dev/#logo"}},{"@id":"https://unlighthouse.dev/tools/cwv-compare#/schema/web-application/1","@type":"WebApplication","applicationCategory":"DeveloperApplication","description":"Bulk test and compare Core Web Vitals across multiple websites. See how your LCP, CLS, and INP stack up against competitors with real Chrome user data.","name":"Bulk Core Web Vitals Test - Compare CWV Across Sites","operatingSystem":"Web","url":"https://unlighthouse.dev/tools/cwv-compare","offers":{"@type":"Offer","price":"0","priceCurrency":"USD"}},{"@id":"https://unlighthouse.dev/tools/cwv-compare#/schema/faqpage/1","@type":"FAQPage","mainEntity":[{"@type":"Question","name":"What data is being compared?","acceptedAnswer":{"@type":"Answer","text":"This tool compares real user performance data from the Chrome User Experience Report (CrUX). It shows P75 values—the experience of 75% of your users."}},{"@type":"Question","name":"Why is there no data for a site?","acceptedAnswer":{"@type":"Answer","text":"Sites need sufficient Chrome traffic to appear in CrUX. New sites, low-traffic sites, or sites blocking data collection won't have field data available."}},{"@type":"Question","name":"How is the winner determined?","acceptedAnswer":{"@type":"Answer","text":"For each metric, the site with the lowest (fastest/best) P75 value wins. Overall winner prioritizes the number of good Core Web Vitals metrics, then combined metric performance."}},{"@type":"Question","name":"Can I share this comparison?","acceptedAnswer":{"@type":"Answer","text":"Yes! The URL updates as you compare sites. Copy and share the URL to show others the same comparison results."}}]},{"@id":"https://unlighthouse.dev/#logo","@type":"ImageObject","caption":"Unlighthouse","contentUrl":"https://unlighthouse.dev/logo.png","inLanguage":"en","url":"https://unlighthouse.dev/logo.png"}]}
```
---
- **Page:** Core Web Vitals History - Track Performance Over Time · Unlighthouse
- **Source:** https://unlighthouse.dev/tools/cwv-history
- **Description:** Free CrUX history viewer. Track 25 weeks of LCP, CLS, and INP trends from real Chrome users. Monitor Core Web Vitals changes over time.
```yaml
meta:
og:image: https://unlighthouse.dev/_og/s/o_be5b97d576fb046d.png
og:image:height: "600"
og:image:type: image/png
og:image:width: "1200"
twitter:image: https://unlighthouse.dev/_og/s/o_be5b97d576fb046d.png
```
# **Core Web Vitals **History
Track Core Web Vitals trends over time with 25 weeks of real Chrome user data.
**CrUX Historical Data**Field data from real Chrome users
Enter a domain to view CrUX history
Tracks real Chrome user data over 25 weeks
### **Optimize Your Core Web Vitals **
[**Full Guide **](https://unlighthouse.dev/learn-lighthouse/core-web-vitals) [** Fix LCP **](https://unlighthouse.dev/learn-lighthouse/lcp) [** Fix CLS **](https://unlighthouse.dev/learn-lighthouse/cls) [** Fix INP **](https://unlighthouse.dev/learn-lighthouse/inp)
## **Frequently Asked Questions **
**01**
### **What is Core Web Vitals history data?**
CrUX (Chrome User Experience Report) stores 25 weeks of real user performance data for sites with sufficient traffic. This historical data shows how your Core Web Vitals (LCP, CLS, INP) have changed over time, helping you track improvement or detect regressions.
**02**
### **Where does this historical performance data come from?**
Historical data comes from CrUX, Google's dataset of real Chrome user experiences. Google collects anonymized performance metrics from Chrome users who have opted in. The data represents the 75th percentile (p75) of real user experiences over 28-day rolling periods.
**03**
### **Why don't I see historical data for my site?**
CrUX only includes sites with sufficient traffic from Chrome users. New sites, low-traffic pages, or sites visited primarily by non-Chrome browsers may not have data. Origin-level data aggregates all pages and requires less traffic than URL-specific data.
**04**
### **What can I learn from Core Web Vitals trends?**
Trends help you: correlate performance changes with deployments, detect gradual degradation before users notice, measure the impact of optimizations over time, compare mobile vs desktop performance, and identify seasonal patterns affecting user experience.
**05**
### **How often is CrUX historical data updated?**
CrUX data is updated weekly with a new 28-day rolling window. Each data point represents the 75th percentile of user experiences during that collection period. This means changes you make today will start showing in the data within 1-4 weeks.
```json
{"@context":"https://schema.org","@graph":[{"@id":"https://unlighthouse.dev/#website","@type":"WebSite","description":"Google Lighthouse for your entire site.","name":"Unlighthouse","url":"https://unlighthouse.dev/","publisher":{"@id":"https://unlighthouse.dev/#identity"}},{"@id":"https://unlighthouse.dev/tools/cwv-history#webpage","@type":"WebPage","description":"Free CrUX history viewer. Track 25 weeks of LCP, CLS, and INP trends from real Chrome users. Monitor Core Web Vitals changes over time.","name":"Core Web Vitals History - Track Performance Over Time","url":"https://unlighthouse.dev/tools/cwv-history","isPartOf":{"@id":"https://unlighthouse.dev/#website"},"potentialAction":[{"@type":"ReadAction","target":["https://unlighthouse.dev/tools/cwv-history"]}],"primaryImageOfPage":{"@id":"https://unlighthouse.dev/#logo"}},{"@id":"https://unlighthouse.dev/#identity","@type":"Organization","name":"Unlighthouse","url":"https://unlighthouse.dev","logo":{"@id":"https://unlighthouse.dev/#logo"}},{"@id":"https://unlighthouse.dev/tools/cwv-history#/schema/web-application/1","@type":"WebApplication","applicationCategory":"DeveloperApplication","description":"Free CrUX history viewer. Track 25 weeks of LCP, CLS, and INP trends from real Chrome users. Monitor Core Web Vitals changes over time.","name":"Core Web Vitals History - Track Performance Over Time","operatingSystem":"Web","url":"https://unlighthouse.dev/tools/cwv-history","offers":{"@type":"Offer","price":"0","priceCurrency":"USD"}},{"@id":"https://unlighthouse.dev/tools/cwv-history#/schema/faqpage/1","@type":"FAQPage","mainEntity":[{"@type":"Question","name":"What is Core Web Vitals history data?","acceptedAnswer":{"@type":"Answer","text":"CrUX (Chrome User Experience Report) stores 25 weeks of real user performance data for sites with sufficient traffic. This historical data shows how your Core Web Vitals (LCP, CLS, INP) have changed over time, helping you track improvement or detect regressions."}},{"@type":"Question","name":"Where does this historical performance data come from?","acceptedAnswer":{"@type":"Answer","text":"Historical data comes from CrUX, Google's dataset of real Chrome user experiences. Google collects anonymized performance metrics from Chrome users who have opted in. The data represents the 75th percentile (p75) of real user experiences over 28-day rolling periods."}},{"@type":"Question","name":"Why don't I see historical data for my site?","acceptedAnswer":{"@type":"Answer","text":"CrUX only includes sites with sufficient traffic from Chrome users. New sites, low-traffic pages, or sites visited primarily by non-Chrome browsers may not have data. Origin-level data aggregates all pages and requires less traffic than URL-specific data."}},{"@type":"Question","name":"What can I learn from Core Web Vitals trends?","acceptedAnswer":{"@type":"Answer","text":"Trends help you: correlate performance changes with deployments, detect gradual degradation before users notice, measure the impact of optimizations over time, compare mobile vs desktop performance, and identify seasonal patterns affecting user experience."}},{"@type":"Question","name":"How often is CrUX historical data updated?","acceptedAnswer":{"@type":"Answer","text":"CrUX data is updated weekly with a new 28-day rolling window. Each data point represents the 75th percentile of user experiences during that collection period. This means changes you make today will start showing in the data within 1-4 weeks."}}]},{"@id":"https://unlighthouse.dev/#logo","@type":"ImageObject","caption":"Unlighthouse","contentUrl":"https://unlighthouse.dev/logo.png","inLanguage":"en","url":"https://unlighthouse.dev/logo.png"}]}
```
---
- **Page:** HAR File Viewer - Analyze HTTP Archive Files Online Free · Unlighthouse
- **Source:** https://unlighthouse.dev/tools/har-viewer
- **Description:** Free HAR file viewer and network analyzer. Upload HAR files to visualize waterfall charts, request timing, resource breakdown, and protocol analysis. Entirely client-side, no data uploaded.
```yaml
meta:
og:image: https://unlighthouse.dev/_og/s/o_f7c654b41d5b27b9.png
og:image:height: "600"
og:image:type: image/png
og:image:width: "1200"
twitter:image: https://unlighthouse.dev/_og/s/o_f7c654b41d5b27b9.png
```
# **HAR File **Viewer
Upload a HAR file to analyze network requests, waterfall timing, and resource breakdown. Entirely client-side.
**HAR File Analyzer**
**Drop your HAR file here **
or click to browse files
**How to export a HAR file: **
1. Open Chrome DevTools (F12) → Network tab
2. Reload the page to capture all requests
3. Right-click the request list → "Save all as HAR with content"
## **How to Read a HAR File **
A HAR file logs every HTTP request your browser makes when loading a page. Each entry captures the **URL, method, status code, headers, timing data, and response size**. The waterfall chart visualizes the sequence and overlap of these requests.
Focus on requests with long **wait times (TTFB)** — these indicate slow server responses. Large **receive phases** point to oversized assets that need compression or optimization.
### **Timing Phases Explained **
**blocked**
Time spent queued before the request could be sent
**DNS Lookup**
Time to resolve the domain name to an IP address
**connect**
Time to establish a TCP connection
**SSL/TLS**
Time for the TLS/SSL handshake
**send**
Time to send the HTTP request to the server
**Waiting (TTFB)**
Time waiting for the server to respond (Time to First Byte)
**receive**
Time to download the response body
## **What to Look For in HAR Files **
### **Slow TTFB **
Wait times over 200ms for the main document suggest server-side bottlenecks — slow databases, no caching, or distant servers.
### **Too Many Requests **
Pages with 80+ requests are above median. Combine scripts, use sprites, and lazy-load below-fold assets.
### **Missing Compression **
If transfer size equals uncompressed size for text files, Brotli or Gzip compression isn't enabled on your server.
### **HTTP/1.1 Bottlenecks **
Staircase waterfall patterns indicate HTTP/1.1 connection limits. Upgrade to HTTP/2 or HTTP/3 for multiplexing.
### **Third-Party Bloat **
Check the domain breakdown — third-party scripts (analytics, ads) often account for 30-50% of total page weight.
### **Low Cache Hit Rate **
A rate below 30% means most assets aren't cached. Set proper Cache-Control headers for static resources.
## **Frequently Asked Questions **
**01**
### **What is a HAR file?**
A HAR (HTTP Archive) file is a JSON-formatted log of all HTTP transactions between a browser and a website. It records every request and response, including URLs, headers, timing data, status codes, and response sizes. HAR files are used to diagnose network performance issues, debug API calls, and analyze page load behavior.
**02**
### **How do I export a HAR file from Chrome?**
Open Chrome DevTools (F12), go to the Network tab, load your page, then right-click the request list and select "Save all as HAR with content." Alternatively, click the download arrow icon in the Network toolbar. Make sure to check "Preserve log" if you need to capture redirects.
**03**
### **How do I export a HAR file from Firefox?**
Open Firefox DevTools (F12), go to the Network tab, load your page, then click the gear icon and select "Save All As HAR." Firefox HAR exports include the same timing and header data as Chrome exports.
**04**
### **Is my data safe when using this HAR viewer?**
Yes. This viewer runs entirely in your browser — your HAR file is never uploaded to any server. However, OWASP warns that HAR files pose a major security risk as they capture full request payloads, including plaintext passwords in postData and active Cookie session tokens. Never share raw HAR files publicly without first sanitizing sensitive headers.
**05**
### **How do I read a waterfall chart?**
Each horizontal bar represents one HTTP request. The bar is divided into colored phases. A "Staircase" pattern indicates sequential loading, while a "Wall" pattern suggests HTTP/2 or HTTP/3 (QUIC) multiplexing. Long "waiting" (TTFB) bars point to backend bottlenecks, and long "receiving" bars indicate large unoptimized assets. Note that with HTTP/3, connect and SSL phases often collapse into a single 1-RTT event.
**06**
### **Why is my HAR file so large?**
HAR files include full response bodies by default, with binary content (images, fonts) base64-encoded. A typical page load can produce a 5-50MB HAR file. To reduce size, some tools offer options to export without response bodies.
Explore more performance tools
[**Lighthouse Viewer **](https://unlighthouse.dev/tools/lighthouse-report-viewer) [** PageSpeed Insights **](https://unlighthouse.dev/tools/pagespeed-insights-performance) [** CWV Checker **](https://unlighthouse.dev/tools/cwv-checker)
```json
{"@context":"https://schema.org","@graph":[{"@id":"https://unlighthouse.dev/#website","@type":"WebSite","description":"Google Lighthouse for your entire site.","name":"Unlighthouse","url":"https://unlighthouse.dev/","publisher":{"@id":"https://unlighthouse.dev/#identity"}},{"@id":"https://unlighthouse.dev/tools/har-viewer#webpage","@type":"WebPage","description":"Free HAR file viewer and network analyzer. Upload HAR files to visualize waterfall charts, request timing, resource breakdown, and protocol analysis. Entirely client-side, no data uploaded.","name":"HAR File Viewer - Analyze HTTP Archive Files Online Free","url":"https://unlighthouse.dev/tools/har-viewer","isPartOf":{"@id":"https://unlighthouse.dev/#website"},"potentialAction":[{"@type":"ReadAction","target":["https://unlighthouse.dev/tools/har-viewer"]}],"primaryImageOfPage":{"@id":"https://unlighthouse.dev/#logo"}},{"@id":"https://unlighthouse.dev/#identity","@type":"Organization","name":"Unlighthouse","url":"https://unlighthouse.dev","logo":{"@id":"https://unlighthouse.dev/#logo"}},{"@id":"https://unlighthouse.dev/tools/har-viewer#/schema/web-application/1","@type":"WebApplication","applicationCategory":"DeveloperApplication","description":"Free HAR file viewer and network analyzer. Upload HAR files to visualize waterfall charts, request timing, resource breakdown, and protocol analysis. Entirely client-side, no data uploaded.","name":"HAR File Viewer - Analyze HTTP Archive Files Online Free","operatingSystem":"Web","url":"https://unlighthouse.dev/tools/har-viewer","offers":{"@type":"Offer","price":"0","priceCurrency":"USD"}},{"@id":"https://unlighthouse.dev/tools/har-viewer#/schema/faqpage/1","@type":"FAQPage","mainEntity":[{"@type":"Question","name":"What is a HAR file?","acceptedAnswer":{"@type":"Answer","text":"A HAR (HTTP Archive) file is a JSON-formatted log of all HTTP transactions between a browser and a website. It records every request and response, including URLs, headers, timing data, status codes, and response sizes. HAR files are used to diagnose network performance issues, debug API calls, and analyze page load behavior."}},{"@type":"Question","name":"How do I export a HAR file from Chrome?","acceptedAnswer":{"@type":"Answer","text":"Open Chrome DevTools (F12), go to the Network tab, load your page, then right-click the request list and select \"Save all as HAR with content.\" Alternatively, click the download arrow icon in the Network toolbar. Make sure to check \"Preserve log\" if you need to capture redirects."}},{"@type":"Question","name":"How do I export a HAR file from Firefox?","acceptedAnswer":{"@type":"Answer","text":"Open Firefox DevTools (F12), go to the Network tab, load your page, then click the gear icon and select \"Save All As HAR.\" Firefox HAR exports include the same timing and header data as Chrome exports."}},{"@type":"Question","name":"Is my data safe when using this HAR viewer?","acceptedAnswer":{"@type":"Answer","text":"Yes. This viewer runs entirely in your browser — your HAR file is never uploaded to any server. However, OWASP warns that HAR files pose a major security risk as they capture full request payloads, including plaintext passwords in postData and active Cookie session tokens. Never share raw HAR files publicly without first sanitizing sensitive headers."}},{"@type":"Question","name":"How do I read a waterfall chart?","acceptedAnswer":{"@type":"Answer","text":"Each horizontal bar represents one HTTP request. The bar is divided into colored phases. A \"Staircase\" pattern indicates sequential loading, while a \"Wall\" pattern suggests HTTP/2 or HTTP/3 (QUIC) multiplexing. Long \"waiting\" (TTFB) bars point to backend bottlenecks, and long \"receiving\" bars indicate large unoptimized assets. Note that with HTTP/3, connect and SSL phases often collapse into a single 1-RTT event."}},{"@type":"Question","name":"Why is my HAR file so large?","acceptedAnswer":{"@type":"Answer","text":"HAR files include full response bodies by default, with binary content (images, fonts) base64-encoded. A typical page load can produce a 5-50MB HAR file. To reduce size, some tools offer options to export without response bodies."}}]},{"@id":"https://unlighthouse.dev/#logo","@type":"ImageObject","caption":"Unlighthouse","contentUrl":"https://unlighthouse.dev/logo.png","inLanguage":"en","url":"https://unlighthouse.dev/logo.png"}]}
```
---
- **Page:** INP Analyzer - Test Interaction to Next Paint · Unlighthouse
- **Source:** https://unlighthouse.dev/tools/inp-analyzer
- **Description:** Free INP testing tool. Analyze your Interaction to Next Paint score, find long tasks blocking the main thread, and improve responsiveness.
```yaml
meta:
og:image: https://unlighthouse.dev/_og/s/o_577783cfe6a376ed.png
og:image:height: "600"
og:image:type: image/png
og:image:width: "1200"
twitter:image: https://unlighthouse.dev/_og/s/o_577783cfe6a376ed.png
```
# **INP **Analyzer
Find what's blocking your main thread and slowing down interactions.
**INP Analysis**
Enter a URL to analyze INP
## **What is Interaction to Next Paint? **
INP measures how quickly your page responds to user interactions like clicks, taps, and keyboard input. It captures the **worst interaction latency** during a page visit, reporting when the browser finally paints a response. Google replaced FID with INP as a [Core Web Vital](https://web.dev/vitals/) in March 2024.
Since INP requires real user interactions, lab tools like Lighthouse use [**Total Blocking Time (TBT) **](https://unlighthouse.dev/glossary/tbt) as a proxy. TBT measures how long the main thread was blocked by long tasks during page load—a strong predictor of poor INP.
### **INP Timeline **
Click
Processing
**Paint **
Good INP**≤200ms**
## **Common Causes of Poor INP **
### [Long Tasks](https://unlighthouse.dev/learn-lighthouse/inp/long-running-javascript)
JavaScript executing for >50ms blocks the main thread. Break up work with `requestIdleCallback` or `scheduler.yield()`.
### [Third-Party Scripts](https://unlighthouse.dev/learn-lighthouse/inp/third-party-scripts)
Analytics, chat widgets, and ads often block the main thread. Load them async or use Partytown to run in a web worker.
### [Hydration](https://unlighthouse.dev/learn-lighthouse/inp/hydration-issues)
Framework hydration can block interactions. Use progressive hydration, islands architecture, or server components.
### [Large DOM](https://unlighthouse.dev/learn-lighthouse/inp/dom-size)
Too many DOM nodes slow down style calculations and layout. Keep nodes under 1,500 and virtualize long lists.
### [Layout Thrashing](https://unlighthouse.dev/learn-lighthouse/inp/heavy-dom-operations)
Reading and writing layout properties in a loop forces synchronous reflows. Batch DOM reads and writes.
### **Bundle Size **
Large JavaScript bundles take longer to parse and execute. Use code splitting, tree shaking, and lazy loading.
## **Frequently Asked Questions **
**01**
### **What is Interaction to Next Paint (INP)?**
Interaction to Next Paint (INP) is a Core Web Vital that measures responsiveness. It tracks the delay between user interactions (clicks, taps, key presses) and the visual feedback. A good INP score is 200 milliseconds or less, indicating a responsive experience.
**02**
### **How is INP different from First Input Delay (FID)?**
INP replaced FID as a Core Web Vital in March 2024. While FID only measured the first interaction, INP measures ALL interactions throughout the page lifecycle and reports the worst one. This makes INP a more comprehensive measure of real-world interactivity.
**03**
### **What causes poor INP scores?**
Poor INP is typically caused by: long JavaScript tasks blocking the main thread, heavy third-party scripts (analytics, ads, widgets), unoptimized event handlers, layout thrashing from DOM manipulation, and large JavaScript bundles that take time to parse and execute.
**04**
### **How do I improve my INP score?**
To improve INP: break long tasks into smaller chunks using yield patterns, defer non-critical JavaScript, use code splitting to reduce bundle size, optimize event handlers to avoid forced layouts, move heavy computation to web workers, and audit third-party scripts for performance impact.
**05**
### **Why does lab data show TBT instead of INP?**
Total Blocking Time (TBT) is used as a lab proxy for INP because true INP requires real user interactions. TBT measures time spent on long tasks (>50ms) during page load, which correlates with interactivity. Field data from real users provides actual INP measurements.
### **Related Tools **
[**LCP Finder **](https://unlighthouse.dev/tools/lcp-finder) [** Performance Score Calculator **](https://unlighthouse.dev/tools/lighthouse-score-calculator) [** INP Optimization Guide **](https://unlighthouse.dev/learn-lighthouse/inp) [** LCP Guide **](https://unlighthouse.dev/learn-lighthouse/lcp) [** CLS Guide **](https://unlighthouse.dev/learn-lighthouse/cls) [** INP Glossary **](https://unlighthouse.dev/glossary/inp)
```json
{"@context":"https://schema.org","@graph":[{"@id":"https://unlighthouse.dev/#website","@type":"WebSite","description":"Google Lighthouse for your entire site.","name":"Unlighthouse","url":"https://unlighthouse.dev/","publisher":{"@id":"https://unlighthouse.dev/#identity"}},{"@id":"https://unlighthouse.dev/tools/inp-analyzer#webpage","@type":"WebPage","description":"Free INP testing tool. Analyze your Interaction to Next Paint score, find long tasks blocking the main thread, and improve responsiveness.","name":"INP Analyzer - Test Interaction to Next Paint","url":"https://unlighthouse.dev/tools/inp-analyzer","isPartOf":{"@id":"https://unlighthouse.dev/#website"},"potentialAction":[{"@type":"ReadAction","target":["https://unlighthouse.dev/tools/inp-analyzer"]}],"primaryImageOfPage":{"@id":"https://unlighthouse.dev/#logo"}},{"@id":"https://unlighthouse.dev/#identity","@type":"Organization","name":"Unlighthouse","url":"https://unlighthouse.dev","logo":{"@id":"https://unlighthouse.dev/#logo"}},{"@id":"https://unlighthouse.dev/tools/inp-analyzer#/schema/web-application/1","@type":"WebApplication","applicationCategory":"DeveloperApplication","description":"Free INP testing tool. Analyze your Interaction to Next Paint score, find long tasks blocking the main thread, and improve responsiveness.","name":"INP Analyzer - Test Interaction to Next Paint","operatingSystem":"Web","url":"https://unlighthouse.dev/tools/inp-analyzer","offers":{"@type":"Offer","price":"0","priceCurrency":"USD"}},{"@id":"https://unlighthouse.dev/tools/inp-analyzer#/schema/faqpage/1","@type":"FAQPage","mainEntity":[{"@type":"Question","name":"What is Interaction to Next Paint (INP)?","acceptedAnswer":{"@type":"Answer","text":"Interaction to Next Paint (INP) is a Core Web Vital that measures responsiveness. It tracks the delay between user interactions (clicks, taps, key presses) and the visual feedback. A good INP score is 200 milliseconds or less, indicating a responsive experience."}},{"@type":"Question","name":"How is INP different from First Input Delay (FID)?","acceptedAnswer":{"@type":"Answer","text":"INP replaced FID as a Core Web Vital in March 2024. While FID only measured the first interaction, INP measures ALL interactions throughout the page lifecycle and reports the worst one. This makes INP a more comprehensive measure of real-world interactivity."}},{"@type":"Question","name":"What causes poor INP scores?","acceptedAnswer":{"@type":"Answer","text":"Poor INP is typically caused by: long JavaScript tasks blocking the main thread, heavy third-party scripts (analytics, ads, widgets), unoptimized event handlers, layout thrashing from DOM manipulation, and large JavaScript bundles that take time to parse and execute."}},{"@type":"Question","name":"How do I improve my INP score?","acceptedAnswer":{"@type":"Answer","text":"To improve INP: break long tasks into smaller chunks using yield patterns, defer non-critical JavaScript, use code splitting to reduce bundle size, optimize event handlers to avoid forced layouts, move heavy computation to web workers, and audit third-party scripts for performance impact."}},{"@type":"Question","name":"Why does lab data show TBT instead of INP?","acceptedAnswer":{"@type":"Answer","text":"Total Blocking Time (TBT) is used as a lab proxy for INP because true INP requires real user interactions. TBT measures time spent on long tasks (>50ms) during page load, which correlates with interactivity. Field data from real users provides actual INP measurements."}}]},{"@id":"https://unlighthouse.dev/#logo","@type":"ImageObject","caption":"Unlighthouse","contentUrl":"https://unlighthouse.dev/logo.png","inLanguage":"en","url":"https://unlighthouse.dev/logo.png"}]}
```
---
- **Page:** JSON Size Calculator: Raw, Minified, and Compressed Size · Unlighthouse
- **Source:** https://unlighthouse.dev/tools/json-size
- **Description:** Paste JSON to measure raw and minified bytes and estimate gzip and brotli size. See which keys, nesting, and duplicate keys add weight. Runs in your browser.
```yaml
meta:
og:image: https://unlighthouse.dev/_og/s/o_7f356bb6e02edef1.png
og:image:height: "600"
og:image:type: image/png
og:image:width: "1200"
twitter:image: https://unlighthouse.dev/_og/s/o_7f356bb6e02edef1.png
```
# **JSON Size **Analyzer
Paste JSON to analyze size, minification savings, compression estimates, and key contributions. Entirely client-side.
**JSON Size Analysis**
## **Why JSON Size Matters **
JSON is the most common data format for APIs and configuration files. Large JSON payloads directly impact **page load time, Time to First Byte (TTFB), and Largest Contentful Paint (LCP)**. Every kilobyte matters on mobile networks.
Minification removes whitespace and formatting, typically saving **10-30%** of raw size. Server compression (gzip/brotli) provides another **70-85%** reduction on top of that.
### **Compression Comparison **
**Raw **
100%
**Minified **
\~75%
**Gzip **
\~22%
**Brotli **
\~20%
## **Tips to Reduce JSON Size **
### **Shorten Key Names **
In arrays of objects, key names repeat for every item. Shorter keys like "n" instead of "name" save bytes multiplied by array length.
### **Remove Nulls **
Omit null and empty string fields from API responses. The absence of a key is more compact than "key":null.
### **Enable Compression **
Always serve JSON with Content-Encoding: br (Brotli) or gzip. This is the single biggest size reduction you can apply.
### **Paginate Large Arrays **
Don't return 1000 items when the client only shows 20. Use cursor-based pagination to keep payloads small.
### **Use Field Selection **
Implement sparse fieldsets or GraphQL to let clients request only the fields they need, reducing payload size.
### **Consider Alternatives **
For very large datasets, consider MessagePack, Protocol Buffers, or streaming JSON (NDJSON) instead of monolithic JSON.
## **Frequently Asked Questions **
**01**
### **How is JSON size calculated?**
Raw size is measured in UTF-8 bytes using the Blob API. Minified size is computed by parsing the JSON and re-serializing with JSON.stringify (no whitespace). The difference between raw and minified is your savings from removing formatting.
**02**
### **How accurate are the gzip and brotli estimates?**
They are rough. The tool does not compress your JSON. It divides the minified size by fixed ratios: 4.5 for gzip and 5.1 for brotli. Real compressed size depends on how repetitive the data is and on the compression level your server uses. For an exact number, check the transferred size of the response in the DevTools Network panel.
**03**
### **Why should I optimize JSON size?**
Large JSON payloads hurt performance in two ways: network transfer time and mobile CPU parsing. On mobile devices, native JSON.parse is highly optimized (V8 parses >10KB payloads 1.5x faster than JS literals), but main-thread execution time for massive payloads can block the UI. Additionally, REST API over-fetching often results in 30-50% of returned data being discarded by the client. Optimizing reduces mobile latency and CPU blocking.
**04**
### **What does "duplicate key bytes" mean?**
When you have an array of objects with the same keys (like API responses), the key names are repeated for every object. Duplicate key bytes shows how much space is wasted on repeated key strings. This overhead shrinks dramatically with compression.
**05**
### **Is my JSON data uploaded anywhere?**
No. This tool runs entirely in your browser. Your JSON is never sent to any server. All parsing, analysis, and minification happen client-side using JavaScript.
**06**
### **Why does my JSON fail to parse?**
Common issues include trailing commas (not valid JSON), single quotes instead of double quotes, unquoted keys, comments, or JavaScript expressions like undefined. Use a JSON validator to find the exact error location.
**07**
### **How can I reduce my JSON payload size?**
Minify by removing whitespace. Use shorter key names for large arrays of objects. Remove null/empty fields. Enable gzip or brotli compression on your server. Consider binary formats like MessagePack or Protocol Buffers for very large payloads.
Explore more performance tools
[**HAR Viewer **](https://unlighthouse.dev/tools/har-viewer) [** PageSpeed Insights **](https://unlighthouse.dev/tools/pagespeed-insights-performance) [** Lighthouse Viewer **](https://unlighthouse.dev/tools/lighthouse-report-viewer)
```json
{"@context":"https://schema.org","@graph":[{"@id":"https://unlighthouse.dev/#website","@type":"WebSite","description":"Google Lighthouse for your entire site.","name":"Unlighthouse","url":"https://unlighthouse.dev/","publisher":{"@id":"https://unlighthouse.dev/#identity"}},{"@id":"https://unlighthouse.dev/tools/json-size#webpage","@type":"WebPage","description":"Paste JSON to measure raw and minified bytes and estimate gzip and brotli size. See which keys, nesting, and duplicate keys add weight. Runs in your browser.","name":"JSON Size Calculator: Raw, Minified, and Compressed Size","url":"https://unlighthouse.dev/tools/json-size","isPartOf":{"@id":"https://unlighthouse.dev/#website"},"potentialAction":[{"@type":"ReadAction","target":["https://unlighthouse.dev/tools/json-size"]}],"primaryImageOfPage":{"@id":"https://unlighthouse.dev/#logo"}},{"@id":"https://unlighthouse.dev/#identity","@type":"Organization","name":"Unlighthouse","url":"https://unlighthouse.dev","logo":{"@id":"https://unlighthouse.dev/#logo"}},{"@id":"https://unlighthouse.dev/tools/json-size#/schema/web-application/1","@type":"WebApplication","applicationCategory":"DeveloperApplication","description":"Paste JSON to measure raw and minified bytes and estimate gzip and brotli size. See which keys, nesting, and duplicate keys add weight. Runs in your browser.","name":"JSON Size Calculator: Raw, Minified, and Compressed Size","operatingSystem":"Web","url":"https://unlighthouse.dev/tools/json-size","offers":{"@type":"Offer","price":"0","priceCurrency":"USD"}},{"@id":"https://unlighthouse.dev/tools/json-size#/schema/faqpage/1","@type":"FAQPage","mainEntity":[{"@type":"Question","name":"How is JSON size calculated?","acceptedAnswer":{"@type":"Answer","text":"Raw size is measured in UTF-8 bytes using the Blob API. Minified size is computed by parsing the JSON and re-serializing with JSON.stringify (no whitespace). The difference between raw and minified is your savings from removing formatting."}},{"@type":"Question","name":"How accurate are the gzip and brotli estimates?","acceptedAnswer":{"@type":"Answer","text":"They are rough. The tool does not compress your JSON. It divides the minified size by fixed ratios: 4.5 for gzip and 5.1 for brotli. Real compressed size depends on how repetitive the data is and on the compression level your server uses. For an exact number, check the transferred size of the response in the DevTools Network panel."}},{"@type":"Question","name":"Why should I optimize JSON size?","acceptedAnswer":{"@type":"Answer","text":"Large JSON payloads hurt performance in two ways: network transfer time and mobile CPU parsing. On mobile devices, native JSON.parse is highly optimized (V8 parses >10KB payloads 1.5x faster than JS literals), but main-thread execution time for massive payloads can block the UI. Additionally, REST API over-fetching often results in 30-50% of returned data being discarded by the client. Optimizing reduces mobile latency and CPU blocking."}},{"@type":"Question","name":"What does \"duplicate key bytes\" mean?","acceptedAnswer":{"@type":"Answer","text":"When you have an array of objects with the same keys (like API responses), the key names are repeated for every object. Duplicate key bytes shows how much space is wasted on repeated key strings. This overhead shrinks dramatically with compression."}},{"@type":"Question","name":"Is my JSON data uploaded anywhere?","acceptedAnswer":{"@type":"Answer","text":"No. This tool runs entirely in your browser. Your JSON is never sent to any server. All parsing, analysis, and minification happen client-side using JavaScript."}},{"@type":"Question","name":"Why does my JSON fail to parse?","acceptedAnswer":{"@type":"Answer","text":"Common issues include trailing commas (not valid JSON), single quotes instead of double quotes, unquoted keys, comments, or JavaScript expressions like undefined. Use a JSON validator to find the exact error location."}},{"@type":"Question","name":"How can I reduce my JSON payload size?","acceptedAnswer":{"@type":"Answer","text":"Minify by removing whitespace. Use shorter key names for large arrays of objects. Remove null/empty fields. Enable gzip or brotli compression on your server. Consider binary formats like MessagePack or Protocol Buffers for very large payloads."}}]},{"@id":"https://unlighthouse.dev/#logo","@type":"ImageObject","caption":"Unlighthouse","contentUrl":"https://unlighthouse.dev/logo.png","inLanguage":"en","url":"https://unlighthouse.dev/logo.png"}]}
```
---
- **Page:** LCP Element Finder - Identify Your Largest Contentful Paint · Unlighthouse
- **Source:** https://unlighthouse.dev/tools/lcp-finder
- **Description:** Free LCP test tool. Find your Largest Contentful Paint element, see timing breakdowns, and get actionable recommendations to improve loading speed.
```yaml
meta:
og:image: https://unlighthouse.dev/_og/s/o_87c6be55a5dfbcc8.png
og:image:height: "600"
og:image:type: image/png
og:image:width: "1200"
twitter:image: https://unlighthouse.dev/_og/s/o_87c6be55a5dfbcc8.png
```
# **LCP Element **Finder
Identify which element is your Largest Contentful Paint and get actionable fixes.
**LCP Analysis**
Enter a URL to find the LCP element
## **What is Largest Contentful Paint? **
LCP measures how long it takes for the **largest visible content element** to render on screen. This is typically a hero image, headline, or large text block. Google uses LCP as one of the three [Core Web Vitals](https://web.dev/vitals/) that directly affect search rankings.
A good LCP score means users perceive your page as **loaded quickly**—even if other content is still loading in the background. The LCP element changes as the page loads, so the final LCP is measured when the largest element stops changing.
### **LCP Timeline **
0ms
Navigation
\~800ms
FCP
**2.5s **
**LCP ✓ **
LCP marks when the **largest element** finishes rendering.
## **LCP Phases Breakdown **
See how time is spent loading your largest element
Slowed 4× for clarity
Total: 2500ms
TTFB800ms
Load Delay400ms
Load Time600ms
Render Delay700ms
### **Time to First Byte**
Phase 1 of 4
**800ms**
25%
Time waiting for the server to respond with the first byte of HTML.
**How to optimize **
- Use a CDN to serve content closer to users
- Enable server-side caching
### **Resource Load Delay**
Phase 2 of 4
**400ms**
15%
Time between TTFB and when the browser starts loading the LCP resource.
**How to optimize **
- Add \ for LCP image
- Avoid lazy-loading the LCP image
### **Resource Load Duration**
Phase 3 of 4
**600ms**
25%
Time spent downloading the LCP image or video resource.
**How to optimize **
- Compress images with WebP or AVIF
- Use responsive images with srcset
### **Element Render Delay**
Phase 4 of 4
**700ms**
35%
Time from resource loaded (or TTFB for text) until the element is painted.
**How to optimize **
- Reduce JavaScript bundle size
- Use font-display: optional for web fonts
Based on [DebugBear](https://www.debugbear.com/docs/lcp-by-phase) and [web.dev](https://web.dev/articles/optimize-lcp)
### **LCP Scoring Thresholds **
Google's LCP thresholds are based on **real user data** from millions of websites. To pass Core Web Vitals, **75% of page visits** must have an LCP under 2.5 seconds.
**≤2.5s **
**Good **
**2.5-4s **
**Needs improvement **
**\>4s **
**Poor **
**LCP Score Distribution **
0s**2.5s****4.0s**8s**Good****Meh****Poor**
Source: [web.dev/lcp](https://web.dev/lcp/)
### **Common LCP Elements **
What typically becomes the LCP element
**Hero Images**
Large banner or header images above the fold
**H1 Headlines**
Large text headings on text-heavy pages
**Background Images**
CSS background-image on large containers
**Video Posters**
Poster images for \