監査レポート対象

soedja.com

最終監査日 Aug 17, 2026

Performance needs significant optimization to improve user experience and search rankings

The site has a strong SEO foundation with high scores but suffers from poor performance metrics including a slow Largest Contentful Paint and high Total Blocking Time. Several opportunities exist to reduce JavaScript bloat and improve resource loading.

0/100
総合
05090100

スコアプロファイル

カテゴリー別インサイト

パフォーマンス73

LCP is 4876ms and TBT is 232ms which are above recommended thresholds. There are multiple opportunities to reduce unused JavaScript and optimize resource loading.

SEO92

SEO score is 92 with no major issues identified. The site has proper meta tags, structured data, and canonical tags in place.

アクセシビリティ100

Accessibility score is 100 with no critical issues reported.

ベストプラクティス100

Best Practices score is 100 with no critical issues reported.

AI対応度100

AI readiness score is 100 with no critical issues reported.

パフォーマンス指標

4.9s
Largest Contentful Paint
ラボ
0.03
Cumulative Layout Shift
ラボ
232ms
Total Blocking Time
ラボ
1.4s
First Contentful Paint
ラボ
2.1 MB
ページ容量
ラボ
1.28 g
訪問あたりのCO2
ラボ

マーケティング対応度

ウェブ解析

あり

広告ピクセル

あり

ライブチャット

なし

ブログ・コンテンツ

あり

料金ページ

なし

メール取得

あり

AIクローラーのアクセス

ChatGPT

許可

Claude

許可

Perplexity

許可

Gemini

許可

Common Crawl

許可

llms.txt

あり

構造化データ

あり

検出された技術とツール

Google AnalyticsMeta PixelNext.js

ソーシャルの存在感

競合と比較

改善提案

17 件の問題

Remove unused JavaScript

Est savings of 286 KiB

修正方法

Use tools like Webpack Bundle Analyzer or Source Maps to identify and remove unused JavaScript code. Implement tree shaking to eliminate dead code.

インパクト

Reduce payload size by 286 KiB

Webpack Bundle AnalyzerTree Shaking

Optimize image delivery

Est savings of 57 KiB

修正方法

Convert images to next-gen formats like WebP or AVIF. Use responsive image attributes such as srcset and sizes to serve appropriately sized images.

インパクト

Reduce image payload by 57 KiB

WebPAVIFsrcsetsizes

Defer non-critical JavaScript

Minimize main-thread work of 5.7 s

修正方法

Identify and defer non-critical JavaScript using the async or defer attributes. Move JavaScript execution to after the page is interactive.

インパクト

Reduce main-thread work by 5.7 s

asyncdefer

Improve cache lifetimes

Est savings of 214 KiB

修正方法

Set appropriate HTTP caching headers for static assets such as images and CSS. Use long cache lifetimes for assets that do not change frequently.

インパクト

Reduce network requests by 214 KiB

HTTP Caching Headers

Reduce JavaScript execution time

3.5 s

修正方法

Profile JavaScript execution using Chrome DevTools. Optimize or split large functions into smaller ones. Consider lazy loading non-essential scripts.

インパクト

Reduce JavaScript execution time by 3.5 s

Chrome DevToolsLazy Loading

Eliminate render-blocking resources

Est savings of 710 ms

修正方法

Identify and defer render-blocking CSS and JavaScript. Use asynchronous loading for non-critical resources and inline critical CSS.

インパクト

Reduce render-blocking time by 710 ms

Async LoadingInline Critical CSS

Preload key assets

Initial server response time was short at 30 ms

修正方法

Use link preload to prioritize loading of critical resources. Add <link rel="preload"> for fonts, images, and scripts that are needed early.

インパクト

Improve load time by prioritizing critical assets

Link Preload

Avoid legacy JavaScript

Est savings of 68 KiB

修正方法

Replace or update legacy JavaScript libraries. Use modern ES6+ features and modular code structures to reduce overhead.

インパクト

Reduce JavaScript payload by 68 KiB

ES6+Modular Code

Reduce duplicated JavaScript

Est savings of 8 KiB

修正方法

Identify and remove duplicate JavaScript files. Consolidate shared code into common modules or libraries.

インパクト

Reduce JavaScript payload by 8 KiB

Code SplittingModule Consolidation

Implement HTTP/2

No specific finding but performance can benefit

修正方法

Ensure the site is served over HTTP/2 to enable multiplexing and reduce latency for multiple requests.

インパクト

Improve overall performance and reduce load times

HTTP/2

Optimize LCP element

LCP is 4876ms

修正方法

Identify the LCP element and optimize its loading. Reduce the size of the element or defer non-critical content until after the LCP.

インパクト

Reduce LCP time by optimizing the largest content element

LCP OptimizationCritical Rendering Path

Fix Total Blocking Time

Total Blocking Time is 232ms

修正方法

Profile and reduce long tasks on the main thread. Defer non-essential JavaScript and optimize rendering processes.

インパクト

Reduce Total Blocking Time by 232ms

Chrome DevToolsMain Thread Optimization

Enable Content-Security-Policy header

No Content-Security-Policy header

修正方法

Configure the server to include the Content-Security-Policy HTTP header to prevent potential security risks and improve performance.

インパクト

Enhance security and potentially improve performance

Content-Security-Policy

Improve Time to Interactive

Time to Interactive is 9.0 s

修正方法

Optimize JavaScript execution and reduce the number of long tasks. Prioritize critical resources and use lazy loading for non-essential elements.

インパクト

Reduce Time to Interactive by optimizing JavaScript and resource loading

JavaScript OptimizationLazy Loading

改善して製品を成長させませんか?

soedja.com website audit and score | Soedja