Skip to content
Audit Complete

Results for https://jugem.jp

Visit site
JP · JPY (¥) · Estimated Applicable regulations: APPI Dev cost: ¥8,000/hr How jurisdiction is detected
Spain Spain · Madrid Completed: Apr 22, 2026 21:56 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)
D68

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.

Well-optimized for search — your content is discoverable.

Solid infrastructure — fast server responses across the board.

Several regulatory requirements are not yet met.

Good content signals with minor gaps.

Reasonable footprint with room for optimization.

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

Font Awesome · 505 peers
You 68
·
Avg 73
At average
0 50 100
Better than 2% of Font Awesome sites See full Font Awesome benchmark →
HSTS · 2189 peers
You 68
·
Avg 74
-6 below average
0 50 100
Better than 2% of HSTS sites See full HSTS 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

Cookie 'XSRF-TOKEN' is missing the Secure flag

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

Security › Cookie Security
3

Cookie 'laravel_session' is missing the Secure flag

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

Security › Cookie Security
4

No Content-Security-Policy header found

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

Security › Content Security Policy
5

No <main> landmark found

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

Accessibility › Landmark Structure
View fix priority matrix

Fix Priority Matrix

5 findings

Quick Wins

4

High impact, low effort — start here.

Strategic

1

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%2Fjugem.jp)](https://beavercheck.com/results/e842452d-0146-4876-9143-08e8b07de749)
<a href="https://beavercheck.com/results/e842452d-0146-4876-9143-08e8b07de749"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fjugem.jp" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fjugem.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. The 4 security gaps leave your users exposed — modern browsers increasingly warn visitors about insecure sites. Addressing the critical issues below would have the most immediate impact on your user trust.

4 security gaps detected — browsers may warn visitors about your site.
1 accessibility issue excludes users who rely on assistive technology.
C
Could reach Estimate based on resolving critical issues

Conversion Barriers

2 critical 7 warning

9 barrier(s) likely increasing bounce by ~32%.

Speed (2)

Page takes 7.4s to load

+12% bounce

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

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

Page feels frozen for 1.2s

+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 (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

2 broken link(s) on the page

+3% 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

¥28,000 investment → ¥579,931/month returns + JPY 100,000,000 risk avoided

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

Investment

¥28,000

4h · 5 findings

Monthly returns

¥579,931 /mo

~¥6,959,175 / year

  • Conversions recovered ¥579,831
  • Bandwidth savings ¥101

Regulatory risk avoided

JPY 100,000,000

if kept compliant

  • APPI JPY 100,000,000

Payback period

0 12mo 24mo

¥16,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

¥28,000

3.5 developer hours at ¥8000/hr

Based on Japan rates (¥8000/hr)

Quick wins
¥16,000 4 fixes in ~120 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,434 / month at risk

~¥100,001,209 / year if left unfixed

Compliance Risk

¥100,000,000

APPI
  • No privacy policy link detected
    APPI: JPY 100,000 – JPY 100,000,000
  • 3 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

¥101 /mo

8435.9 MB/mo × 11.940 JPY/GB

  • Optimize transfer: save ~844 KB per page load
    Saves ¥101/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.

43
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
69
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.
92
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.

2.46 s

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

7.40 s

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

1.19 s

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

0.030

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

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

17.91 s

Detailed Report

Audit breakdown by category with detailed findings.

43

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
imaging.jugem.jp/images/portal/index/top_bg.jpg?201603100.0 ms394.4 KiB
fam.adingo.jp/bid-strap/jugem/pb.js600.0 s207.3 KiB
imaging.jugem.jp/images/portal/index/top_device.png0.0 ms135.1 KiB
imaging.jugem.jp/images/portal/index/recommend_fashionable.png0.0 ms126.9 KiB
imaging.jugem.jp/images/portal/index/intro_propose.png0.0 ms121.1 KiB
imaging.jugem.jp/images/portal/index/bottom_bg.jpg0.0 ms97.8 KiB
imaging.jugem.jp/images/portal/index/intro_question_smp.png0.0 ms97.2 KiB
imaging.jugem.jp/images/portal/index/recommend_basic.png0.0 ms88.4 KiB
c.amazon-adsystem.com/aax2/apstag.js3600.0 s90.9 KiB
imaging.jugem.jp/images/portal/index/intro_question_pc.png0.0 ms70.8 KiB
imaging.jugem.jp/images/portal/index/recommend_pan.png0.0 ms64.8 KiB
imaging.jugem.jp/images/portal/index/intro_answer_pc.png0.0 ms61.9 KiB
imaging.jugem.jp/images/portal/index/intro_headline_pc.png0.0 ms60.9 KiB
/pagead/managed/js/activeview/current/ufs_web_display.js3600.0 s73.1 KiB
imaging.jugem.jp/images/portal/index/recommend_maisonclip.png0.0 ms50.5 KiB
jugem.jp/css/index.css0.0 ms36.8 KiB
imaging.jugem.jp/images/portal/index/intro_headline_smp.png0.0 ms34.2 KiB
imaging.jugem.jp/images/portal/index/function_analytics.png0.0 ms28.2 KiB
imaging.jugem.jp/images/portal/index/function_upload.png0.0 ms20.7 KiB
static.criteo.net/js/ld/publishertag.js86400.0 s47.6 KiB
pdn.adingo.jp/p.js600.0 s20.7 KiB
imaging.jugem.jp/images/portal/index/function_domain.png0.0 ms18.1 KiB
imaging.jugem.jp/images/portal/index/intro_answer_decorate.png0.0 ms16.9 KiB
imaging.jugem.jp/images/portal/index/free_device.png0.0 ms16.7 KiB
www.google-analytics.com/analytics.js7200.0 s20.9 KiB
imaging.jugem.jp/images/portal/common/logo_pc.png0.0 ms15.6 KiB
imaging.jugem.jp/images/portal/index/free_template.png0.0 ms15.5 KiB
imaging.jugem.jp/images/portal/index/intro_question_decorate.png0.0 ms13.4 KiB
imaging.jugem.jp/images/portal/common/logo_smp.png0.0 ms13.1 KiB
imaging.jugem.jp/images/portal/index/function_password.png0.0 ms12.1 KiB
imaging.jugem.jp/images/portal/index/free_sns.png0.0 ms11.2 KiB
j.zucks.net.zimg.jp/j?f=71567796.0 s8.0 KiB
imaging.jugem.jp/images/portal/index/intro_propose_underline.png0.0 ms5.8 KiB
use.fontawesome.com/c1576d6d27.js1800.0 s4.1 KiB
cdn.nidan.d2c.ne.jp/1.0/index.js86400.0 s3.6 KiB
use.fontawesome.com/c1576d6d27.css1800.0 s715 B
linkback.contentsfeed.com/src/lb4pbfluct.min.js0.0 ms318 B
/id/nidan/pre?callback=d2c.nidan.ns&origin=https%3A%2F%2F...7200.0 s159 B
image8.pubmatic.com/AdServer/ImgSync?p=1608360.0 ms69 B
/pagead/managed/js/activeview/current/ufs_web_display.js3600.0 s0 B
/pagead/managed/js/activeview/current/ufs_web_display.js3600.0 s0 B
static.criteo.net/js/ld/publishertag.js86400.0 s0 B
pdn.adingo.jp/p.js600.0 s0 B
pdn.adingo.jp/p.js600.0 s0 B
pdn.adingo.jp/p.js600.0 s0 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.

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-DIV
nodeLabel: Advertisement
path: 1,HTML,1,BODY,2,DIV,0,SECTION,0,DIV
selector: body > div.wrapper > section.top > div.top-bg
snippet: <div class="top-bg">

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.

URLTransfer SizeDuration
jugem.jp/css/index.css36.8 KiB894 ms
use.fontawesome.com/c1576d6d27.js4.1 KiB806 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.

URLResource SizeEst Savings
PCもスマホも広告非表示 section.intro > div.intro-inner > div.intro-propose > img
imaging.jugem.jp/images/portal/index/intro_propose.png120.7 KiB69.4 KiB
「自分の書いた記事の間に、広告が...」「広告を間違えて押してしまった...」 section.intro > div.intro-inner > div.intro-question > img.intro-question-smp
imaging.jugem.jp/images/portal/index/intro_question_smp.png96.7 KiB65.5 KiB
section.intro > div.intro-inner > div.intro-answer > img.intro-answer-smp
imaging.jugem.jp/images/portal/index/intro_answer_pc.png61.5 KiB43.2 KiB
JUGEMプラス 月額330円(税込) section.intro > div.intro-inner > div.intro-headline > img.intro-headline-smp
imaging.jugem.jp/images/portal/index/intro_headline_smp.png33.8 KiB22.8 KiB
JUGEMブログ div.header-contents > h1 > a > img.logo-smp
imaging.jugem.jp/images/portal/common/logo_smp.png12.6 KiB11.1 KiB
div.function-inner > ul > li > img
imaging.jugem.jp/images/portal/index/function_analytics.png27.8 KiB10.0 KiB
div.function-inner > ul > li > img
imaging.jugem.jp/images/portal/index/function_upload.png20.4 KiB4.8 KiB
div.function-inner > ul > li > img
imaging.jugem.jp/images/portal/index/function_domain.png17.7 KiB4.2 KiB
JUGEMプラス h4 > ul > li.intro-propose-bottom > span
imaging.jugem.jp/images/portal/index/intro_propose_underline.png5.5 KiB4.1 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 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 Evaluation3.0 s
Other784 ms
Script Parsing & Compilation360 ms
Style & Layout256 ms
Garbage Collection61 ms
Parse HTML & CSS60 ms
Rendering38 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 10.8 KiB
URLTransfer SizeEst Savings
jugem.jp/css/index.css36.8 KiB10.8 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 17.5 KiB
URLTransfer SizeEst Savings
jugem.jp/css/index.css36.5 KiB17.5 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
「自分の書いた記事の間に、広告が...」「広告を間違えて押してしまった...」 section.intro > div.intro-inner > div.intro-question > img.intro-question-smp
imaging.jugem.jp/images/portal/index/intro_question_smp.png
PCもスマホも広告非表示 section.intro > div.intro-inner > div.intro-propose > img
imaging.jugem.jp/images/portal/index/intro_propose.png
section.intro > div.intro-inner > div.intro-answer > img.intro-answer-smp
imaging.jugem.jp/images/portal/index/intro_answer_pc.png
JUGEMプラス 月額330円(税込) section.intro > div.intro-inner > div.intro-headline > img.intro-headline-smp
imaging.jugem.jp/images/portal/index/intro_headline_smp.png
div.function-inner > ul > li > img
imaging.jugem.jp/images/portal/index/function_analytics.png
div.function-inner > ul > li > img
imaging.jugem.jp/images/portal/index/function_password.png
div.function-inner > ul > li > img
imaging.jugem.jp/images/portal/index/function_upload.png
div.function-inner > ul > li > img
imaging.jugem.jp/images/portal/index/function_domain.png
div.free-inner > ul > li > img
imaging.jugem.jp/images/portal/index/free_device.png
div.free-inner > ul > li > img
imaging.jugem.jp/images/portal/index/free_template.png
div.free-inner > ul > li > img
imaging.jugem.jp/images/portal/index/free_sns.png
JUGEMブログ div.header-contents > h1 > a > img.logo-smp
imaging.jugem.jp/images/portal/common/logo_smp.png

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
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 17 long tasks found
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 260 ms
Server Backend Latencies 740 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 290 ms
Avoid large layout shifts 1 layout shift found
INP breakdown
Avoid non-composited animations
69

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
無料登録 div.header-nav > ul.header-nav-inner > li.header-nav__signup > a
まずは無料ではじめてみる div.top-register-inner > ul > li.register-button > a
無料 section.free > div.free-inner > h3 > strong
PC・スマホで、見られる・書ける。 ul > li > dl > dd
お気に入りがきっと、見つかるはず。 ul > li > dl > dd
連携して、ブログの可能性を広げませんか。 ul > li > dl > dd
スマホ・PC別、記事別、時間帯別でアクセス数を解析。どれだけ見られているのかチェックできます。 ul > li > dl > dd
ブログ全体や、記事別にも鍵がかけられ、プライベートで共有したい記事も安心して書けます。 ul > li > dl > dd
写真を一括でアップロード、容量無制限だから、お気に入りの写真は全て載せられます。 ul > li > dl > dd
世界に1つだけ!あなたの取得したドメインを使って、ブログのURLにも、こだわりを出せます。 ul > li > dl > dd
まずは無料ではじめてみる div.bottom-register > ul > li.bottom-register-free > a
Copyright © 2003-2026 株式会社メディアーノ footer.footer > div.footer-inner > div.footer-copyright > p

These are opportunities to improve the legibility of your content.

Internationalization and localization

If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html.fa-events-icons-ready html.fa-events-icons-ready

These are opportunities to improve the interpretation of your content by users in different locales.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.free-inner > ul > li > img
div.free-inner > ul > li > img
div.free-inner > ul > li > img
section.intro > div.intro-inner > div.intro-answer > img.intro-answer-smp
div.function-inner > ul > li > img
div.function-inner > ul > li > img
div.function-inner > ul > li > img
div.function-inner > ul > li > img

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
JUGEMブログ div.header-inner > div.header-contents > h1 > 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

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

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
利用規約 nav.footer-nav > ul > li > a
プライバシーポリシー nav.footer-nav > ul > li > a
サポート nav.footer-nav > ul > li > a
サイトマップ nav.footer-nav > ul > li > a

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.fa-events-icons-ready html.fa-events-icons-ready

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-*]` attributes match their roles
`[aria-hidden="true"]` is not present on the document `<body>`
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
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
`<frame>` or `<iframe>` elements have a title
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
Heading elements appear in a sequentially-descending order
`[accesskey]` values are unique
`button`, `link`, and `menuitem` elements have accessible names
Deprecated ARIA roles were not used
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
`[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
Buttons have an accessible name
The page contains a heading, skip link, or landmark region
ARIA IDs are unique
No form fields have multiple labels
`<html>` element has a valid value for its `[lang]` attribute
`<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.
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
`<video>` elements contain a `<track>` element with `[kind="captions"]`
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.
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
Topics

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
Access to fetch at 'https://ad.ad-stir.com/prebid' from origin 'https://jugem.jp' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
Access to fetch at 'https://ad.ad-stir.com/prebid' from origin 'https://jugem.jp' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
Access to fetch at 'https://ad.ad-stir.com/prebid' from origin 'https://jugem.jp' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
Access to fetch at 'https://ad.ad-stir.com/prebid' from origin 'https://jugem.jp' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
Access to fetch at 'https://ad.ad-stir.com/prebid' from origin 'https://jugem.jp' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
Access to fetch at 'https://ad.ad-stir.com/prebid' from origin 'https://jugem.jp' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
Access to fetch at 'https://aladdin.genieesspv.jp/yie/ld/api/ad_call/v2?zoneid=1585699&cb=64719911455&charset=UTF-8&loc=https%3A%2F%2Fjugem.jp%2F&ct0=undefined&referer=undefined&topframe=1&cur=JPY&requestid=a597ed81-6280-428e-8a08-6341067c75c6&ua=Mozilla%2F5.0%20(Linux%3B%20Android%2011%3B%20moto%20g%20power%20(2022))%20AppleWebKit%2F537.36%20(KHTML%2C%20like%20Gecko)%20Chrome%2F147.0.0.0%20Mobile%20Safari%2F537.36&tpaf=1&cks=1&schain=%7B%22ver%22%3A%221.0%22%2C%22complete%22%3A1%2C%22nodes%22%3A%5B%7B%22asi%22%3A%22adingo.jp%22%2C%22sid%22%3A%223248%22%2C%22hp%22%3A1%7D%5D%7D&gpid=%2F66065524%2Fjugem_sp_top%2Fjugem_sp_top_body_1&fl_pr=2&title=JUGEM%25E3%2583%2596%25E3%2583%25AD%25E3%2582%25B0%2520%257C%2520%25E8%2587%25AA%25E5%2588%2586%25E3%2581%25A0%25E3%2581%2591%25E3%2581%25AE%25E3%2581%2593%25E3%2581%25A0%25E3%2582%258F%25E3%2582%258A%25E3%2583%2596%25E3%2583%25AD%25E3%2582%25B0%25E3%2582%2592%25E3%2581%25AF%25E3%2581%2598%25E3%2582%2581%25E3%2582%2588%25E3%2581%2586&sw=412&sh=823&ucmbl=%3F0' from origin 'https://jugem.jp' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
Access to fetch at 'https://aladdin.genieesspv.jp/yie/ld/api/ad_call/v2?zoneid=1585700&cb=82043314652&charset=UTF-8&loc=https%3A%2F%2Fjugem.jp%2F&ct0=undefined&referer=undefined&topframe=1&cur=JPY&requestid=20650d2e-afe3-4fc6-ad5a-8866ff255a97&ua=Mozilla%2F5.0%20(Linux%3B%20Android%2011%3B%20moto%20g%20power%20(2022))%20AppleWebKit%2F537.36%20(KHTML%2C%20like%20Gecko)%20Chrome%2F147.0.0.0%20Mobile%20Safari%2F537.36&tpaf=1&cks=1&schain=%7B%22ver%22%3A%221.0%22%2C%22complete%22%3A1%2C%22nodes%22%3A%5B%7B%22asi%22%3A%22adingo.jp%22%2C%22sid%22%3A%223248%22%2C%22hp%22%3A1%7D%5D%7D&gpid=%2F66065524%2Fjugem_sp_top%2Fjugem_sp_top_body_2&fl_pr=2&title=JUGEM%25E3%2583%2596%25E3%2583%25AD%25E3%2582%25B0%2520%257C%2520%25E8%2587%25AA%25E5%2588%2586%25E3%2581%25A0%25E3%2581%2591%25E3%2581%25AE%25E3%2581%2593%25E3%2581%25A0%25E3%2582%258F%25E3%2582%258A%25E3%2583%2596%25E3%2583%25AD%25E3%2582%25B0%25E3%2582%2592%25E3%2581%25AF%25E3%2581%2598%25E3%2582%2581%25E3%2582%2588%25E3%2581%2586&sw=412&sh=823&ucmbl=%3F0' from origin 'https://jugem.jp' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
Access to fetch at 'https://aladdin.genieesspv.jp/yie/ld/api/ad_call/v2?zoneid=1585701&cb=25468413395&charset=UTF-8&loc=https%3A%2F%2Fjugem.jp%2F&ct0=undefined&referer=undefined&topframe=1&cur=JPY&requestid=064f8884-22c9-4b97-b1dc-68b1be40f46c&ua=Mozilla%2F5.0%20(Linux%3B%20Android%2011%3B%20moto%20g%20power%20(2022))%20AppleWebKit%2F537.36%20(KHTML%2C%20like%20Gecko)%20Chrome%2F147.0.0.0%20Mobile%20Safari%2F537.36&tpaf=1&cks=1&schain=%7B%22ver%22%3A%221.0%22%2C%22complete%22%3A1%2C%22nodes%22%3A%5B%7B%22asi%22%3A%22adingo.jp%22%2C%22sid%22%3A%223248%22%2C%22hp%22%3A1%7D%5D%7D&gpid=%2F66065524%2Fjugem_sp_top%2Fjugem_sp_top_body_3&fl_pr=2&title=JUGEM%25E3%2583%2596%25E3%2583%25AD%25E3%2582%25B0%2520%257C%2520%25E8%2587%25AA%25E5%2588%2586%25E3%2581%25A0%25E3%2581%2591%25E3%2581%25AE%25E3%2581%2593%25E3%2581%25A0%25E3%2582%258F%25E3%2582%258A%25E3%2583%2596%25E3%2583%25AD%25E3%2582%25B0%25E3%2582%2592%25E3%2581%25AF%25E3%2581%2598%25E3%2582%2581%25E3%2582%2588%25E3%2581%2586&sw=412&sh=823&ucmbl=%3F0' from origin 'https://jugem.jp' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
Access to fetch at 'https://aladdin.genieesspv.jp/yie/ld/api/ad_call/v2?zoneid=1585702&cb=87846712701&charset=UTF-8&loc=https%3A%2F%2Fjugem.jp%2F&ct0=undefined&referer=undefined&topframe=1&cur=JPY&requestid=9306ea94-76bf-4388-a581-7698380693c8&ua=Mozilla%2F5.0%20(Linux%3B%20Android%2011%3B%20moto%20g%20power%20(2022))%20AppleWebKit%2F537.36%20(KHTML%2C%20like%20Gecko)%20Chrome%2F147.0.0.0%20Mobile%20Safari%2F537.36&tpaf=1&cks=1&schain=%7B%22ver%22%3A%221.0%22%2C%22complete%22%3A1%2C%22nodes%22%3A%5B%7B%22asi%22%3A%22adingo.jp%22%2C%22sid%22%3A%223248%22%2C%22hp%22%3A1%7D%5D%7D&gpid=%2F66065524%2Fjugem_sp_top%2Fjugem_sp_top_body_4&fl_pr=2&title=JUGEM%25E3%2583%2596%25E3%2583%25AD%25E3%2582%25B0%2520%257C%2520%25E8%2587%25AA%25E5%2588%2586%25E3%2581%25A0%25E3%2581%2591%25E3%2581%25AE%25E3%2581%2593%25E3%2581%25A0%25E3%2582%258F%25E3%2582%258A%25E3%2583%2596%25E3%2583%25AD%25E3%2582%25B0%25E3%2582%2592%25E3%2581%25AF%25E3%2581%2598%25E3%2582%2581%25E3%2582%2588%25E3%2581%2586&sw=412&sh=823&ucmbl=%3F0' from origin 'https://jugem.jp' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
Access to fetch at 'https://aladdin.genieesspv.jp/yie/ld/api/ad_call/v2?zoneid=1585703&cb=50739985463&charset=UTF-8&loc=https%3A%2F%2Fjugem.jp%2F&ct0=undefined&referer=undefined&topframe=1&cur=JPY&requestid=eaf944c8-a4a7-4e38-81d0-3364f6323973&ua=Mozilla%2F5.0%20(Linux%3B%20Android%2011%3B%20moto%20g%20power%20(2022))%20AppleWebKit%2F537.36%20(KHTML%2C%20like%20Gecko)%20Chrome%2F147.0.0.0%20Mobile%20Safari%2F537.36&tpaf=1&cks=1&schain=%7B%22ver%22%3A%221.0%22%2C%22complete%22%3A1%2C%22nodes%22%3A%5B%7B%22asi%22%3A%22adingo.jp%22%2C%22sid%22%3A%223248%22%2C%22hp%22%3A1%7D%5D%7D&gpid=%2F66065524%2Fjugem_sp_top%2Fjugem_sp_top_footer&fl_pr=2&title=JUGEM%25E3%2583%2596%25E3%2583%25AD%25E3%2582%25B0%2520%257C%2520%25E8%2587%25AA%25E5%2588%2586%25E3%2581%25A0%25E3%2581%2591%25E3%2581%25AE%25E3%2581%2593%25E3%2581%25A0%25E3%2582%258F%25E3%2582%258A%25E3%2583%2596%25E3%2583%25AD%25E3%2582%25B0%25E3%2582%2592%25E3%2581%25AF%25E3%2581%2598%25E3%2582%2581%25E3%2582%2588%25E3%2581%2586&sw=412&sh=823&ucmbl=%3F0' from origin 'https://jugem.jp' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
Access to fetch at 'https://aladdin.genieesspv.jp/yie/ld/api/ad_call/v2?zoneid=1585704&cb=87367747127&charset=UTF-8&loc=https%3A%2F%2Fjugem.jp%2F&ct0=undefined&referer=undefined&topframe=1&cur=JPY&requestid=aff2ffe4-a6a4-4723-9922-076bbddb3951&ua=Mozilla%2F5.0%20(Linux%3B%20Android%2011%3B%20moto%20g%20power%20(2022))%20AppleWebKit%2F537.36%20(KHTML%2C%20like%20Gecko)%20Chrome%2F147.0.0.0%20Mobile%20Safari%2F537.36&tpaf=1&cks=1&schain=%7B%22ver%22%3A%221.0%22%2C%22complete%22%3A1%2C%22nodes%22%3A%5B%7B%22asi%22%3A%22adingo.jp%22%2C%22sid%22%3A%223248%22%2C%22hp%22%3A1%7D%5D%7D&gpid=%2F66065524%2Fjugem_sp_top%2Fjugem_sp_top_header&fl_pr=2&title=JUGEM%25E3%2583%2596%25E3%2583%25AD%25E3%2582%25B0%2520%257C%2520%25E8%2587%25AA%25E5%2588%2586%25E3%2581%25A0%25E3%2581%2591%25E3%2581%25AE%25E3%2581%2593%25E3%2581%25A0%25E3%2582%258F%25E3%2582%258A%25E3%2583%2596%25E3%2583%25AD%25E3%2582%25B0%25E3%2582%2592%25E3%2581%25AF%25E3%2581%2598%25E3%2582%2581%25E3%2582%2588%25E3%2581%2586&sw=412&sh=823&ucmbl=%3F0' from origin 'https://jugem.jp' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
Access to fetch at 'https://hb.adingo.jp/prebid/?dfpUnitCode=undefined&tagId=41207%3A1000281355&groupId=1000176925' from origin 'https://jugem.jp' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource.
Access to fetch at 'https://hb.adingo.jp/prebid/?dfpUnitCode=undefined&tagId=41207%3A1000281356&groupId=1000176925' from origin 'https://jugem.jp' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource.
Access to fetch at 'https://hb.adingo.jp/prebid/?dfpUnitCode=undefined&tagId=41207%3A1000281357&groupId=1000176925' from origin 'https://jugem.jp' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource.
Access to fetch at 'https://hb.adingo.jp/prebid/?dfpUnitCode=undefined&tagId=41207%3A1000281360&groupId=1000176925' from origin 'https://jugem.jp' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource.
Access to fetch at 'https://hb.adingo.jp/prebid/?dfpUnitCode=undefined&tagId=41207%3A1000281375&groupId=1000176925' from origin 'https://jugem.jp' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource.
Access to fetch at 'https://hb.adingo.jp/prebid/?dfpUnitCode=undefined&tagId=41207%3A1000281377&groupId=1000176925' from origin 'https://jugem.jp' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource.
Access to fetch at 'https://sp.gmossp-sp.jp/hb/prebid/query.ad?tid=ud26aa5d7-c8b7-442c-b396-24c066f517d0&bid=67d006de-b41c-4b75-bdab-31ca619cb9e6&ver=11.6.0&sid=g946783&url=https%3A%2F%2Fjugem.jp%2F&meta_url=https%3A%2F%2Fjugem.jp%2F&cur=JPY&' from origin 'https://jugem.jp' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
Failed to load resource: net::ERR_FAILED
Failed to load resource: net::ERR_FAILED
Failed to load resource: net::ERR_FAILED
Failed to load resource: net::ERR_FAILED
Failed to load resource: net::ERR_FAILED
Failed to load resource: net::ERR_FAILED
Failed to load resource: net::ERR_FAILED
Failed to load resource: net::ERR_FAILED
Failed to load resource: net::ERR_FAILED
Failed to load resource: net::ERR_FAILED
Failed to load resource: net::ERR_FAILED
Failed to load resource: net::ERR_FAILED
Failed to load resource: net::ERR_FAILED
Failed to load resource: net::ERR_FAILED
Failed to load resource: net::ERR_FAILED
Failed to load resource: net::ERR_FAILED
Failed to load resource: net::ERR_FAILED
Failed to load resource: net::ERR_FAILED
Failed to load resource: net::ERR_FAILED
Uncaught Error: Unauthorized
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 clickjacking with XFO or CSP
Mitigate DOM-based XSS with Trusted Types
Page has valid source maps
Redirects HTTP traffic to HTTPS
Detected JavaScript libraries
92

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.

Content Best Practices

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.free-inner > ul > li > img
div.free-inner > ul > li > img
div.free-inner > ul > li > img
section.intro > div.intro-inner > div.intro-answer > img.intro-answer-smp
div.function-inner > ul > li > img
div.function-inner > ul > li > img
div.function-inner > ul > li > img
div.function-inner > ul > li > img

Format your HTML in a way that enables crawlers to better understand your app’s content.

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
Document has a valid `hreflang`
Document has a valid `rel=canonical`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

78
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
58
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.
92
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.

1.69 s

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

2.39 s

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

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

1.95 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.73 s

Detailed Report

Audit breakdown by category with detailed findings.

78

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
imaging.jugem.jp/images/portal/index/top_bg.jpg?201603100.0 ms394.4 KiB
fam.adingo.jp/bid-strap/jugem/pb.js600.0 s207.3 KiB
imaging.jugem.jp/images/portal/index/top_device.png0.0 ms135.1 KiB
imaging.jugem.jp/images/portal/index/recommend_fashionable.png0.0 ms126.9 KiB
imaging.jugem.jp/images/portal/index/intro_propose.png0.0 ms121.1 KiB
imaging.jugem.jp/images/portal/index/bottom_bg.jpg0.0 ms97.8 KiB
imaging.jugem.jp/images/portal/index/intro_question_smp.png0.0 ms97.2 KiB
imaging.jugem.jp/images/portal/index/recommend_basic.png0.0 ms88.4 KiB
c.amazon-adsystem.com/aax2/apstag.js3600.0 s90.9 KiB
imaging.jugem.jp/images/portal/index/intro_question_pc.png0.0 ms70.8 KiB
imaging.jugem.jp/images/portal/index/recommend_pan.png0.0 ms64.8 KiB
imaging.jugem.jp/images/portal/index/intro_answer_pc.png0.0 ms61.9 KiB
imaging.jugem.jp/images/portal/index/intro_headline_pc.png0.0 ms60.9 KiB
imaging.jugem.jp/images/portal/index/recommend_maisonclip.png0.0 ms50.5 KiB
jugem.jp/css/index.css0.0 ms36.8 KiB
imaging.jugem.jp/images/portal/index/intro_headline_smp.png0.0 ms34.2 KiB
imaging.jugem.jp/images/portal/index/function_analytics.png0.0 ms28.2 KiB
imaging.jugem.jp/images/portal/index/function_upload.png0.0 ms20.7 KiB
pdn.adingo.jp/p.js600.0 s20.7 KiB
imaging.jugem.jp/images/portal/index/function_domain.png0.0 ms18.1 KiB
imaging.jugem.jp/images/portal/index/intro_answer_decorate.png0.0 ms16.9 KiB
imaging.jugem.jp/images/portal/index/free_device.png0.0 ms16.7 KiB
www.google-analytics.com/analytics.js7200.0 s20.9 KiB
imaging.jugem.jp/images/portal/common/logo_pc.png0.0 ms15.6 KiB
imaging.jugem.jp/images/portal/index/free_template.png0.0 ms15.5 KiB
imaging.jugem.jp/images/portal/index/intro_question_decorate.png0.0 ms13.4 KiB
imaging.jugem.jp/images/portal/common/logo_smp.png0.0 ms13.1 KiB
imaging.jugem.jp/images/portal/index/function_password.png0.0 ms12.1 KiB
imaging.jugem.jp/images/portal/index/free_sns.png0.0 ms11.2 KiB
imaging.jugem.jp/images/portal/index/intro_propose_underline.png0.0 ms5.8 KiB
use.fontawesome.com/c1576d6d27.js1800.0 s4.1 KiB
cdn.nidan.d2c.ne.jp/1.0/index.js86400.0 s3.6 KiB
imaging.jugem.jp/images/portal/index/intro_answer_underline.png0.0 ms1.4 KiB
use.fontawesome.com/c1576d6d27.css1800.0 s713 B
linkback.contentsfeed.com/src/lb4pbfluct.min.js0.0 ms318 B
/id/nidan/pre?callback=d2c.nidan.ns&origin=https%3A%2F%2F...7200.0 s159 B
image8.pubmatic.com/AdServer/ImgSync?p=1608360.0 ms69 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:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:33.048 source:map[type:text value:[unattributed]]]]

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-DIV
nodeLabel: body > div.wrapper > section.top > div.top-bg
path: 1,HTML,1,BODY,2,DIV,0,SECTION,0,DIV
selector: body > div.wrapper > section.top > div.top-bg
snippet: <div class="top-bg">

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.

URLTransfer SizeDuration
jugem.jp/css/index.css36.8 KiB675 ms
use.fontawesome.com/c1576d6d27.js4.1 KiB255 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.

URLResource SizeEst Savings
おしゃれ手帖 light li.recommend-item > a > div.recommend-item-inner > img
imaging.jugem.jp/images/portal/index/recommend_fashionable.png126.3 KiB100.8 KiB
PCもスマホも広告非表示 section.intro > div.intro-inner > div.intro-propose > img
imaging.jugem.jp/images/portal/index/intro_propose.png120.7 KiB90.5 KiB
ベーシック li.recommend-item > a > div.recommend-item-inner > img
imaging.jugem.jp/images/portal/index/recommend_basic.png87.9 KiB62.4 KiB
「自分の書いた記事の間に、広告が...」「広告を間違えて押してしまった...」 section.intro > div.intro-inner > div.intro-question > img.intro-question-pc
imaging.jugem.jp/images/portal/index/intro_question_pc.png70.4 KiB52.8 KiB
section.intro > div.intro-inner > div.intro-answer > img.intro-answer-pc
imaging.jugem.jp/images/portal/index/intro_answer_pc.png61.5 KiB46.2 KiB
JUGEMプラス 月額330円(税込) section.intro > div.intro-inner > div.intro-headline > img.intro-headline-pc
imaging.jugem.jp/images/portal/index/intro_headline_pc.png60.4 KiB45.3 KiB
あさひるぱん li.recommend-item > a > div.recommend-item-inner > img
imaging.jugem.jp/images/portal/index/recommend_pan.png64.3 KiB38.9 KiB
MasonClip - retro li.recommend-item > a > div.recommend-item-inner > img
imaging.jugem.jp/images/portal/index/recommend_maisonclip.png50.1 KiB28.3 KiB
div.function-inner > ul > li > img
imaging.jugem.jp/images/portal/index/function_analytics.png27.8 KiB22.0 KiB
div.function-inner > ul > li > img
imaging.jugem.jp/images/portal/index/function_upload.png20.4 KiB15.3 KiB
JUGEMブログ div.header-contents > h1 > a > img.logo-pc
imaging.jugem.jp/images/portal/common/logo_pc.png15.2 KiB14.7 KiB
div.function-inner > ul > li > img
imaging.jugem.jp/images/portal/index/function_domain.png17.7 KiB13.3 KiB
div.free-inner > ul > li > img
imaging.jugem.jp/images/portal/index/free_device.png16.4 KiB12.8 KiB
div.intro-inner > div.intro-answer > h4 > img
imaging.jugem.jp/images/portal/index/intro_answer_decorate.png16.6 KiB12.4 KiB
div.free-inner > ul > li > img
imaging.jugem.jp/images/portal/index/free_template.png15.2 KiB11.6 KiB
div.intro-inner > div.intro-question > h4 > img
imaging.jugem.jp/images/portal/index/intro_question_decorate.png13.0 KiB9.8 KiB
div.function-inner > ul > li > img
imaging.jugem.jp/images/portal/index/function_password.png11.8 KiB8.8 KiB
div.free-inner > ul > li > img
imaging.jugem.jp/images/portal/index/free_sns.png10.9 KiB8.2 KiB
JUGEMプラス h4 > ul > li.intro-propose-bottom > span
imaging.jugem.jp/images/portal/index/intro_propose_underline.png5.5 KiB4.1 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

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: 60 ms 351.3 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 10.8 KiB
URLTransfer SizeEst Savings
jugem.jp/css/index.css36.8 KiB10.8 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 16.8 KiB
URLTransfer SizeEst Savings
jugem.jp/css/index.css36.5 KiB16.8 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
JUGEMプラス 月額330円(税込) section.intro > div.intro-inner > div.intro-headline > img.intro-headline-pc
imaging.jugem.jp/images/portal/index/intro_headline_pc.png
PCもスマホも広告非表示 section.intro > div.intro-inner > div.intro-propose > img
imaging.jugem.jp/images/portal/index/intro_propose.png
「自分の書いた記事の間に、広告が...」「広告を間違えて押してしまった...」 section.intro > div.intro-inner > div.intro-question > img.intro-question-pc
imaging.jugem.jp/images/portal/index/intro_question_pc.png
section.intro > div.intro-inner > div.intro-answer > img.intro-answer-pc
imaging.jugem.jp/images/portal/index/intro_answer_pc.png
ベーシック li.recommend-item > a > div.recommend-item-inner > img
imaging.jugem.jp/images/portal/index/recommend_basic.png
あさひるぱん li.recommend-item > a > div.recommend-item-inner > img
imaging.jugem.jp/images/portal/index/recommend_pan.png
おしゃれ手帖 light li.recommend-item > a > div.recommend-item-inner > img
imaging.jugem.jp/images/portal/index/recommend_fashionable.png
MasonClip - retro li.recommend-item > a > div.recommend-item-inner > img
imaging.jugem.jp/images/portal/index/recommend_maisonclip.png
div.intro-inner > div.intro-answer > h4 > img
imaging.jugem.jp/images/portal/index/intro_answer_decorate.png
div.function-inner > ul > li > img
imaging.jugem.jp/images/portal/index/function_analytics.png
div.function-inner > ul > li > img
imaging.jugem.jp/images/portal/index/function_password.png
div.function-inner > ul > li > img
imaging.jugem.jp/images/portal/index/function_upload.png
div.function-inner > ul > li > img
imaging.jugem.jp/images/portal/index/function_domain.png
div.intro-inner > div.intro-question > h4 > img
imaging.jugem.jp/images/portal/index/intro_question_decorate.png
div.free-inner > ul > li > img
imaging.jugem.jp/images/portal/index/free_device.png
div.free-inner > ul > li > img
imaging.jugem.jp/images/portal/index/free_template.png
div.free-inner > ul > li > img
imaging.jugem.jp/images/portal/index/free_sns.png
JUGEMブログ div.header-contents > h1 > a > img.logo-pc
imaging.jugem.jp/images/portal/common/logo_pc.png

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

Max Potential First Input Delay 100 ms
Layout shift culprits
Document request latency
Optimize DOM size
LCP breakdown
Modern HTTP
Optimize viewport for mobile
Minify JavaScript
Avoids enormous network payloads Total size was 2,536 KiB
User Timing marks and measures 5 user timings
JavaScript execution time 0.3 s
Minimizes main-thread work 0.7 s
Avoid long main-thread tasks 2 long tasks found
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 260 ms
Server Backend Latencies 340 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 290 ms
INP breakdown
Avoid non-composited animations
Avoid large layout shifts
58

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
無料登録 div.header-nav > ul.header-nav-inner > li.header-nav__signup > a
まずは無料ではじめてみる div.top-register-inner > ul > li.register-button > a
無料 section.free > div.free-inner > h3 > strong
PC・スマホで、見られる・書ける。 ul > li > dl > dd
お気に入りがきっと、見つかるはず。 ul > li > dl > dd
連携して、ブログの可能性を広げませんか。 ul > li > dl > dd
スマホ・PC別、記事別、時間帯別でアクセス数を解析。どれだけ見られているのかチェックできます。 ul > li > dl > dd
ブログ全体や、記事別にも鍵がかけられ、プライベートで共有したい記事も安心して書けます。 ul > li > dl > dd
写真を一括でアップロード、容量無制限だから、お気に入りの写真は全て載せられます。 ul > li > dl > dd
世界に1つだけ!あなたの取得したドメインを使って、ブログのURLにも、こだわりを出せます。 ul > li > dl > dd
書きやすく、読みやすい、ベーシックなテンプレートです。長文を書く方や、写真ブログにも。 a > div.recommend-item-inner > dl > dd
今にも食べたくなる!手描きのパンがかわいい、温かみのあるテンプレートです。パン好きにはたまりません。 a > div.recommend-item-inner > dl > dd
ナチュラルでかわいい模様が印象的なテンプレートです。雑貨好きな方やハンドメイド作家さんにもおすすめ。 a > div.recommend-item-inner > dl > dd
ウィンドウサイズに合わせて記事の並びが変わるのが特徴のテンプレートです。シックな赤のレトロなデザイン。 a > div.recommend-item-inner > dl > dd
まずは無料ではじめてみる div.bottom-register > ul > li.bottom-register-free > a
Copyright © 2003-2026 株式会社メディアーノ All Rights Reserved. footer.footer > div.footer-inner > div.footer-copyright > p
All Rights Reserved. div.footer-inner > div.footer-copyright > p > span

These are opportunities to improve the legibility of your content.

Internationalization and localization

If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html.fa-events-icons-ready html.fa-events-icons-ready

These are opportunities to improve the interpretation of your content by users in different locales.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.free-inner > ul > li > img
div.free-inner > ul > li > img
div.free-inner > ul > li > img
div.intro-inner > div.intro-question > h4 > img
div.intro-inner > div.intro-answer > h4 > img
section.intro > div.intro-inner > div.intro-answer > img.intro-answer-pc
div.function-inner > ul > li > img
div.function-inner > ul > li > img
div.function-inner > ul > li > img
div.function-inner > ul > li > img

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
JUGEMブログ div.header-inner > div.header-contents > h1 > 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

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.fa-events-icons-ready html.fa-events-icons-ready

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>`
`[aria-hidden="true"]` elements do not contain focusable descendents
`<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
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
`[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 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
ARIA IDs are unique
No form fields have multiple labels
`<frame>` or `<iframe>` elements have a title
`<html>` element has a valid value for its `[lang]` attribute
`<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
`<video>` elements contain a `<track>` element with `[kind="captions"]`
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.
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
Topics

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
Access to fetch at 'https://ad.ad-stir.com/prebid' from origin 'https://jugem.jp' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
Access to fetch at 'https://ad.ad-stir.com/prebid' from origin 'https://jugem.jp' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
Access to fetch at 'https://ad.ad-stir.com/prebid' from origin 'https://jugem.jp' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
Access to fetch at 'https://ad.ad-stir.com/prebid' from origin 'https://jugem.jp' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
Access to fetch at 'https://ad.ad-stir.com/prebid' from origin 'https://jugem.jp' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
Access to fetch at 'https://aladdin.genieesspv.jp/yie/ld/api/ad_call/v2?zoneid=1585694&cb=71623258621&charset=UTF-8&loc=https%3A%2F%2Fjugem.jp%2F&ct0=undefined&referer=undefined&topframe=1&cur=JPY&requestid=6ddd8ced-9bd9-457c-b351-8da386a75d6a&ua=Mozilla%2F5.0%20(Macintosh%3B%20Intel%20Mac%20OS%20X%2010_15_7)%20AppleWebKit%2F537.36%20(KHTML%2C%20like%20Gecko)%20Chrome%2F147.0.0.0%20Safari%2F537.36&tpaf=1&cks=1&schain=%7B%22ver%22%3A%221.0%22%2C%22complete%22%3A1%2C%22nodes%22%3A%5B%7B%22asi%22%3A%22adingo.jp%22%2C%22sid%22%3A%223248%22%2C%22hp%22%3A1%7D%5D%7D&gpid=%2F66065524%2Fjugem_pc_top%2Fjugem_pc_top_body_1_left&fl_pr=2&title=JUGEM%25E3%2583%2596%25E3%2583%25AD%25E3%2582%25B0%2520%257C%2520%25E8%2587%25AA%25E5%2588%2586%25E3%2581%25A0%25E3%2581%2591%25E3%2581%25AE%25E3%2581%2593%25E3%2581%25A0%25E3%2582%258F%25E3%2582%258A%25E3%2583%2596%25E3%2583%25AD%25E3%2582%25B0%25E3%2582%2592%25E3%2581%25AF%25E3%2581%2598%25E3%2582%2581%25E3%2582%2588%25E3%2581%2586&sw=600&sh=800&ucmbl=%3F0' from origin 'https://jugem.jp' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
Access to fetch at 'https://aladdin.genieesspv.jp/yie/ld/api/ad_call/v2?zoneid=1585695&cb=4817378137&charset=UTF-8&loc=https%3A%2F%2Fjugem.jp%2F&ct0=undefined&referer=undefined&topframe=1&cur=JPY&requestid=c2f79a8c-cdb3-49e3-83b7-12a4fd7cc010&ua=Mozilla%2F5.0%20(Macintosh%3B%20Intel%20Mac%20OS%20X%2010_15_7)%20AppleWebKit%2F537.36%20(KHTML%2C%20like%20Gecko)%20Chrome%2F147.0.0.0%20Safari%2F537.36&tpaf=1&cks=1&schain=%7B%22ver%22%3A%221.0%22%2C%22complete%22%3A1%2C%22nodes%22%3A%5B%7B%22asi%22%3A%22adingo.jp%22%2C%22sid%22%3A%223248%22%2C%22hp%22%3A1%7D%5D%7D&gpid=%2F66065524%2Fjugem_pc_top%2Fjugem_pc_top_body_1_right&fl_pr=2&title=JUGEM%25E3%2583%2596%25E3%2583%25AD%25E3%2582%25B0%2520%257C%2520%25E8%2587%25AA%25E5%2588%2586%25E3%2581%25A0%25E3%2581%2591%25E3%2581%25AE%25E3%2581%2593%25E3%2581%25A0%25E3%2582%258F%25E3%2582%258A%25E3%2583%2596%25E3%2583%25AD%25E3%2582%25B0%25E3%2582%2592%25E3%2581%25AF%25E3%2581%2598%25E3%2582%2581%25E3%2582%2588%25E3%2581%2586&sw=600&sh=800&ucmbl=%3F0' from origin 'https://jugem.jp' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
Access to fetch at 'https://aladdin.genieesspv.jp/yie/ld/api/ad_call/v2?zoneid=1585696&cb=75039198833&charset=UTF-8&loc=https%3A%2F%2Fjugem.jp%2F&ct0=undefined&referer=undefined&topframe=1&cur=JPY&requestid=2295820c-8f1d-48a2-b515-46c548fa2955&ua=Mozilla%2F5.0%20(Macintosh%3B%20Intel%20Mac%20OS%20X%2010_15_7)%20AppleWebKit%2F537.36%20(KHTML%2C%20like%20Gecko)%20Chrome%2F147.0.0.0%20Safari%2F537.36&tpaf=1&cks=1&schain=%7B%22ver%22%3A%221.0%22%2C%22complete%22%3A1%2C%22nodes%22%3A%5B%7B%22asi%22%3A%22adingo.jp%22%2C%22sid%22%3A%223248%22%2C%22hp%22%3A1%7D%5D%7D&gpid=%2F66065524%2Fjugem_pc_top%2Fjugem_pc_top_body_2&fl_pr=2&title=JUGEM%25E3%2583%2596%25E3%2583%25AD%25E3%2582%25B0%2520%257C%2520%25E8%2587%25AA%25E5%2588%2586%25E3%2581%25A0%25E3%2581%2591%25E3%2581%25AE%25E3%2581%2593%25E3%2581%25A0%25E3%2582%258F%25E3%2582%258A%25E3%2583%2596%25E3%2583%25AD%25E3%2582%25B0%25E3%2582%2592%25E3%2581%25AF%25E3%2581%2598%25E3%2582%2581%25E3%2582%2588%25E3%2581%2586&sw=600&sh=800&ucmbl=%3F0' from origin 'https://jugem.jp' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
Access to fetch at 'https://aladdin.genieesspv.jp/yie/ld/api/ad_call/v2?zoneid=1585697&cb=23446056044&charset=UTF-8&loc=https%3A%2F%2Fjugem.jp%2F&ct0=undefined&referer=undefined&topframe=1&cur=JPY&requestid=35d20134-0b01-4ce2-a3ab-a8c9d0890b43&ua=Mozilla%2F5.0%20(Macintosh%3B%20Intel%20Mac%20OS%20X%2010_15_7)%20AppleWebKit%2F537.36%20(KHTML%2C%20like%20Gecko)%20Chrome%2F147.0.0.0%20Safari%2F537.36&tpaf=1&cks=1&schain=%7B%22ver%22%3A%221.0%22%2C%22complete%22%3A1%2C%22nodes%22%3A%5B%7B%22asi%22%3A%22adingo.jp%22%2C%22sid%22%3A%223248%22%2C%22hp%22%3A1%7D%5D%7D&gpid=%2F66065524%2Fjugem_pc_top%2Fjugem_pc_top_body_3&fl_pr=2&title=JUGEM%25E3%2583%2596%25E3%2583%25AD%25E3%2582%25B0%2520%257C%2520%25E8%2587%25AA%25E5%2588%2586%25E3%2581%25A0%25E3%2581%2591%25E3%2581%25AE%25E3%2581%2593%25E3%2581%25A0%25E3%2582%258F%25E3%2582%258A%25E3%2583%2596%25E3%2583%25AD%25E3%2582%25B0%25E3%2582%2592%25E3%2581%25AF%25E3%2581%2598%25E3%2582%2581%25E3%2582%2588%25E3%2581%2586&sw=600&sh=800&ucmbl=%3F0' from origin 'https://jugem.jp' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
Access to fetch at 'https://aladdin.genieesspv.jp/yie/ld/api/ad_call/v2?zoneid=1585698&cb=90667458069&charset=UTF-8&loc=https%3A%2F%2Fjugem.jp%2F&ct0=undefined&referer=undefined&topframe=1&cur=JPY&requestid=84fba987-64fb-4424-9592-0ac5af6e51f0&ua=Mozilla%2F5.0%20(Macintosh%3B%20Intel%20Mac%20OS%20X%2010_15_7)%20AppleWebKit%2F537.36%20(KHTML%2C%20like%20Gecko)%20Chrome%2F147.0.0.0%20Safari%2F537.36&tpaf=1&cks=1&schain=%7B%22ver%22%3A%221.0%22%2C%22complete%22%3A1%2C%22nodes%22%3A%5B%7B%22asi%22%3A%22adingo.jp%22%2C%22sid%22%3A%223248%22%2C%22hp%22%3A1%7D%5D%7D&gpid=%2F66065524%2Fjugem_pc_top%2Fjugem_pc_top_footer&fl_pr=2&title=JUGEM%25E3%2583%2596%25E3%2583%25AD%25E3%2582%25B0%2520%257C%2520%25E8%2587%25AA%25E5%2588%2586%25E3%2581%25A0%25E3%2581%2591%25E3%2581%25AE%25E3%2581%2593%25E3%2581%25A0%25E3%2582%258F%25E3%2582%258A%25E3%2583%2596%25E3%2583%25AD%25E3%2582%25B0%25E3%2582%2592%25E3%2581%25AF%25E3%2581%2598%25E3%2582%2581%25E3%2582%2588%25E3%2581%2586&sw=600&sh=800&ucmbl=%3F0' from origin 'https://jugem.jp' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
Access to fetch at 'https://hb.adingo.jp/prebid/?dfpUnitCode=undefined&tagId=41206%3A1000281335&groupId=1000176922' from origin 'https://jugem.jp' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource.
Access to fetch at 'https://hb.adingo.jp/prebid/?dfpUnitCode=undefined&tagId=41206%3A1000281337&groupId=1000176922' from origin 'https://jugem.jp' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource.
Access to fetch at 'https://hb.adingo.jp/prebid/?dfpUnitCode=undefined&tagId=41206%3A1000281340&groupId=1000176922' from origin 'https://jugem.jp' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource.
Access to fetch at 'https://hb.adingo.jp/prebid/?dfpUnitCode=undefined&tagId=41206%3A1000281347&groupId=1000176922' from origin 'https://jugem.jp' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource.
Access to fetch at 'https://hb.adingo.jp/prebid/?dfpUnitCode=undefined&tagId=41206%3A1000281349&groupId=1000176922' from origin 'https://jugem.jp' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource.
Access to fetch at 'https://sp.gmossp-sp.jp/hb/prebid/query.ad?tid=ubbc85267-c9d9-45a2-9a3a-23da4b502931&bid=c628ee9a-96fe-4850-8ea1-95fca162b76c&ver=11.6.0&sid=g946781&url=https%3A%2F%2Fjugem.jp%2F&meta_url=https%3A%2F%2Fjugem.jp%2F&cur=JPY&' from origin 'https://jugem.jp' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
Failed to load resource: net::ERR_FAILED
Failed to load resource: net::ERR_FAILED
Failed to load resource: net::ERR_FAILED
Failed to load resource: net::ERR_FAILED
Failed to load resource: net::ERR_FAILED
Failed to load resource: net::ERR_FAILED
Failed to load resource: net::ERR_FAILED
Failed to load resource: net::ERR_FAILED
Failed to load resource: net::ERR_FAILED
Failed to load resource: net::ERR_FAILED
Failed to load resource: net::ERR_FAILED
Failed to load resource: net::ERR_FAILED
Failed to load resource: net::ERR_FAILED
Failed to load resource: net::ERR_FAILED
Failed to load resource: net::ERR_FAILED
Failed to load resource: net::ERR_FAILED
Uncaught Error: Unauthorized
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 clickjacking with XFO or CSP
Mitigate DOM-based XSS with Trusted Types
Page has valid source maps
Redirects HTTP traffic to HTTPS
Detected JavaScript libraries
92

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.

Content Best Practices

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.free-inner > ul > li > img
div.free-inner > ul > li > img
div.free-inner > ul > li > img
div.intro-inner > div.intro-question > h4 > img
div.intro-inner > div.intro-answer > h4 > img
section.intro > div.intro-inner > div.intro-answer > img.intro-answer-pc
div.function-inner > ul > li > img
div.function-inner > ul > li > img
div.function-inner > ul > li > img
div.function-inner > ul > li > img

Format your HTML in a way that enables crawlers to better understand your app’s content.

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
Document has a valid `hreflang`
Document has a valid `rel=canonical`

Send Feedback