Fwinc.co.jp Site Title

フロンティアワークス公式サイト|アニメ・書籍・ゲーム・キャラクターグッズ・ミュージカルetc多様なコンテンツを展開

Fwinc.co.jp Meta Description

映像・出版・SNS・グッズ制作・CD・ライブコンテンツを取り扱うフロンティアワークスの公式サイトです。商品リリース、イベントなど最新情報を掲載中!

Fwinc.co.jp Test Results

Fwinc.co.jp Mobile Performance: 34/100
Quick overview:
Time to Interactive
29.6 s
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.
Max Potential First Input Delay
1,980 ms
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.
Script Treemap Data
Used for treemap app
Metrics
Collects all available metrics.
Network Requests
Lists the network requests that were made during page load.
Tasks
Lists the toplevel main thread tasks that executed during page load.
Network Round Trip Times
0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance. Learn more about the Round Trip Time.
Diagnostics
Collection of useful page vitals.
Server Backend Latencies
0 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance. Learn more about server response time.
Final Screenshot
The last screenshot captured of the pageload.

475897979986


Fwinc.co.jp Mobile SEO: 93/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 about the `alt` attribute.

Fwinc.co.jp Mobile Best Practices: 75/100
Quick overview:
General
Issues were logged 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.
Detected JavaScript libraries
All front-end JavaScript libraries detected on the page. Learn more about this JavaScript library detection diagnostic audit.
User Experience
Displays images with incorrect aspect ratio
Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.
Trust and Safety
Does not use HTTPS
60 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 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.
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
Fwinc.co.jp Mobile PWA: 22/100
Quick overview:
PWA Optimized
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 about Service Workers.
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 about maskable manifest icons. No manifest was fetched
Does not set a theme color for the address bar.
The browser address bar can be themed to match your site. Learn more about theming the address bar. Failures: No manifest was fetched, No `<meta name="theme-color">` 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 about splash screens. 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 how to size content for the viewport. The viewport size of 640px does not match the window size of 412px.
Installable
Web app manifest or service worker do not meet the installability requirements
1 reason
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. With proper service worker and manifest implementations, browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement. Learn more about manifest installability requirements.
Fwinc.co.jp Mobile Accessibility: 68/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 about the `alt` attribute.
`<frame>` or `<iframe>` elements do not have a title
Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
`[aria-*]` attributes do not 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 input fields do not 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-*]` attributes do not 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.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` are missing some or all of those 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.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
`<html>` element does not have 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.
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 how to provide sufficient color contrast.
Similar tests
www.fwinc.com
www.fwinc.net
www.fwinc.org
www.fwinc.info
www.fwinc.biz
www.fwinc.us
www.fwinc.mobi
www.winc.co.jp
www.fwinc.co.jp
www.cwinc.co.jp
www.fcwinc.co.jp
www.cfwinc.co.jp
www.dwinc.co.jp
www.fdwinc.co.jp
www.dfwinc.co.jp
www.rwinc.co.jp
www.frwinc.co.jp
www.rfwinc.co.jp
www.twinc.co.jp
www.ftwinc.co.jp
www.tfwinc.co.jp
www.gwinc.co.jp
www.fgwinc.co.jp
www.gfwinc.co.jp
www.vwinc.co.jp
www.fvwinc.co.jp
www.vfwinc.co.jp
www.finc.co.jp
www.fqinc.co.jp
www.fwqinc.co.jp
www.fqwinc.co.jp
www.fainc.co.jp
www.fwainc.co.jp
www.fawinc.co.jp
www.fsinc.co.jp
www.fwsinc.co.jp
www.fswinc.co.jp
www.feinc.co.jp
www.fweinc.co.jp
www.fewinc.co.jp
www.fwnc.co.jp
www.fwunc.co.jp
www.fwiunc.co.jp
www.fwuinc.co.jp
www.fwjnc.co.jp
www.fwijnc.co.jp
www.fwjinc.co.jp
www.fwknc.co.jp
www.fwiknc.co.jp
www.fwkinc.co.jp
www.fwonc.co.jp
www.fwionc.co.jp
www.fwoinc.co.jp
www.fwic.co.jp
www.fwibc.co.jp
www.fwinbc.co.jp
www.fwibnc.co.jp
www.fwihc.co.jp
www.fwinhc.co.jp
www.fwihnc.co.jp
www.fwijc.co.jp
www.fwinjc.co.jp
www.fwimc.co.jp
www.fwinmc.co.jp
www.fwimnc.co.jp
www.fwin.co.jp
www.fwinx.co.jp
www.fwincx.co.jp
www.fwinxc.co.jp
www.fwind.co.jp
www.fwincd.co.jp
www.fwindc.co.jp
www.fwinf.co.jp
www.fwincf.co.jp
www.fwinfc.co.jp
www.fwinv.co.jp
www.fwincv.co.jp
www.fwinvc.co.jp
Last Tested: