Skip to content
Audit Complete

Results for https://shop-pro.jp

Visit site
JP · JPY (¥) · Estimated Applicable regulations: APPI Dev cost: ¥8,000/hr How jurisdiction is detected
E-commerce · estimated Tracking: purchases
Singapore Singapore · Singapore Completed: Apr 22, 2026 21:23 UTC
Download JSON Download Markdown Report

Mobile 375 × 812

Screenshot of the audited page (Mobile 375×812)

Desktop 1440 × 900

Screenshot of the audited page (Desktop 1440×900)
C72

Site Health

Score: 72 / 100

Based on 8 categories, 0 sections

Room to improve — your 16.6s load time is above Google's 2.5s 'Good' threshold.

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.

Solid infrastructure — fast server responses across the board.

Mostly compliant — a few items need attention.

Good content signals with minor gaps.

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

Cart Functionality · 487 peers
You 72
·
Avg 72
At average
0 50 100
Better than 36% of Cart Functionality sites See full Cart Functionality benchmark →
Astro · 47 peers
You 72
·
Avg 75
At average
0 50 100
Better than 10% of Astro sites See full Astro benchmark →

Top Priorities (5)

1

Content-Security-Policy header is missing

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

Security › Security Headers
2

No Content-Security-Policy header found

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

Security › Content Security Policy
3

Page weighs 10.8 MB (6.7 MB transferred)

Performance issues directly impact user engagement and conversion rates.

Performance › Page Weight Budget
4

1 button(s) with no accessible text

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

Accessibility › Link & Button Quality
5

4 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

Quick Wins

2

High impact, low effort — start here.

Strategic

3

High impact, requires investment.

Easy Improvements

0

Small gains, minimal effort.

Nothing in this quadrant — good news.

Deprioritize

0

Low impact, high effort — do last.

Nothing in this quadrant — good news.

← Low effort High effort →
BeaverCheck badge
Embed this badge
[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fshop-pro.jp)](https://beavercheck.com/results/aca20d7f-c09e-47a5-b02b-4c098d68731a)
<a href="https://beavercheck.com/results/aca20d7f-c09e-47a5-b02b-4c098d68731a"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fshop-pro.jp" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fshop-pro.jp

This badge auto-updates with your latest scan result.

What fixing these means

Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. Your LCP of 16.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.

2 security gaps detected — browsers may warn visitors about your site.
Your LCP is 16.6s — fixing the 1 performance critical could bring it under Google's 2.5s 'Good' threshold.
2 accessibility issues exclude users who rely on assistive technology.

Conversion Barriers

3 critical 4 warning

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

Speed (2)

Page takes 16.6s to load

+12% bounce

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

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

Page feels frozen for 3.6s

+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

Content (1)

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

Navigation (2)

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

3 broken link(s) on the page

+5% bounce

Clicks land on 404s — trust drops and the session often ends

Fix: Fix or remove the broken destinations surfaced on the Content tab

Preliminary CRO audit — each barrier links to the tab with detailed analysis.

Return on Investment

¥48,000 investment → ¥252/month returns + JPY 100,000,000 risk avoided

Payback period: > 2 years First-year ROI: -94%

Investment

¥48,000

6h · 5 findings

Monthly returns

¥252 /mo

~¥3,026 / year

  • Bandwidth savings ¥252

Regulatory risk avoided

JPY 100,000,000

if kept compliant

  • APPI JPY 100,000,000

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

Full methodology & sources

Estimated Remediation Cost

¥48,000

6.0 developer hours at ¥8000/hr

Based on Japan rates (¥8000/hr)

Quick wins
¥8,000 2 fixes in ~60 minutes

Start here for the best return on investment

Cost by category

Cost by effort level

Adjust assumptions
¥ /hr

Rates reflect fully-loaded developer cost including overhead

How developer rates are sourced

What Inaction Is Costing You

¥8,333,585 / month at risk

~¥100,003,026 / year if left unfixed

Compliance Risk

¥100,000,000

APPI
  • No privacy policy link detected
    APPI: JPY 100,000 – JPY 100,000,000
  • 7 advertising/retargeting trackers detected
    APPI: JPY 100,000 – JPY 100,000,000
  • Trackers detected but no cookie policy found
    APPI: JPY 100,000 – JPY 100,000,000

+2 more

Bandwidth Waste

¥252 /mo

21117.1 MB/mo × 11.940 JPY/GB

  • Optimize transfer: save ~2.1 MB per page load
    Saves ¥252/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

Unique monthly visitors from your analytics

Purchases, signups, or key actions

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

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

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

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.

8.50 s

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

16.61 s

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

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

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

37.40 s

Detailed Report

Audit breakdown by category with detailed findings.

26

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.

RequestCache TTLTransfer Size
shop-pro.jp/example/wp-content/uploads/2026/04/tabby_eyecatch.png0.0 ms923.1 KiB
static-www.shop-pro.jp/_astro/image_feature-support_01.Dsqx544a.jpg3600.0 s364.1 KiB
static-www.shop-pro.jp/_astro/logo_corporate-all.-rdgkIVE.png3600.0 s359.1 KiB
static-www.shop-pro.jp/_astro/image_ai-efficiency_sp_01.C1EqVOB0.jpg3600.0 s330.1 KiB
shop-pro.jp/example/wp-content/uploads/2026/04/IMG_4313-2.jpg0.0 ms202.4 KiB
static-www.shop-pro.jp/assets/images/shared/bg_texture_01.png3600.0 s214.0 KiB
static-www.shop-pro.jp/_astro/bg_texture_01.Cm4SSkrI.png3600.0 s214.0 KiB
shop-pro.jp/example/wp-content/uploads/2026/04/studs_eye.jpg0.0 ms170.6 KiB
static-www.shop-pro.jp/_astro/image_pickup_function_03.TxRK3HB-.jpg3600.0 s212.5 KiB
static-www.shop-pro.jp/_astro/image_pickup_function_02.BZz2VeI9.jpg3600.0 s180.3 KiB
shop-pro.jp/example/wp-content/uploads/2026/04/001.jpg0.0 ms111.3 KiB
shop-pro.jp/example/wp-content/uploads/2026/04/jtb_eyecaych2.jpg0.0 ms104.9 KiB
connect.facebook.net/en_US/fbevents.js1200.0 s96.6 KiB
cdn.activity.smart-bdash.com/tag-manager/bd-rb8n52/btm.js0.0 ms70.6 KiB
static-www.shop-pro.jp/_astro/image_pickup_function_01.ZUJqJnIs.jpg3600.0 s59.6 KiB
static-www.shop-pro.jp/_astro/image_campaign_shienkin_01.Clilc48F.png3600.0 s59.1 KiB
static-www.shop-pro.jp/_astro/image_first-view_01_sp.C1_6jorU.png3600.0 s57.1 KiB
static-www.shop-pro.jp/_astro/image_pickup_example_01.CRN73Jzd.jpg3600.0 s52.8 KiB
/signals/config/481563874184726?v=2.9.303&r=stable&domain...1200.0 s46.5 KiB
js-na2.hs-analytics.net/analytics/1776887700000/47416332.js300.0 s42.3 KiB
static-www.shop-pro.jp/_astro/bg_first-view_01.Bo4RxFYo.jpg3600.0 s40.4 KiB
static-www.shop-pro.jp/_astro/popup-banner-consultation.CeX9-mBB.jpg3600.0 s38.7 KiB
static-www.shop-pro.jp/_astro/media-kit.COfs9W4U.css3600.0 s34.1 KiB
static-www.shop-pro.jp/_astro/splide.esm.CtpvrVZh.js3600.0 s32.6 KiB
js-na2.hs-banner.com/v2/47416332/banner.js300.0 s24.6 KiB
b99.yahoo.co.jp/pagead/conversion_async.js0.0 ms23.5 KiB
static-www.shop-pro.jp/_astro/banner_free-consultation_01.BECy0eAh.png3600.0 s24.4 KiB
www.google-analytics.com/analytics.js7200.0 s20.9 KiB
static-www.shop-pro.jp/_astro/index.DXToC2GO.css3600.0 s18.0 KiB
js.adsrvr.org/up_loader.1.1.0.js0.0 ms12.5 KiB
t.afi-b.com/jslib/lpcv.js?cid=72511232&pid=e669V86400.0 s28.2 KiB
static-www.shop-pro.jp/_astro/logo_gmo-brand-security.CguShVOD.png3600.0 s14.1 KiB
s.yimg.jp/images/listing/tool/cv/ytag.js600.0 s11.8 KiB
scripts.clarity.ms/0.8.59-beta/clarity.js86400.0 s26.2 KiB
statics.a8.net/a8sales/a8sales.js0.0 ms9.7 KiB
static-www.shop-pro.jp/_astro/inhouse-icons.1qrmVAEG.woff23600.0 s9.2 KiB
static-www.shop-pro.jp/_astro/logo_gmo-global-sign.C7d6ios2.png3600.0 s7.7 KiB
static-www.shop-pro.jp/_astro/logo_colorme_04.CNPQq0dB.svg3600.0 s7.6 KiB
static-www.shop-pro.jp/_astro/media-kit.CQXpoThI.css3600.0 s7.1 KiB
static-www.shop-pro.jp/_astro/media-kit.DlVFFWdM.css3600.0 s7.0 KiB
cdn.activity.smart-bdash.com/tracking-script/bdash_log.js7200.0 s7.0 KiB
static-www.shop-pro.jp/_astro/logo_gmo-cyber-security.DnPaV0Vq.png3600.0 s6.0 KiB
cache.img.gmo.jp/gmo/header/script.min.js86400.0 s11.4 KiB
static-www.shop-pro.jp/_astro/splide-extension-auto-scroll.esm.Bv3OVTVU.js3600.0 s5.7 KiB
static-www.shop-pro.jp/_astro/logo_gmo-payment-gateway.CsYdqMTv.png3600.0 s5.5 KiB
static-www.shop-pro.jp/_astro/index.BRKXMWAJ.css3600.0 s5.4 KiB
static-www.shop-pro.jp/_astro/features-lower-page.B01AeCWc.css3600.0 s5.4 KiB
static-www.shop-pro.jp/_astro/app-store.8d2v-Ldu.css3600.0 s4.9 KiB
static-www.shop-pro.jp/_astro/hoisted.KRSTUxG5.js3600.0 s4.8 KiB
js-na2.hsadspixel.net/pixels.js600.0 s3.9 KiB
gmo-cybersecurity.com/siteseal/siteseal.js0.0 ms3.4 KiB
static-www.shop-pro.jp/_astro/logo_gmo-epsilon.CQYRbdn9.png3600.0 s3.9 KiB
r.moshimo.com/af/r/maftag.js0.0 ms2.8 KiB
static-www.shop-pro.jp/_astro/icon_chatbot_01.HQ5o16di.svg3600.0 s3.2 KiB
cache.img.gmo.jp/gmo/footer/script.min.js86400.0 s5.9 KiB
analytics.ahrefs.com/analytics.js14400.0 s3.0 KiB
static-www.shop-pro.jp/assets/images/shared/bg_gradation_indigo_01.svg3600.0 s2.5 KiB
static-www.shop-pro.jp/assets/images/shared/bg_gradation_orange_01.svg3600.0 s2.5 KiB
static-www.shop-pro.jp/_astro/bg_gradation_orange_01.B3Nfx-DR.svg3600.0 s2.5 KiB
d.line-scdn.net/n/line_tag/public/release/v1/lt.js404385.0 s10.1 KiB
static-www.shop-pro.jp/_astro/hoisted.l-D3zfkr.js3600.0 s1.9 KiB
static-www.shop-pro.jp/_astro/preload-helper.CmsKOCeN.js3600.0 s1.7 KiB
static-www.shop-pro.jp/_astro/icon_share_01.D2sVwjHD.svg3600.0 s1.6 KiB
static-www.shop-pro.jp/_astro/hoisted._BGJQOLg.js3600.0 s1.5 KiB
cache.img.gmo.jp/gmo/security/script.min.js86400.0 s2.7 KiB
js.adsrvr.org/universal_pixel.js0.0 ms957 B
/_astro/CorporateLogo.astro_astro_type_script_index_0_lan...3600.0 s1.1 KiB
js-na2.hs-scripts.com/47416332.js0.0 ms853 B
static-www.shop-pro.jp/_astro/icon_x_01.DTHLBMhQ.svg3600.0 s1013 B
www.google-analytics.com/plugins/ua/linkid.js3600.0 s995 B
static-www.shop-pro.jp/_astro/hoisted.CBrSBtjX.js3600.0 s922 B
static-www.shop-pro.jp/_astro/bg_line_01.w1zY8oyi.svg3600.0 s858 B
static-www.shop-pro.jp/_astro/icon_chevron-down_01.CMlAuWeZ.svg3600.0 s810 B
seal.brandsecurity.gmo/static/js/siteseal.js14400.0 s899 B
/tr/?id=481563874184726&ev=PageView&dl=https%3A%2F%2Fshop...0.0 ms16 B

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.

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:source label:Top function call valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:163.968 source:map[column:322 line:885 type:source-location url:https://www.googletagmanager.com/gtm.js?id=GTM-PNPH9V urlProvider:network]]]
headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:163.968 source:map[column:55 line:883 type:source-location url:https://www.googletagmanager.com/gtm.js?id=GTM-PNPH9V urlProvider:network]] map[reflowTime:132.891 source:map[column:44 line:881 type:source-location url:https://www.googletagmanager.com/gtm.js?id=GTM-PNPH9V urlProvider:network]] map[reflowTime:87.716 source:map[column:2351 line:5 type:source-location url:https://static-www.shop-pro.jp/_astro/splide.esm.CtpvrVZh.js urlProvider:network]] map[reflowTime:0.512 source:map[column:86058 line:22 type:source-location url:https://js-na2.hs-analytics.net/analytics/1776887700000/47416332.js urlProvider:network]] map[reflowTime:0.1 source:map[column:55 line:905 type:source-location url:https://www.googletagmanager.com/gtag/js?id=G-CV529VZLKV&cx=c&gtm=4e64k0h1 urlProvider:network]]]

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-SECTION
nodeLabel: 総導入件数22万件以上 サポート満足度94.4% やることを減らして、売上を増やそう。 AIに任せて伸ばすECカート お試しは何度でも 無料で始める 資料…
path: 1,HTML,1,BODY,21,DIV,0,MAIN,0,SECTION
selector: body > div.main-content > main > section.first-view
snippet: <section class="first-view" data-astro-cid-wdpvoigt="" style="--bgFirstView: url(https://static-www.shop-pro.jp/_astro/bg_first-view_01.…;">

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

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.

URLResource SizeEst Savings
人×AIサポート。AIチャットボット・設定代行・AIコネクター・制作代行・電話サポート・ECアドバイザー。 div.c-section__container > div.c-section__body > div.feature-support__image > img
static-www.shop-pro.jp/_astro/image_feature-support_01.Dsqx544a.jpg363.1 KiB316.4 KiB
AI活用で効率UP div.ai-efficiency-banner > a > picture > img
static-www.shop-pro.jp/_astro/image_ai-efficiency_sp_01.C1EqVOB0.jpg329.2 KiB297.6 KiB
div#splide01-track > div#splide01-list > div#splide01-slide01 > img.corporate-logo__image div#splide01-track > div#splide01-list > div#splide01-slide01 > img.corporate-logo__image
static-www.shop-pro.jp/_astro/logo_corporate-all.-rdgkIVE.png358.2 KiB215.3 KiB
li#splide02-slide01 > a.card > div.card__image > img li#splide02-slide01 > a.card > div.card__image > img
shop-pro.jp/example/wp-content/uploads/2026/04/IMG_4313-2.jpg202.0 KiB158.0 KiB
新規開設のご相談 div#js-popup-banner > div.popup-banner__container > a.popup-banner__link > img
static-www.shop-pro.jp/_astro/popup-banner-consultation.CeX9-mBB.jpg38.1 KiB29.0 KiB
GMOブランドセキュリティ div.c-section__footer > div.gmo-brands > div.gmo-brands__img-container > img.gmo-brands__img
static-www.shop-pro.jp/_astro/logo_gmo-brand-security.CguShVOD.png13.5 KiB11.9 KiB
GMOグローバルサイン div.c-section__footer > div.gmo-brands > div.gmo-brands__img-container > img.gmo-brands__img
static-www.shop-pro.jp/_astro/logo_gmo-global-sign.C7d6ios2.png7.1 KiB6.3 KiB
GMOサイバーセキュリティ div.c-section__footer > div.gmo-brands > div.gmo-brands__img-container > img.gmo-brands__img
static-www.shop-pro.jp/_astro/logo_gmo-cyber-security.DnPaV0Vq.png5.5 KiB4.8 KiB
GMOペイメントゲートウェイ div.c-section__footer > div.gmo-brands > div.gmo-brands__img-container > img.gmo-brands__img
static-www.shop-pro.jp/_astro/logo_gmo-payment-gateway.CsYdqMTv.png5.0 KiB4.4 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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

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.

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: 600 ms 78.7 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

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

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.

URLTotal CPU TimeScript EvaluationScript Parse
shop-pro.jp/2.5 s33 ms4.7 ms
static-www.shop-pro.jp/_astro/splide-extension-auto-scroll.esm.Bv3OVTVU.js2.4 s1.0 s0.1 ms
www.googletagmanager.com/gtm.js?id=GTM-PNPH9V2.3 s929 ms99 ms
Unattributable1.5 s100 ms0.0 ms
js-na2.hs-analytics.net/analytics/1776887700000/47416332.js1.0 s844 ms15 ms
scripts.clarity.ms/0.8.59-beta/clarity.js719 ms644 ms11 ms
www.googletagmanager.com/gtag/js?id=G-CV529VZLKV&cx=c&gtm=4e64k0h1553 ms469 ms77 ms
www.googletagmanager.com/gtag/js?id=AW-1047068674&cx=c&gtm=4e64k0h1540 ms418 ms65 ms
static-www.shop-pro.jp/_astro/splide.esm.CtpvrVZh.js392 ms137 ms0.4 ms
analytics.tiktok.com/i18n/pixel/static/main.MWE0ZWQ3ZWQwMQ.js336 ms249 ms60 ms
www.googletagmanager.com/gtag/js?id=AW-17525090963324 ms264 ms55 ms
www.googletagmanager.com/gtm.js?id=GTM-PG4PZZ311 ms245 ms56 ms
asset.pepabo.com/pepabo-footer/pepabo-footer.js278 ms203 ms21 ms
/signals/config/481563874184726?v=2.9.303&r=stable&domain...255 ms178 ms27 ms
connect.facebook.net/en_US/fbevents.js195 ms143 ms50 ms
cdn.activity.smart-bdash.com/tag-manager/bd-rb8n52/btm.js188 ms160 ms19 ms
www.google-analytics.com/analytics.js156 ms76 ms60 ms
static.ads-twitter.com/uwt.js138 ms113 ms21 ms
www.googletagmanager.com/gtag/js?id=AW-16577889689134 ms74 ms58 ms
www.google-analytics.com/plugins/ua/linkid.js106 ms100 ms0.5 ms
www.googletagmanager.com/gtag/js?id=AW-16577889689&cx=c&gtm=4e64k1h288 ms30 ms58 ms
www.googletagmanager.com/gtag/js?id=AW-17525090963&cx=c&gtm=4e64k1h279 ms27 ms52 ms
cache.img.gmo.jp/gmo/footer/script.min.js62 ms46 ms2.2 ms
js-na2.hs-banner.com/v2/47416332/banner.js60 ms43 ms11 ms
analytics.tiktok.com/i18n/pixel/static/identify_5cff1caf.js58 ms37 ms21 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.

CategoryTime Spent
Script Evaluation7.6 s
Style & Layout4.0 s
Other2.5 s
Script Parsing & Compilation942 ms
Rendering554 ms
Garbage Collection188 ms
Parse HTML & CSS136 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.4 KiB
URLTransfer SizeEst Savings
/css2?family=Roboto:wght@400;500;700&family=Noto+Sans+JP:...61.0 KiB6.4 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
ul.__pepabo-footer__gmo-group-security-seal > li.__pepabo-footer__gmo-group-security-seal-item > div#ss_gmo_globalsign_secured_site_seal > img#ss_gmo_globalsign_img ul.__pepabo-footer__gmo-group-security-seal > li.__pepabo-footer__gmo-group-security-seal-item > div#ss_gmo_globalsign_secured_site_seal > img#ss_gmo_globalsign_img
/gss/one/image?p1=shop-pro.jp&p2=seal_100-50_ja.png&p3=gs...

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

Layout shift culprits
Document request latency
Optimize DOM size
LCP breakdown
Modern HTTP
Optimize viewport for mobile
Minify JavaScript
User Timing marks and measures 26 user timings
Avoid long main-thread tasks 20 long tasks found
Avoid non-composited animations 5 animated elements found
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 250 ms
Server Backend Latencies 960 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Avoid multiple page redirects
Initial server response time was short Root document took 540 ms
INP breakdown
Avoid large layout shifts
89

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.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
人気 No.1 div.plan-list__item > div.plan-card > div.plan-card__header > div.plan-card__badge
おすすめ div.plan-list__item > div.plan-card > div.plan-card__header > div.plan-card__badge
長期契約で月額費用がお得に! dl.plan-card__emphasis > div > dd.plan-fee > p.plan-notice
FAQ div.c-section__title > div.section-title > div.section-title__text-unit > span.section-title__sub
AIに聞いてみる div.miibo-toast > button#chat-button > span.miibo-toast__content > span.miibo-toast__cta

These are opportunities to improve the legibility of your content.

Names and labels

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.gmoGroupHeader > div.gmoGroupHeader_logo > div.gmoGroupHeader_3wins > a div.gmoGroupHeader > div.gmoGroupHeader_logo > div.gmoGroupHeader_3wins > a

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
バナーを閉じる main > div#js-popup-banner > div.popup-banner__container > button#js-popup-close

These items highlight common accessibility best practices.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
無料診断 div.gmoGroupHeader > div.gmoGroupHeader_secCont > div.gmoGroupHeader_sec > a
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-*]` attributes match their roles
`[aria-hidden="true"]` is not present on the document `<body>`
`[role]`s have all required `[aria-*]` attributes
`[role]` values are valid
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
Buttons have an accessible name
Image elements have `[alt]` attributes
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
ARIA attributes are used as specified for the element's role
`[aria-hidden="true"]` elements do not contain focusable descendents
Elements use only permitted ARIA attributes
`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Definition list items are wrapped in `<dl>` elements
Document has a `<title>` element
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Heading elements appear in a sequentially-descending order
Document has a main landmark.
Deprecated ARIA roles were not used
Uses ARIA roles only on compatible elements
Identical links have the same purpose.
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.
`[accesskey]` values are unique
`button`, `link`, and `menuitem` elements have accessible names
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
ARIA input fields have accessible names
ARIA `meter` elements have accessible names
ARIA `progressbar` elements have accessible names
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
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
The page contains a heading, skip link, or landmark region
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
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
`[lang]` attributes have a valid value
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Tables have different content in the summary attribute and `<caption>`.
All heading elements contain content.
Image elements do not have `[alt]` attributes that are redundant text.
77

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 / WarningSource
AttributionReporting

Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit

Why this matters

Performance issues directly impact user engagement and conversion rates.

SourceDescription
Uncaught SyntaxError: Unexpected identifier 'content'
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 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 DOM-based XSS with Trusted Types
Detected JavaScript libraries
Page has valid source maps
Redirects HTTP traffic to HTTPS
Mitigate clickjacking with XFO or CSP
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
Image elements have `[alt]` attributes
Document has a valid `hreflang`
Document has a valid `rel=canonical`
robots.txt is valid

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

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

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.

2.09 s

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

3.47 s

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

281 ms

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

0.039

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

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

6.03 s

Detailed Report

Audit breakdown by category with detailed findings.

54

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.

RequestCache TTLTransfer Size
shop-pro.jp/example/wp-content/uploads/2026/04/tabby_eyecatch.png0.0 ms923.1 KiB
static-www.shop-pro.jp/_astro/image_ai-efficiency_01.D2kv5yRO.jpg3600.0 s573.9 KiB
static-www.shop-pro.jp/_astro/image_feature-support_01.Dsqx544a.jpg3600.0 s364.1 KiB
static-www.shop-pro.jp/_astro/logo_corporate-all.-rdgkIVE.png3600.0 s359.4 KiB
shop-pro.jp/example/wp-content/uploads/2026/04/IMG_4313-2.jpg0.0 ms202.4 KiB
static-www.shop-pro.jp/assets/images/shared/bg_texture_01.png3600.0 s214.0 KiB
static-www.shop-pro.jp/_astro/bg_texture_01.Cm4SSkrI.png3600.0 s214.0 KiB
shop-pro.jp/example/wp-content/uploads/2026/04/studs_eye.jpg0.0 ms170.6 KiB
static-www.shop-pro.jp/_astro/image_pickup_function_03.TxRK3HB-.jpg3600.0 s212.5 KiB
static-www.shop-pro.jp/_astro/image_pickup_function_02.BZz2VeI9.jpg3600.0 s180.3 KiB
shop-pro.jp/example/wp-content/uploads/2026/04/001.jpg0.0 ms111.3 KiB
shop-pro.jp/example/wp-content/uploads/2026/04/jtb_eyecaych2.jpg0.0 ms104.9 KiB
connect.facebook.net/en_US/fbevents.js1200.0 s96.6 KiB
static-www.shop-pro.jp/_astro/image_first-view_01.DSygPBAr.png3600.0 s102.6 KiB
cdn.activity.smart-bdash.com/tag-manager/bd-rb8n52/btm.js0.0 ms70.6 KiB
static-www.shop-pro.jp/_astro/image_case-title_01.DvQ-Pn3k.jpg3600.0 s68.1 KiB
static-www.shop-pro.jp/_astro/image_pickup_function_01.ZUJqJnIs.jpg3600.0 s59.6 KiB
static-www.shop-pro.jp/_astro/image_campaign_shienkin_01.Clilc48F.png3600.0 s59.1 KiB
static-www.shop-pro.jp/_astro/image_pickup_example_01.CRN73Jzd.jpg3600.0 s52.8 KiB
/signals/config/481563874184726?v=2.9.303&r=stable&domain...1200.0 s46.5 KiB
js-na2.hs-analytics.net/analytics/1776887700000/47416332.js300.0 s42.3 KiB
static-www.shop-pro.jp/_astro/bg_first-view_01.Bo4RxFYo.jpg3600.0 s40.4 KiB
static-www.shop-pro.jp/_astro/popup-banner-consultation.CeX9-mBB.jpg3600.0 s38.7 KiB
static-www.shop-pro.jp/_astro/media-kit.COfs9W4U.css3600.0 s34.1 KiB
static-www.shop-pro.jp/_astro/splide.esm.CtpvrVZh.js3600.0 s32.6 KiB
js-na2.hs-banner.com/v2/47416332/banner.js300.0 s24.6 KiB
b99.yahoo.co.jp/pagead/conversion_async.js0.0 ms23.5 KiB
static-www.shop-pro.jp/_astro/banner_free-consultation_01.BECy0eAh.png3600.0 s24.4 KiB
www.google-analytics.com/analytics.js7200.0 s20.9 KiB
static-www.shop-pro.jp/_astro/index.DXToC2GO.css3600.0 s18.0 KiB
js.adsrvr.org/up_loader.1.1.0.js0.0 ms12.5 KiB
t.afi-b.com/jslib/lpcv.js?cid=72511232&pid=e669V86400.0 s28.2 KiB
static-www.shop-pro.jp/_astro/logo_gmo-brand-security.CguShVOD.png3600.0 s14.1 KiB
s.yimg.jp/images/listing/tool/cv/ytag.js600.0 s11.8 KiB
scripts.clarity.ms/0.8.59-beta/clarity.js86400.0 s26.2 KiB
statics.a8.net/a8sales/a8sales.js0.0 ms9.7 KiB
static-www.shop-pro.jp/_astro/inhouse-icons.1qrmVAEG.woff23600.0 s9.2 KiB
static-www.shop-pro.jp/_astro/logo_gmo-global-sign.C7d6ios2.png3600.0 s7.7 KiB
static-www.shop-pro.jp/_astro/logo_colorme_04.CNPQq0dB.svg3600.0 s7.6 KiB
static-www.shop-pro.jp/_astro/media-kit.CQXpoThI.css3600.0 s7.1 KiB
static-www.shop-pro.jp/_astro/media-kit.DlVFFWdM.css3600.0 s7.0 KiB
cdn.activity.smart-bdash.com/tracking-script/bdash_log.js7200.0 s7.0 KiB
static-www.shop-pro.jp/_astro/logo_gmo-cyber-security.DnPaV0Vq.png3600.0 s6.0 KiB
cache.img.gmo.jp/gmo/header/script.min.js86400.0 s11.4 KiB
static-www.shop-pro.jp/_astro/splide-extension-auto-scroll.esm.Bv3OVTVU.js3600.0 s5.7 KiB
static-www.shop-pro.jp/_astro/logo_gmo-payment-gateway.CsYdqMTv.png3600.0 s5.5 KiB
static-www.shop-pro.jp/_astro/index.BRKXMWAJ.css3600.0 s5.4 KiB
static-www.shop-pro.jp/_astro/features-lower-page.B01AeCWc.css3600.0 s5.4 KiB
static-www.shop-pro.jp/_astro/app-store.8d2v-Ldu.css3600.0 s4.9 KiB
static-www.shop-pro.jp/_astro/hoisted.KRSTUxG5.js3600.0 s4.8 KiB
js-na2.hsadspixel.net/pixels.js600.0 s3.9 KiB
gmo-cybersecurity.com/siteseal/siteseal.js0.0 ms3.4 KiB
static-www.shop-pro.jp/_astro/logo_gmo-epsilon.CQYRbdn9.png3600.0 s3.9 KiB
r.moshimo.com/af/r/maftag.js0.0 ms2.8 KiB
static-www.shop-pro.jp/_astro/icon_chatbot_01.HQ5o16di.svg3600.0 s3.2 KiB
cache.img.gmo.jp/gmo/footer/script.min.js86400.0 s5.9 KiB
analytics.ahrefs.com/analytics.js14400.0 s3.0 KiB
static-www.shop-pro.jp/assets/images/shared/bg_gradation_indigo_01.svg3600.0 s2.5 KiB
static-www.shop-pro.jp/_astro/bg_gradation_orange_01.B3Nfx-DR.svg3600.0 s2.5 KiB
static-www.shop-pro.jp/assets/images/shared/bg_gradation_orange_01.svg3600.0 s2.5 KiB
d.line-scdn.net/n/line_tag/public/release/v1/lt.js404358.0 s10.1 KiB
static-www.shop-pro.jp/_astro/hoisted.l-D3zfkr.js3600.0 s1.9 KiB
static-www.shop-pro.jp/_astro/preload-helper.CmsKOCeN.js3600.0 s1.7 KiB
static-www.shop-pro.jp/_astro/icon_share_01.D2sVwjHD.svg3600.0 s1.6 KiB
static-www.shop-pro.jp/_astro/hoisted._BGJQOLg.js3600.0 s1.5 KiB
static-www.shop-pro.jp/_astro/icon_earth_01.C0E8mqBm.svg3600.0 s1.4 KiB
cache.img.gmo.jp/gmo/security/script.min.js86400.0 s2.7 KiB
js.adsrvr.org/universal_pixel.js0.0 ms957 B
static-www.shop-pro.jp/_astro/icon_phone_01.C7TaKx9p.svg3600.0 s1.2 KiB
/_astro/CorporateLogo.astro_astro_type_script_index_0_lan...3600.0 s1.1 KiB
js-na2.hs-scripts.com/47416332.js0.0 ms853 B
static-www.shop-pro.jp/_astro/icon_x_01.DTHLBMhQ.svg3600.0 s1014 B
www.google-analytics.com/plugins/ua/linkid.js3600.0 s995 B
static-www.shop-pro.jp/_astro/icon_smartphone_01.BQILNVaX.svg3600.0 s970 B
static-www.shop-pro.jp/_astro/hoisted.CBrSBtjX.js3600.0 s923 B
static-www.shop-pro.jp/_astro/bg_line_01.w1zY8oyi.svg3600.0 s858 B
static-www.shop-pro.jp/_astro/icon_chevron-down_01.CMlAuWeZ.svg3600.0 s810 B
seal.brandsecurity.gmo/static/js/siteseal.js14400.0 s899 B
/tr/?id=481563874184726&ev=PageView&dl=https%3A%2F%2Fshop...0.0 ms19 B

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.

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:source label:Top function call valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:405.675 source:map[column:449 line:885 type:source-location url:https://www.googletagmanager.com/gtm.js?id=GTM-PNPH9V urlProvider:network]]]
headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:187.53 source:map[column:376 line:883 type:source-location url:https://www.googletagmanager.com/gtm.js?id=GTM-PNPH9V urlProvider:network]] map[reflowTime:437.775 source:map[column:44 line:881 type:source-location url:https://www.googletagmanager.com/gtm.js?id=GTM-PNPH9V urlProvider:network]] map[reflowTime:11.29 source:map[column:286570 line:0 type:source-location url:https://analytics.tiktok.com/i18n/pixel/static/main.MWE0ZWQ3ZWQwMQ.js urlProvider:network]] map[reflowTime:0.508 source:map[column:86058 line:22 type:source-location url:https://js-na2.hs-analytics.net/analytics/1776887700000/47416332.js urlProvider:network]] map[reflowTime:0.291 source:map[column:2351 line:5 type:source-location url:https://static-www.shop-pro.jp/_astro/splide.esm.CtpvrVZh.js urlProvider:network]] map[reflowTime:3.131 source:map[column:376 line:859 type:source-location url:https://www.googletagmanager.com/gtag/js?id=G-CV529VZLKV&cx=c&gtm=4e64k0 urlProvider:network]] map[reflowTime:0.976 source:map[column:490 line:33 type:source-location url:https://cache.img.gmo.jp/gmo/header/script.min.js urlProvider:network]] map[reflowTime:85.741 source:map[column:31524 line:1 type:source-location url:https://scripts.clarity.ms/0.8.59-beta/clarity.js urlProvider:network]]]

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-SECTION
nodeLabel: 総導入件数22万件以上 サポート満足度94.4% “手が回らない”はAIと人のサポートが解決 安心して始められるECカート お試しは何度でも 無料で始める…
path: 1,HTML,1,BODY,21,DIV,0,MAIN,0,SECTION
selector: body > div.main-content > main > section.first-view
snippet: <section class="first-view" data-astro-cid-wdpvoigt="" style="--bgFirstView: url(https://static-www.shop-pro.jp/_astro/bg_first-view_01.…;">

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

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.

URLResource SizeEst Savings
li#splide02-slide03 > a.card > div.card__image > img li#splide02-slide03 > a.card > div.card__image > img
shop-pro.jp/example/wp-content/uploads/2026/04/tabby_eyecatch.png921.9 KiB907.7 KiB
AI活用で効率UP div.ai-efficiency-banner > a > picture > img
static-www.shop-pro.jp/_astro/image_ai-efficiency_01.D2kv5yRO.jpg572.6 KiB551.7 KiB
div#splide01-track > div#splide01-list > div#splide01-slide01 > img.corporate-logo__image div#splide01-track > div#splide01-list > div#splide01-slide01 > img.corporate-logo__image
static-www.shop-pro.jp/_astro/logo_corporate-all.-rdgkIVE.png358.2 KiB311.5 KiB
人×AIサポート。AIチャットボット・設定代行・AIコネクター・制作代行・電話サポート・ECアドバイザー。 div.c-section__container > div.c-section__body > div.feature-support__image > img
static-www.shop-pro.jp/_astro/image_feature-support_01.Dsqx544a.jpg363.1 KiB276.9 KiB
国内カート初 AIコネクター(MCP) 提供開始! ul#splide03-list > li#splide03-slide02 > a.pickup-banner-list > img
static-www.shop-pro.jp/_astro/image_pickup_function_03.TxRK3HB-.jpg211.8 KiB208.4 KiB
li#splide02-slide01 > a.card > div.card__image > img li#splide02-slide01 > a.card > div.card__image > img
shop-pro.jp/example/wp-content/uploads/2026/04/IMG_4313-2.jpg202.0 KiB188.3 KiB
国内カート初 Amazon Pay Buy Now提供開始! ul#splide03-list > li#splide03-slide03 > a.pickup-banner-list > img
static-www.shop-pro.jp/_astro/image_pickup_function_02.BZz2VeI9.jpg179.6 KiB176.2 KiB
li#splide02-slide02 > a.card > div.card__image > img li#splide02-slide02 > a.card > div.card__image > img
shop-pro.jp/example/wp-content/uploads/2026/04/001.jpg111.0 KiB99.2 KiB
li#splide02-slide04 > a.card > div.card__image > img li#splide02-slide04 > a.card > div.card__image > img
shop-pro.jp/example/wp-content/uploads/2026/04/jtb_eyecaych2.jpg104.6 KiB91.0 KiB
div.first-view__container > div.first-view__image > picture > img div.first-view__container > div.first-view__image > picture > img
static-www.shop-pro.jp/_astro/image_first-view_01.DSygPBAr.png101.9 KiB81.8 KiB
無料でできる海外販売代行 ul#splide03-list > li#splide03-slide04 > a.pickup-banner-list > img
static-www.shop-pro.jp/_astro/image_pickup_function_01.ZUJqJnIs.jpg59.0 KiB56.0 KiB
毎月先着5ショップ限定 カート利用料金1年分0円 ul#splide03-list > li#splide03-slide01 > a.pickup-banner-list > img
static-www.shop-pro.jp/_astro/image_campaign_shienkin_01.Clilc48F.png58.5 KiB55.5 KiB
div.c-section__title > div.section-title > div.section-title__image-unit > img.section-title__image div.c-section__title > div.section-title > div.section-title__image-unit > img.section-title__image
static-www.shop-pro.jp/_astro/image_case-title_01.DvQ-Pn3k.jpg67.5 KiB50.6 KiB
新規開設のご相談 div#js-popup-banner > div.popup-banner__container > a.popup-banner__link > img
static-www.shop-pro.jp/_astro/popup-banner-consultation.CeX9-mBB.jpg38.1 KiB33.1 KiB
GMOブランドセキュリティ div.c-section__footer > div.gmo-brands > div.gmo-brands__img-container > img.gmo-brands__img
static-www.shop-pro.jp/_astro/logo_gmo-brand-security.CguShVOD.png13.5 KiB13.0 KiB
GMOグローバルサイン div.c-section__footer > div.gmo-brands > div.gmo-brands__img-container > img.gmo-brands__img
static-www.shop-pro.jp/_astro/logo_gmo-global-sign.C7d6ios2.png7.1 KiB6.8 KiB
GMOサイバーセキュリティ div.c-section__footer > div.gmo-brands > div.gmo-brands__img-container > img.gmo-brands__img
static-www.shop-pro.jp/_astro/logo_gmo-cyber-security.DnPaV0Vq.png5.5 KiB5.3 KiB
GMOペイメントゲートウェイ div.c-section__footer > div.gmo-brands > div.gmo-brands__img-container > img.gmo-brands__img
static-www.shop-pro.jp/_astro/logo_gmo-payment-gateway.CsYdqMTv.png5.0 KiB4.8 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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

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.

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: 90 ms 73.2 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

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

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.

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.

CategoryTime Spent
Script Evaluation1.7 s
Style & Layout1.1 s
Other596 ms
Script Parsing & Compilation239 ms
Rendering122 ms
Garbage Collection46 ms
Parse HTML & CSS44 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.4 KiB
URLTransfer SizeEst Savings
/css2?family=Roboto:wght@400;500;700&family=Noto+Sans+JP:...61.0 KiB6.4 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
ul.__pepabo-footer__gmo-group-security-seal > li.__pepabo-footer__gmo-group-security-seal-item > div#ss_gmo_globalsign_secured_site_seal > img#ss_gmo_globalsign_img ul.__pepabo-footer__gmo-group-security-seal > li.__pepabo-footer__gmo-group-security-seal-item > div#ss_gmo_globalsign_secured_site_seal > img#ss_gmo_globalsign_img
/gss/one/image?p1=shop-pro.jp&p2=seal_100-50_ja.png&p3=gs...

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

Layout shift culprits
Document request latency
Optimize DOM size
LCP breakdown
Modern HTTP
Optimize viewport for mobile
Minify JavaScript
User Timing marks and measures 26 user timings
Avoid long main-thread tasks 10 long tasks found
Avoid non-composited animations 5 animated elements found
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 240 ms
Server Backend Latencies 300 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Avoid multiple page redirects
Initial server response time was short Root document took 510 ms
Avoid large layout shifts 4 layout shifts found
INP breakdown
91

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.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
人気 No.1 div.plan-list__item > div.plan-card > div.plan-card__header > div.plan-card__badge
おすすめ div.plan-list__item > div.plan-card > div.plan-card__header > div.plan-card__badge
長期契約で月額費用がお得に! dl.plan-card__emphasis > div > dd.plan-fee > p.plan-notice
FAQ div.c-section__title > div.section-title > div.section-title__text-unit > span.section-title__sub
AIに聞いてみる div.miibo-toast > button#chat-button > span.miibo-toast__content > span.miibo-toast__cta

These are opportunities to improve the legibility of your content.

Names and labels

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.mega-menu-header > ul.mega-menu-header__list > li > a div.mega-menu-header > ul.mega-menu-header__list > li > a
div.mega-menu-header > ul.mega-menu-header__list > li > a div.mega-menu-header > ul.mega-menu-header__list > li > a
div.mega-menu-header > ul.mega-menu-header__list > li > a div.mega-menu-header > ul.mega-menu-header__list > li > a
div.mega-menu-header > ul.mega-menu-header__list > li > a div.mega-menu-header > ul.mega-menu-header__list > li > a

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
バナーを閉じる main > div#js-popup-banner > div.popup-banner__container > button#js-popup-close

These items highlight common accessibility best practices.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
無料診断 div.gmoGroupHeader > div.gmoGroupHeader_secCont > div.gmoGroupHeader_sec > a
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-*]` attributes match their roles
`[aria-hidden="true"]` is not present on the document `<body>`
`[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
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
Buttons have an accessible name
Image elements have `[alt]` attributes
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
ARIA attributes are used as specified for the element's role
`[aria-hidden="true"]` elements do not contain focusable descendents
Elements use only permitted ARIA attributes
`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Definition list items are wrapped in `<dl>` elements
Document has a `<title>` element
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
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.
Heading elements appear in a sequentially-descending order
Document has a main landmark.
Deprecated ARIA roles were not used
Uses ARIA roles only on compatible elements
Identical links have the same purpose.
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.
`[accesskey]` values are unique
`button`, `link`, and `menuitem` elements have accessible names
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
ARIA input fields have accessible names
ARIA `meter` elements have accessible names
ARIA `progressbar` elements have accessible names
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
The page contains a heading, skip link, or landmark region
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.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
`[lang]` attributes have a valid value
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Tables have different content in the summary attribute and `<caption>`.
All heading elements contain content.
Image elements do not have `[alt]` attributes that are redundant text.
77

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 / WarningSource
AttributionReporting

Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit

Why this matters

Performance issues directly impact user engagement and conversion rates.

SourceDescription
Uncaught SyntaxError: Unexpected identifier 'content'
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 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 DOM-based XSS with Trusted Types
Detected JavaScript libraries
Page has valid source maps
Redirects HTTP traffic to HTTPS
Mitigate clickjacking with XFO or CSP
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
Image elements have `[alt]` attributes
Document has a valid `hreflang`
Document has a valid `rel=canonical`
robots.txt is valid

Send Feedback