PageSpeed Insights logo
PageSpeed Insights
PageSpeed Insights
This site uses cookies from Google to deliver its services and to analyze traffic.
Report from Mar 27, 2025, 11:38:29 AM
Discover what your real users are experiencing
No data found.
The Chrome User Experience Report does not have sufficient real-world speed data for this page.
Core Web Vitals Assessment: Failed
Largest Contentful Paint (LCP)
1 s
Page LoadsGood (≤ 2.5 s)96%Needs Improvement (2.5 s - 4 s)1%Poor (> 4 s)2%75th Percentile - 1 sCore Web Vital
Interaction to Next Paint (INP)
114 ms
Page LoadsGood (≤ 200 ms)94%Needs Improvement (200 ms - 500 ms)6%Poor (> 500 ms)1%75th Percentile - 114 msCore Web Vital
Cumulative Layout Shift (CLS)
0.2
Page LoadsGood (≤ 0.1)64%Needs Improvement (0.1 - 0.25)14%Poor (> 0.25)23%75th Percentile - 0.2Core Web Vital
Other Notable Metrics
First Contentful Paint (FCP)
1 s
Page LoadsGood (≤ 1.8 s)93%Needs Improvement (1.8 s - 3 s)5%Poor (> 3 s)3%75th Percentile - 1 s 
Time to First Byte (TTFB)
0.4 s
Page LoadsGood (≤ 0.8 s)90%Needs Improvement (0.8 s - 1.8 s)8%Poor (> 1.8 s)2%75th Percentile - 0.4 sExperimental
Latest 28-day collection period
Various mobile devicesMany samples (Chrome UX Report)Full visit durationsVarious network connectionsAll Chrome versions
Diagnose performance issues
57
Performance
90
Accessibility
100
Best Practices
92
SEO
57
Performance
90
Accessibility
100
Best Practices
92
SEO
57 FCP+0LCP+0TBT+29CLS+25SI+3 Performance
Values are estimated and may vary. The performance score is calculated directly from these metrics.See calculator.
0–49 50–89 90–100
Final Screenshot
Metrics
First Contentful Paint
7.6 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric.
Largest Contentful Paint
12.8 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric
Total Blocking Time
100 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more about the Total Blocking Time metric.
Cumulative Layout Shift
0
Cumulative Layout Shift measures the movement of visible elements within the viewport. Learn more about the Cumulative Layout Shift metric.
Speed Index
7.6 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric.
  • Captured at Mar 27, 2025, 11:38 AM UTC
  • Emulated Moto G Power with Lighthouse 12.4.0
    Unthrottled CPU/Memory Power: 498 CPU throttling: 1.2x slowdown (Simulated) Screen emulation: 412x823, DPR 1.75 Axe version: 4.10.2
  • Single page session
    This data is taken from a single page session, as opposed to field data summarizing many sessions.
  • Initial page load
  • Slow 4G throttling
    Network throttling: 150 ms TCP RTT, 1,638.4 kb/s throughput (Simulated) Browser location: Asia
  • Using HeadlessChromium 133.0.6943.141 with lr
    User agent (network): "Mozilla/5.0 (Linux; Android 11; moto g power (2022)) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/119.0.0.0 Mobile Safari/537.36"
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Show audits relevant to:
Diagnostics
Largest Contentful Paint element 12,830 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint elementLCP
Element
問題解決に役立つロジカルシンキング（論理思考）を基礎から学ぶ。 ロジカルシンキング研修.com
<header id="header" class="header ba-fixed cf" itemscope="" itemtype="https://schema.org/WPHeader">
Phase
% of LCP
Timing
TTFB
5%
600 ms
Load Delay
18%
2,310 ms
Load Time
6%
760 ms
Render Delay
71%
9,160 ms
Eliminate render-blocking resources Potential savings of 3,910 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn how to eliminate render-blocking resources.LCPFCP
URL
Transfer Size
Potential Savings
Google CDN
cdn
31.3 KiB
1,350 ms
…3.6.1/jquery.min.js?ver=3.6.1
(ajax.googleapis.com)
31.3 KiB
1,350 ms
Reduce unused JavaScript Potential savings of 344 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.LCPFCP
URL
Transfer Size
Potential Savings
Google CDN
cdn
430.5 KiB
200.9 KiB
…bUO1BXI8H…/recaptcha__en.js
(www.gstatic.com)
215.2 KiB
101.2 KiB
…bUO1BXI8H…/recaptcha__en.js
(www.gstatic.com)
215.2 KiB
99.7 KiB
Other Google APIs/SDKs
utility
144.8 KiB
88.3 KiB
…75c56d121cde450a/cse_element__ja.js?usqp=CAI%3D
(www.google.com)
94.7 KiB
47.6 KiB
…search/async-ads.js
(cse.google.com)
50.0 KiB
40.7 KiB
Google Tag Manager
tag-manager
141.2 KiB
54.4 KiB
/gtag/js?id=G-G55FP7SF13
(www.googletagmanager.com)
141.2 KiB
54.4 KiB
Defer offscreen images Potential savings of 221 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn how to defer offscreen images.LCPFCP
URL
Resource Size
Potential Savings
ltkensyu.com
1st party
220.7 KiB
220.7 KiB
header.article-header > div.eye-catch-wrap > figure.eye-catch > img
<img src="https://www.ltkensyu.com/wp-content/uploads/2022/10/TopImage36.jpg" width="1280" height="720" alt="">
…10/TopImage36.jpg
(www.ltkensyu.com)
206.4 KiB
206.4 KiB
a.blogcard-wrap > div.blogcard > figure.blogcard-thumbnail > img.blogcard-thumb-image
<img decoding="async" width="160" height="90" src="https://www.ltkensyu.com/wp-content/uploads/2018/05/training-min-320x180.j…" class="blogcard-thumb-image internal-blogcard-thumb-image wp-post-image" alt="" srcset="https://www.ltkensyu.com/wp-content/uploads/2018/05/training-min-160x90.jp…" sizes="(max-width: 160px) 100vw, 160px">
…05/training-min-320x180.jpg.webp
(www.ltkensyu.com)
9.3 KiB
9.3 KiB
a.blogcard-wrap > div.blogcard > figure.blogcard-thumbnail > img.blogcard-thumb-image
<img decoding="async" width="160" height="90" src="https://www.ltkensyu.com/wp-content/uploads/2018/05/pyramid-min-320x180.jp…" class="blogcard-thumb-image internal-blogcard-thumb-image wp-post-image" alt="" srcset="https://www.ltkensyu.com/wp-content/uploads/2018/05/pyramid-min-160x90.jpg…" sizes="(max-width: 160px) 100vw, 160px">
…05/pyramid-min-320x180.jpg.webp
(www.ltkensyu.com)
5.0 KiB
5.0 KiB
Reduce unused CSS Potential savings of 137 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.LCPFCP
URL
Transfer Size
Potential Savings
ltkensyu.com
1st party
62.1 KiB
58.6 KiB
…css/cda8090….css?ver=c57ea
(www.ltkensyu.com)
36.5 KiB
33.1 KiB
…css/1d70816….css?ver=be978
(www.ltkensyu.com)
13.8 KiB
13.8 KiB
…css/06b3d3a….css?ver=abb37
(www.ltkensyu.com)
11.8 KiB
11.7 KiB
Unattributable
40.3 KiB
39.8 KiB
#header-container,#header-container .navi,#navi .navi-in>.menu-header .sub-menu,.article h2,.sideba…
28.3 KiB
27.9 KiB
span.PIN_1743075513375_embed_grid { 
  width: 100%;
  max-width: 257px;
  min-width: 140px; … } …
12.0 KiB
12.0 KiB
Google CDN
cdn
41.0 KiB
38.9 KiB
…bUO1BXI8H…/styles__ltr.css
(www.gstatic.com)
41.0 KiB
38.9 KiB
Serve images in next-gen formats Potential savings of 35 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more about modern image formats.LCPFCP
URL
Resource Size
Potential Savings
ltkensyu.com
1st party
206.4 KiB
35.4 KiB
header.article-header > div.eye-catch-wrap > figure.eye-catch > img
<img src="https://www.ltkensyu.com/wp-content/uploads/2022/10/TopImage36.jpg" width="1280" height="720" alt="">
…10/TopImage36.jpg
(www.ltkensyu.com)
206.4 KiB
35.4 KiB
Minify CSS Potential savings of 3 KiB
Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.LCPFCP
URL
Transfer Size
Potential Savings
Other Google APIs/SDKs
utility
9.7 KiB
2.9 KiB
…75c56d121cde450a/default+ja.css
(www.google.com)
9.7 KiB
2.9 KiB
Serve static assets with an efficient cache policy 5 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
URL
Cache TTL
Transfer Size
Pinterest
social
19 KiB
/js/pinit_main.js
(assets.pinterest.com)
5m
19 KiB
Other Google APIs/SDKs
utility
5 KiB
/cse.js?cx=e2d2463f24035e1c2
(cse.google.com)
None
3 KiB
…v4/default.css
(www.google.com)
50m
2 KiB
Google CDN
cdn
3 KiB
…api2/logo_48.png
(www.gstatic.com)
7d
3 KiB
gstatic.com
1 KiB
/faviconV2?client=…
(t3.gstatic.com)
7d
1 KiB
Ensure text remains visible during webfont load
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more about font-display.
URL
Potential Savings
Google Fonts
cdn
10 ms
…v18/KFOmCnqEu….woff2
(fonts.gstatic.com)
0 ms
…v18/KFOlCnqEu….woff2
(fonts.gstatic.com)
0 ms
Avoid serving legacy JavaScript to modern browsers Potential savings of 11 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers. Learn how to serve modern JavaScriptLCPFCP
URL
Potential Savings
ltkensyu.com
1st party
10.7 KiB
…js/e4aeb08….js?ver=4287d
(www.ltkensyu.com)
10.7 KiB
…js/e4aeb08….js?ver=4287d:7:6597
(www.ltkensyu.com)
Array.prototype.forEach
…js/e4aeb08….js?ver=4287d:7:6704
(www.ltkensyu.com)
Array.prototype.filter
…js/1b78179….js?ver=c6067
(www.ltkensyu.com)
0.1 KiB
…js/1b78179….js?ver=c6067:6:86
(www.ltkensyu.com)
@babel/plugin-transform-classes
Avoid an excessive DOM size 1,057 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn how to avoid an excessive DOM size.TBT
Statistic
Element
Value
Total DOM Elements
1,057
Maximum DOM Depth
×
<span class="gscb_a" id="gs_cb50" aria-hidden="true">
23
Maximum Child Elements
ロジカルシンキングを必要とする背景とは 目次 ロジカルシンキングを必要とする背景とは 解決困難な問題に取り囲まれている 問題を解決する力が要る 講座を通じて独…
<div class="entry-content cf" itemprop="mainEntityOfPage">
34
Minimize third-party usage Third-party code blocked the main thread for 230 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn how to minimize third-party impact.TBT
Third-Party
Transfer Size
Main-Thread Blocking Time
Google CDN
cdn
725 KiB
153 ms
…bUO1BXI8H…/recaptcha__en.js
(www.gstatic.com)
649 KiB
153 ms
…3.6.1/jquery.min.js?ver=3.6.1
(ajax.googleapis.com)
31 KiB
0 ms
…bUO1BXI8H…/styles__ltr.css
(www.gstatic.com)
42 KiB
0 ms
…api2/logo_48.png
(www.gstatic.com)
3 KiB
0 ms
Other Google APIs/SDKs
utility
234 KiB
40 ms
…api2/anchor?ar=…
(www.google.com)
42 KiB
38 ms
/cse.js?cx=e2d2463f24035e1c2
(cse.google.com)
3 KiB
2 ms
/recaptcha/api.js?render=6Lfe6HQoA…&ver=3.0
(www.google.com)
2 KiB
0 ms
…75c56d121cde450a/cse_element__ja.js?usqp=CAI%3D
(www.google.com)
96 KiB
0 ms
…search/async-ads.js
(cse.google.com)
51 KiB
0 ms
…api2/reload?k=6Lfe6HQoA…
(www.google.com)
21 KiB
0 ms
…75c56d121cde450a/default+ja.css
(www.google.com)
10 KiB
0 ms
…ja/branding.png
(www.google.com)
3 KiB
0 ms
…75c56d121cde450a/mobile+ja.css
(www.google.com)
2 KiB
0 ms
…v4/default.css
(www.google.com)
2 KiB
0 ms
…api2/clr?k=6Lfe6HQoA…
(www.google.com)
1 KiB
0 ms
…api2/webworker.js?hl=en&v=bUO1BXI8H…
(www.google.com)
1 KiB
0 ms
/s2/favicons?domain=https://www.ltkensyu.com
(www.google.com)
1 KiB
0 ms
Google Tag Manager
tag-manager
142 KiB
38 ms
/gtag/js?id=G-G55FP7SF13
(www.googletagmanager.com)
142 KiB
38 ms
Cloudflare CDN
cdn
5 KiB
2 ms
…3.3.2/jquery-migrate.min.js?ver=3.0.1
(cdnjs.cloudflare.com)
5 KiB
2 ms
Google Fonts
cdn
23 KiB
0 ms
…v18/KFOlCnqEu….woff2
(fonts.gstatic.com)
11 KiB
0 ms
…v18/KFOmCnqEu….woff2
(fonts.gstatic.com)
11 KiB
0 ms
Pinterest
social
19 KiB
0 ms
/js/pinit_main.js
(assets.pinterest.com)
19 KiB
0 ms
/?type=…
(log.pinterest.com)
1 KiB
0 ms
gstatic.com
1 KiB
0 ms
/faviconV2?client=…
(t3.gstatic.com)
1 KiB
0 ms
Google Analytics
analytics
1 KiB
0 ms
/g/collect?v=…
(analytics.google.com)
1 KiB
0 ms
Google/Doubleclick Ads
ad
1 KiB
0 ms
…ga/rul?tid=…
(td.doubleclick.net)
1 KiB
0 ms
/g/collect?v=…
(stats.g.doubleclick.net)
0 KiB
0 ms
google.com
0 KiB
0 ms
/generate_204
(clients1.google.com)
0 KiB
0 ms
Avoid long main-thread tasks 7 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn how to avoid long main-thread tasksTBT
URL
Start Time
Duration
Google CDN
cdn
441 ms
…bUO1BXI8H…/recaptcha__en.js
(www.gstatic.com)
12,993 ms
134 ms
…bUO1BXI8H…/recaptcha__en.js
(www.gstatic.com)
12,829 ms
99 ms
…bUO1BXI8H…/recaptcha__en.js
(www.gstatic.com)
12,592 ms
96 ms
…bUO1BXI8H…/recaptcha__en.js
(www.gstatic.com)
12,768 ms
61 ms
…bUO1BXI8H…/recaptcha__en.js
(www.gstatic.com)
12,928 ms
51 ms
ltkensyu.com
1st party
188 ms
…js/css_async.min.js
(www.ltkensyu.com)
6,603 ms
125 ms
…js/2af5d9e….js?ver=8b590
(www.ltkensyu.com)
6,776 ms
63 ms
Avoid non-composited animations 1 animated element found
Animations which are not composited can be janky and increase CLS. Learn how to avoid non-composited animationsCLS
Element
Name
Pinterest
<a class="sns-button share-button pinterest-button pinterest-share-button-sq" target="_blank" rel="nofollow noopener noreferrer" data-pin-do="buttonBookmark" data-pin-custom="true" aria-label="Pinterestでシェア" data-pin-log="button_pinit_bookmarklet" data-pin-href="https://www.pinterest.com/pin/create/button/">
Unsupported CSS Property: background-color
background-color
Unsupported CSS Property: color
color
Avoid chaining critical requests 1 chain found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn how to avoid chaining critical requests.
Maximum critical path latency: 250.192 ms
Initial Navigation
https://www.ltkensyu.com
…3.6.1/jquery.min.js?ver=3.6.1
(ajax.googleapis.com)
- 9.87 ms, 31.31 KiB
More information about the performance of your application. These numbers don't directly affect the Performance score.
Passed audits (21)
Show Hide
Properly size images
Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.LCPFCP
Minify JavaScript
Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.LCPFCP
Efficiently encode images
Optimized images load faster and consume less cellular data. Learn how to efficiently encode images.LCPFCP
Enable text compression
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more about text compression.LCPFCP
Preconnect to required origins
Consider adding preconnect or dns-prefetch resource hints to establish early connections to important third-party origins. Learn how to preconnect to required origins.LCPFCP
Initial server response time was short Root document took 50 ms
Keep the server response time for the main document short because all other requests depend on it. Learn more about the Time to First Byte metric.LCPFCP
URL
Time Spent
ltkensyu.com
1st party
50 ms
https://www.ltkensyu.com
50 ms
Avoid multiple page redirects
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.LCPFCP
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more about efficient video formatsLCPFCP
Remove duplicate modules in JavaScript bundles
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity. LCPFCP
Preload Largest Contentful Paint image
If the LCP element is dynamically added to the page, you should preload the image in order to improve LCP. Learn more about preloading LCP elements.LCP
Avoids enormous network payloads Total size was 1,762 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
URL
Transfer Size
Google CDN
cdn
648.6 KiB
…bUO1BXI8H…/recaptcha__en.js
(www.gstatic.com)
216.2 KiB
…bUO1BXI8H…/recaptcha__en.js
(www.gstatic.com)
216.2 KiB
…bUO1BXI8H…/recaptcha__en.js
(www.gstatic.com)
216.2 KiB
ltkensyu.com
1st party
405.0 KiB
…10/TopImage36.jpg
(www.ltkensyu.com)
206.9 KiB
…webfonts/fa-solid-900.woff2
(www.ltkensyu.com)
77.0 KiB
…webfonts/fa-brands-400.woff2
(www.ltkensyu.com)
75.5 KiB
https://www.ltkensyu.com
45.7 KiB
Other Google APIs/SDKs
utility
146.5 KiB
…75c56d121cde450a/cse_element__ja.js?usqp=CAI%3D
(www.google.com)
95.7 KiB
…search/async-ads.js
(cse.google.com)
50.8 KiB
Google Tag Manager
tag-manager
142.2 KiB
/gtag/js?id=G-G55FP7SF13
(www.googletagmanager.com)
142.2 KiB
User Timing marks and measures
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more about User Timing marks.
JavaScript execution time 1.2 s
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.TBT
URL
Total CPU Time
Script Evaluation
Script Parse
Google CDN
cdn
979 ms
872 ms
25 ms
…bUO1BXI8H…/recaptcha__en.js
(www.gstatic.com)
979 ms
872 ms
25 ms
Google Tag Manager
tag-manager
209 ms
101 ms
10 ms
/gtag/js?id=G-G55FP7SF13
(www.googletagmanager.com)
209 ms
101 ms
10 ms
ltkensyu.com
1st party
206 ms
13 ms
1 ms
https://www.ltkensyu.com
119 ms
8 ms
1 ms
…js/56bd8ed….js?ver=918c5
(www.ltkensyu.com)
87 ms
5 ms
0 ms
Unattributable
190 ms
60 ms
0 ms
Unattributable
133 ms
3 ms
0 ms
data:text/javascript;base64,d2luZG93LmRhdGFMYXllcj13aW5kb3cuZGF…
57 ms
57 ms
0 ms
Other Google APIs/SDKs
utility
159 ms
143 ms
3 ms
…api2/anchor?ar=…
(www.google.com)
95 ms
87 ms
3 ms
/cse.js?cx=e2d2463f24035e1c2
(cse.google.com)
64 ms
55 ms
0 ms
Minimizes main-thread work 1.9 s
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 workTBT
Category
Time Spent
Script Evaluation
1,311 ms
Style & Layout
243 ms
Other
171 ms
Parse HTML & CSS
74 ms
Script Parsing & Compilation
58 ms
Garbage Collection
38 ms
Rendering
8 ms
Lazy load third-party resources with facades
Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required. Learn how to defer third-parties with a facade.TBT
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint. Learn more about optimal lazy loading.LCP
Element
問題解決に役立つロジカルシンキング（論理思考）を基礎から学ぶ。 ロジカルシンキング研修.com
<header id="header" class="header ba-fixed cf" itemscope="" itemtype="https://schema.org/WPHeader">
Avoid large layout shifts
These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLSCLS
Uses passive listeners to improve scrolling performance
Consider marking your touch and wheel event listeners as passive to improve your page's scroll performance. Learn more about adopting passive event listeners.
Avoids document.write()
For users on slow connections, external scripts dynamically injected via document.write() can delay page load by tens of seconds. Learn how to avoid document.write().
Image elements have explicit width and height
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensionsCLS
Has a <meta name="viewport"> tag with width or initial-scale
A <meta name="viewport"> not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn more about using the viewport meta tag.
90
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
Background and foreground colors do not have a sufficient contrast ratio.
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
Failing Elements
　1）人にわかるように伝えられる
<span style="color: #ff0000;">
ホーム 2016.10.272025.03.25 ロジカルシンキングを必要とする背景とは 目次 ロジカルシンキングを必要とする背景とは 解決困難な問題に取り囲…
<main id="main" class="main" itemscope="" itemtype="https://schema.org/Blog">
　2）問題解決に取り組める
<span style="color: #ff0000;">
ホーム 2016.10.272025.03.25 ロジカルシンキングを必要とする背景とは 目次 ロジカルシンキングを必要とする背景とは 解決困難な問題に取り囲…
<main id="main" class="main" itemscope="" itemtype="https://schema.org/Blog">
These are opportunities to improve the legibility of your content.
Tables and lists
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.
Failing Elements
ビデオ講座で学ぶなら、さほど難しくない 基礎を理解すれば自信が持てる 実務で活用しなければ身に付かない どのような効果が期待できる？ 困りごと（コミュニケーシ…
<ul>
ビデオ講座で学ぶなら、さほど難しくない 基礎を理解すれば自信が持てる 実務で活用しなければ身に付かない どのような効果が期待できる？ 困りごと（コミュニケーシ…
<ul>
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Navigation
Heading elements are not in a sequentially-descending order
Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.
Failing Elements
ビデオ講座で学ぶなら、さほど難しくない
<h4>
These are opportunities to improve keyboard navigation in your application.
Additional items to manually check (10)
Show Hide
Interactive controls are keyboard focusable
Custom interactive controls are keyboard focusable and display a focus indicator. Learn how to make custom controls focusable.
Interactive elements indicate their purpose and state
Interactive elements, such as links and buttons, should indicate their state and be distinguishable from non-interactive elements. Learn how to decorate interactive elements with affordance hints.
The page has a logical tab order
Tabbing through the page follows the visual layout. Users cannot focus elements that are offscreen. Learn more about logical tab ordering.
Visual order on the page follows DOM order
DOM order matches the visual order, improving navigation for assistive technology. Learn more about DOM and visual ordering.
User focus is not accidentally trapped in a region
A user can tab into and out of any control or region without accidentally trapping their focus. Learn how to avoid focus traps.
The user's focus is directed to new content added to the page
If new content, such as a dialog, is added to the page, the user's focus is directed to it. Learn how to direct focus to new content.
HTML5 landmark elements are used to improve navigation
Landmark elements (<main>, <nav>, etc.) are used to improve the keyboard navigation of the page for assistive technology. Learn more about landmark elements.
Offscreen content is hidden from assistive technology
Offscreen content is hidden with display: none or aria-hidden=true. Learn how to properly hide offscreen content.
Custom controls have associated labels
Custom interactive controls have associated labels, provided by aria-label or aria-labelledby. Learn more about custom controls and labels.
Custom controls have ARIA roles
Custom interactive controls have appropriate ARIA roles. Learn how to add roles to custom controls.
These items address areas which an automated testing tool cannot cover. Learn more in our guide on conducting an accessibility review.
Passed audits (21)
Show Hide
[aria-*] attributes match their roles
Each ARIA role supports a specific subset of aria-* attributes. Mismatching these invalidates the aria-* attributes. Learn how to match ARIA attributes to their roles.
[aria-hidden="true"] is not present on the document <body>
Assistive technologies, like screen readers, work inconsistently when aria-hidden="true" is set on the document <body>. Learn how aria-hidden affects the document body.
[aria-*] attributes have valid values
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more about valid values for ARIA attributes.
[aria-*] attributes are valid and not misspelled
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid names. Learn more about valid ARIA attributes.
Buttons have an accessible name
When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.
Image elements have [alt] attributes
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.
[user-scalable="no"] is not used in the <meta name="viewport"> element and the [maximum-scale] attribute is not less than 5.
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.
ARIA attributes are used as specified for the element's role
Some ARIA attributes are only allowed on an element under certain conditions. Learn more about conditional ARIA attributes.
[aria-hidden="true"] elements do not contain focusable descendents
Focusable descendents within an [aria-hidden="true"] element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how aria-hidden affects focusable elements.
Elements use only permitted ARIA attributes
Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.
Document has a <title> element
The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. Learn more about document titles.
<html> element has a [lang] attribute
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.
<html> element has a valid value for its [lang] attribute
Specifying a valid BCP 47 language helps screen readers announce text properly. Learn how to use the lang attribute.
Form elements have associated labels
Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.
Links are distinguishable without relying on color.
Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.
Links have a discernible name
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.
List items (<li>) are contained within <ul>, <ol> or <menu> parent elements
Screen readers require list items (<li>) to be contained within a parent <ul>, <ol> or <menu> to be announced properly. Learn more about proper list structure.
No element has a [tabindex] value greater than 0
A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the tabindex attribute.
Touch targets have sufficient size and spacing.
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.
Uses ARIA roles only on compatible elements
Many HTML elements can only be assigned certain ARIA roles. Using ARIA roles where they are not allowed can interfere with the accessibility of the web page. Learn more about ARIA roles.
Image elements do not have [alt] attributes that are redundant text.
Informative elements should aim for short, descriptive alternative text. Alternative text that is exactly the same as the text adjacent to the link or image is potentially confusing for screen reader users, because the text will be read twice. Learn more about the alt attribute.
Not applicable (33)
Show Hide
[accesskey] values are unique
Access keys let users quickly focus a part of the page. For proper navigation, each access key must be unique. Learn more about access keys.
button, link, and menuitem elements have accessible names
When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to make command elements more accessible.
Deprecated ARIA roles were not used
Deprecated ARIA roles may not be processed correctly by assistive technology. Learn more about deprecated ARIA roles.
Elements with role="dialog" or role="alertdialog" have accessible names.
ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.
ARIA input fields have accessible names
When an input field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about input field labels.
ARIA meter elements have accessible names
When a meter element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to name meter elements.
ARIA progressbar elements have accessible names
When a progressbar element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to label progressbar elements.
[role]s have all required [aria-*] attributes
Some ARIA roles have required attributes that describe the state of the element to screen readers. Learn more about roles and required attributes.
Elements with an ARIA [role] that require children to contain a specific [role] have all required children.
Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.
[role]s are contained by their required parent element
Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. Learn more about ARIA roles and required parent element.
[role] values are valid
ARIA roles must have valid values in order to perform their intended accessibility functions. Learn more about valid ARIA roles.
Elements with the role=text attribute do not have focusable descendents.
Adding role=text around a text node split by markup enables VoiceOver to treat it as one phrase, but the element's focusable descendents will not be announced. Learn more about the role=text attribute.
ARIA toggle fields have accessible names
When a toggle field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about toggle fields.
ARIA tooltip elements have accessible names
When a tooltip element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to name tooltip elements.
ARIA treeitem elements have accessible names
When a treeitem element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about labeling treeitem elements.
The page contains a heading, skip link, or landmark region
Adding ways to bypass repetitive content lets keyboard users navigate the page more efficiently. Learn more about bypass blocks.
<dl>'s contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.
When definition lists are not properly marked up, screen readers may produce confusing or inaccurate output. Learn how to structure definition lists correctly.
Definition list items are wrapped in <dl> elements
Definition list items (<dt> and <dd>) must be wrapped in a parent <dl> element to ensure that screen readers can properly announce them. Learn how to structure definition lists correctly.
ARIA IDs are unique
The value of an ARIA ID must be unique to prevent other instances from being overlooked by assistive technologies. Learn how to fix duplicate ARIA IDs.
No form fields have multiple labels
Form fields with multiple labels can be confusingly announced by assistive technologies like screen readers which use either the first, the last, or all of the labels. Learn how to use form labels.
<frame> or <iframe> elements have a title
Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.
<html> element has an [xml:lang] attribute with the same base language as the [lang] attribute.
If the webpage does not specify a consistent language, then the screen reader might not announce the page's text correctly. Learn more about the lang attribute.
Input buttons have discernible text.
Adding discernable and accessible text to input buttons may help screen reader users understand the purpose of the input button. Learn more about input buttons.
<input type="image"> elements have [alt] text
When an image is being used as an <input> button, providing alternative text can help screen reader users understand the purpose of the button. Learn about input image alt text.
The document does not use <meta http-equiv="refresh">
Users do not expect a page to refresh automatically, and doing so will move focus back to the top of the page. This may create a frustrating or confusing experience. Learn more about the refresh meta tag.
<object> elements have alternate text
Screen readers cannot translate non-text content. Adding alternate text to <object> elements helps screen readers convey meaning to users. Learn more about alt text for object elements.
Select elements have associated label elements.
Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the select element.
Tables have different content in the summary attribute and <caption>.
The summary attribute should describe the table structure, while <caption> should have the onscreen title. Accurate table mark-up helps users of screen readers. Learn more about summary and caption.
Cells in a <table> element that use the [headers] attribute refer to table cells within the same table.
Screen readers have features to make navigating tables easier. Ensuring <td> cells using the [headers] attribute only refer to other cells in the same table may improve the experience for screen reader users. Learn more about the headers attribute.
<th> elements and elements with [role="columnheader"/"rowheader"] have data cells they describe.
Screen readers have features to make navigating tables easier. Ensuring table headers always refer to some set of cells may improve the experience for screen reader users. Learn more about table headers.
[lang] attributes have a valid value
Specifying a valid BCP 47 language on elements helps ensure that text is pronounced correctly by a screen reader. Learn how to use the lang attribute.
<video> elements contain a <track> element with [kind="captions"]
When a video provides a caption it is easier for deaf and hearing impaired users to access its information. Learn more about video captions.
100
Best Practices
Trust and Safety
Ensure CSP is effective against XSS attacks
A strong Content Security Policy (CSP) significantly reduces the risk of cross-site scripting (XSS) attacks. Learn how to use a CSP to prevent XSS
Description
Directive
Severity
No CSP found in enforcement mode
High
Use a strong HSTS policy
Deployment of the HSTS header significantly reduces the risk of downgrading HTTP connections and eavesdropping attacks. A rollout in stages, starting with a low max-age is recommended. Learn more about using a strong HSTS policy.
Description
Directive
Severity
No `preload` directive found
preload
Medium
Ensure proper origin isolation with COOP
The Cross-Origin-Opener-Policy (COOP) can be used to isolate the top-level window from other documents such as pop-ups. Learn more about deploying the COOP header.
Description
Directive
Severity
No COOP header found
High
Mitigate clickjacking with XFO or CSP
The X-Frame-Options (XFO) header or the frame-ancestors directive in the Content-Security-Policy (CSP) header control where a page can be embedded. These can mitigate clickjacking attacks by blocking some or all sites from embedding the page. Learn more about mitigating clickjacking.
Description
Severity
No frame control policy found
High
General
Detected JavaScript libraries
All front-end JavaScript libraries detected on the page. Learn more about this JavaScript library detection diagnostic audit.
Name
Version
jQuery
3.6.1
core-js
core-js-global@3.35.1
Passed audits (15)
Show Hide
Uses HTTPS
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more about HTTPS.
Avoids deprecated APIs
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
Avoids third-party cookies
Chrome is moving towards a new experience that allows users to choose to browse without third-party cookies. Learn more about third-party cookies.
Allows users to paste into input fields
Preventing input pasting is a bad practice for the UX, and weakens security by blocking password managers.Learn more about user-friendly input fields.
Avoids requesting the geolocation permission on page load
Users are mistrustful of or confused by sites that request their location without context. Consider tying the request to a user action instead. Learn more about the geolocation permission.
Avoids requesting the notification permission on page load
Users are mistrustful of or confused by sites that request to send notifications without context. Consider tying the request to user gestures instead. Learn more about responsibly getting permission for notifications.
Displays images with correct aspect ratio
Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.
Serves images with appropriate resolution
Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn how to provide responsive images.
Has a <meta name="viewport"> tag with width or initial-scale
A <meta name="viewport"> not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn more about using the viewport meta tag.
Document uses legible font sizes 94.35% legible text
Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px. Learn more about legible font sizes.
Source
Selector
% of Page Text
Font Size
ltkensyu.com
1st party
…css/cda8090….css?ver=c57ea:21:14136
(www.ltkensyu.com)
.blogcard-snippet
5.25%
9.9456px
…css/cda8090….css?ver=c57ea:1:4075
(www.ltkensyu.com)
.post-date, .post-update, .post-author, .amp-back, .entry-category
0.17%
11.2px
…css/cda8090….css?ver=c57ea:11:19341
(www.ltkensyu.com)
.mobile-menu-buttons .menu-caption
0.13%
9px
Google CDN
cdn
…bUO1BXI8H…/styles__ltr.css:1:52632
(www.gstatic.com)
.rc-anchor-normal .rc-anchor-pt, .rc-anchor-invisible .rc-anchor-pt, .rc-anchor-compact .rc-anchor-pt
0.11%
8px
Unattributable
Legible text
94.35%
≥ 12px
Page has the HTML doctype
Specifying a doctype prevents the browser from switching to quirks-mode. Learn more about the doctype declaration.
Properly defines charset
A character encoding declaration is required. It can be done with a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header. Learn more about declaring the character encoding.
No browser errors logged to the console
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
No issues in the Issues panel in Chrome Devtools
Issues logged to the Issues panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.
Page has valid source maps
Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.
URL
Map URL
Cloudflare CDN
cdn
…3.3.2/jquery-migrate.min.js?ver=3.0.1
(cdnjs.cloudflare.com)
…3.3.2/jquery-migrate.min.map
(cdnjs.cloudflare.com)
Warning: missing 2 items in `.sourcesContent`
Not applicable (1)
Show Hide
Redirects HTTP traffic to HTTPS
Make sure that you redirect all HTTP traffic to HTTPS in order to enable secure web features for all your users. Learn more.
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.
Crawling and Indexing
Links are not crawlable
Search engines may use href attributes on links to crawl websites. Ensure that the href attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable
Uncrawlable Link
Pinterest
<a class="sns-button share-button pinterest-button pinterest-share-button-sq" target="_blank" rel="nofollow noopener noreferrer" data-pin-do="buttonBookmark" data-pin-custom="true" aria-label="Pinterestでシェア" data-pin-log="button_pinit_bookmarklet" data-pin-href="https://www.pinterest.com/pin/create/button/">
To appear in search results, crawlers need access to your app.
Additional items to manually check (1)
Show Hide
Structured data is valid
Run the Structured Data Testing Tool and the Structured Data Linter to validate structured data. Learn more about Structured Data.
Run these additional validators on your site to check additional SEO best practices.
Passed audits (9)
Show Hide
Page isn’t blocked from indexing
Search engines are unable to include your pages in search results if they don't have permission to crawl them. Learn more about crawler directives.
Document has a <title> element
The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. Learn more about document titles.
Document has a meta description
Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.
Page has successful HTTP status code
Pages with unsuccessful HTTP status codes may not be indexed properly. Learn more about HTTP status codes.
Links have descriptive text
Descriptive link text helps search engines understand your content. Learn how to make links more accessible.
robots.txt is valid
If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more about robots.txt.
Image elements have [alt] attributes
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.
Document has a valid hreflang
hreflang links tell search engines what version of a page they should list in search results for a given language or region. Learn more about hreflang.
Document has a valid rel=canonical
Canonical links suggest which URL to show in search results. Learn more about canonical links.
Discover what your real users are experiencing
No data found.
The Chrome User Experience Report does not have sufficient real-world speed data for this page.
Core Web Vitals Assessment: Passed
Largest Contentful Paint (LCP)
0.8 s
Page LoadsGood (≤ 2.5 s)99%Needs Improvement (2.5 s - 4 s)1%Poor (> 4 s)0%75th Percentile - 0.8 sCore Web Vital
Interaction to Next Paint (INP)
42 ms
Page LoadsGood (≤ 200 ms)98%Needs Improvement (200 ms - 500 ms)1%Poor (> 500 ms)1%75th Percentile - 42 msCore Web Vital
Cumulative Layout Shift (CLS)
0.09
Page LoadsGood (≤ 0.1)75%Needs Improvement (0.1 - 0.25)18%Poor (> 0.25)7%75th Percentile - 0.09Core Web Vital
Other Notable Metrics
First Contentful Paint (FCP)
0.7 s
Page LoadsGood (≤ 1.8 s)97%Needs Improvement (1.8 s - 3 s)2%Poor (> 3 s)1%75th Percentile - 0.7 s 
Time to First Byte (TTFB)
0.3 s
Page LoadsGood (≤ 0.8 s)93%Needs Improvement (0.8 s - 1.8 s)6%Poor (> 1.8 s)1%75th Percentile - 0.3 sExperimental
Latest 28-day collection period
Various desktop devicesMany samples (Chrome UX Report)Full visit durationsVarious network connectionsAll Chrome versions
Diagnose performance issues
84
Performance
91
Accessibility
100
Best Practices
92
SEO
84
Performance
91
Accessibility
100
Best Practices
92
SEO
84 FCP+9LCP+18TBT+26CLS+21SI+9 Performance
Values are estimated and may vary. The performance score is calculated directly from these metrics.See calculator.
0–49 50–89 90–100
Final Screenshot
Metrics
First Contentful Paint
0.9 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric.
Largest Contentful Paint
1.7 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric
Total Blocking Time
160 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more about the Total Blocking Time metric.
Cumulative Layout Shift
0.12
Cumulative Layout Shift measures the movement of visible elements within the viewport. Learn more about the Cumulative Layout Shift metric.
Speed Index
1.2 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric.
  • Captured at Mar 27, 2025, 11:38 AM UTC
  • Emulated Desktop with Lighthouse 12.4.0
    Unthrottled CPU/Memory Power: 482 CPU throttling: 1x slowdown (Simulated) Screen emulation: 1350x940, DPR 1 Axe version: 4.10.2
  • Single page session
    This data is taken from a single page session, as opposed to field data summarizing many sessions.
  • Initial page load
  • Custom throttling
    Network throttling: 40 ms TCP RTT, 10,240 kb/s throughput (Simulated) Browser location: Asia
  • Using HeadlessChromium 133.0.6943.141 with lr
    User agent (network): "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/119.0.0.0 Safari/537.36"
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Show audits relevant to:
Diagnostics
Avoid large layout shifts 2 layout shifts found
These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLSCLS
Element
Layout shift score
ホーム 2016.10.272025.03.25 ロジカルシンキングを必要とする背景とは 目次 ロジカルシンキングを必要とする背景とは 解決困難な問題に取り囲…
<article id="post-10" class="article post-10 page type-page status-publish hentry" itemscope="itemscope" itemprop="blogPost" itemtype="https://schema.org/BlogPosting" data-clarity-region="article">
0.109
おすすめ記事 どこがマズイ？なぜなぜ分析 簡単な例でわかる なぜなぜ分析に役立つロジカルシンキング：問題の改善や経営の改善を意図した問題解決の１つの原因分析ツ…
<aside id="custom_html-3" class="widget_text widget widget-sidebar widget-sidebar-standard widget_custom_ht…">
0.011
a.blogcard-wrap > div.blogcard > figure.blogcard-thumbnail > img.blogcard-thumb-image
<img width="160" height="90" src="https://www.ltkensyu.com/wp-content/uploads/2019/01/why-mark-min-160x90.jp…" class="blogcard-thumb-image internal-blogcard-thumb-image wp-post-image" alt="" decoding="async" loading="lazy" srcset="https://www.ltkensyu.com/wp-content/uploads/2019/01/why-mark-min-160x90.jp…" sizes="(max-width: 160px) 100vw, 160px">
Media element lacking an explicit size
Largest Contentful Paint element 1,700 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint elementLCP
Element
問題解決に役立つロジカルシンキング（論理思考）を基礎から学ぶ。 ロジカルシンキング研修.com
<header id="header" class="header ba-fixed cf" itemscope="" itemtype="https://schema.org/WPHeader">
Phase
% of LCP
Timing
TTFB
9%
160 ms
Load Delay
41%
690 ms
Load Time
5%
90 ms
Render Delay
45%
770 ms
Defer offscreen images Potential savings of 206 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn how to defer offscreen images.LCPFCP
URL
Resource Size
Potential Savings
ltkensyu.com
1st party
206.4 KiB
206.4 KiB
header.article-header > div.eye-catch-wrap > figure.eye-catch > img
<img src="https://www.ltkensyu.com/wp-content/uploads/2022/10/TopImage36.jpg" width="1280" height="720" alt="">
…10/TopImage36.jpg
(www.ltkensyu.com)
206.4 KiB
206.4 KiB
Avoid an excessive DOM size 1,056 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn how to avoid an excessive DOM size.TBT
Statistic
Element
Value
Total DOM Elements
1,056
Maximum DOM Depth
×
<span class="gscb_a" id="gs_cb50" aria-hidden="true">
23
Maximum Child Elements
ロジカルシンキングを必要とする背景とは 目次 ロジカルシンキングを必要とする背景とは 解決困難な問題に取り囲まれている 問題を解決する力が要る 講座を通じて独…
<div class="entry-content cf" itemprop="mainEntityOfPage">
34
Reduce unused CSS Potential savings of 138 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.LCPFCP
URL
Transfer Size
Potential Savings
ltkensyu.com
1st party
62.1 KiB
59.1 KiB
…css/cda8090….css?ver=c57ea
(www.ltkensyu.com)
36.5 KiB
33.7 KiB
…css/1d70816….css?ver=be978
(www.ltkensyu.com)
13.8 KiB
13.8 KiB
…css/06b3d3a….css?ver=abb37
(www.ltkensyu.com)
11.8 KiB
11.7 KiB
Unattributable
40.3 KiB
39.8 KiB
#header-container,#header-container .navi,#navi .navi-in>.menu-header .sub-menu,.article h2,.sideba…
28.3 KiB
27.8 KiB
span.PIN_1743075513895_embed_grid { 
  width: 100%;
  max-width: 257px;
  min-width: 140px; … } …
12.0 KiB
12.0 KiB
Google CDN
cdn
41.0 KiB
38.9 KiB
…bUO1BXI8H…/styles__ltr.css
(www.gstatic.com)
41.0 KiB
38.9 KiB
Reduce unused JavaScript Potential savings of 344 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.LCPFCP
URL
Transfer Size
Potential Savings
Google CDN
cdn
430.5 KiB
200.9 KiB
…bUO1BXI8H…/recaptcha__en.js
(www.gstatic.com)
215.2 KiB
101.2 KiB
…bUO1BXI8H…/recaptcha__en.js
(www.gstatic.com)
215.2 KiB
99.7 KiB
Other Google APIs/SDKs
utility
144.8 KiB
88.4 KiB
…75c56d121cde450a/cse_element__ja.js?usqp=CAI%3D
(www.google.com)
94.7 KiB
47.7 KiB
…search/async-ads.js
(cse.google.com)
50.0 KiB
40.7 KiB
Google Tag Manager
tag-manager
141.1 KiB
54.3 KiB
/gtag/js?id=G-G55FP7SF13
(www.googletagmanager.com)
141.1 KiB
54.3 KiB
Eliminate render-blocking resources Potential savings of 40 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn how to eliminate render-blocking resources.LCPFCP
URL
Transfer Size
Potential Savings
Google CDN
cdn
31.3 KiB
240 ms
…3.6.1/jquery.min.js?ver=3.6.1
(ajax.googleapis.com)
31.3 KiB
240 ms
Minify CSS Potential savings of 3 KiB
Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.LCPFCP
URL
Transfer Size
Potential Savings
Other Google APIs/SDKs
utility
9.7 KiB
2.9 KiB
…75c56d121cde450a/default+ja.css
(www.google.com)
9.7 KiB
2.9 KiB
Serve images in next-gen formats Potential savings of 35 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more about modern image formats.LCPFCP
URL
Resource Size
Potential Savings
ltkensyu.com
1st party
206.4 KiB
35.4 KiB
header.article-header > div.eye-catch-wrap > figure.eye-catch > img
<img src="https://www.ltkensyu.com/wp-content/uploads/2022/10/TopImage36.jpg" width="1280" height="720" alt="">
…10/TopImage36.jpg
(www.ltkensyu.com)
206.4 KiB
35.4 KiB
Serve static assets with an efficient cache policy 5 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
URL
Cache TTL
Transfer Size
Pinterest
social
19 KiB
/js/pinit_main.js
(assets.pinterest.com)
5m
19 KiB
Other Google APIs/SDKs
utility
6 KiB
/cse.js?cx=e2d2463f24035e1c2
(cse.google.com)
None
4 KiB
…v4/default.css
(www.google.com)
50m
2 KiB
Google CDN
cdn
3 KiB
…api2/logo_48.png
(www.gstatic.com)
7d
3 KiB
gstatic.com
1 KiB
/faviconV2?client=…
(t0.gstatic.com)
7d
1 KiB
Ensure text remains visible during webfont load
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more about font-display.
URL
Potential Savings
Google Fonts
cdn
10 ms
…v18/KFOmCnqEu….woff2
(fonts.gstatic.com)
0 ms
…v18/KFOlCnqEu….woff2
(fonts.gstatic.com)
0 ms
Avoid serving legacy JavaScript to modern browsers Potential savings of 11 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers. Learn how to serve modern JavaScriptLCPFCP
URL
Potential Savings
ltkensyu.com
1st party
10.7 KiB
…js/e4aeb08….js?ver=4287d
(www.ltkensyu.com)
10.7 KiB
…js/e4aeb08….js?ver=4287d:7:6597
(www.ltkensyu.com)
Array.prototype.forEach
…js/e4aeb08….js?ver=4287d:7:6704
(www.ltkensyu.com)
Array.prototype.filter
…js/1b78179….js?ver=c6067
(www.ltkensyu.com)
0.1 KiB
…js/1b78179….js?ver=c6067:6:86
(www.ltkensyu.com)
@babel/plugin-transform-classes
Minimize third-party usage Third-party code blocked the main thread for 140 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn how to minimize third-party impact.TBT
Third-Party
Transfer Size
Main-Thread Blocking Time
Google CDN
cdn
725 KiB
68 ms
…bUO1BXI8H…/recaptcha__en.js
(www.gstatic.com)
649 KiB
68 ms
…3.6.1/jquery.min.js?ver=3.6.1
(ajax.googleapis.com)
31 KiB
0 ms
…bUO1BXI8H…/styles__ltr.css
(www.gstatic.com)
42 KiB
0 ms
…api2/logo_48.png
(www.gstatic.com)
3 KiB
0 ms
Google Tag Manager
tag-manager
142 KiB
39 ms
/gtag/js?id=G-G55FP7SF13
(www.googletagmanager.com)
142 KiB
39 ms
Other Google APIs/SDKs
utility
233 KiB
35 ms
…api2/anchor?ar=…
(www.google.com)
42 KiB
24 ms
/cse.js?cx=e2d2463f24035e1c2
(cse.google.com)
4 KiB
8 ms
…75c56d121cde450a/cse_element__ja.js?usqp=CAI%3D
(www.google.com)
96 KiB
2 ms
/recaptcha/api.js?render=6Lfe6HQoA…&ver=3.0
(www.google.com)
2 KiB
1 ms
…search/async-ads.js
(cse.google.com)
51 KiB
0 ms
…api2/reload?k=6Lfe6HQoA…
(www.google.com)
21 KiB
0 ms
…75c56d121cde450a/default+ja.css
(www.google.com)
10 KiB
0 ms
…v4/default.css
(www.google.com)
2 KiB
0 ms
…ja/branding.png
(www.google.com)
2 KiB
0 ms
…v2/clear.png
(www.google.com)
2 KiB
0 ms
…api2/clr?k=6Lfe6HQoA…
(www.google.com)
1 KiB
0 ms
…api2/webworker.js?hl=en&v=bUO1BXI8H…
(www.google.com)
1 KiB
0 ms
/s2/favicons?domain=https://www.ltkensyu.com
(www.google.com)
1 KiB
0 ms
Google Fonts
cdn
23 KiB
0 ms
…v18/KFOlCnqEu….woff2
(fonts.gstatic.com)
11 KiB
0 ms
…v18/KFOmCnqEu….woff2
(fonts.gstatic.com)
11 KiB
0 ms
Pinterest
social
19 KiB
0 ms
/js/pinit_main.js
(assets.pinterest.com)
19 KiB
0 ms
/?type=…
(log.pinterest.com)
1 KiB
0 ms
Cloudflare CDN
cdn
5 KiB
0 ms
…3.3.2/jquery-migrate.min.js?ver=3.0.1
(cdnjs.cloudflare.com)
5 KiB
0 ms
gstatic.com
1 KiB
0 ms
/faviconV2?client=…
(t0.gstatic.com)
1 KiB
0 ms
Google Analytics
analytics
1 KiB
0 ms
/g/collect?v=…
(analytics.google.com)
1 KiB
0 ms
Google/Doubleclick Ads
ad
1 KiB
0 ms
…ga/rul?tid=…
(td.doubleclick.net)
1 KiB
0 ms
/g/collect?v=…
(stats.g.doubleclick.net)
0 KiB
0 ms
google.com
0 KiB
0 ms
/generate_204
(clients1.google.com)
0 KiB
0 ms
Avoid long main-thread tasks 7 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn how to avoid long main-thread tasksTBT
URL
Start Time
Duration
Google CDN
cdn
242 ms
…bUO1BXI8H…/recaptcha__en.js
(www.gstatic.com)
3,048 ms
95 ms
…bUO1BXI8H…/recaptcha__en.js
(www.gstatic.com)
2,703 ms
75 ms
…bUO1BXI8H…/recaptcha__en.js
(www.gstatic.com)
2,920 ms
72 ms
ltkensyu.com
1st party
188 ms
…js/css_async.min.js
(www.ltkensyu.com)
1,481 ms
95 ms
…js/37c4e26….js?ver=d9407
(www.ltkensyu.com)
1,651 ms
93 ms
Google Tag Manager
tag-manager
65 ms
/gtag/js?id=G-G55FP7SF13
(www.googletagmanager.com)
1,576 ms
65 ms
Other Google APIs/SDKs
utility
60 ms
…75c56d121cde450a/cse_element__ja.js?usqp=CAI%3D
(www.google.com)
1,744 ms
60 ms
Avoid non-composited animations 33 animated elements found
Animations which are not composited can be janky and increase CLS. Learn how to avoid non-composited animationsCLS
Element
Name
論理思考補足編
<a href="https://www.ltkensyu.com/supplemental/">
Unsupported CSS Property: font-size
font-size
Unsupported CSS Property: padding-left
padding-left
Unsupported CSS Property: padding-right
padding-right
リーダーによるビジョン構築 ロジカルシンキングを身につけたリーダーの皆さんへ：あなたの組織は、ありたい姿、あるべき姿、あり得る姿を統合した進むべき方向を自覚で…
<a href="https://www.ltkensyu.com/supplemental/3-6" class="blogcard-wrap internal-blogcard-wrap a-wrap cf">
Unsupported CSS Property: color
color
ロジカルシンキングで演繹法の使い方！実例に学ぶ妥当性の判定法
<a href="https://www.ltkensyu.com/2309/" class="new-entry-card-link widget-entry-card-link a-wrap">
Unsupported CSS Property: color
color
プライバシーポリシー
<a rel="privacy-policy" href="https://www.ltkensyu.com/privacy-policy/">
Unsupported CSS Property: font-size
font-size
Unsupported CSS Property: padding-left
padding-left
Unsupported CSS Property: padding-right
padding-right
ロジカルシンキングで問題解決！みんなで使う問題解決プロセス！
<a href="https://www.ltkensyu.com/2583/" class="new-entry-card-link widget-entry-card-link a-wrap">
Unsupported CSS Property: color
color
ロジカルシンキング、例題問題と解答・答えのある例題集・本の活用法！
<a href="https://www.ltkensyu.com/1927/" class="new-entry-card-link widget-entry-card-link a-wrap">
Unsupported CSS Property: color
color
ロジカルシンキング記事集
<a href="https://www.ltkensyu.com/articles/">
Unsupported CSS Property: font-size
font-size
Unsupported CSS Property: padding-left
padding-left
Unsupported CSS Property: padding-right
padding-right
ロジックツリーの作成 ロジックツリー展開の例から学ぶ：ロジックツリーは目的に合った切り口を使って、できるだけMECEに（ミッシー：ダブリもモレもなく）分解し、…
<a href="https://www.ltkensyu.com/logicalthinking/1-4/4-1" class="blogcard-wrap internal-blogcard-wrap a-wrap cf">
Unsupported CSS Property: color
color
論理思考テキスト講座
<a href="https://www.ltkensyu.com/logicalthinking/">
Unsupported CSS Property: font-size
font-size
Unsupported CSS Property: padding-left
padding-left
Unsupported CSS Property: padding-right
padding-right
X
<a href="https://x.com/intent/tweet?text=%E3%83%9B%E3%83%BC%E3%83%A0&amp;url=https%3A%2…" class="sns-button share-button twitter-button twitter-share-button-sq x-corp-butt…" target="_blank" rel="nofollow noopener noreferrer" aria-label="Xでシェア">
Unsupported CSS Property: border-top-left-radius
border-top-left-radius
Unsupported CSS Property: border-top-right-radius
border-top-right-radius
Unsupported CSS Property: background-color
background-color
Unsupported CSS Property: color
color
Unsupported CSS Property: border-bottom-left-radius
border-bottom-left-radius
Unsupported CSS Property: border-bottom-right-radius
border-bottom-right-radius
ロジカルシンキングで帰納法と演繹法の活用法！論理ピラミッド構築事例と演習問題！
<a href="https://www.ltkensyu.com/2360/" class="new-entry-card-link widget-entry-card-link a-wrap">
Unsupported CSS Property: color
color
サイトマップ
<a href="https://www.ltkensyu.com/map/">
Unsupported CSS Property: font-size
font-size
Unsupported CSS Property: padding-left
padding-left
Unsupported CSS Property: padding-right
padding-right
どこがマズイ？なぜなぜ分析 簡単な例でわかる なぜなぜ分析に役立つロジカルシンキング：問題の改善や経営の改善を意図した問題解決の１つの原因分析ツールとして、「…
<a href="https://www.ltkensyu.com/supplemental/3-3" class="blogcard-wrap internal-blogcard-wrap a-wrap cf">
Unsupported CSS Property: color
color
ロジカルシンキングにおけるフレームワークとは？フレームワーク思考で問題解決！
<a href="https://www.ltkensyu.com/2182/" class="new-entry-card-link widget-entry-card-link a-wrap">
Unsupported CSS Property: color
color
ホーム
<a href="https://www.ltkensyu.com/" aria-current="page">
Unsupported CSS Property: font-size
font-size
Unsupported CSS Property: padding-left
padding-left
Unsupported CSS Property: padding-right
padding-right
おすすめの無料ロジカルシンキング研修！知る人ぞ知る秘密の講座！
<a href="https://www.ltkensyu.com/2159/" class="new-entry-card-link widget-entry-card-link a-wrap">
Unsupported CSS Property: color
color
“就活のためのロジカルシンキング”とは？おすすめの本ランキングTOP3！
<a href="https://www.ltkensyu.com/1846/" class="new-entry-card-link widget-entry-card-link a-wrap">
Unsupported CSS Property: color
color
ロジカルシンキングで帰納法を使いこなす！概念形成力を磨け！
<a href="https://www.ltkensyu.com/2330/" class="new-entry-card-link widget-entry-card-link a-wrap">
Unsupported CSS Property: color
color
論理思考ビデオ講座
<a href="https://www.ltkensyu.com/video/">
Unsupported CSS Property: font-size
font-size
Unsupported CSS Property: padding-left
padding-left
Unsupported CSS Property: padding-right
padding-right
ロジカルシンキングで問題解決！解決策アイディアの創出方法と例題！
<a href="https://www.ltkensyu.com/2632/" class="new-entry-card-link widget-entry-card-link a-wrap">
Unsupported CSS Property: color
color
お問い合わせ
<a href="https://www.ltkensyu.com/contact/">
Unsupported CSS Property: font-size
font-size
Unsupported CSS Property: padding-left
padding-left
Unsupported CSS Property: padding-right
padding-right
ロジカルシンキングの日常トレーニング方法！アプリの例題の落とし穴！ 「ロジカルシンキング力」（論理的思考力）を向上させるための日常トレーニングの必要性、方法、…
<a href="https://www.ltkensyu.com/2106/" class="blogcard-wrap internal-blogcard-wrap a-wrap cf">
Unsupported CSS Property: color
color
ロジカルシンキングの日常トレーニング方法！アプリの例題の落とし穴！
<a href="https://www.ltkensyu.com/2106/" class="new-entry-card-link widget-entry-card-link a-wrap">
Unsupported CSS Property: color
color
ロジカルシンキングで問題解決！例題で学んでおきたい解決策立案のコツ！
<a href="https://www.ltkensyu.com/2539/" class="new-entry-card-link widget-entry-card-link a-wrap">
Unsupported CSS Property: color
color
Pinterest
<a class="sns-button share-button pinterest-button pinterest-share-button-sq" target="_blank" rel="nofollow noopener noreferrer" data-pin-do="buttonBookmark" data-pin-custom="true" aria-label="Pinterestでシェア" data-pin-log="button_pinit_bookmarklet" data-pin-href="https://www.pinterest.com/pin/create/button/">
Unsupported CSS Property: border-top-left-radius
border-top-left-radius
Unsupported CSS Property: border-top-right-radius
border-top-right-radius
Unsupported CSS Property: background-color
background-color
Unsupported CSS Property: background-color
background-color
Unsupported CSS Property: color
color
Unsupported CSS Property: color
color
Unsupported CSS Property: border-bottom-left-radius
border-bottom-left-radius
Unsupported CSS Property: border-bottom-right-radius
border-bottom-right-radius
ロジカルシンキング、例題問題と解答・答えのある例題集・本の活用法！ 「ロジカルシンキング」を学びながら、あるいは学んだ後で、単なる「わかった」状態から「使える…
<a href="https://www.ltkensyu.com/1927/" class="blogcard-wrap internal-blogcard-wrap a-wrap cf">
Unsupported CSS Property: color
color
ロジカルシンキングで問題解決！例題で問題の設定にチャレンジ！
<a href="https://www.ltkensyu.com/2483/" class="new-entry-card-link widget-entry-card-link a-wrap">
Unsupported CSS Property: color
color
ロジカルシンキングの簡単な例題でわかる！子供におススメの本はこれ！
<a href="https://www.ltkensyu.com/1690/" class="new-entry-card-link widget-entry-card-link a-wrap">
Unsupported CSS Property: color
color
ロジカルシンキングで問題解決！みんなで使う問題解決プロセス！ 普遍的な「問題解決プロセス」を紹介するとともに、問題解決に取組む際の大事なステップの要点とプロセ…
<a href="https://www.ltkensyu.com/2583" class="blogcard-wrap internal-blogcard-wrap a-wrap cf">
Unsupported CSS Property: color
color
ロジカルシンキングで因果関係図の作成法！因果関係の解明・例題と解答
<a href="https://www.ltkensyu.com/2430/" class="new-entry-card-link widget-entry-card-link a-wrap">
Unsupported CSS Property: color
color
ロジカルシンキングのロジックツリー例題でトレーニング！MECEでもNGな訳とは？
<a href="https://www.ltkensyu.com/2241/" class="new-entry-card-link widget-entry-card-link a-wrap">
Unsupported CSS Property: color
color
Facebook
<a href="//www.facebook.com/sharer/sharer.php?u=https%3A%2F%2Fwww.ltkensyu.com%2F&amp;t…" class="sns-button share-button facebook-button facebook-share-button-sq" target="_blank" rel="nofollow noopener noreferrer" aria-label="Facebookでシェア">
Unsupported CSS Property: border-top-left-radius
border-top-left-radius
Unsupported CSS Property: border-top-right-radius
border-top-right-radius
Unsupported CSS Property: background-color
background-color
Unsupported CSS Property: color
color
Unsupported CSS Property: border-bottom-left-radius
border-bottom-left-radius
Unsupported CSS Property: border-bottom-right-radius
border-bottom-right-radius
ロジカルシンキングの初心者でも例題から学べる本・わかりやすい入門書とは？
<a href="https://www.ltkensyu.com/1813/" class="new-entry-card-link widget-entry-card-link a-wrap">
Unsupported CSS Property: color
color
Avoid chaining critical requests 1 chain found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn how to avoid chaining critical requests.
Maximum critical path latency: 256.373 ms
Initial Navigation
https://www.ltkensyu.com
…3.6.1/jquery.min.js?ver=3.6.1
(ajax.googleapis.com)
- 21.143 ms, 31.31 KiB
More information about the performance of your application. These numbers don't directly affect the Performance score.
Passed audits (20)
Show Hide
Properly size images
Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.LCPFCP
Minify JavaScript
Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.LCPFCP
Efficiently encode images
Optimized images load faster and consume less cellular data. Learn how to efficiently encode images.LCPFCP
Enable text compression
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more about text compression.LCPFCP
Preconnect to required origins
Consider adding preconnect or dns-prefetch resource hints to establish early connections to important third-party origins. Learn how to preconnect to required origins.LCPFCP
Initial server response time was short Root document took 170 ms
Keep the server response time for the main document short because all other requests depend on it. Learn more about the Time to First Byte metric.LCPFCP
URL
Time Spent
ltkensyu.com
1st party
170 ms
https://www.ltkensyu.com
170 ms
Avoid multiple page redirects
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.LCPFCP
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more about efficient video formatsLCPFCP
Remove duplicate modules in JavaScript bundles
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity. LCPFCP
Preload Largest Contentful Paint image
If the LCP element is dynamically added to the page, you should preload the image in order to improve LCP. Learn more about preloading LCP elements.LCP
Avoids enormous network payloads Total size was 1,812 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
URL
Transfer Size
Google CDN
cdn
648.6 KiB
…bUO1BXI8H…/recaptcha__en.js
(www.gstatic.com)
216.2 KiB
…bUO1BXI8H…/recaptcha__en.js
(www.gstatic.com)
216.2 KiB
…bUO1BXI8H…/recaptcha__en.js
(www.gstatic.com)
216.2 KiB
ltkensyu.com
1st party
405.0 KiB
…10/TopImage36.jpg
(www.ltkensyu.com)
206.9 KiB
…webfonts/fa-solid-900.woff2
(www.ltkensyu.com)
77.0 KiB
…webfonts/fa-brands-400.woff2
(www.ltkensyu.com)
75.5 KiB
https://www.ltkensyu.com
45.7 KiB
Other Google APIs/SDKs
utility
146.5 KiB
…75c56d121cde450a/cse_element__ja.js?usqp=CAI%3D
(www.google.com)
95.7 KiB
…search/async-ads.js
(cse.google.com)
50.8 KiB
Google Tag Manager
tag-manager
142.2 KiB
/gtag/js?id=G-G55FP7SF13
(www.googletagmanager.com)
142.2 KiB
User Timing marks and measures
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more about User Timing marks.
JavaScript execution time 0.9 s
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.TBT
URL
Total CPU Time
Script Evaluation
Script Parse
Google CDN
cdn
714 ms
630 ms
25 ms
…bUO1BXI8H…/recaptcha__en.js
(www.gstatic.com)
714 ms
630 ms
25 ms
Unattributable
283 ms
9 ms
0 ms
data:text/javascript;base64,KGZ1bmN0aW9uKCQpe2Z1bmN0aW9uIHN0aWN…
163 ms
6 ms
0 ms
Unattributable
120 ms
3 ms
0 ms
Google Tag Manager
tag-manager
220 ms
80 ms
8 ms
/gtag/js?id=G-G55FP7SF13
(www.googletagmanager.com)
220 ms
80 ms
8 ms
ltkensyu.com
1st party
213 ms
10 ms
0 ms
https://www.ltkensyu.com
213 ms
10 ms
0 ms
Other Google APIs/SDKs
utility
208 ms
158 ms
2 ms
…api2/anchor?ar=…
(www.google.com)
109 ms
97 ms
2 ms
/cse.js?cx=e2d2463f24035e1c2
(cse.google.com)
99 ms
61 ms
0 ms
Minimizes main-thread work 1.8 s
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 workTBT
Category
Time Spent
Script Evaluation
1,045 ms
Style & Layout
404 ms
Other
194 ms
Parse HTML & CSS
65 ms
Script Parsing & Compilation
53 ms
Rendering
31 ms
Garbage Collection
30 ms
Lazy load third-party resources with facades
Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required. Learn how to defer third-parties with a facade.TBT
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint. Learn more about optimal lazy loading.LCP
Element
問題解決に役立つロジカルシンキング（論理思考）を基礎から学ぶ。 ロジカルシンキング研修.com
<header id="header" class="header ba-fixed cf" itemscope="" itemtype="https://schema.org/WPHeader">
Uses passive listeners to improve scrolling performance
Consider marking your touch and wheel event listeners as passive to improve your page's scroll performance. Learn more about adopting passive event listeners.
Avoids document.write()
For users on slow connections, external scripts dynamically injected via document.write() can delay page load by tens of seconds. Learn how to avoid document.write().
Image elements have explicit width and height
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensionsCLS
Has a <meta name="viewport"> tag with width or initial-scale
A <meta name="viewport"> not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn more about using the viewport meta tag.
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
Background and foreground colors do not have a sufficient contrast ratio.
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
Failing Elements
　1）人にわかるように伝えられる
<span style="color: #ff0000;">
ホーム 2016.10.272025.03.25 ロジカルシンキングを必要とする背景とは 目次 ロジカルシンキングを必要とする背景とは 解決困難な問題に取り囲…
<main id="main" class="main" itemscope="" itemtype="https://schema.org/Blog">
　2）問題解決に取り組める
<span style="color: #ff0000;">
ホーム 2016.10.272025.03.25 ロジカルシンキングを必要とする背景とは 目次 ロジカルシンキングを必要とする背景とは 解決困難な問題に取り囲…
<main id="main" class="main" itemscope="" itemtype="https://schema.org/Blog">
These are opportunities to improve the legibility of your content.
Tables and lists
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.
Failing Elements
ビデオ講座で学ぶなら、さほど難しくない 基礎を理解すれば自信が持てる 実務で活用しなければ身に付かない どのような効果が期待できる？ 困りごと（コミュニケーシ…
<ul>
ビデオ講座で学ぶなら、さほど難しくない 基礎を理解すれば自信が持てる 実務で活用しなければ身に付かない どのような効果が期待できる？ 困りごと（コミュニケーシ…
<ul>
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Navigation
Heading elements are not in a sequentially-descending order
Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.
Failing Elements
ビデオ講座で学ぶなら、さほど難しくない
<h4>
These are opportunities to improve keyboard navigation in your application.
Additional items to manually check (10)
Show Hide
Interactive controls are keyboard focusable
Custom interactive controls are keyboard focusable and display a focus indicator. Learn how to make custom controls focusable.
Interactive elements indicate their purpose and state
Interactive elements, such as links and buttons, should indicate their state and be distinguishable from non-interactive elements. Learn how to decorate interactive elements with affordance hints.
The page has a logical tab order
Tabbing through the page follows the visual layout. Users cannot focus elements that are offscreen. Learn more about logical tab ordering.
Visual order on the page follows DOM order
DOM order matches the visual order, improving navigation for assistive technology. Learn more about DOM and visual ordering.
User focus is not accidentally trapped in a region
A user can tab into and out of any control or region without accidentally trapping their focus. Learn how to avoid focus traps.
The user's focus is directed to new content added to the page
If new content, such as a dialog, is added to the page, the user's focus is directed to it. Learn how to direct focus to new content.
HTML5 landmark elements are used to improve navigation
Landmark elements (<main>, <nav>, etc.) are used to improve the keyboard navigation of the page for assistive technology. Learn more about landmark elements.
Offscreen content is hidden from assistive technology
Offscreen content is hidden with display: none or aria-hidden=true. Learn how to properly hide offscreen content.
Custom controls have associated labels
Custom interactive controls have associated labels, provided by aria-label or aria-labelledby. Learn more about custom controls and labels.
Custom controls have ARIA roles
Custom interactive controls have appropriate ARIA roles. Learn how to add roles to custom controls.
These items address areas which an automated testing tool cannot cover. Learn more in our guide on conducting an accessibility review.
Passed audits (25)
Show Hide
[aria-*] attributes match their roles
Each ARIA role supports a specific subset of aria-* attributes. Mismatching these invalidates the aria-* attributes. Learn how to match ARIA attributes to their roles.
[aria-hidden="true"] is not present on the document <body>
Assistive technologies, like screen readers, work inconsistently when aria-hidden="true" is set on the document <body>. Learn how aria-hidden affects the document body.
[role]s have all required [aria-*] attributes
Some ARIA roles have required attributes that describe the state of the element to screen readers. Learn more about roles and required attributes.
[aria-*] attributes have valid values
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more about valid values for ARIA attributes.
[aria-*] attributes are valid and not misspelled
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid names. Learn more about valid ARIA attributes.
Buttons have an accessible name
When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.
Image elements have [alt] attributes
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.
[user-scalable="no"] is not used in the <meta name="viewport"> element and the [maximum-scale] attribute is not less than 5.
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.
ARIA attributes are used as specified for the element's role
Some ARIA attributes are only allowed on an element under certain conditions. Learn more about conditional ARIA attributes.
[aria-hidden="true"] elements do not contain focusable descendents
Focusable descendents within an [aria-hidden="true"] element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how aria-hidden affects focusable elements.
Elements use only permitted ARIA attributes
Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.
[role] values are valid
ARIA roles must have valid values in order to perform their intended accessibility functions. Learn more about valid ARIA roles.
Document has a <title> element
The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. Learn more about document titles.
<html> element has a [lang] attribute
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.
<html> element has a valid value for its [lang] attribute
Specifying a valid BCP 47 language helps screen readers announce text properly. Learn how to use the lang attribute.
Form elements have associated labels
Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.
Links are distinguishable without relying on color.
Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.
Links have a discernible name
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.
List items (<li>) are contained within <ul>, <ol> or <menu> parent elements
Screen readers require list items (<li>) to be contained within a parent <ul>, <ol> or <menu> to be announced properly. Learn more about proper list structure.
No element has a [tabindex] value greater than 0
A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the tabindex attribute.
Touch targets have sufficient size and spacing.
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.
Uses ARIA roles only on compatible elements
Many HTML elements can only be assigned certain ARIA roles. Using ARIA roles where they are not allowed can interfere with the accessibility of the web page. Learn more about ARIA roles.
Deprecated ARIA roles were not used
Deprecated ARIA roles may not be processed correctly by assistive technology. Learn more about deprecated ARIA roles.
Image elements do not have [alt] attributes that are redundant text.
Informative elements should aim for short, descriptive alternative text. Alternative text that is exactly the same as the text adjacent to the link or image is potentially confusing for screen reader users, because the text will be read twice. Learn more about the alt attribute.
Tables have different content in the summary attribute and <caption>.
The summary attribute should describe the table structure, while <caption> should have the onscreen title. Accurate table mark-up helps users of screen readers. Learn more about summary and caption.
Not applicable (29)
Show Hide
[accesskey] values are unique
Access keys let users quickly focus a part of the page. For proper navigation, each access key must be unique. Learn more about access keys.
button, link, and menuitem elements have accessible names
When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to make command elements more accessible.
Elements with role="dialog" or role="alertdialog" have accessible names.
ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.
ARIA input fields have accessible names
When an input field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about input field labels.
ARIA meter elements have accessible names
When a meter element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to name meter elements.
ARIA progressbar elements have accessible names
When a progressbar element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to label progressbar elements.
Elements with an ARIA [role] that require children to contain a specific [role] have all required children.
Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.
[role]s are contained by their required parent element
Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. Learn more about ARIA roles and required parent element.
Elements with the role=text attribute do not have focusable descendents.
Adding role=text around a text node split by markup enables VoiceOver to treat it as one phrase, but the element's focusable descendents will not be announced. Learn more about the role=text attribute.
ARIA toggle fields have accessible names
When a toggle field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about toggle fields.
ARIA tooltip elements have accessible names
When a tooltip element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to name tooltip elements.
ARIA treeitem elements have accessible names
When a treeitem element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about labeling treeitem elements.
The page contains a heading, skip link, or landmark region
Adding ways to bypass repetitive content lets keyboard users navigate the page more efficiently. Learn more about bypass blocks.
<dl>'s contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.
When definition lists are not properly marked up, screen readers may produce confusing or inaccurate output. Learn how to structure definition lists correctly.
Definition list items are wrapped in <dl> elements
Definition list items (<dt> and <dd>) must be wrapped in a parent <dl> element to ensure that screen readers can properly announce them. Learn how to structure definition lists correctly.
ARIA IDs are unique
The value of an ARIA ID must be unique to prevent other instances from being overlooked by assistive technologies. Learn how to fix duplicate ARIA IDs.
No form fields have multiple labels
Form fields with multiple labels can be confusingly announced by assistive technologies like screen readers which use either the first, the last, or all of the labels. Learn how to use form labels.
<frame> or <iframe> elements have a title
Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.
<html> element has an [xml:lang] attribute with the same base language as the [lang] attribute.
If the webpage does not specify a consistent language, then the screen reader might not announce the page's text correctly. Learn more about the lang attribute.
Input buttons have discernible text.
Adding discernable and accessible text to input buttons may help screen reader users understand the purpose of the input button. Learn more about input buttons.
<input type="image"> elements have [alt] text
When an image is being used as an <input> button, providing alternative text can help screen reader users understand the purpose of the button. Learn about input image alt text.
The document does not use <meta http-equiv="refresh">
Users do not expect a page to refresh automatically, and doing so will move focus back to the top of the page. This may create a frustrating or confusing experience. Learn more about the refresh meta tag.
<object> elements have alternate text
Screen readers cannot translate non-text content. Adding alternate text to <object> elements helps screen readers convey meaning to users. Learn more about alt text for object elements.
Select elements have associated label elements.
Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the select element.
Cells in a <table> element that use the [headers] attribute refer to table cells within the same table.
Screen readers have features to make navigating tables easier. Ensuring <td> cells using the [headers] attribute only refer to other cells in the same table may improve the experience for screen reader users. Learn more about the headers attribute.
<th> elements and elements with [role="columnheader"/"rowheader"] have data cells they describe.
Screen readers have features to make navigating tables easier. Ensuring table headers always refer to some set of cells may improve the experience for screen reader users. Learn more about table headers.
[lang] attributes have a valid value
Specifying a valid BCP 47 language on elements helps ensure that text is pronounced correctly by a screen reader. Learn how to use the lang attribute.
<video> elements contain a <track> element with [kind="captions"]
When a video provides a caption it is easier for deaf and hearing impaired users to access its information. Learn more about video captions.
100
Best Practices
Trust and Safety
Ensure CSP is effective against XSS attacks
A strong Content Security Policy (CSP) significantly reduces the risk of cross-site scripting (XSS) attacks. Learn how to use a CSP to prevent XSS
Description
Directive
Severity
No CSP found in enforcement mode
High
Use a strong HSTS policy
Deployment of the HSTS header significantly reduces the risk of downgrading HTTP connections and eavesdropping attacks. A rollout in stages, starting with a low max-age is recommended. Learn more about using a strong HSTS policy.
Description
Directive
Severity
No `preload` directive found
preload
Medium
Ensure proper origin isolation with COOP
The Cross-Origin-Opener-Policy (COOP) can be used to isolate the top-level window from other documents such as pop-ups. Learn more about deploying the COOP header.
Description
Directive
Severity
No COOP header found
High
Mitigate clickjacking with XFO or CSP
The X-Frame-Options (XFO) header or the frame-ancestors directive in the Content-Security-Policy (CSP) header control where a page can be embedded. These can mitigate clickjacking attacks by blocking some or all sites from embedding the page. Learn more about mitigating clickjacking.
Description
Severity
No frame control policy found
High
General
Detected JavaScript libraries
All front-end JavaScript libraries detected on the page. Learn more about this JavaScript library detection diagnostic audit.
Name
Version
jQuery
3.6.1
core-js
core-js-global@3.35.1
Passed audits (14)
Show Hide
Uses HTTPS
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more about HTTPS.
Avoids deprecated APIs
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
Avoids third-party cookies
Chrome is moving towards a new experience that allows users to choose to browse without third-party cookies. Learn more about third-party cookies.
Allows users to paste into input fields
Preventing input pasting is a bad practice for the UX, and weakens security by blocking password managers.Learn more about user-friendly input fields.
Avoids requesting the geolocation permission on page load
Users are mistrustful of or confused by sites that request their location without context. Consider tying the request to a user action instead. Learn more about the geolocation permission.
Avoids requesting the notification permission on page load
Users are mistrustful of or confused by sites that request to send notifications without context. Consider tying the request to user gestures instead. Learn more about responsibly getting permission for notifications.
Displays images with correct aspect ratio
Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.
Serves images with appropriate resolution
Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn how to provide responsive images.
Has a <meta name="viewport"> tag with width or initial-scale
A <meta name="viewport"> not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn more about using the viewport meta tag.
Page has the HTML doctype
Specifying a doctype prevents the browser from switching to quirks-mode. Learn more about the doctype declaration.
Properly defines charset
A character encoding declaration is required. It can be done with a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header. Learn more about declaring the character encoding.
No browser errors logged to the console
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
No issues in the Issues panel in Chrome Devtools
Issues logged to the Issues panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.
Page has valid source maps
Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.
URL
Map URL
Cloudflare CDN
cdn
…3.3.2/jquery-migrate.min.js?ver=3.0.1
(cdnjs.cloudflare.com)
…3.3.2/jquery-migrate.min.map
(cdnjs.cloudflare.com)
Warning: missing 2 items in `.sourcesContent`
Not applicable (2)
Show Hide
Redirects HTTP traffic to HTTPS
Make sure that you redirect all HTTP traffic to HTTPS in order to enable secure web features for all your users. Learn more.
Document uses legible font sizes
Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px. Learn more about legible font sizes.
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.
Crawling and Indexing
Links are not crawlable
Search engines may use href attributes on links to crawl websites. Ensure that the href attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable
Uncrawlable Link
Pinterest
<a class="sns-button share-button pinterest-button pinterest-share-button-sq" target="_blank" rel="nofollow noopener noreferrer" data-pin-do="buttonBookmark" data-pin-custom="true" aria-label="Pinterestでシェア" data-pin-log="button_pinit_bookmarklet" data-pin-href="https://www.pinterest.com/pin/create/button/">
To appear in search results, crawlers need access to your app.
Additional items to manually check (1)
Show Hide
Structured data is valid
Run the Structured Data Testing Tool and the Structured Data Linter to validate structured data. Learn more about Structured Data.
Run these additional validators on your site to check additional SEO best practices.
Passed audits (9)
Show Hide
Page isn’t blocked from indexing
Search engines are unable to include your pages in search results if they don't have permission to crawl them. Learn more about crawler directives.
Document has a <title> element
The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. Learn more about document titles.
Document has a meta description
Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.
Page has successful HTTP status code
Pages with unsuccessful HTTP status codes may not be indexed properly. Learn more about HTTP status codes.
Links have descriptive text
Descriptive link text helps search engines understand your content. Learn how to make links more accessible.
robots.txt is valid
If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more about robots.txt.
Image elements have [alt] attributes
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.
Document has a valid hreflang
hreflang links tell search engines what version of a page they should list in search results for a given language or region. Learn more about hreflang.
Document has a valid rel=canonical
Canonical links suggest which URL to show in search results. Learn more about canonical links.