Shingeki.net Site Title
進撃の巨人 作品公式サイト
Shingeki.net Meta Description
単行本世界累計発行部数1億部を突破！『進撃の巨人』の公式サイト
Shingeki.net Test Results
Shingeki.net Mobile Performance: 0/100
Quick overview:
Opportunities
These suggestions can help your page load faster. They don't directly affect the Performance score.
Preload key requests. Potential savings of 1,980 ms
Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load. Learn more.
Reduce unused JavaScript. Potential savings of 333 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn more.
Reduce initial server response time. Root document took 1,290 ms
Keep the server response time for the main document short because all other requests depend on it. Learn more.
Reduce unused CSS. Potential savings of 90 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn more.
Preconnect to required origins. 0 ms
Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins. Learn more.
Preload Largest Contentful Paint image. 0 ms
Preload the image used by the LCP element in order to improve your LCP time. Learn more.
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Image elements do not have explicit `width` and `height`
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. 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.
Serve static assets with an efficient cache policy
11 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.
Avoids an excessive DOM size
740 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn more.
JavaScript execution time
1.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 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 more
Keep request counts low and transfer sizes small
25 requests • 741 KiB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.
Shingeki.net Mobile SEO: 0/100
Quick overview:
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
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.
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.
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.
Document doesn't use legible font sizes
32.74% 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.
Shingeki.net Mobile Best Practices: 87/100
Quick overview:
Trust and Safety
Does not use HTTPS
9 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.
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.
Ensure CSP is effective against XSS attacks
A strong Content Security Policy (CSP) significantly reduces the risk of cross-site scripting (XSS) attacks. Learn more
Shingeki.net Mobile Progressive Web App: 50/100
Quick overview:
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.
PWA Optimized
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 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.
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.
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.
Shingeki.net Mobile Accessibility: 0/100
Quick overview:
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-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 more.
`[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.
ARIA `meter` 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 more.
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.
`[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.
ARIA `treeitem` 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 more.
ARIA `tooltip` 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 more.
`[aria-*]` attributes are valid and not misspelled
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid names. Learn more.
`[aria-*]` attributes have valid values
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more.
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.
ARIA `progressbar` 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 more.
`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 more.
`[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 more.
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.
ARIA IDs are unique
The value of an ARIA ID must be unique to prevent other instances from being overlooked by assistive technologies. Learn more.
`[role]` values are valid
ARIA roles must have valid values in order to perform their intended accessibility functions. Learn more.
`[aria-*]` attributes match their roles
Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn more.
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 have `[alt]` attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more.
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.
`<object>` elements have `[alt]` text
Screen readers cannot translate non-text content. Adding alt text to `<object>` elements helps screen readers convey meaning to users. Learn more.
`<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 more.
Form elements have associated labels
Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more.
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 more.
`<frame>` or `<iframe>` elements have a title
Screen reader users rely on frame titles to describe the contents of frames. Learn more.
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 more.
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 more.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
`[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 more.
`<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.
`<html>` element has a valid value for its `[lang]` attribute
Specifying a valid BCP 47 language helps screen readers announce text properly. Learn more.
Contrast
These are opportunities to improve the legibility of your content.
Background and foreground colors have a sufficient contrast ratio
Low-contrast text is difficult or impossible for many users to read. Learn more.
Navigation
These are opportunities to improve keyboard navigation in your application.
`[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.
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.
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.
`[id]` attributes on active, focusable elements are unique
All focusable elements must have a unique `id` to ensure that they're visible to assistive technologies. Learn more.
Heading elements appear 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.
Audio and video
These are opportunities to provide alternative content for audio and video. This may improve the experience for users with hearing or vision impairments.
`<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.
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
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 more.
`<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 more.
`<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.
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
Screen readers require list items (`<li>`) to be contained within a parent `<ul>` or `<ol>` to be announced properly. Learn more.
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.
Lists 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.
Best practices
These items highlight common accessibility best practices.
`[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.
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.
Similar sites
Similar tests
www.shingeki.com
www.shingeki.net
www.shingeki.org
www.shingeki.info
www.shingeki.biz
www.shingeki.us
www.shingeki.mobi
www.hingeki.net
www.shingeki.net
www.whingeki.net
www.swhingeki.net
www.wshingeki.net
www.ehingeki.net
www.sehingeki.net
www.eshingeki.net
www.dhingeki.net
www.sdhingeki.net
www.dshingeki.net
www.zhingeki.net
www.szhingeki.net
www.zshingeki.net
www.xhingeki.net
www.sxhingeki.net
www.xshingeki.net
www.ahingeki.net
www.sahingeki.net
www.ashingeki.net
www.singeki.net
www.sbingeki.net
www.shbingeki.net
www.sbhingeki.net
www.sgingeki.net
www.shgingeki.net
www.sghingeki.net
www.syingeki.net
www.shyingeki.net
www.syhingeki.net
www.suingeki.net
www.shuingeki.net
www.suhingeki.net
www.sjingeki.net
www.shjingeki.net
www.sjhingeki.net
www.sningeki.net
www.shningeki.net
www.snhingeki.net
www.shngeki.net
www.shungeki.net
www.shiungeki.net
www.shjngeki.net
www.shijngeki.net
www.shkngeki.net
www.shikngeki.net
www.shkingeki.net
www.shongeki.net
www.shiongeki.net
www.shoingeki.net
www.shigeki.net
www.shibgeki.net
www.shinbgeki.net
www.shibngeki.net
www.shihgeki.net
www.shinhgeki.net
www.shihngeki.net
www.shijgeki.net
www.shinjgeki.net
www.shimgeki.net
www.shinmgeki.net
www.shimngeki.net
www.shineki.net
www.shinfeki.net
www.shingfeki.net
www.shinfgeki.net
www.shinveki.net
www.shingveki.net
www.shinvgeki.net
www.shinteki.net
www.shingteki.net
www.shintgeki.net
www.shinbeki.net
www.shingbeki.net
www.shinyeki.net
www.shingyeki.net
www.shinygeki.net
www.shinheki.net
www.shingheki.net
www.shingki.net
www.shingwki.net
www.shingewki.net
www.shingweki.net
www.shingski.net
www.shingeski.net
www.shingseki.net
www.shingdki.net
www.shingedki.net
www.shingdeki.net
www.shingrki.net
www.shingerki.net
www.shingreki.net
www.shingei.net
www.shingeji.net
www.shingekji.net
www.shingejki.net
www.shingeii.net
www.shingekii.net
www.shingeiki.net
www.shingemi.net
www.shingekmi.net
www.shingemki.net
www.shingeli.net
www.shingekli.net
www.shingelki.net
www.shingeoi.net
www.shingekoi.net
www.shingeoki.net
www.shingek.net
www.shingeku.net
www.shingekiu.net
www.shingekui.net
www.shingekj.net
www.shingekij.net
www.shingekk.net
www.shingekik.net
www.shingekki.net
www.shingeko.net
www.shingekio.net
www.shingeki.net
www.shingeki.org
www.shingeki.info
www.shingeki.biz
www.shingeki.us
www.shingeki.mobi
www.hingeki.net
www.shingeki.net
www.whingeki.net
www.swhingeki.net
www.wshingeki.net
www.ehingeki.net
www.sehingeki.net
www.eshingeki.net
www.dhingeki.net
www.sdhingeki.net
www.dshingeki.net
www.zhingeki.net
www.szhingeki.net
www.zshingeki.net
www.xhingeki.net
www.sxhingeki.net
www.xshingeki.net
www.ahingeki.net
www.sahingeki.net
www.ashingeki.net
www.singeki.net
www.sbingeki.net
www.shbingeki.net
www.sbhingeki.net
www.sgingeki.net
www.shgingeki.net
www.sghingeki.net
www.syingeki.net
www.shyingeki.net
www.syhingeki.net
www.suingeki.net
www.shuingeki.net
www.suhingeki.net
www.sjingeki.net
www.shjingeki.net
www.sjhingeki.net
www.sningeki.net
www.shningeki.net
www.snhingeki.net
www.shngeki.net
www.shungeki.net
www.shiungeki.net
www.shjngeki.net
www.shijngeki.net
www.shkngeki.net
www.shikngeki.net
www.shkingeki.net
www.shongeki.net
www.shiongeki.net
www.shoingeki.net
www.shigeki.net
www.shibgeki.net
www.shinbgeki.net
www.shibngeki.net
www.shihgeki.net
www.shinhgeki.net
www.shihngeki.net
www.shijgeki.net
www.shinjgeki.net
www.shimgeki.net
www.shinmgeki.net
www.shimngeki.net
www.shineki.net
www.shinfeki.net
www.shingfeki.net
www.shinfgeki.net
www.shinveki.net
www.shingveki.net
www.shinvgeki.net
www.shinteki.net
www.shingteki.net
www.shintgeki.net
www.shinbeki.net
www.shingbeki.net
www.shinyeki.net
www.shingyeki.net
www.shinygeki.net
www.shinheki.net
www.shingheki.net
www.shingki.net
www.shingwki.net
www.shingewki.net
www.shingweki.net
www.shingski.net
www.shingeski.net
www.shingseki.net
www.shingdki.net
www.shingedki.net
www.shingdeki.net
www.shingrki.net
www.shingerki.net
www.shingreki.net
www.shingei.net
www.shingeji.net
www.shingekji.net
www.shingejki.net
www.shingeii.net
www.shingekii.net
www.shingeiki.net
www.shingemi.net
www.shingekmi.net
www.shingemki.net
www.shingeli.net
www.shingekli.net
www.shingelki.net
www.shingeoi.net
www.shingekoi.net
www.shingeoki.net
www.shingek.net
www.shingeku.net
www.shingekiu.net
www.shingekui.net
www.shingekj.net
www.shingekij.net
www.shingekk.net
www.shingekik.net
www.shingekki.net
www.shingeko.net
www.shingekio.net