Skip to content
https://seesaa.net

Lighthouse Mobile

· 0 checks — Mobile Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.
SCORE
0
GRADE
FIX
0
REVIEW
0
PASS
0
INFO
0

Detailed Report

Audit breakdown by category with detailed findings.

51

Performance

Insights

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling

Why this matters

Performance issues directly impact user engagement and conversion rates.

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

Why this matters

Performance issues directly impact user engagement and conversion rates.

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

Why this matters

Performance issues directly impact user engagement and conversion rates.

RequestCache TTLTransfer Size
/image/E382B9E382AFE383AAE383BCE383B3E382B7E383A7E38383E3...0.0 ms2.6 MiB
brow2ing.up.seesaa.net/image/image-3bd53.png0.0 ms1.5 MiB
/image/E382B9E382AFE383AAE383BCE383B3E382B7E383A7E38383E3...0.0 ms1.1 MiB
blog.seesaa.jp/portal/img/main.jpg0.0 ms327.9 KiB
ebishoku.up.seesaa.net/image/30146-5c817.png0.0 ms193.9 KiB
/image/1C59B941-B257-4EC6-BCD7-3D13C753C1C7-thumbnail2.jpeg0.0 ms186.8 KiB
test2019test20.up.seesaa.net/image/E784A1E9A18C806_20260422073448-thumbnail2.png0.0 ms146.1 KiB
sinapon16.up.seesaa.net/image/PXL_20260419_0124176727E2-thumbnail2.jpg0.0 ms125.8 KiB
packyaramared.up.seesaa.net/image/E784A1E9A18C798_20260422065749-thumbnail2.png0.0 ms124.7 KiB
tv-point.up.seesaa.net/image/travel_kuji_200200.jpg0.0 ms101.9 KiB
youknow55.up.seesaa.net/image/81YQJPZYk5L-thumbnail2.jpg0.0 ms96.9 KiB
zoroku24.up.seesaa.net/image/20260422070306-thumbnail2.jpg0.0 ms95.9 KiB
aitoheiwanocranking.up.seesaa.net/image/-nmefpe-thumbnail2.jpg0.0 ms94.6 KiB
yassyworld-tsuiteru.up.seesaa.net/image/IMG_6293-thumbnail2.jpeg0.0 ms91.4 KiB
yabuska.up.seesaa.net/image/260421201638143-thumbnail2.JPG0.0 ms81.1 KiB
blog.seesaa.jp/portal/css/webfonts/fa-solid-900.woff20.0 ms74.2 KiB
vsnp.up.seesaa.net/image/kaigo_rourou_easy-7ba48.png14400.0 s104.0 KiB
news4wide.up.seesaa.net/image/hate_speech.png14400.0 s97.5 KiB
calciomatome.up.seesaa.net/image/ACLEE38388E383ADE38395E382A3E383BC.jpg0.0 ms59.8 KiB
friskies.up.seesaa.net/image/IMG_20260422_072204-thumbnail2.jpg0.0 ms40.5 KiB
mv-gossip.up.seesaa.net/image/12-c61c3.png14400.0 s53.7 KiB
blog.seesaa.jp/portal/img/noimage.png0.0 ms24.7 KiB
blog.seesaa.jp/portal/css/sp.css?v=1.0.80.0 ms21.6 KiB
js.ad-stir.com/js/adstir.js3600.0 s25.1 KiB
blog.seesaa.jp/portal/img/svg/logo.svg0.0 ms2.8 KiB
dmp.im-apps.net/sdk/im-uid.js5789.0 s3.0 KiB
blog.seesaa.jp/portal/img/svg/domain.svg0.0 ms1.9 KiB
blog.seesaa.jp/portal/img/svg/ads.svg0.0 ms1.2 KiB
blog.seesaa.jp/portal/img/svg/blogs_x2.svg0.0 ms1.2 KiB
blog.seesaa.jp/portal/img/svg/podcast.svg0.0 ms1.1 KiB
blog.seesaa.jp/portal/img/svg/hdd.svg0.0 ms914 B
blog.seesaa.jp/portal/img/svg/ssl.svg0.0 ms781 B
blog.seesaa.jp/portal/img/svg/rss.svg0.0 ms757 B
blog.seesaa.jp/portal/js/sp.js?v=1.0.80.0 ms707 B
pagead2.googlesyndication.com/pagead/js/google_top_exp.js?fcd=true1209600.0 s67 B

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:label label:Subpart valueType:text] map[key:duration label:Duration valueType:ms]]
items: [map[duration:1689.726 label:Time to first byte subpart:timeToFirstByte] map[duration:597.772 label:Resource load delay subpart:resourceLoadDelay] map[duration:1626.296 label:Resource load duration subpart:resourceLoadDuration] map[duration:43.231 label:Element render delay subpart:elementRenderDelay]]
lhId: page-0-DIV
nodeLabel: アフィリエイトからまとめまで Seesaaブログで思いどおりに 新しくブログをはじめたい方へ
path: 1,HTML,1,BODY,3,DIV,0,DIV
selector: body > div.wrapper > div.section-index-header
snippet: <div class="section-index-header">

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

lhId: page-0-DIV
nodeLabel: アフィリエイトからまとめまで Seesaaブログで思いどおりに 新しくブログをはじめたい方へ
path: 1,HTML,1,BODY,3,DIV,0,DIV
selector: body > div.wrapper > div.section-index-header
snippet: <div class="section-index-header">

Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

Why this matters

Performance issues directly impact user engagement and conversion rates.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.
title: Preconnected origins
value: no origins were preconnected
description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.
title: Preconnect candidates

Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLResource SizeEst Savings
a > div.media > div.thumb > div.image-holder a > div.media > div.thumb > div.image-holder
/image/E382B9E382AFE383AAE383BCE383B3E382B7E383A7E38383E3...2.6 MiB2.2 MiB
a > div.media > div.thumb > div.image-holder a > div.media > div.thumb > div.image-holder
brow2ing.up.seesaa.net/image/image-3bd53.png1.5 MiB1.2 MiB
a > div.media > div.thumb > div.image-holder a > div.media > div.thumb > div.image-holder
/image/E382B9E382AFE383AAE383BCE383B3E382B7E383A7E38383E3...1.1 MiB983.9 KiB
a > div.media > div.thumb > div.image-holder a > div.media > div.thumb > div.image-holder
ebishoku.up.seesaa.net/image/30146-5c817.png193.6 KiB179.0 KiB
a > div.media > div.thumb > div.image-holder a > div.media > div.thumb > div.image-holder
/image/1C59B941-B257-4EC6-BCD7-3D13C753C1C7-thumbnail2.jpeg186.5 KiB122.4 KiB
a > div.media > div.thumb > div.image-holder a > div.media > div.thumb > div.image-holder
packyaramared.up.seesaa.net/image/E784A1E9A18C798_20260422065749-thumbnail2.png124.4 KiB111.9 KiB
a > div.media > div.thumb > div.image-holder a > div.media > div.thumb > div.image-holder
vsnp.up.seesaa.net/image/kaigo_rourou_easy-7ba48.png103.8 KiB80.2 KiB
li.cover > a > div.cover > div.image-holder li.cover > a > div.cover > div.image-holder
test2019test20.up.seesaa.net/image/E784A1E9A18C806_20260422073448-thumbnail2.png145.8 KiB79.1 KiB
a > div.media > div.thumb > div.image-holder a > div.media > div.thumb > div.image-holder
sinapon16.up.seesaa.net/image/PXL_20260419_0124176727E2-thumbnail2.jpg125.5 KiB75.5 KiB
a > div.media > div.thumb > div.image-holder a > div.media > div.thumb > div.image-holder
news4wide.up.seesaa.net/image/hate_speech.png97.3 KiB73.2 KiB
li.cover > a > div.cover > div.image-holder li.cover > a > div.cover > div.image-holder
yassyworld-tsuiteru.up.seesaa.net/image/IMG_6293-thumbnail2.jpeg91.1 KiB63.0 KiB
a > div.media > div.thumb > div.image-holder a > div.media > div.thumb > div.image-holder
zoroku24.up.seesaa.net/image/20260422070306-thumbnail2.jpg95.6 KiB53.2 KiB
li.cover > a > div.cover > div.image-holder li.cover > a > div.cover > div.image-holder
youknow55.up.seesaa.net/image/81YQJPZYk5L-thumbnail2.jpg96.6 KiB49.6 KiB
a > div.media > div.thumb > div.image-holder a > div.media > div.thumb > div.image-holder
aitoheiwanocranking.up.seesaa.net/image/-nmefpe-thumbnail2.jpg94.4 KiB44.4 KiB
li.cover > a > div.cover > div.image-holder li.cover > a > div.cover > div.image-holder
yabuska.up.seesaa.net/image/260421201638143-thumbnail2.JPG80.9 KiB30.9 KiB
a > div.media > div.thumb > div.image-holder a > div.media > div.thumb > div.image-holder
calciomatome.up.seesaa.net/image/ACLEE38388E383ADE38395E382A3E383BC.jpg59.7 KiB29.0 KiB
a > div.media > div.thumb > div.image-holder a > div.media > div.thumb > div.image-holder
mv-gossip.up.seesaa.net/image/12-c61c3.png53.5 KiB24.4 KiB
a > div.media > div.thumb > div.image-holder a > div.media > div.thumb > div.image-holder
friskies.up.seesaa.net/image/IMG_20260422_072204-thumbnail2.jpg40.3 KiB23.6 KiB

These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 1.6 s
URLTime Spent
seesaa.net/1.6 s
blog.seesaa.jp/0.0 ms

Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Diagnostics

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work

Why this matters

Performance issues directly impact user engagement and conversion rates.

CategoryTime Spent
Style & Layout1.2 s
Script Evaluation1.1 s
Other836 ms
Script Parsing & Compilation211 ms
Rendering146 ms
Garbage Collection55 ms
Parse HTML & CSS42 ms

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 4.6 KiB
URLTransfer SizeEst Savings
blog.seesaa.jp/portal/css/sp.css?v=1.0.821.6 KiB4.6 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 19.2 KiB
URLTransfer SizeEst Savings
blog.seesaa.jp/portal/css/sp.css?v=1.0.821.4 KiB19.2 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL
Seesaaブログ div.inner > div.logo > a > img
blog.seesaa.jp/portal/img/svg/logo.svg

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

●Layout shift culprits
●Optimize DOM size
●Forced reflow
●Optimize viewport for mobile
●Minify JavaScript
●User Timing marks and measures 7 user timings
●JavaScript execution time 1.2 s
●Avoid long main-thread tasks 10 long tasks found
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 280 ms
●Server Backend Latencies 1,000 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Initial server response time was short Root document took 270 ms
○INP breakdown
○Avoid non-composited animations
○Avoid large layout shifts
78

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

Contrast

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
マイブログ div.inner > ul > li > a.login
できるだけ人生や愛とは関係ない延長戦 li.cover > a > div.text > div.footer
Tokyo2072 li.cover > a > div.text > div.footer
安田プロの「ツイてる!」日記‐静岡県伊東・沼津のゴルフスクール・ラウンドレッスン‐安田ゴルフアカデミー li.cover > a > div.text > div.footer
いつもどこかで的中だ!! li.cover > a > div.text > div.footer
木漏れ日の記録 a > div.media > div.body > div.footer
パッキャラマード祭り a > div.media > div.body > div.footer
主婦にも色々あるわけで~扶養内パート主婦ブログ~ a > div.media > div.body > div.footer
ポン散歩 a > div.media > div.body > div.footer
愛と平和のクランキン木村遊船クランカー号@琵琶湖 a > div.media > div.body > div.footer
令和6年森羅万象 a > div.media > div.body > div.footer
人気ブログランキング div.sp-scroll > div.boxes > div.box > h3.title-baloon
人気記事ランキング div.sp-scroll > div.boxes > div.box > h3.title-baloon
楽天市場ポイントキャンペーン a > div.media > div.body > div.footer
ブラブラブラウジング a > div.media > div.body > div.footer
カルチョまとめブログ a > div.media > div.body > div.footer
のんびりなまけにっき2 a > div.media > div.body > div.footer
リードメールメモ a > div.media > div.body > div.footer
2026-04-21 div.section-contents > ul.list-information > li > div.date
2026-04-14 div.section-contents > ul.list-information > li > div.date
2026-03-16 div.section-contents > ul.list-information > li > div.date
利用規約 div.inner > ul > li > a
プライバシーポリシー div.inner > ul > li > a
広告掲載について div.inner > ul > li > a
お問い合わせ div.inner > ul > li > a
Copyright(c) Shitaraba, Inc. All Rights Reserved body > footer.global-footer > div.inner > div.copyright

These are opportunities to improve the legibility of your content.

Best practices

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

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
head > meta head > meta

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

These items highlight common accessibility best practices.

○Interactive controls are keyboard focusable
○Interactive elements indicate their purpose and state
○The page has a logical tab order
○Visual order on the page follows DOM order
○User focus is not accidentally trapped in a region
○The user's focus is directed to new content added to the page
○HTML5 landmark elements are used to improve navigation
○Offscreen content is hidden from assistive technology
○Custom controls have associated labels
○Custom controls have ARIA roles
●`[aria-hidden="true"]` is not present on the document `<body>`
●Image elements have `[alt]` attributes
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links have a discernible name
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
○`[accesskey]` values are unique
○`[aria-*]` attributes match their roles
○`button`, `link`, and `menuitem` elements have accessible names
○ARIA attributes are used as specified for the element's role
○Deprecated ARIA roles were not used
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○`[aria-hidden="true"]` elements do not contain focusable descendents
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements use only permitted ARIA attributes
○`[role]`s have all required `[aria-*]` attributes
○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
○`[role]`s are contained by their required parent element
○`[role]` values are valid
○Elements with the `role=text` attribute do not have focusable descendents.
○ARIA toggle fields have accessible names
○ARIA `tooltip` elements have accessible names
○ARIA `treeitem` elements have accessible names
○`[aria-*]` attributes have valid values
○`[aria-*]` attributes are valid and not misspelled
○Buttons have an accessible name
○The page contains a heading, skip link, or landmark region
○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
○Definition list items are wrapped in `<dl>` elements
○ARIA IDs are unique
○No form fields have multiple labels
○`<frame>` or `<iframe>` elements have a title
○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○Input buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○Form elements have associated labels
○Links are distinguishable without relying on color.
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○No element has a `[tabindex]` value greater than 0
○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
○`[lang]` attributes have a valid value
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○Uses ARIA roles only on compatible elements
○Image elements do not have `[alt]` attributes that are redundant text.
○Identical links have the same purpose.
○Elements with visible text labels have matching accessible names.
○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
○`<td>` elements in a large `<table>` have one or more table headers.
96

Best Practices

General

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

SourceDescription
Failed to load resource: the server responded with a status of 404 ()
●Uses HTTPS
●Avoids deprecated APIs
●Avoids third-party cookies
●Allows users to paste into input fields
●Avoids requesting the geolocation permission on page load
●Avoids requesting the notification permission on page load
●Displays images with correct aspect ratio
●Serves images with appropriate resolution
●Page has the HTML doctype
●Properly defines charset
●No issues in the `Issues` panel in Chrome Devtools
●Ensure CSP is effective against XSS attacks
●Use a strong HSTS policy
●Ensure proper origin isolation with COOP
●Mitigate clickjacking with XFO or CSP
●Mitigate DOM-based XSS with Trusted Types
●Detected JavaScript libraries
●Page has valid source maps
○Redirects HTTP traffic to HTTPS
100

SEO

These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.

○Structured data is valid
●Page isn’t blocked from indexing
●Document has a `<title>` element
●Document has a meta description
●Page has successful HTTP status code
●Links have descriptive text
●Links are crawlable
●Image elements have `[alt]` attributes
●Document has a valid `hreflang`
○robots.txt is valid
○Document has a valid `rel=canonical`

Send Feedback