Mobile 375 × 812

Desktop 1440 × 900

Score: 69 / 100
Based on 8 categories, 0 sections
Decent speed, but optimizing further could improve engagement.
Several missing protections leave your users and data exposed.
Several issues make your site difficult for assistive technology users.
Well-optimized for search — your content is discoverable.
Good server performance with room for optimization.
Mostly compliant — a few items need attention.
Rich content metadata — your pages look great everywhere.
Heavier than average — reducing page weight saves energy and bandwidth.
The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.
Weights reflect general web best practices. Individual needs may differ.
Content-Security-Policy header is missing
Security gaps expose your site and users to attacks, eroding trust.
No Content-Security-Policy header found
Security gaps expose your site and users to attacks, eroding trust.
No <main> landmark found
Accessibility issues exclude users with disabilities — up to 15% of your potential audience.
Soft 404: server returns HTTP 200 for non-existent pages
Accessibility issues exclude users with disabilities — up to 15% of your potential audience.
243 third-party resources (100% of weight)
Performance issues directly impact user engagement and conversion rates.
High impact, low effort — start here.
High impact, requires investment.
Small gains, minimal effort.
Nothing in this quadrant — good news.
Low impact, high effort — do last.
Nothing in this quadrant — good news.
[](https://beavercheck.com/results/5ffe4e5a-2f69-4454-9797-dfb243650994)<a href="https://beavercheck.com/results/5ffe4e5a-2f69-4454-9797-dfb243650994"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fitmedia.co.jp" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fitmedia.co.jpThis badge auto-updates with your latest scan result.
Your site has several issues that may be affecting user experience and business outcomes. Your LCP of 4.6s exceeds Google's 2.5s 'Good' threshold and the 1 performance issue below directly contributes to it. Accessibility issues exclude users who rely on assistive technology — an estimated 15% of your potential audience. Addressing the critical issues below would have the most immediate impact on your user trust.
6 barrier(s) likely increasing bounce by ~26%.
Page takes 4.6s to load
+12% bounceUsers abandon at ~3s — you're 2.1s over the 2.5s threshold
Fix: Optimize render-blocking resources, preload the hero image, and compress images
Page feels frozen for 3.9s
+5% bounceClicks on the primary CTA are ignored while JavaScript runs
Fix: Break up long tasks; defer non-critical JavaScript to post-hydration
No HSTS header
+1% bounceReturning visitors are briefly exposed to downgrade attacks on first request
Fix: Set Strict-Transport-Security: max-age=31536000; includeSubDomains
No Content-Security-Policy header
+1% bounceHigher XSS blast radius — one compromised script can exfiltrate the checkout form
Fix: Ship a reporting-only CSP first, then enforce once violations are clean
No structured data
+2% bounceNo rich-result eligibility in Google — lower SERP CTR vs competitors with stars and prices
Fix: Add JSON-LD for your page type (Product, Article, FAQPage, LocalBusiness, …)
No skip-to-content link
+1% bounceKeyboard and screen-reader users must tab through the entire header on every page
Fix: Add a visible-on-focus <a href="#main">Skip to content</a> as the first focusable element
Preliminary CRO audit — each barrier links to the tab with detailed analysis.
¥48,000 investment → ¥361,424/month returns + JPY 100,000,000 risk avoided
¥48,000
6h · 5 findings
¥361,424 /mo
~¥4,337,091 / year
JPY 100,000,000
if kept compliant
¥8,000 — in quick wins — start here for the fastest payback
Figures combine localized regulatory fine ceilings, search/conversion value priced against local CPC, and bandwidth waste estimates. Results depend on implementation quality and audience composition. Not legal or financial advice.
6.0 developer hours at ¥8000/hr
Based on Japan rates (¥8000/hr)
Start here for the best return on investment
¥8,333,435 / month at risk
~¥100,001,217 / year if left unfixed
¥100,000,000
+2 more
¥101 /mo
8496.1 MB/mo × 11.940 JPY/GB
Compliance figures represent the statutory maximum fine for the most severe triggered category, capped per regulation — not the sum of per-finding penalties. Based on published regulatory fine ranges. This is not legal advice.
Unique monthly visitors from your analytics
Purchases, signups, or key actions
Optional — for revenue estimation
more engaged visitors from reduced bounce
Fix 4 critical issues to capture this value
Based on Google/Deloitte research ("Milliseconds Make Millions") showing a ~7% bounce rate increase per additional second of LCP above the 2.5s "Good" threshold.
Your site's LCP: → estimated after fixes.
These are estimates based on industry research — actual results vary
Your data stays in your browser — nothing is sent to our servers
Thanks for your feedback!
We'll use a cached audit if available, or offer to scan.
Industry-standard audits powered by Google Lighthouse.
Key metrics that affect user experience.
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
3.92 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
4.61 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
3.92 s
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.000
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
7.10 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.
24.50 s
Audit breakdown by category with detailed findings.
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
Performance issues directly impact user engagement and conversion rates.
Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling
Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.
Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.
Source: Google web.dev / Lighthouse
3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.
Performance issues directly impact user engagement and conversion rates.
A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.
Performance issues directly impact user engagement and conversion rates.
Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading
Performance issues directly impact user engagement and conversion rates.
Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
Performance issues directly impact user engagement and conversion rates.
Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Duration |
|---|---|---|
| tr.api.itmedia.co.jp/cc/v1.js | 350 B | 825 ms |
| www.itmedia.co.jp/js/spv/html5base.js?date=202512091010 | 8.6 KiB | 150 ms |
| cx.api.itmedia.co.jp/v1.js | 241 B | 822 ms |
| www.itmedia.co.jp/css/spv/html5base_v2.css?date=202601281532 | 7.9 KiB | 150 ms |
| www.itmedia.co.jp/js/lib/gam_common.js?date=202511251350 | 3.4 KiB | |
| www.itmedia.co.jp/js/lib/cx_v2.js?date=202507231610 | 10.2 KiB | 150 ms |
| www.itmedia.co.jp/css/spv/gam.css?date=202604031023 | 1.5 KiB | 150 ms |
| www.itmedia.co.jp/js/spv/movePC2SP.js?date=202509161040 | 4.7 KiB | |
| cdn.cxense.com/cx.js | 0 B | |
| www.itmedia.co.jp/js/gamServerEnvironment.js?date=202107151140 | 0 B |
A long cache lifetime can speed up repeat visits to your page. Learn more about caching.
Performance issues directly impact user engagement and conversion rates.
Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size
Performance issues directly impact user engagement and conversion rates.
| URL | Resource Size | Est Savings | |
|---|---|---|---|
from エンタープライズ & エグゼクティブ & TechTarget & マーケティング & キーマンズネット div#colBoxIndexTheme4 > div.colBoxOuter > div.colBoxInner > div.colBoxHead2 | s0.2mdn.net/simgad/9085392786287634694 | 66.1 KiB | 55.9 KiB |
icon div.colBoxIndex > div.colBoxIcon > a > img | image.itmedia.co.jp/business/articles/2604/22/top_news022.jpg | 6.4 KiB | 4.6 KiB |
icon div.colBoxIndex > div.colBoxIcon > a > img | image.itmedia.co.jp/news/articles/2604/05/top_news003.jpg | 6.2 KiB | 4.5 KiB |
These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.
Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.
Performance issues directly impact user engagement and conversion rates.
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Performance issues directly impact user engagement and conversion rates.
| URL | Time Spent |
|---|---|
| itmedia.co.jp/ | 954 ms |
| www.itmedia.co.jp/ | 2.7 s |
| www.itmedia.co.jp/spv/ | 0.0 ms |
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.
Performance issues directly impact user engagement and conversion rates.
Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Est Savings |
|---|---|---|
| www.itmedia.co.jp/js/spv/html5base.js?date=202512091010 | 8.3 KiB | 2.6 KiB |
| www.itmedia.co.jp/js/lib/cx_v2.js?date=202507231610 | 10.0 KiB | 2.5 KiB |
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.
Multi-megabyte JavaScript bundles delay every interactive feature on the page.
This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.
Source: Google web.dev / Lighthouse
| URL | Transfer Size | Est Savings |
|---|---|---|
| www.googletagmanager.com/gtag/js?id=AW-10976778865&cx=c>m=4e64k0h2 | 143.4 KiB | 105.8 KiB |
| www.googletagmanager.com/gtag/js?id=AW-1032582312&cx=c>m=4e64k0h2 | 146.4 KiB | 104.8 KiB |
| www.googletagmanager.com/gtag/js?id=AW-578569290&cx=c>m=4e64k0h2 | 136.4 KiB | 102.5 KiB |
| /pagead/managed/js/gpt/m202604170101/pubads_impl.js?cb=31... | 187.4 KiB | 89.6 KiB |
| www.googletagmanager.com/gtag/js?id=G-419SLCGX56&cx=c>m=4e64k0h2 | 152.0 KiB | 63.4 KiB |
| www.googletagmanager.com/gtm.js?id=GTM-W3CLTQN | 187.8 KiB | 52.3 KiB |
| fundingchoicesmessages.google.com/i/43042345?ers=3 | 68.5 KiB | 36.4 KiB |
| connect.facebook.net/en_US/fbevents.js | 96.5 KiB | 33.6 KiB |
| cdn.cxense.com/cx.js | 37.5 KiB | 31.5 KiB |
| cdn.cxense.com/cx.js | 37.5 KiB | 31.5 KiB |
| cdn.cxense.com/cx.js | 37.5 KiB | 31.5 KiB |
| cdn.id5-sync.com/api/1.0/esp.js | 34.4 KiB | 30.7 KiB |
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.
Performance issues directly impact user engagement and conversion rates.
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work
Performance issues directly impact user engagement and conversion rates.
| Category | Time Spent |
|---|---|
| Script Evaluation | 6.6 s |
| Other | 1.5 s |
| Script Parsing & Compilation | 1.2 s |
| Style & Layout | 417 ms |
| Garbage Collection | 183 ms |
| Parse HTML & CSS | 67 ms |
| Rendering | 58 ms |
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
Performance issues directly impact user engagement and conversion rates.
More information about the performance of your application. These numbers don't directly affect the Performance score.
These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.
One main landmark helps screen reader users navigate a web page. Learn more about landmarks.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
html html |
These items highlight common accessibility best practices.
Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn how to provide responsive images.
Performance issues directly impact user engagement and conversion rates.
| URL | Displayed size | Actual size | Expected size | |
|---|---|---|---|---|
icon div.colBoxIndex > div.colBoxIcon > a > img | image.itmedia.co.jp/business/articles/2604/22/top_news012.jpg | 120 x 90 | 120 x 90 | 180 x 135 |
icon div.colBoxIndex > div.colBoxIcon > a > img | image.itmedia.co.jp/business/articles/2604/22/top_news022.jpg | 120 x 90 | 120 x 90 | 180 x 135 |
icon div.colBoxIndex > div.colBoxIcon > a > img | image.itmedia.co.jp/business/articles/2604/22/top_news023.jpg | 120 x 90 | 120 x 90 | 180 x 135 |
icon div.colBoxIndex > div.colBoxIcon > a > img | image.itmedia.co.jp/news/articles/2604/05/top_news003.jpg | 120 x 90 | 120 x 90 | 180 x 135 |
icon div.colBoxIndex > div.colBoxIcon > a > img | image.itmedia.co.jp/news/articles/2604/22/top_news026.jpg | 120 x 90 | 120 x 90 | 180 x 135 |
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
Performance issues directly impact user engagement and conversion rates.
| Deprecation / Warning | Source |
|---|---|
| AttributionReporting | connect.facebook.net/en_US/fbevents.js line 279, col 769 |
| Topics | invstatic101.creativecdn.com/encrypted-signals/encrypted-tag-g.js line 5, col 1847 |
These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.
Canonical links suggest which URL to show in search results. Learn more about canonical links.
Performance issues directly impact user engagement and conversion rates.
Format your HTML in a way that enables crawlers to better understand your app’s content.
Industry-standard audits powered by Google Lighthouse. — Desktop
Key metrics that affect user experience. — Desktop
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
1.31 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
1.42 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
872 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.007
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
4.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.
8.03 s
Audit breakdown by category with detailed findings.
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
Performance issues directly impact user engagement and conversion rates.
Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling
Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.
Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.
Source: Google web.dev / Lighthouse
3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.
Performance issues directly impact user engagement and conversion rates.
A long cache lifetime can speed up repeat visits to your page. Learn more about caching.
Performance issues directly impact user engagement and conversion rates.
Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.
Performance issues directly impact user engagement and conversion rates.
A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.
Performance issues directly impact user engagement and conversion rates.
Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
Performance issues directly impact user engagement and conversion rates.
Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Duration |
|---|---|---|
| tr.api.itmedia.co.jp/cc/v1.js | 350 B | 292 ms |
| www.itmedia.co.jp/js/base_v2.js?202501291050 | 9.2 KiB | 107 ms |
| fc.itmedia.co.jp/fpcookie?site_id=itm_ | 1001 B | 275 ms |
| cx.api.itmedia.co.jp/v1.js | 241 B | 274 ms |
| www.itmedia.co.jp/js/gamServerEnvironment.js?date=202107151140 | 356 B | |
| www.itmedia.co.jp/js/lib/cx_v2.js?202507231610 | 10.2 KiB | |
| www.itmedia.co.jp/css/top/base.css?202511251430 | 2.3 KiB | |
| www.itmedia.co.jp/js/spv/movePC2SP.js?date=250916104008 | 4.7 KiB | |
| www.itmedia.co.jp/css/gnavi.css?date=202601281531 | 4.0 KiB | |
| www.itmedia.co.jp/css/base.css?202509161104 | 5.0 KiB | |
| cdn.cxense.com/cx.js | 38.1 KiB | 167 ms |
Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.
Performance issues directly impact user engagement and conversion rates.
Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size
Performance issues directly impact user engagement and conversion rates.
| URL | Resource Size | Est Savings | |
|---|---|---|---|
body > div#google_image_div > a#aw0 > img.img_ad body > div#google_image_div > a#aw0 > img.img_ad | tpc.googlesyndication.com/simgad/14211902422675294702 | 137.2 KiB | 97.7 KiB |
・OpenAI、“視覚的思考パートナー”「ChatGPT Images 2.0」発表 Web検索結果を反映する画像生成も可能に div.colBoxIndex > div.colBoxUlist > ul > li | tpc.googlesyndication.com/simgad/8942407595710879420? | 49.2 KiB | 48.4 KiB |
icon div.colBoxIndex > div.colBoxIcon > a > img | tpc.googlesyndication.com/simgad/12555551469554340024? | 38.8 KiB | 38.0 KiB |
・“Mythos級”AI到来に備え、自民党が日本版「Project Glasswing」組成を検討 div.colBoxIndex > div.colBoxUlist > ul > li | tpc.googlesyndication.com/simgad/4846201149167440866? | 22.2 KiB | 21.4 KiB |
メディア一覧 | 公式SNS | 広告案内 | お問い合わせ | プライバシーポリシー | RSS | 運営会社 | 採用情報 | 推奨環境 div#globalFooter > div#globalFooterCorp > div#globalFooterCorpIn > p#globalFooterCorpLink | /simgad/7370903963884609559?sqp=uqWu0g0ICPoBEKwCQGQ&rs=AO... | 27.1 KiB | 14.9 KiB |
アイティメディアのタイアップコンテンツページへのリンク div.colBoxIndex > div.colBoxBanner > a > img | image.itmedia.co.jp/images0509/tot_banner_1_1703141393.jpg | 7.0 KiB | 5.1 KiB |
icon div.colBoxIndex > div.colBoxIcon > a > img | image.itmedia.co.jp/business/articles/2604/22/top_news022.jpg | 6.4 KiB | 4.6 KiB |
icon div.colBoxIndex > div.colBoxIcon > a > img | image.itmedia.co.jp/news/articles/2604/05/top_news003.jpg | 6.2 KiB | 4.5 KiB |
These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Performance issues directly impact user engagement and conversion rates.
| URL | Time Spent |
|---|---|
| itmedia.co.jp/ | 403 ms |
| www.itmedia.co.jp/ | 0.0 ms |
Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.
Performance issues directly impact user engagement and conversion rates.
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.
Performance issues directly impact user engagement and conversion rates.
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.
Performance issues directly impact user engagement and conversion rates.
| URL | Total CPU Time | Script Evaluation | Script Parse |
|---|---|---|---|
| /pagead/managed/js/gpt/m202604160201/pubads_impl.js?cb=31... | 1.8 s | 1.6 s | 19 ms |
| Unattributable | 844 ms | 293 ms | 0.0 ms |
| fundingchoicesmessages.google.com/i/43042345?ers=3 | 732 ms | 713 ms | 7.1 ms |
| cdn.cxense.com/cx.js | 544 ms | 90 ms | 9.4 ms |
| www.itmedia.co.jp/ | 378 ms | 16 ms | 5.1 ms |
| www.googletagmanager.com/gtm.js?id=GTM-W3CLTQN | 236 ms | 201 ms | 26 ms |
| /pagead/managed/js/activeview/current/ufs_web_display.js | 116 ms | 103 ms | 8.1 ms |
| www.googletagmanager.com/gtag/js?id=AW-1032582312 | 103 ms | 87 ms | 15 ms |
| www.googletagmanager.com/gtag/js?id=AW-10976778865 | 89 ms | 74 ms | 14 ms |
| www.googletagmanager.com/gtag/js?id=AW-578569290 | 88 ms | 63 ms | 14 ms |
| flux-cdn.com/client/00046/itmedia_01591.min.js | 86 ms | 53 ms | 26 ms |
| www.googletagmanager.com/gtag/js?id=G-419SLCGX56&cx=c>m=4e64h1 | 84 ms | 68 ms | 15 ms |
| rumcdn.geoedge.be/2d032b73-7223-4c17-9dc4-0b563e86d770/grumi-ip.js | 58 ms | 36 ms | 5.8 ms |
| /signals/config/185005748502834?v=2.9.303&r=stable&domain... | 58 ms | 39 ms | 6.5 ms |
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work
Performance issues directly impact user engagement and conversion rates.
| Category | Time Spent |
|---|---|
| Script Evaluation | 3.8 s |
| Other | 1.1 s |
| Style & Layout | 355 ms |
| Script Parsing & Compilation | 321 ms |
| Garbage Collection | 103 ms |
| Rendering | 64 ms |
| Parse HTML & CSS | 44 ms |
Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Est Savings |
|---|---|---|
| www.google.com/cse/static/element/b33cba5881f68fbf/default_v6+ja.css | 9.7 KiB | 2.8 KiB |
Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Est Savings |
|---|---|---|
| www.itmedia.co.jp/js/lib/cx_v2.js?202507231610 | 10.0 KiB | 2.5 KiB |
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.
Multi-megabyte JavaScript bundles delay every interactive feature on the page.
This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.
Source: Google web.dev / Lighthouse
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
Performance issues directly impact user engagement and conversion rates.
More information about the performance of your application. These numbers don't directly affect the Performance score.
These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.
Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
AI+ div.colBoxIndex > div.colBoxTitle > span.colBoxInfo > a |
These are opportunities to improve the legibility of your content.
One main landmark helps screen reader users navigate a web page. Learn more about landmarks.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
html#masterChannel-top html#masterChannel-top |
These items highlight common accessibility best practices.
Specifying a doctype prevents the browser from switching to quirks-mode. Learn more about the doctype declaration.
Performance issues directly impact user engagement and conversion rates.
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
Performance issues directly impact user engagement and conversion rates.
| Deprecation / Warning | Source |
|---|---|
| AttributionReporting | connect.facebook.net/en_US/fbevents.js line 279, col 769 |
| SharedStorage | /pagead/managed/js/activeview/current/ufs_web_display.js line 252, col 234 |
| Topics | invstatic101.creativecdn.com/encrypted-signals/encrypted-tag-g.js line 5, col 1847 |
These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.
Send Feedback