Poe.jp Site Title
縲仙涵邇峨闃ｱ縺ｮ蜷肴園縲大涵邇峨闃ｱ縲ｼｿ鷹リ縺ｮ繝輔Λ繝ｯ繝ｼ繧ｬ繝ｼ繝Φ繝ｻ闃ｱ繧ｹ繝昴ャ繝医→隕ｳ蜈画ュ蝣ｱ縲よ淵遲門逵溘弱⊃縺峨驛ｨ螻九
Poe.jp Meta Description
縲仙涵邇峨闃ｱ縺ｮ蜷肴園縲大涵邇臥恁縺ｮ闃ｱ縺ｮ蜷肴園繧剃ｸｭ蠢↓髢｢譚ｱ縺ｮ闃ｱ縲繝輔Λ繝ｯ繝ｼ繧ｬ繝ｼ繝Φｼ干繧ｹ繝昴ャ繝医ｒ邏ｹ莉九ゅ弱⊃縺峨上′陦後▲縺溷逵滄､ｨ繧りｦ九※縺上□縺輔＞縺ｭ縺り干謨｣遲悶ｄ譽ｮ譫玲ｵｴ縲∝慍蝓溘隕ｳ蜈画ュ蝣ｱ縺ｪ縺ｩ繧ゅメ繝ｩ繝帙Λ邏ｹ莉九＠縺ｦ縺∪縺
Poe.jp Test Results
Poe.jp Mobile Performance: 20/100
Quick overview:
Opportunities
These suggestions can help your page load faster. They don't directly affect the Performance score.
Properly size images. Potential savings of 2,471 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.
Use video formats for animated content. Potential savings of 2,240 KiB
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
Serve images in next-gen formats. Potential savings of 1,863 KiB
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more.
Efficiently encode images. Potential savings of 1,187 KiB
Optimized images load faster and consume less cellular data. Learn more.
Remove unused JavaScript. Potential savings of 246 KiB
Remove unused JavaScript to reduce bytes consumed by network activity. Learn more.
Eliminate render-blocking resources. Potential savings of 1,270 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.
Remove unused CSS. Potential savings of 41 KiB
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity. Learn more.
Preload key requests. Potential savings of 180 ms
Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load. Learn more.
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Serve static assets with an efficient cache policy
82 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.
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.
Does not use 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.
Reduce the impact of third-party code
Third-party code blocked the main thread for 2,220 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 more.
Avoid `document.write()`
For users on slow connections, external scripts dynamically injected via `document.write()` can delay page load by tens of seconds. Learn more.
Avoid enormous network payloads
Total size was 7,651 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.
Minimize main-thread work
11.1 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more
Avoid an excessive DOM size
2,465 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn more.
Reduce JavaScript execution time
3.5 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.
Largest Contentful Paint element
1 element found
This is the largest contentful element painted within the viewport. Learn More
Keep request counts low and transfer sizes small
170 requests • 7,651 KiB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.
Avoid chaining critical requests
11 chains 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 more.
Avoid large layout shifts
5 elements found
These DOM elements contribute most to the CLS of the page.
Avoid long main-thread tasks
20 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn more
Poe.jp Mobile SEO: 67/100
Quick overview:
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Image elements do not have `[alt]` attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more.
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. Learn more.
Tap targets are not sized appropriately
Interactive elements like buttons and links should be large enough (48x48px), and have enough space around them, to be easy enough to tap without overlapping onto other elements. Learn more. Tap targets are too small because there's no viewport meta tag optimized for mobile screens
Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
Add a `<meta name="viewport">` tag to optimize your app for mobile screens. Learn more. No `<meta name="viewport">` tag found
Document doesn't use 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. Text is illegible because there's no viewport meta tag optimized for mobile screens.
Poe.jp Mobile Best Practices: 57/100
Quick overview:
User Experience
Serves images with low resolution
Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn more.
Displays images with incorrect aspect ratio
Image display dimensions should match natural aspect ratio. Learn more.
General
Browser errors were 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
Browser Compatibility
Page lacks the HTML doctype, thus triggering quirks-mode
Specifying a doctype prevents the browser from switching to quirks-mode. Learn more. Expected publicId to be an empty string
Trust and Safety
Does not use HTTPS
64 insecure requests found
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 servedover 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.
Links to cross-origin destinations are unsafe
Add `rel="noopener"` or `rel="noreferrer"` to any external links to improve performance and prevent security vulnerabilities. Learn more.
Poe.jp Mobile Progressive Web App: 4/100
Quick overview:
Installable
Web app manifest does not meet the installability requirements
Browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement. Learn more. Failures: No manifest was fetched.
Does not register a service worker that controls page and `start_url`
The service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. Learn more.
Does not use HTTPS
64 insecure requests found
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 servedover 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.
Fast and reliable
Current page does not respond with a 200 when offline
If you're building a Progressive Web App, consider using a service worker so that your app can work offline. Learn more.
Page load is not fast enough on mobile networks
Interactive at 14.3 s
A fast page load over a cellular network ensures a good mobile user experience. Learn more. Your page loads too slowly and is not interactive within 10 seconds. Look at the opportunities and diagnostics in the "Performance" section to learn how to improve.
`start_url` does not respond with a 200 when offline
A service worker enables your web app to be reliable in unpredictable network conditions. Learn more. No usable web app manifest found on page.
PWA Optimized
Does not set a theme color for the address bar.
The browser address bar can be themed to match your site. Learn more. Failures: No manifest was fetched,
No `<meta name="theme-color">` tag found.
Manifest doesn't have a maskable icon
A maskable icon ensures that the image fills the entire shape without being letterboxed when installing the app on a device. Learn more. No manifest was fetched
Does not redirect HTTP traffic to HTTPS
If you've already set up HTTPS, make sure that you redirect all HTTP traffic to HTTPS in order to enable secure web features for all your users. Learn more.
Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
Add a `<meta name="viewport">` tag to optimize your app for mobile screens. Learn more. No `<meta name="viewport">` tag found
Is not configured for a custom splash screen
A themed splash screen ensures a high-quality experience when users launch your app from their homescreens. Learn more. Failures: No manifest was fetched.
Content is not sized correctly for the viewport
If the width of your app's content doesn't match the width of the viewport, your app might not be optimized for mobile screens. Learn more. The viewport size of 1020px does not match the window size of 360px.
Does not provide a valid `apple-touch-icon`
For ideal appearance on iOS when users add a progressive web app to the home screen, define an `apple-touch-icon`. It must point to a non-transparent 192px (or 180px) square PNG. Learn More.
Poe.jp Mobile Accessibility: 61/100
Quick overview:
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Image elements do not have `[alt]` attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more.
Links do not 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 more.
`<frame>` or `<iframe>` elements do not have a title
Screen reader users rely on frame titles to describe the contents of frames. Learn more.
Navigation
These are opportunities to improve keyboard navigation in your application.
The page does not contain a heading, skip link, or landmark region
Adding ways to bypass repetitive content lets keyboard users navigate the page more efficiently. Learn more.
Contrast
These are opportunities to improve the legibility of your content.
Background and foreground colors do not have a sufficient contrast ratio.
Low-contrast text is difficult or impossible for many users to read. Learn more.
Similar tests
www.poe.com
www.poe.net
www.poe.org
www.poe.info
www.poe.biz
www.poe.us
www.poe.mobi
www.oe.jp
www.poe.jp
www.ooe.jp
www.pooe.jp
www.opoe.jp
www.loe.jp
www.ploe.jp
www.lpoe.jp
www.pe.jp
www.pie.jp
www.poie.jp
www.pioe.jp
www.pke.jp
www.poke.jp
www.pkoe.jp
www.ple.jp
www.pole.jp
www.ppe.jp
www.pope.jp
www.ppoe.jp
www.po.jp
www.pow.jp
www.poew.jp
www.powe.jp
www.pos.jp
www.poes.jp
www.pose.jp
www.pod.jp
www.poed.jp
www.pode.jp
www.por.jp
www.poer.jp
www.pore.jp
www.poe.net
www.poe.org
www.poe.info
www.poe.biz
www.poe.us
www.poe.mobi
www.oe.jp
www.poe.jp
www.ooe.jp
www.pooe.jp
www.opoe.jp
www.loe.jp
www.ploe.jp
www.lpoe.jp
www.pe.jp
www.pie.jp
www.poie.jp
www.pioe.jp
www.pke.jp
www.poke.jp
www.pkoe.jp
www.ple.jp
www.pole.jp
www.ppe.jp
www.pope.jp
www.ppoe.jp
www.po.jp
www.pow.jp
www.poew.jp
www.powe.jp
www.pos.jp
www.poes.jp
www.pose.jp
www.pod.jp
www.poed.jp
www.pode.jp
www.por.jp
www.poer.jp
www.pore.jp