D — https://nikkeibp.co.jp | BeaverCheck Audit

Site Health

Score: 68 / 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.

Solid SEO basics — a few optimizations could boost rankings.

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.

How is this calculated?

The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.

Performance 25%Security 25%Accessibility 15%SEO 10%Infrastructure 10%Compliance 8%Content 5%Sustainability 2%

Weights reflect general web best practices. Individual needs may differ.

How the composite score is calculated

How you compare

Amazon Route 53 · 975 peers

You 68

Avg 72

At average

0 50 100

Better than 5% of Amazon Route 53 sites See full Amazon Route 53 benchmark →

core-js · 1488 peers

You 68

Avg 72

At average

0 50 100

Better than 5% of core-js sites See full core-js benchmark →

Top Priorities (5)

Content-Security-Policy header is missing

Security gaps expose your site and users to attacks, eroding trust.

Security › Security Headers

HSTS header is missing

Security gaps expose your site and users to attacks, eroding trust.

Security › Security Headers

No Content-Security-Policy header found

Security gaps expose your site and users to attacks, eroding trust.

Security › Content Security Policy

Page weighs 13.0 MB (11.8 MB transferred)

Performance issues directly impact user engagement and conversion rates.

Performance › Page Weight Budget

1 image(s) missing alt attribute

Accessibility issues exclude users with disabilities — up to 15% of your potential audience.

Accessibility › Alt Text Quality

View fix priority matrix

Fix Priority Matrix

5 findings

Impact

Quick Wins

High impact, low effort — start here.

Strategic

High impact, requires investment.

Easy Improvements

Small gains, minimal effort.

Nothing in this quadrant — good news.

Deprioritize

Low impact, high effort — do last.

Nothing in this quadrant — good news.

← Low effort High effort →

Embed this badge

Markdown

[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fnikkeibp.co.jp)](https://beavercheck.com/results/12fc63b3-2359-40c1-bbe3-dc4ef4c0e02f)

HTML

<a href="https://beavercheck.com/results/12fc63b3-2359-40c1-bbe3-dc4ef4c0e02f"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fnikkeibp.co.jp" alt="BeaverCheck Score"></a>

Image URL

https://beavercheck.com/badge?url=https%3A%2F%2Fnikkeibp.co.jp

This badge auto-updates with your latest scan result.

What fixing these means

Your site has several issues that may be affecting user experience and business outcomes. Your LCP of 7.7s 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.

3 security gaps detected — browsers may warn visitors about your site.

Your LCP is 7.7s — fixing the 1 performance critical could bring it under Google's 2.5s 'Good' threshold.

1 accessibility issue excludes users who rely on assistive technology.

Could reach Estimate based on resolving critical issues

Conversion Barriers

2 critical 6 warning

8 barrier(s) likely increasing bounce by ~30%.

Speed (2)

Page takes 7.7s to load

+12% bounce

Users abandon at ~3s — you're 5.2s over the 2.5s threshold

Fix: Optimize render-blocking resources, preload the hero image, and compress images

Page feels frozen for 614ms

+5% bounce

Clicks on the primary CTA are ignored while JavaScript runs

Fix: Break up long tasks; defer non-critical JavaScript to post-hydration

Trust (2)

No HSTS header

+1% bounce

Returning 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% bounce

Higher XSS blast radius — one compromised script can exfiltrate the checkout form

Fix: Ship a reporting-only CSP first, then enforce once violations are clean

Usability (1)

Viewport disables user zoom

+2% bounce

Visitors with low vision can't read the page — and some jurisdictions treat this as a legal risk

Fix: Remove user-scalable=no; drop maximum-scale if it's below 2

Content (2)

No structured data

+2% bounce

No 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, …)

Thin content

+3% bounce

Under 300 words — visitors bounce looking for substance, search engines rank competitors first

Fix: Add a substantive FAQ, product detail, or case-study section

Navigation (1)

No skip-to-content link

+1% bounce

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

Return on Investment

¥40,000 investment → ¥604,248/month returns + JPY 100,000,000 risk avoided

Payback period: < 1 month First-year ROI: +18027%

Investment

¥40,000

5h · 5 findings

Monthly returns

¥604,248 /mo

~¥7,250,972 / year

Conversions recovered ¥603,803
Bandwidth savings ¥445

Regulatory risk avoided

JPY 100,000,000

if kept compliant

APPI JPY 100,000,000

Payback period

0 12mo 24mo

¥12,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.

Full methodology & sources

Estimated Remediation Cost

¥40,000

5.0 developer hours at ¥8000/hr

Based on Japan rates (¥8000/hr)

Quick wins

¥12,000 3 fixes in ~90 minutes

Start here for the best return on investment

Cost by category

Cost by effort level

Adjust assumptions

Custom rate

¥ /hr

Rates reflect fully-loaded developer cost including overhead

How developer rates are sourced

What Inaction Is Costing You

¥8,333,778 / month at risk

~¥100,005,339 / year if left unfixed

Compliance Risk

¥100,000,000

APPI

No privacy policy link detected
APPI: JPY 100,000 – JPY 100,000,000
Trackers detected but no cookie policy found
APPI: JPY 100,000 – JPY 100,000,000
Trackers detected but no privacy policy found
APPI: JPY 100,000 – JPY 100,000,000

+1 more

Bandwidth Waste

¥445 /mo

37260.1 MB/mo × 11.940 JPY/GB

Optimize transfer: save ~3.7 MB per page load
Saves ¥445/mo

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.

Compliance methodology · SEO assumptions · Bandwidth model

Your performance is already good — improvements may show diminishing returns

Monthly visitors

Unique monthly visitors from your analytics

Conversion rate (%)

Purchases, signups, or key actions

Avg. order value

Optional — for revenue estimation

additional conversions/month

more engaged visitors from reduced bounce

potential monthly revenue

Current bounce (est.)

After fixes (est.)

Estimated bounce reduction

Fix 5 critical issues to capture this value

How this is calculated

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

Bounce-rate model & assumptions

Your data stays in your browser — nothing is sent to our servers

Was this report useful?

Thanks for your feedback!

We'll use a cached audit if available, or offer to scan.

Checking for existing audit...

Press ? for shortcuts

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

Performance

Accessibility

Best Practices

100

SEO

Core Web Vitals

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.47 s

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

7.70 s

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

614 ms

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.

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

11.82 s

Detailed Report

Audit breakdown by category with detailed findings.

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Why this matters

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

Why this matters

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more ▾

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.

Why this matters

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Request	Cache TTL	Transfer Size
connect.facebook.net/en_US/fbevents.js	1200.0 s	96.6 KiB
www.nikkeibp.co.jp/images/www/2018/index/bgi-services_02.jpg	86400.0 s	209.0 KiB
www.nikkeibp.co.jp/images/www/2018/common/bgi-map_01_sp.svg?191011	86400.0 s	142.5 KiB
www.nikkeibp.co.jp/images/www/2018/index/bgi-services_03.jpg	86400.0 s	139.7 KiB
www.nikkeibp.co.jp/images/www/2018/index/bgi-services_04.jpg	86400.0 s	137.1 KiB
www.nikkeibp.co.jp/images/www/2018/index/bgi-services_01.jpg	86400.0 s	123.4 KiB
www.nikkeibp.co.jp/images/www/2018/index/bgi-other_01.jpg	86400.0 s	121.8 KiB
/signals/config/151720335485995?v=2.9.303&r=stable&domain...	1200.0 s	53.4 KiB
www.nikkeibp.co.jp/js/bpcommon/jquery-1.x.min.js	86400.0 s	95.3 KiB
cdn.cxense.com/cx.js	3600.0 s	38.1 KiB
cdn.cxense.com/cx.js	3600.0 s	38.1 KiB
www.nikkeibp.co.jp/images/www/2018/index/bnr-recruit_01.jpg?230118	86400.0 s	55.8 KiB
www.nikkeibp.co.jp/images/www/2018/index/bnr-recruit_02.jpg?230118	86400.0 s	42.5 KiB
www.nikkeibp.co.jp/js/www/2018/slick.min.js?20200826	86400.0 s	41.2 KiB
www.nikkeibp.co.jp/css/www/2018/index.css?251020	86400.0 s	24.2 KiB
www.nikkeibp.co.jp/css/www/2018/common.css?20231122	86400.0 s	17.9 KiB
www.nikkeibp.co.jp/css/www/2018/font/oswald-v16-latin-regular.woff2	86400.0 s	15.1 KiB
cdn.cxense.com/cx.cce.js	3600.0 s	6.8 KiB
www.nikkeibp.co.jp/images/www/2018/index/ico-services_04.png	86400.0 s	12.6 KiB
www.nikkeibp.co.jp/images/www/2018/index/bnr-data_06_2.png	86400.0 s	8.9 KiB
www.nikkeibp.co.jp/js/www/2018/index.js?20200826	0.0 ms	3.5 KiB
www.nikkeibp.co.jp/images/www/2018/index/img-main-title_03.svg	86400.0 s	7.4 KiB
www.nikkeibp.co.jp/images/www/2018/index/ico-services_01.png	86400.0 s	7.2 KiB
www.nikkeibp.co.jp/images/www/2018/index/img-main-title_02.svg	86400.0 s	7.1 KiB
www.nikkeibp.co.jp/images/www/2018/index/ico-services_02.png	86400.0 s	6.6 KiB
www.nikkeibp.co.jp/js/bpcommon/onetag/bpTrackVarsCommon.js	0.0 ms	2.6 KiB
www.nikkeibp.co.jp/images/www/2018/index/bnr-data_05.png	86400.0 s	6.3 KiB
www.nikkeibp.co.jp/images/www/2018/index/bnr-data_01.png	86400.0 s	6.2 KiB
www.nikkeibp.co.jp/js/www/2018/common.js?20200121	0.0 ms	2.4 KiB
www.nikkeibp.co.jp/images/www/2018/index/bnr-data_04.png	86400.0 s	5.9 KiB
www.nikkeibp.co.jp/images/www/2018/index/bnr-data_03.png	86400.0 s	5.8 KiB
www.nikkeibp.co.jp/images/www/2018/index/bnr-data_02.png	86400.0 s	5.5 KiB
www.nikkeibp.co.jp/images/www/2018/index/ico-services_03.png	86400.0 s	3.8 KiB
www.nikkeibp.co.jp/js/www/2018/jquery.matchHeight-min.js	86400.0 s	3.5 KiB
www.nikkeibp.co.jp/js/www/2018/form.js?20181212	0.0 ms	1.3 KiB
www.nikkeibp.co.jp/images/www/2018/index/log-main_01.svg	86400.0 s	2.1 KiB
www.nikkeibp.co.jp/images/bplogo/logo.svg	86400.0 s	2.0 KiB
www.nikkeibp.co.jp/js/bpcommon/onetag/bpTrackVars.js	0.0 ms	643 B
/Repo/rep.gif?ver=3.3.0&typ=pgv&rnd=mo98f8vkrxu7m4g4&sid=...	0.0 ms	413 B
www.nikkeibp.co.jp/images/www/2018/common/ico-win_01.svg?20181210	86400.0 s	921 B
www.nikkeibp.co.jp/images/www/2018/common/ico-arrow_01.svg	86400.0 s	845 B
www.nikkeibp.co.jp/css/www/2018/font.css	86400.0 s	601 B
/tr/?id=151720335485995&ev=PageView&dl=https%3A%2F%2Fwww....	0.0 ms	16 B
/5207194079175/20220512182908_beb0d5d2fc7b112b7103bc0ac41...	0.0 ms	0 B

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Est Savings
www.nikkeibp.co.jp/css/www/2018/font/oswald-v16-latin-regular.woff2	100 ms

Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

Why this matters

Performance issues directly impact user engagement and conversion rates.

lhId: page-0-VIDEO

nodeLabel: div#wrap > div#topMain > div.movie > video#video

path: 1,HTML,1,BODY,0,DIV,3,DIV,1,DIV,0,VIDEO

selector: div#wrap > div#topMain > div.movie > video#video

snippet: <video src="https://d2bx7bt5963zg8.cloudfront.net/5207194079175/20220512182908_beb0d5d…" id="video" preload="none" playsinline="" muted="" autoplay="">

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.

title: Preconnected origins

value: no origins were preconnected

description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.

title: Preconnect candidates

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size	Duration
www.nikkeibp.co.jp/js/bpcommon/jquery-1.x.min.js	95.3 KiB	655 ms
www.nikkeibp.co.jp/js/www/2018/index.js?20200826	3.5 KiB	218 ms
www.nikkeibp.co.jp/js/www/2018/common.js?20200121	2.4 KiB
www.nikkeibp.co.jp/js/www/2018/form.js?20181212	1.3 KiB
www.nikkeibp.co.jp/js/www/2018/slick.min.js?20200826	41.2 KiB	218 ms
www.nikkeibp.co.jp/css/www/2018/font.css	601 B
www.nikkeibp.co.jp/js/www/2018/jquery.matchHeight-min.js	3.5 KiB
www.nikkeibp.co.jp/css/www/2018/common.css?20231122	17.9 KiB
www.nikkeibp.co.jp/css/www/2018/index.css?251020	24.2 KiB	218 ms

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL	Resource Size	Est Savings
ソリューション SOLUTION `div#services > div.col2 > div.col > a`	www.nikkeibp.co.jp/images/www/2018/index/bgi-services_02.jpg	208.6 KiB	135.7 KiB
出版・書籍 PUBLICATION `div#services > div.col2 > div.col > a`	www.nikkeibp.co.jp/images/www/2018/index/bgi-services_03.jpg	139.4 KiB	66.5 KiB
イベント・セミナー EVENT SEMINAR `div#services > div.col2 > div.col > a`	www.nikkeibp.co.jp/images/www/2018/index/bgi-services_04.jpg	136.7 KiB	63.8 KiB
日経BPとは会社概要日経BPのあゆみ SDGs/ESG への取り組み `body#top > div#wrap > div#other`	www.nikkeibp.co.jp/images/www/2018/index/bgi-other_01.jpg	121.5 KiB	56.9 KiB
メディア MEDIA `div#services > div.col2 > div.col > a`	www.nikkeibp.co.jp/images/www/2018/index/bgi-services_01.jpg	123.0 KiB	50.1 KiB
日経BP採用案内 `ul#bnr > li > a > img.sp`	www.nikkeibp.co.jp/images/www/2018/index/bnr-recruit_02.jpg?230118	42.3 KiB	26.3 KiB
div.col2 > div.col > a > img `div.col2 > div.col > a > img`	www.nikkeibp.co.jp/images/www/2018/index/ico-services_04.png	12.4 KiB	5.9 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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 951 ms

URL	Time Spent
nikkeibp.co.jp/	951 ms
www.nikkeibp.co.jp/	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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

Diagnostics

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Why this matters

Multi-megabyte JavaScript bundles delay every interactive feature on the page.

Learn more ▾

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

Estimated savings: 1.1 s 247.8 KiB

URL	Transfer Size	Est Savings
www.googletagmanager.com/gtag/js?id=G-PM8FXLP65G&cx=c&gtm=4e64h1	151.7 KiB	63.9 KiB
www.googletagmanager.com/gtm.js?id=GTM-N67TT5M	143.0 KiB	63.2 KiB
www.nikkeibp.co.jp/js/bpcommon/jquery-1.x.min.js	95.0 KiB	48.7 KiB
www.nikkeibp.co.jp/js/www/2018/slick.min.js?20200826	41.0 KiB	37.8 KiB
connect.facebook.net/en_US/fbevents.js	96.5 KiB	34.1 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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Total CPU Time	Script Evaluation	Script Parse
www.nikkeibp.co.jp/	1.2 s	202 ms	1.5 ms
Unattributable	900 ms	69 ms	0.0 ms
www.googletagmanager.com/gtag/js?id=G-PM8FXLP65G&cx=c&gtm=4e64h1	422 ms	327 ms	91 ms
www.googletagmanager.com/gtm.js?id=GTM-N67TT5M	356 ms	252 ms	73 ms
/signals/config/151720335485995?v=2.9.303&r=stable&domain...	301 ms	272 ms	28 ms
connect.facebook.net/en_US/fbevents.js	219 ms	146 ms	67 ms
cdn.cxense.com/cx.js	210 ms	181 ms	17 ms
img.ak.impact-ad.jp/ut/a1/tracking.min.js	202 ms	157 ms	33 ms
www.nikkeibp.co.jp/js/bpcommon/jquery-1.x.min.js	180 ms	117 ms	13 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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Category	Time Spent
Script Evaluation	1.8 s
Other	1.2 s
Style & Layout	618 ms
Script Parsing & Compilation	342 ms
Rendering	73 ms
Parse HTML & CSS	38 ms

Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 6.9 KiB

URL	Transfer Size	Est Savings
www.nikkeibp.co.jp/css/www/2018/index.css?251020	24.2 KiB	3.8 KiB
www.nikkeibp.co.jp/css/www/2018/common.css?20231122	17.9 KiB	3.1 KiB

Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 11.6 KiB

URL	Transfer Size	Est Savings
www.nikkeibp.co.jp/css/www/2018/common.css?20231122	17.7 KiB	11.6 KiB

Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size
/5207194079175/20220512182908_beb0d5d2fc7b112b7103bc0ac41...	10.0 MiB
www.nikkeibp.co.jp/images/www/2018/index/bgi-services_02.jpg	209.0 KiB
www.googletagmanager.com/gtag/js?id=G-PM8FXLP65G&cx=c&gtm=4e64h1	151.8 KiB
www.googletagmanager.com/gtm.js?id=GTM-N67TT5M	143.4 KiB
www.nikkeibp.co.jp/images/www/2018/common/bgi-map_01_sp.svg?191011	142.5 KiB
www.nikkeibp.co.jp/images/www/2018/index/bgi-services_03.jpg	139.7 KiB
www.nikkeibp.co.jp/images/www/2018/index/bgi-services_04.jpg	137.1 KiB
www.nikkeibp.co.jp/images/www/2018/index/bgi-services_01.jpg	123.4 KiB
www.nikkeibp.co.jp/images/www/2018/index/bgi-other_01.jpg	121.8 KiB
connect.facebook.net/en_US/fbevents.js	96.6 KiB

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL
日経BP採用案内 `ul#bnr > li > a > img.sp`	www.nikkeibp.co.jp/images/www/2018/index/bnr-recruit_02.jpg?230118
50を超えるメディア `ul > li > div.box > img`	www.nikkeibp.co.jp/images/www/2018/index/bnr-data_01.png
専門雑誌一筋50年 `ul > li > div.box > img`	www.nikkeibp.co.jp/images/www/2018/index/bnr-data_02.png
930万ビジネスパーソンID `ul > li > div.box > img`	www.nikkeibp.co.jp/images/www/2018/index/bnr-data_03.png
調査データアーカイブ100万本 `ul > li > div.box > img`	www.nikkeibp.co.jp/images/www/2018/index/bnr-data_04.png
300人以上の専門記者 `ul > li > div.box > img`	www.nikkeibp.co.jp/images/www/2018/index/bnr-data_05.png
年間約1,000回のセミナー・イベント `ul > li > div.box > img`	www.nikkeibp.co.jp/images/www/2018/index/bnr-data_06_2.png
div.col2 > div.col > a > img `div.col2 > div.col > a > img`	www.nikkeibp.co.jp/images/www/2018/index/ico-services_01.png
div.col2 > div.col > a > img `div.col2 > div.col > a > img`	www.nikkeibp.co.jp/images/www/2018/index/ico-services_02.png
div.col2 > div.col > a > img `div.col2 > div.col > a > img`	www.nikkeibp.co.jp/images/www/2018/index/ico-services_03.png
div.col2 > div.col > a > img `div.col2 > div.col > a > img`	www.nikkeibp.co.jp/images/www/2018/index/ico-services_04.png

More information about the performance of your application. These numbers don't directly affect the Performance score.

●Layout shift culprits

●Optimize DOM size

●Forced reflow

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify JavaScript

●User Timing marks and measures 5 user timings

●Avoid long main-thread tasks 12 long tasks found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 160 ms

●Server Backend Latencies 110 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Initial server response time was short Root document took 140 ms

○INP breakdown

○Avoid non-composited animations

○Avoid large layout shifts

Accessibility

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.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
head > meta `head > meta`

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html `html`

These items highlight common accessibility best practices.

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

○The user's focus is directed to new content added to the page

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

●`[aria-hidden="true"]` is not present on the document `<body>`

●Image elements have `[alt]` attributes

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Links have a discernible name

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●`<video>` elements contain a `<track>` element with `[kind="captions"]`

○`[accesskey]` values are unique

○`[aria-*]` attributes match their roles

○`button`, `link`, and `menuitem` elements have accessible names

○ARIA attributes are used as specified for the element's role

○Deprecated ARIA roles were not used

○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

○`[aria-hidden="true"]` elements do not contain focusable descendents

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements use only permitted ARIA attributes

○`[role]`s have all required `[aria-*]` attributes

○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

○`[role]`s are contained by their required parent element

○`[role]` values are valid

○Elements with the `role=text` attribute do not have focusable descendents.

○ARIA toggle fields have accessible names

○ARIA `tooltip` elements have accessible names

○ARIA `treeitem` elements have accessible names

○`[aria-*]` attributes have valid values

○`[aria-*]` attributes are valid and not misspelled

○Buttons have an accessible name

○The page contains a heading, skip link, or landmark region

○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

○Definition list items are wrapped in `<dl>` elements

○ARIA IDs are unique

○No form fields have multiple labels

○`<frame>` or `<iframe>` elements have a title

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

○Form elements have associated labels

○Links are distinguishable without relying on color.

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

○No element has a `[tabindex]` value greater than 0

○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.

○`[lang]` attributes have a valid value

○Tables have different content in the summary attribute and `<caption>`.

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

○Image elements do not have `[alt]` attributes that are redundant text.

○Identical links have the same purpose.

○Elements with visible text labels have matching accessible names.

○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

○`<td>` elements in a large `<table>` have one or more table headers.

Best Practices

General

Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Deprecation / Warning	Source
AttributionReporting	connect.facebook.net/en_US/fbevents.js line 279, col 769

●Uses HTTPS

●Avoids third-party cookies

●Allows users to paste into input fields

●Avoids requesting the geolocation permission on page load

●Avoids requesting the notification permission on page load

●Displays images with correct aspect ratio

●Serves images with appropriate resolution

●Page has the HTML doctype

●Properly defines charset

●No browser errors logged to the console

●No issues in the `Issues` panel in Chrome Devtools

●Ensure CSP is effective against XSS attacks

●Use a strong HSTS policy

●Ensure proper origin isolation with COOP

●Mitigate clickjacking with XFO or CSP

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

100

SEO

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.

○Structured data is valid

●Page isn’t blocked from indexing

●Document has a `<title>` element

●Document has a meta description

●Page has successful HTTP status code

●Links have descriptive text

●Links are crawlable

●robots.txt is valid

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

Performance

Accessibility

Best Practices

100

SEO

Core Web Vitals

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.33 s

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

22 ms

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.

2.55 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

2.59 s

Detailed Report

Audit breakdown by category with detailed findings.

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Why this matters

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more ▾

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.

Why this matters

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Request	Cache TTL	Transfer Size
connect.facebook.net/en_US/fbevents.js	1200.0 s	96.6 KiB
www.nikkeibp.co.jp/images/www/2018/index/bgi-services_02.jpg	86400.0 s	209.0 KiB
www.nikkeibp.co.jp/images/www/2018/common/bgi-map_01.svg?191011	86400.0 s	140.7 KiB
www.nikkeibp.co.jp/images/www/2018/index/bgi-services_03.jpg	86400.0 s	139.7 KiB
www.nikkeibp.co.jp/images/www/2018/index/bgi-services_04.jpg	86400.0 s	137.1 KiB
www.nikkeibp.co.jp/images/www/2018/index/bgi-services_01.jpg	86400.0 s	123.4 KiB
www.nikkeibp.co.jp/images/www/2018/index/bgi-other_01.jpg	86400.0 s	121.8 KiB
/signals/config/151720335485995?v=2.9.303&r=stable&domain...	1200.0 s	53.4 KiB
www.nikkeibp.co.jp/js/bpcommon/jquery-1.x.min.js	86400.0 s	95.3 KiB
cdn.cxense.com/cx.js	3600.0 s	38.1 KiB
cdn.cxense.com/cx.js	3600.0 s	38.1 KiB
www.nikkeibp.co.jp/images/www/2018/index/bnr-recruit_01.jpg?230118	86400.0 s	55.8 KiB
www.nikkeibp.co.jp/images/www/2018/index/bnr-recruit_02.jpg?230118	86400.0 s	42.5 KiB
www.nikkeibp.co.jp/js/www/2018/slick.min.js?20200826	86400.0 s	41.2 KiB
www.nikkeibp.co.jp/css/www/2018/index.css?251020	86400.0 s	24.2 KiB
www.nikkeibp.co.jp/css/www/2018/common.css?20231122	86400.0 s	17.9 KiB
www.nikkeibp.co.jp/images/www/2018/index/bnr-bg_01.jpg	86400.0 s	16.1 KiB
www.nikkeibp.co.jp/css/www/2018/font/oswald-v16-latin-regular.woff2	86400.0 s	15.1 KiB
cdn.cxense.com/cx.cce.js	3600.0 s	6.8 KiB
www.nikkeibp.co.jp/images/www/2018/index/ico-services_04.png	86400.0 s	12.6 KiB
www.nikkeibp.co.jp/images/www/2018/index/bnr-data_06_2.png	86400.0 s	8.9 KiB
www.nikkeibp.co.jp/js/www/2018/index.js?20200826	0.0 ms	3.5 KiB
www.nikkeibp.co.jp/images/www/2018/index/img-main-title_03.svg	86400.0 s	7.4 KiB
www.nikkeibp.co.jp/images/www/2018/index/ico-services_01.png	86400.0 s	7.2 KiB
www.nikkeibp.co.jp/images/www/2018/index/img-main-title_02.svg	86400.0 s	7.1 KiB
www.nikkeibp.co.jp/images/www/2018/index/ico-services_02.png	86400.0 s	6.6 KiB
www.nikkeibp.co.jp/js/bpcommon/onetag/bpTrackVarsCommon.js	0.0 ms	2.6 KiB
www.nikkeibp.co.jp/images/www/2018/index/bnr-data_05.png	86400.0 s	6.3 KiB
www.nikkeibp.co.jp/images/www/2018/index/bnr-data_01.png	86400.0 s	6.2 KiB
www.nikkeibp.co.jp/js/www/2018/common.js?20200121	0.0 ms	2.4 KiB
www.nikkeibp.co.jp/images/www/2018/index/bnr-data_04.png	86400.0 s	5.9 KiB
www.nikkeibp.co.jp/images/www/2018/index/bnr-data_03.png	86400.0 s	5.8 KiB
www.nikkeibp.co.jp/images/www/2018/index/bnr-data_02.png	86400.0 s	5.5 KiB
www.nikkeibp.co.jp/images/www/2018/index/ico-services_03.png	86400.0 s	3.8 KiB
www.nikkeibp.co.jp/js/www/2018/jquery.matchHeight-min.js	86400.0 s	3.5 KiB
www.nikkeibp.co.jp/js/www/2018/form.js?20181212	0.0 ms	1.3 KiB
www.nikkeibp.co.jp/images/www/2018/index/log-main_01.svg	86400.0 s	2.1 KiB
www.nikkeibp.co.jp/images/bplogo/logo.svg	86400.0 s	2.0 KiB
www.nikkeibp.co.jp/js/bpcommon/onetag/bpTrackVars.js	0.0 ms	643 B
/Repo/rep.gif?ver=3.3.0&typ=pgv&rnd=mo98fn9mhhcqc77h&sid=...	0.0 ms	413 B
www.nikkeibp.co.jp/images/www/2018/common/ico-win_01.svg?20181210	86400.0 s	921 B
www.nikkeibp.co.jp/images/www/2018/common/ico-arrow_01.svg	86400.0 s	845 B
www.nikkeibp.co.jp/css/www/2018/font.css	86400.0 s	601 B
/tr/?id=151720335485995&ev=PageView&dl=https%3A%2F%2Fwww....	0.0 ms	18 B
/5207194079175/20220512182906_3ff58bbb1ed5196188f59fc23b6...	0.0 ms	0 B

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Est Savings
www.nikkeibp.co.jp/css/www/2018/font/oswald-v16-latin-regular.woff2	85 ms

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

title: Preconnected origins

value: no origins were preconnected

description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.

title: Preconnect candidates

value: No additional origins are good candidates for preconnecting

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size	Duration
www.nikkeibp.co.jp/js/bpcommon/jquery-1.x.min.js	95.3 KiB	107 ms
www.nikkeibp.co.jp/js/www/2018/slick.min.js?20200826	41.2 KiB	107 ms
www.nikkeibp.co.jp/js/www/2018/common.js?20200121	2.4 KiB
www.nikkeibp.co.jp/js/www/2018/index.js?20200826	3.5 KiB
www.nikkeibp.co.jp/js/www/2018/form.js?20181212	1.3 KiB
www.nikkeibp.co.jp/css/www/2018/index.css?251020	24.2 KiB	107 ms
www.nikkeibp.co.jp/js/www/2018/jquery.matchHeight-min.js	3.5 KiB
www.nikkeibp.co.jp/css/www/2018/common.css?20231122	17.9 KiB
www.nikkeibp.co.jp/css/www/2018/font.css	601 B

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL	Resource Size	Est Savings
ソリューション SOLUTION 独自の視点・分析、専門領域の人脈・場の創出。真似のできないソリューション `div#services > div.col2 > div.col > a`	www.nikkeibp.co.jp/images/www/2018/index/bgi-services_02.jpg	208.6 KiB	135.7 KiB
出版・書籍 PUBLICATION ロングセラーから時流のテーマまで独自視点のラインナップ `div#services > div.col2 > div.col > a`	www.nikkeibp.co.jp/images/www/2018/index/bgi-services_03.jpg	139.4 KiB	66.5 KiB
イベント・セミナー EVENT SEMINAR 「体感型メディア」で効果的なコミュニケーションを `div#services > div.col2 > div.col > a`	www.nikkeibp.co.jp/images/www/2018/index/bgi-services_04.jpg	136.7 KiB	63.8 KiB
日経BPとは会社概要日経BPのあゆみ SDGs/ESG への取り組み `body#top > div#wrap > div#other`	www.nikkeibp.co.jp/images/www/2018/index/bgi-other_01.jpg	121.5 KiB	56.9 KiB
メディア MEDIA 経営・技術・生活の先端・専門情報を幅広く発信 `div#services > div.col2 > div.col > a`	www.nikkeibp.co.jp/images/www/2018/index/bgi-services_01.jpg	123.0 KiB	50.1 KiB
日経BP採用案内 `ul#bnr > li > a > img.pc`	www.nikkeibp.co.jp/images/www/2018/index/bnr-recruit_01.jpg?230118	55.5 KiB	17.3 KiB
div.col2 > div.col > a > img `div.col2 > div.col > a > img`	www.nikkeibp.co.jp/images/www/2018/index/ico-services_04.png	12.4 KiB	5.9 KiB
年間約1,000回のセミナー・イベント `ul > li > div.box > img`	www.nikkeibp.co.jp/images/www/2018/index/bnr-data_06_2.png	8.7 KiB	4.8 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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 408 ms

URL	Time Spent
nikkeibp.co.jp/	408 ms
www.nikkeibp.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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

Diagnostics

Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 29.3 KiB

URL	Transfer Size	Est Savings
www.nikkeibp.co.jp/css/www/2018/index.css?251020	24.0 KiB	15.7 KiB
www.nikkeibp.co.jp/css/www/2018/common.css?20231122	17.7 KiB	13.6 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.

Why this matters

Multi-megabyte JavaScript bundles delay every interactive feature on the page.

Learn more ▾

Source: Google web.dev / Lighthouse

Estimated savings: 90 ms 248.3 KiB

URL	Transfer Size	Est Savings
www.googletagmanager.com/gtag/js?id=G-PM8FXLP65G&cx=c&gtm=4e64h1	151.7 KiB	63.9 KiB
www.googletagmanager.com/gtm.js?id=GTM-N67TT5M	143.0 KiB	63.2 KiB
www.nikkeibp.co.jp/js/bpcommon/jquery-1.x.min.js	95.0 KiB	48.9 KiB
www.nikkeibp.co.jp/js/www/2018/slick.min.js?20200826	41.0 KiB	37.8 KiB
connect.facebook.net/en_US/fbevents.js	96.5 KiB	34.5 KiB

Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 6.9 KiB

URL	Transfer Size	Est Savings
www.nikkeibp.co.jp/css/www/2018/index.css?251020	24.2 KiB	3.8 KiB
www.nikkeibp.co.jp/css/www/2018/common.css?20231122	17.9 KiB	3.1 KiB

Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size
/5207194079175/20220512182906_3ff58bbb1ed5196188f59fc23b6...	10.0 MiB
www.nikkeibp.co.jp/images/www/2018/index/bgi-services_02.jpg	209.0 KiB
www.googletagmanager.com/gtag/js?id=G-PM8FXLP65G&cx=c&gtm=4e64h1	151.8 KiB
www.googletagmanager.com/gtm.js?id=GTM-N67TT5M	143.4 KiB
www.nikkeibp.co.jp/images/www/2018/common/bgi-map_01.svg?191011	140.7 KiB
www.nikkeibp.co.jp/images/www/2018/index/bgi-services_03.jpg	139.7 KiB
www.nikkeibp.co.jp/images/www/2018/index/bgi-services_04.jpg	137.1 KiB
www.nikkeibp.co.jp/images/www/2018/index/bgi-services_01.jpg	123.4 KiB
www.nikkeibp.co.jp/images/www/2018/index/bgi-other_01.jpg	121.8 KiB
connect.facebook.net/en_US/fbevents.js	96.6 KiB

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL
日経BP採用案内 `ul#bnr > li > a > img.pc`	www.nikkeibp.co.jp/images/www/2018/index/bnr-recruit_01.jpg?230118
50を超えるメディア `ul > li > div.box > img`	www.nikkeibp.co.jp/images/www/2018/index/bnr-data_01.png
専門雑誌一筋50年 `ul > li > div.box > img`	www.nikkeibp.co.jp/images/www/2018/index/bnr-data_02.png
930万ビジネスパーソンID `ul > li > div.box > img`	www.nikkeibp.co.jp/images/www/2018/index/bnr-data_03.png
調査データアーカイブ100万本 `ul > li > div.box > img`	www.nikkeibp.co.jp/images/www/2018/index/bnr-data_04.png
300人以上の専門記者 `ul > li > div.box > img`	www.nikkeibp.co.jp/images/www/2018/index/bnr-data_05.png
年間約1,000回のセミナー・イベント `ul > li > div.box > img`	www.nikkeibp.co.jp/images/www/2018/index/bnr-data_06_2.png
div.col2 > div.col > a > img `div.col2 > div.col > a > img`	www.nikkeibp.co.jp/images/www/2018/index/ico-services_01.png
div.col2 > div.col > a > img `div.col2 > div.col > a > img`	www.nikkeibp.co.jp/images/www/2018/index/ico-services_02.png
div.col2 > div.col > a > img `div.col2 > div.col > a > img`	www.nikkeibp.co.jp/images/www/2018/index/ico-services_03.png
div.col2 > div.col > a > img `div.col2 > div.col > a > img`	www.nikkeibp.co.jp/images/www/2018/index/ico-services_04.png
日経BP `div.inner > div.box > a.logo > img`	www.nikkeibp.co.jp/images/bplogo/logo.svg

More information about the performance of your application. These numbers don't directly affect the Performance score.

●Max Potential First Input Delay 90 ms

●Layout shift culprits

●Optimize DOM size

●Forced reflow

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify JavaScript

●User Timing marks and measures 5 user timings

●JavaScript execution time 0.4 s

●Minimizes main-thread work 1.0 s

●Avoid long main-thread tasks 3 long tasks found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 240 ms

●Server Backend Latencies 200 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Initial server response time was short Root document took 140 ms

○INP breakdown

○LCP request discovery

○Avoid non-composited animations

○Avoid large layout shifts

Accessibility

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
head > meta `head > meta`

These items highlight common accessibility best practices.

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

○The user's focus is directed to new content added to the page

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

●`[aria-hidden="true"]` is not present on the document `<body>`

●Image elements have `[alt]` attributes

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Links have a discernible name

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●`<video>` elements contain a `<track>` element with `[kind="captions"]`

○`[accesskey]` values are unique

○`[aria-*]` attributes match their roles

○`button`, `link`, and `menuitem` elements have accessible names

○ARIA attributes are used as specified for the element's role

○Deprecated ARIA roles were not used

○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

○`[aria-hidden="true"]` elements do not contain focusable descendents

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements use only permitted ARIA attributes

○`[role]`s have all required `[aria-*]` attributes

○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

○`[role]`s are contained by their required parent element

○`[role]` values are valid

○Elements with the `role=text` attribute do not have focusable descendents.

○ARIA toggle fields have accessible names

○ARIA `tooltip` elements have accessible names

○ARIA `treeitem` elements have accessible names

○`[aria-*]` attributes have valid values

○`[aria-*]` attributes are valid and not misspelled

○Buttons have an accessible name

○The page contains a heading, skip link, or landmark region

○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

○Definition list items are wrapped in `<dl>` elements

○ARIA IDs are unique

○No form fields have multiple labels

○`<frame>` or `<iframe>` elements have a title

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

○Form elements have associated labels

○Links are distinguishable without relying on color.

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

○No element has a `[tabindex]` value greater than 0

○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.

○`[lang]` attributes have a valid value

○Tables have different content in the summary attribute and `<caption>`.

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

○Image elements do not have `[alt]` attributes that are redundant text.

○Identical links have the same purpose.

○Elements with visible text labels have matching accessible names.

○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

○`<td>` elements in a large `<table>` have one or more table headers.

Best Practices

General

Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Deprecation / Warning	Source
AttributionReporting	connect.facebook.net/en_US/fbevents.js line 279, col 769

●Uses HTTPS

●Avoids third-party cookies

●Allows users to paste into input fields

●Avoids requesting the geolocation permission on page load

●Avoids requesting the notification permission on page load

●Displays images with correct aspect ratio

●Serves images with appropriate resolution

●Page has the HTML doctype

●Properly defines charset

●No browser errors logged to the console

●No issues in the `Issues` panel in Chrome Devtools

●Ensure CSP is effective against XSS attacks

●Use a strong HSTS policy

●Ensure proper origin isolation with COOP

●Mitigate clickjacking with XFO or CSP

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

100

SEO

○Structured data is valid

●Page isn’t blocked from indexing

●Document has a `<title>` element

●Document has a meta description

●Page has successful HTTP status code

●Links have descriptive text

●Links are crawlable

●robots.txt is valid

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`

Results for https://nikkeibp.co.jp

Site Health

How you compare

Top Priorities (5)

Fix Priority Matrix

Quick Wins

Strategic

Easy Improvements

Deprioritize

What fixing these means

Conversion Barriers

Speed (2)

Trust (2)

Usability (1)

Content (2)

Navigation (1)

Return on Investment

Investment

Monthly returns

Regulatory risk avoided

Payback period

Estimated Remediation Cost

Cost by category

Cost by effort level

What Inaction Is Costing You

Compliance Risk

Bandwidth Waste

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Best practices

Best Practices

General

SEO

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Best practices

Best Practices

General

SEO

Keyboard Shortcuts