future-boy.jp
Free website and domain report on future-boy.jp
Last Updated: 27th October, 2023 Update Now
Overview
Snoop Summary for future-boy.jp
This is a free and comprehensive report about future-boy.jp. The domain future-boy.jp is currently hosted on a server located in Japan with the IP address 210.172.210.244, where the local currency is JPY and Japanese is the local language. Our records indicate that future-boy.jp is owned/operated by Futures Entertainment Co., Ltd.. Future-boy.jp has the potential to be earning an estimated $5 USD per day from advertising revenue. If future-boy.jp was to be sold it would possibly be worth $3,792 USD (based on the daily revenue potential of the website over a 24 month period). Future-boy.jp receives an estimated 1,818 unique visitors every day - a large amount of traffic! This report was last updated 27th October, 2023.
About future-boy.jp
| Site Preview: | |
| Title: | フューチャーボーイ公式サイト |
| Description: | |
| Keywords and Tags: | pornography |
| Related Terms: | |
| Fav Icon: | |
| Age: | |
| Domain Created: | |
| Domain Updated: | |
| Domain Expires: |
Review
Snoop Score
2/5
Valuation
$3,792 USD
Note: All valuation figures are estimates.
Popularity
Modest
Note: Popularity is estimated.
Rank, Reach and Authority
| Alexa Rank: | 399,832 |
| Alexa Reach: | 0.0001% |
| SEMrush Rank (US): | |
| SEMrush Authority Score: | |
| Moz Domain Authority: | 0 |
| Moz Page Authority: | 0 |
Organic vs Paid (Google Ads)
Traffic
Visitors
| Daily Visitors: | 1,818 |
| Monthly Visitors: | 55,334 |
| Yearly Visitors: | 663,570 |
Note: All visitors figures are estimates.
Visitors By Country
Revenue
Revenue
| Daily Revenue: | $5 USD |
| Monthly Revenue: | $158 USD |
| Yearly Revenue: | $1,891 USD |
Note: All revenue figures are estimates.
Revenue By Country
SEO
Backlinks Analysis (SEMrush)
Top New Follow Links
Top Ranking Keywords (US)
Domain Analysis
| Value | Length | |
|---|---|---|
| Domain: | future-boy.jp | 13 |
| Domain Name: | future-boy | 10 |
| Extension (TLD): | jp | 2 |
Page Speed Analysis
| Average Load Time: | |
| Load Time Comparison: |
PageSpeed Insights
Avg. (All Categories)
Performance
Accessibility
Best Practices
SEO
PWA
0–49 (Fail) 50–89 (Average) 90–100 (Pass) 
URL: https://future-boy.jp
Updated: 11th March, 2023
0.61 seconds
First Contentful Paint (FCP)
0.00 seconds
First Input Delay (FID) Performance
Indicates how well the page is performing and highlights opportunities where performance may be improved for future-boy.jp. This includes details about optimizing page load times which can result in a better user experience.Metrics
First Contentful Paint — 0.4 s The time taken for the first image or text on the page to be rendered.
Time to Interactive — 0.7 s The time taken for the page to become fully interactive.
Total Blocking Time — 10 ms The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).
Largest Contentful Paint — 1.0 s The timing of the largest text or image that is painted.
Cumulative Layout Shift — 0.047 Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data
Audits
Max Potential First Input Delay — 60 ms Users could experience a delay when interacting with the page.
First Meaningful Paint — 0.4 s The time taken for the primary content of the page to be rendered.
Network Requests Below is a list of network requests that were made during page load.
| URL | Protocol | Start Time (Ms) | End Time (Ms) | Transfer Size (Bytes) | Resource Size (Bytes) | Status Code | MIME Type | Resource Type |
|---|---|---|---|---|---|---|---|---|
| http://future-boy.jp/ | http/1.1 | 0 | 315.26600010693 | 362 | 0 | 302 | text/html | |
| https://future-boy.jp/ | http/1.1 | 315.75400009751 | 1412.8229999915 | 1292 | 1264 | 200 | text/html | Document |
| https://future-boy.jp/css/grayz.css | http/1.1 | 1424.1040002089 | 2410.2340000682 | 432 | 0 | 404 | text/html | Stylesheet |
| https://future-boy.jp/img/index.jpg | http/1.1 | 1424.467000179 | 2918.393000029 | 451531 | 451249 | 200 | image/jpeg | Image |
| https://www.google-analytics.com/analytics.js | h2 | 2413.0120000336 | 2418.4200000018 | 20594 | 50234 | 200 | text/javascript | Script |
| https://www.google-analytics.com/j/collect?v=1&_v=j99&a=52708640&t=pageview&_s=1&dl=https%3A%2F%2Ffuture-boy.jp%2F&ul=en-us&de=UTF-8&dt=%E3%83%95%E3%83%A5%E3%83%BC%E3%83%81%E3%83%A3%E3%83%BC%E3%83%9C%E3%83%BC%E3%82%A4%E5%85%AC%E5%BC%8F%E3%82%B5%E3%82%A4%E3%83%88&sd=24-bit&sr=800x600&vp=1350x940&je=0&_u=IEBAAAABAAAAAC~&jid=49349889&gjid=646580302&cid=100567673.1678537291&tid=UA-10310513-1&_gid=152946587.1678537291&_r=1&_slc=1&z=1147279572 | h2 | 2501.2090001255 | 2505.1590001676 | 497 | 3 | 200 | text/plain | XHR |
Network Round Trip Times — 0 ms High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks Below is a list of the top-level main thread tasks that executed during page load.
| Start Time (Ms) | End Time (Ms) |
|---|---|
| 1420.619 | 15.272 |
| 2415.967 | 5.915 |
| 2421.916 | 15.527 |
| 2448.12 | 57.257 |
Script Treemap Data Provide as required, for treemap app.
Other
Eliminate render-blocking resources — Potential savings of 60 ms Resources, such as JavaScript and style sheets, can block the first paint of the page. Future-boy.jp should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
| URL | Transfer Size (Bytes) | Potential Savings (Ms) |
|---|---|---|
| https://future-boy.jp/css/grayz.css | 432 | 70 |
Properly size images Images can slow down the page's load time. Future-boy.jp should consider serving more appropriate-sized images.
Defer offscreen images Time to Interactive can be slowed down by resources on the page. Future-boy.jp should consider lazy-loading offscreen and hidden images.
Minify CSS Cascading Style Sheets (CSS) files can contribute to network payload sizes. Future-boy.jp should consider minifying CSS files.
Minify JavaScript JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Future-boy.jp should consider minifying JS files.
Reduce unused CSS Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Future-boy.jp should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Reduce unused JavaScript It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
Enable text compression Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Avoid multiple page redirects — Potential savings of 190 ms Redirects can cause additional delays before the page can begin loading. Future-boy.jp should avoid multiple or unnecessary page redirects.
| URL | Time Spent (Ms) |
|---|---|
| http://future-boy.jp/ | 190 |
| https://future-boy.jp/ | 0 |
Preload key requests Key requests can be preloaded by using '<link rel=preload>'. Future-boy.jp should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
Preload Largest Contentful Paint image It is recommended to preload images used by LCP elements, to improve LCP time.
| URL | Potential Savings (Ms) |
|---|---|
| https://future-boy.jp/img/index.jpg | 0 |
Avoids enormous network payloads — Total size was 464 KiB Large network payloads can cost users money and are linked to long load times.
| URL | Transfer Size (Bytes) |
|---|---|
| https://future-boy.jp/img/index.jpg | 451531 |
| https://www.google-analytics.com/analytics.js | 20594 |
| https://future-boy.jp/ | 1292 |
| https://www.google-analytics.com/j/collect?v=1&_v=j99&a=52708640&t=pageview&_s=1&dl=https%3A%2F%2Ffuture-boy.jp%2F&ul=en-us&de=UTF-8&dt=%E3%83%95%E3%83%A5%E3%83%BC%E3%83%81%E3%83%A3%E3%83%BC%E3%83%9C%E3%83%BC%E3%82%A4%E5%85%AC%E5%BC%8F%E3%82%B5%E3%82%A4%E3%83%88&sd=24-bit&sr=800x600&vp=1350x940&je=0&_u=IEBAAAABAAAAAC~&jid=49349889&gjid=646580302&cid=100567673.1678537291&tid=UA-10310513-1&_gid=152946587.1678537291&_r=1&_slc=1&z=1147279572 | 497 |
| https://future-boy.jp/css/grayz.css | 432 |
| http://future-boy.jp/ | 362 |
Avoids an excessive DOM size — 8 elements A large DOM (Document Object Model) will increase memory usage, cause longer system calculations as well as costly layout reflows.
| Statistic | Element | Value |
|---|---|---|
| Total DOM Elements | 8 | |
| Maximum DOM Depth | 8 | |
| Maximum Child Elements | 2 |
Avoid chaining critical requests — 1 chain found Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Future-boy.jp should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 0.1 s JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
| URL | Total CPU Time (Ms) | Script Evaluation (Ms) | Script Parse (Ms) |
|---|---|---|---|
| https://www.google-analytics.com/analytics.js | 60.792 | 55.46 | 1.532 |
Minimizes main-thread work — 0.1 s Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
| Category | Time Spent (Ms) |
|---|---|
| Script Evaluation | 67.143 |
| Other | 30.615 |
| Style & Layout | 13.929 |
| Parse HTML & CSS | 6.828 |
| Script Parsing & Compilation | 3.844 |
| Rendering | 3.756 |
All text remains visible during webfont loads Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
Keep request counts low and transfer sizes small — 6 requests • 464 KiB It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
| Resource Type | Requests | Transfer Size (Bytes) |
|---|---|---|
| Total | 6 | 474708 |
| Image | 1 | 451531 |
| Script | 1 | 20594 |
| Document | 1 | 1292 |
| Other | 2 | 859 |
| Stylesheet | 1 | 432 |
| Media | 0 | 0 |
| Font | 0 | 0 |
| Third-party | 2 | 21091 |
Minimize third-party usage — Third-party code blocked the main thread for 0 ms It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
| Third-Party | Transfer Size (Bytes) | Main-Thread Blocking Time (Ms) |
|---|---|---|
| 21091 | 3.819 |
Lazy load third-party resources with facades Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found The element which was identified as the Largest Contentful Paint.
| Element |
|---|
Largest Contentful Paint image was not lazily loaded Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
| Element |
|---|
Avoid large layout shifts — 1 element found Below is a list of all DOM elements that contribute to the CLS of the page.
| Element | CLS Contribution |
|---|---|
| 0.046902022589966 |
Uses passive listeners to improve scrolling performance Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()` Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks — 1 long task found Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
| URL | Start Time (Ms) | Duration (Ms) |
|---|---|---|
| https://www.google-analytics.com/analytics.js | 610 | 57 |
Avoid non-composited animations It is recommended to avoid non-composited animations which are often janky and increase CLS.
Avoids `unload` event listeners The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.
Budgets
Performance budget It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.
Timing budget It is advised to set a timing budget to monitor the performance of your site.
Metrics
Speed Index — 1.9 s The time taken for the page contents to be visibly populated.
Other
Efficiently encode images — Potential savings of 280 KiB Unoptimized images can consume more cellular data than what is necessary.
| URL | Resource Size (Bytes) | Potential Savings (Bytes) |
|---|---|---|
| https://future-boy.jp/img/index.jpg | 451249 | 286749 |
Serve images in next-gen formats — Potential savings of 373 KiB Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
| URL | Resource Size (Bytes) | Potential Savings (Bytes) |
|---|---|---|
| https://future-boy.jp/img/index.jpg | 451249 | 381627.2 |
Other
Reduce initial server response time — Root document took 1,100 ms It is advised to keep the server response time short for the main document, because all other requests depend on it.
| URL | Time Spent (Ms) |
|---|---|
| https://future-boy.jp/ | 1098.055 |
Serve static assets with an efficient cache policy — 2 resources found Future-boy.jp can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
| URL | Cache TTL (Ms) | Transfer Size (Bytes) |
|---|---|---|
| https://future-boy.jp/img/index.jpg | 0 | 451531 |
| https://www.google-analytics.com/analytics.js | 7200000 | 20594 |
Image elements do not have explicit `width` and `height` Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
| URL |
|---|
| https://future-boy.jp/img/index.jpg |
Does not have a `<meta name="viewport">` tag with `width` or `initial-scale` It is advised to use a '<meta name="viewport">' tag for the optimization of future-boy.jp on mobile screens.
Accessibility
Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of future-boy.jp. This includes details about various page attributes that can be optimized.Navigation
`[accesskey]` values are unique Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
`[id]` attributes on active, focusable elements are unique Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
Heading elements appear in a sequentially-descending order Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
No element has a `[tabindex]` value greater than 0 Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.
ARIA
`[aria-*]` attributes match their roles Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`button`, `link`, and `menuitem` elements have accessible names Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-hidden="true"]` is not present on the document `<body>` If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
`[aria-hidden="true"]` elements do not contain focusable descendents Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
ARIA input fields have accessible names Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
ARIA `meter` elements have accessible names Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `progressbar` elements have accessible names Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[role]`s have all required `[aria-*]` attributes Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children. Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid All ARIA roles require valid values to perform their intended functions.
ARIA toggle fields have accessible names Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
ARIA `tooltip` elements have accessible names Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `treeitem` elements have accessible names Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-*]` attributes have valid values ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.
ARIA IDs are unique Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.
Names and labels
Buttons have an accessible name Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Document has a `<title>` element Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<frame>` or `<iframe>` elements have a title Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
Image elements have `[alt]` attributes Provide short and descriptive alternative text where possible on informative elements.
`<input type="image">` elements have `[alt]` text Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Form elements have associated labels Screen readers and other assistive technologies rely on labels to properly announce form controls.
Links have a discernible name In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.
`<object>` elements have alternate text It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.
Contrast
Background and foreground colors have a sufficient contrast ratio Many (if not most) users find low-contrast text difficult or impossible to read.
Tables and lists
`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements. Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.
Definition list items are wrapped in `<dl>` elements In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`). Use proper list structure to aid screen readers and other assistive technologies.
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table. Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe. Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.
Internationalization and localization
`<html>` element has a valid value for its `[lang]` attribute Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.
Best practices
The document does not use `<meta http-equiv="refresh">` Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5. For users with low vision who rely on screen magnification, ensure that zooming is not disabled.
Audio and video
`<video>` elements contain a `<track>` element with `[kind="captions"]` Future-boy.jp may provide assistance to deaf or hearing-impaired users with captions on videos.
Internationalization and localization
`<html>` element does not have a `[lang]` attribute It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
| Failing Elements |
|---|
Manual Checks
The page has a logical tab order The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.
Interactive controls are keyboard focusable Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.
Interactive elements indicate their purpose and state Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.
The user's focus is directed to new content added to the page When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.
User focus is not accidentally trapped in a region Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.
Custom controls have associated labels Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.
Custom controls have ARIA roles Ensure that all custom interactive controls have appropriate ARIA roles.
Visual order on the page follows DOM order Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.
Offscreen content is hidden from assistive technology Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.
HTML5 landmark elements are used to improve navigation Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.
Best Practices
Indicates the recommended, best practices currently in place on the page and highlights the best practices that future-boy.jp should incorporate. This includes practices such as protecting pages with HTTPS.Audits
Avoids requesting the geolocation permission on page load When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids front-end JavaScript libraries with known security vulnerabilities Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Ensure CSP is effective against XSS attacks Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).
| Description | Directive | Severity |
|---|---|---|
| No CSP found in enforcement mode | High |
Audits
Allows users to paste into password fields Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.
Displays images with correct aspect ratio Ensure that image display dimensions match their natural aspect ratio.
Serves images with appropriate resolution For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
Fonts with `font-display: optional` are preloaded It is recommended that optional fonts are preloaded.
Audits
Page has the HTML doctype Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Properly defines charset It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.
Audits
Detected JavaScript libraries Below is a list of all front-end JavaScript libraries that were detected on the page.
Avoids deprecated APIs Avoid deprecated APIs which will eventually be removed the browser.
Page has valid source maps Consider deploying source maps for added benefits such as the ability to debug while in production.
No issues in the `Issues` panel in Chrome Devtools There may be unresolved issues logged to Chrome Devtools.
Audits
Does not use HTTPS — 1 insecure request found Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
| Insecure URL | Request Resolution |
|---|---|
| http://future-boy.jp/ | Allowed |
Audits
Browser errors were logged to the console Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
| Source | Description |
|---|---|
| Failed to load resource: the server responded with a status of 404 (Not Found) | |
| Failed to load resource: the server responded with a status of 404 (Not Found) |
SEO
Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for future-boy.jp. This includes optimizations such as providing meta data.Content Best Practices
Document has a `<title>` element Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Links have descriptive text Make use of descriptive link text to assist search engines in understanding the content.
Image elements have `[alt]` attributes Provide short and descriptive alternative text where possible on informative elements.
Document has a valid `hreflang` Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical` Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.
Crawling and Indexing
Page has successful HTTP status code Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Links are crawlable Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.
Page isn’t blocked from indexing Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
robots.txt is valid Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.
Mobile Friendly
Document uses legible font sizes Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Tap targets are sized appropriately Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.
Mobile Friendly
Does not have a `<meta name="viewport">` tag with `width` or `initial-scale` It is advised to use a '<meta name="viewport">' tag for the optimization of future-boy.jp on mobile screens.
Content Best Practices
Document does not have a meta description Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
Manual Checks
Structured data is valid Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
PWA
Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of future-boy.jp. This includes details about web app manifests.PWA Optimized
Content is sized correctly for the viewport Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Installable
Web app manifest or service worker do not meet the installability requirements — 1 reason User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
| Failure reason |
|---|
| No manifest was fetched |
PWA Optimized
Does not register a service worker that controls page and `start_url` A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Is not configured for a custom splash screen Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar. A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Does not have a `<meta name="viewport">` tag with `width` or `initial-scale` It is advised to use a '<meta name="viewport">' tag for the optimization of future-boy.jp on mobile screens.
Does not provide a valid `apple-touch-icon` iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.
Manifest doesn't have a maskable icon Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.
Manual Checks
Site works cross-browser Ensure that the Progressive Web App works correctly across every major browser.
Page transitions don't feel like they block on the network Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.
Each page has a URL Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.
Avg. (All Categories)
Performance
Accessibility
Best Practices
SEO
PWA
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://future-boy.jp
Updated: 11th March, 2023
0.87 seconds
First Contentful Paint (FCP)
0.24 seconds
First Input Delay (FID) Performance
Indicates how well the page is performing and highlights opportunities where performance may be improved for future-boy.jp. This includes details about optimizing page load times which can result in a better user experience.Metrics
First Contentful Paint — 1.3 s The time taken for the first image or text on the page to be rendered.
Time to Interactive — 2.1 s The time taken for the page to become fully interactive.
Total Blocking Time — 30 ms The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).
Cumulative Layout Shift — 0.024 Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data
Audits
Max Potential First Input Delay — 80 ms Users could experience a delay when interacting with the page.
First Meaningful Paint — 1.3 s The time taken for the primary content of the page to be rendered.
Network Requests Below is a list of network requests that were made during page load.
| URL | Protocol | Start Time (Ms) | End Time (Ms) | Transfer Size (Bytes) | Resource Size (Bytes) | Status Code | MIME Type | Resource Type |
|---|---|---|---|---|---|---|---|---|
| http://future-boy.jp/ | http/1.1 | 0 | 416.70500000328 | 362 | 0 | 302 | text/html | |
| https://future-boy.jp/ | http/1.1 | 416.96600000432 | 1413.6470000012 | 1292 | 1264 | 200 | text/html | Document |
| https://future-boy.jp/css/grayz.css | http/1.1 | 1421.6490000035 | 2239.1780000034 | 432 | 0 | 404 | text/html | Stylesheet |
| https://future-boy.jp/img/index.jpg | http/1.1 | 1421.8970000002 | 2578.0060000034 | 451530 | 451249 | 200 | image/jpeg | Image |
| https://www.google-analytics.com/analytics.js | h2 | 2240.6550000014 | 2244.9940000006 | 20594 | 50234 | 200 | text/javascript | Script |
| https://www.google-analytics.com/j/collect?v=1&_v=j99&a=256162269&t=pageview&_s=1&dl=https%3A%2F%2Ffuture-boy.jp%2F&ul=en-us&de=UTF-8&dt=%E3%83%95%E3%83%A5%E3%83%BC%E3%83%81%E3%83%A3%E3%83%BC%E3%83%9C%E3%83%BC%E3%82%A4%E5%85%AC%E5%BC%8F%E3%82%B5%E3%82%A4%E3%83%88&sd=24-bit&sr=360x640&vp=980x1742&je=0&_u=IEBAAAABAAAAAC~&jid=1716894767&gjid=432929250&cid=529548148.1678537314&tid=UA-10310513-1&_gid=2121739913.1678537314&_r=1&_slc=1&z=1300152834 | h2 | 2270.4280000034 | 2273.7360000028 | 497 | 3 | 200 | text/plain | XHR |
Network Round Trip Times — 0 ms High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks Below is a list of the top-level main thread tasks that executed during page load.
| Start Time (Ms) | End Time (Ms) |
|---|---|
| 1417.159 | 8.06 |
| 2251.176 | 20.462 |
Script Treemap Data Provide as required, for treemap app.
Other
Properly size images Images can slow down the page's load time. Future-boy.jp should consider serving more appropriate-sized images.
Defer offscreen images Time to Interactive can be slowed down by resources on the page. Future-boy.jp should consider lazy-loading offscreen and hidden images.
Minify CSS Cascading Style Sheets (CSS) files can contribute to network payload sizes. Future-boy.jp should consider minifying CSS files.
Minify JavaScript JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Future-boy.jp should consider minifying JS files.
Reduce unused CSS Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Future-boy.jp should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Reduce unused JavaScript It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
Enable text compression Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Avoid multiple page redirects — Potential savings of 630 ms Redirects can cause additional delays before the page can begin loading. Future-boy.jp should avoid multiple or unnecessary page redirects.
| URL | Time Spent (Ms) |
|---|---|
| http://future-boy.jp/ | 630 |
| https://future-boy.jp/ | 0 |
Preload key requests Key requests can be preloaded by using '<link rel=preload>'. Future-boy.jp should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
Preload Largest Contentful Paint image It is recommended to preload images used by LCP elements, to improve LCP time.
| URL | Potential Savings (Ms) |
|---|---|
| https://future-boy.jp/img/index.jpg | 0 |
Avoids enormous network payloads — Total size was 464 KiB Large network payloads can cost users money and are linked to long load times.
| URL | Transfer Size (Bytes) |
|---|---|
| https://future-boy.jp/img/index.jpg | 451530 |
| https://www.google-analytics.com/analytics.js | 20594 |
| https://future-boy.jp/ | 1292 |
| https://www.google-analytics.com/j/collect?v=1&_v=j99&a=256162269&t=pageview&_s=1&dl=https%3A%2F%2Ffuture-boy.jp%2F&ul=en-us&de=UTF-8&dt=%E3%83%95%E3%83%A5%E3%83%BC%E3%83%81%E3%83%A3%E3%83%BC%E3%83%9C%E3%83%BC%E3%82%A4%E5%85%AC%E5%BC%8F%E3%82%B5%E3%82%A4%E3%83%88&sd=24-bit&sr=360x640&vp=980x1742&je=0&_u=IEBAAAABAAAAAC~&jid=1716894767&gjid=432929250&cid=529548148.1678537314&tid=UA-10310513-1&_gid=2121739913.1678537314&_r=1&_slc=1&z=1300152834 | 497 |
| https://future-boy.jp/css/grayz.css | 432 |
| http://future-boy.jp/ | 362 |
Avoids an excessive DOM size — 8 elements A large DOM (Document Object Model) will increase memory usage, cause longer system calculations as well as costly layout reflows.
| Statistic | Element | Value |
|---|---|---|
| Total DOM Elements | 8 | |
| Maximum DOM Depth | 8 | |
| Maximum Child Elements | 2 |
Avoid chaining critical requests — 1 chain found Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Future-boy.jp should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 0.1 s JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
| URL | Total CPU Time (Ms) | Script Evaluation (Ms) | Script Parse (Ms) |
|---|---|---|---|
| https://www.google-analytics.com/analytics.js | 85.884 | 79.072 | 3.56 |
| https://future-boy.jp/ | 61.068 | 13.96 | 5.04 |
Minimizes main-thread work — 0.2 s Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
| Category | Time Spent (Ms) |
|---|---|
| Script Evaluation | 97.884 |
| Other | 58.144 |
| Style & Layout | 8.952 |
| Script Parsing & Compilation | 8.6 |
| Rendering | 3.248 |
| Parse HTML & CSS | 3.212 |
All text remains visible during webfont loads Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
Keep request counts low and transfer sizes small — 6 requests • 464 KiB It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
| Resource Type | Requests | Transfer Size (Bytes) |
|---|---|---|
| Total | 6 | 474707 |
| Image | 1 | 451530 |
| Script | 1 | 20594 |
| Document | 1 | 1292 |
| Other | 2 | 859 |
| Stylesheet | 1 | 432 |
| Media | 0 | 0 |
| Font | 0 | 0 |
| Third-party | 2 | 21091 |
Minimize third-party usage — Third-party code blocked the main thread for 30 ms It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
| Third-Party | Transfer Size (Bytes) | Main-Thread Blocking Time (Ms) |
|---|---|---|
| 21091 | 26.256 |
Lazy load third-party resources with facades Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found The element which was identified as the Largest Contentful Paint.
| Element |
|---|
Largest Contentful Paint image was not lazily loaded Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
| Element |
|---|
Avoid large layout shifts — 1 element found Below is a list of all DOM elements that contribute to the CLS of the page.
| Element | CLS Contribution |
|---|---|
| 0.024004626437229 |
Uses passive listeners to improve scrolling performance Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()` Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks — 1 long task found Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
| URL | Start Time (Ms) | Duration (Ms) |
|---|---|---|
| https://www.google-analytics.com/analytics.js | 2040 | 82 |
Avoid non-composited animations It is recommended to avoid non-composited animations which are often janky and increase CLS.
Avoids `unload` event listeners The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.
First Contentful Paint (3G) — 2490 ms The time taken for the first image or text on the page to be rendered while on a 3G network.
Budgets
Performance budget It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.
Timing budget It is advised to set a timing budget to monitor the performance of your site.
Metrics
Speed Index — 4.2 s The time taken for the page contents to be visibly populated.
Other
Eliminate render-blocking resources — Potential savings of 180 ms Resources, such as JavaScript and style sheets, can block the first paint of the page. Future-boy.jp should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
| URL | Transfer Size (Bytes) | Potential Savings (Ms) |
|---|---|---|
| https://future-boy.jp/css/grayz.css | 432 | 180 |
Metrics
Largest Contentful Paint — 4.2 s The timing of the largest text or image that is painted.
Other
Efficiently encode images — Potential savings of 280 KiB Unoptimized images can consume more cellular data than what is necessary.
| URL | Resource Size (Bytes) | Potential Savings (Bytes) |
|---|---|---|
| https://future-boy.jp/img/index.jpg | 451249 | 286749 |
Serve images in next-gen formats — Potential savings of 373 KiB Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
| URL | Resource Size (Bytes) | Potential Savings (Bytes) |
|---|---|---|
| https://future-boy.jp/img/index.jpg | 451249 | 381627.2 |
Reduce initial server response time — Root document took 1,000 ms It is advised to keep the server response time short for the main document, because all other requests depend on it.
| URL | Time Spent (Ms) |
|---|---|
| https://future-boy.jp/ | 997.674 |
Serve static assets with an efficient cache policy — 2 resources found Future-boy.jp can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
| URL | Cache TTL (Ms) | Transfer Size (Bytes) |
|---|---|---|
| https://future-boy.jp/img/index.jpg | 0 | 451530 |
| https://www.google-analytics.com/analytics.js | 7200000 | 20594 |
Image elements do not have explicit `width` and `height` Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
| URL |
|---|
| https://future-boy.jp/img/index.jpg |
Does not have a `<meta name="viewport">` tag with `width` or `initial-scale` It is advised to use a '<meta name="viewport">' tag for the optimization of future-boy.jp on mobile screens.
Accessibility
Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of future-boy.jp. This includes details about various page attributes that can be optimized.Navigation
`[accesskey]` values are unique Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
`[id]` attributes on active, focusable elements are unique Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
Heading elements appear in a sequentially-descending order Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
No element has a `[tabindex]` value greater than 0 Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.
ARIA
`[aria-*]` attributes match their roles Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`button`, `link`, and `menuitem` elements have accessible names Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-hidden="true"]` is not present on the document `<body>` If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
`[aria-hidden="true"]` elements do not contain focusable descendents Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
ARIA input fields have accessible names Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
ARIA `meter` elements have accessible names Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `progressbar` elements have accessible names Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[role]`s have all required `[aria-*]` attributes Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children. Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid All ARIA roles require valid values to perform their intended functions.
ARIA toggle fields have accessible names Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
ARIA `tooltip` elements have accessible names Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `treeitem` elements have accessible names Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-*]` attributes have valid values ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.
ARIA IDs are unique Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.
Names and labels
Buttons have an accessible name Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Document has a `<title>` element Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<frame>` or `<iframe>` elements have a title Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
Image elements have `[alt]` attributes Provide short and descriptive alternative text where possible on informative elements.
`<input type="image">` elements have `[alt]` text Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Form elements have associated labels Screen readers and other assistive technologies rely on labels to properly announce form controls.
Links have a discernible name In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.
`<object>` elements have alternate text It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.
Contrast
Background and foreground colors have a sufficient contrast ratio Many (if not most) users find low-contrast text difficult or impossible to read.
Tables and lists
`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements. Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.
Definition list items are wrapped in `<dl>` elements In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`). Use proper list structure to aid screen readers and other assistive technologies.
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table. Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe. Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.
Internationalization and localization
`<html>` element has a valid value for its `[lang]` attribute Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.
Best practices
The document does not use `<meta http-equiv="refresh">` Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5. For users with low vision who rely on screen magnification, ensure that zooming is not disabled.
Audio and video
`<video>` elements contain a `<track>` element with `[kind="captions"]` Future-boy.jp may provide assistance to deaf or hearing-impaired users with captions on videos.
Internationalization and localization
`<html>` element does not have a `[lang]` attribute It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
| Failing Elements |
|---|
Manual Checks
The page has a logical tab order The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.
Interactive controls are keyboard focusable Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.
Interactive elements indicate their purpose and state Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.
The user's focus is directed to new content added to the page When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.
User focus is not accidentally trapped in a region Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.
Custom controls have associated labels Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.
Custom controls have ARIA roles Ensure that all custom interactive controls have appropriate ARIA roles.
Visual order on the page follows DOM order Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.
Offscreen content is hidden from assistive technology Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.
HTML5 landmark elements are used to improve navigation Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.
Best Practices
Indicates the recommended, best practices currently in place on the page and highlights the best practices that future-boy.jp should incorporate. This includes practices such as protecting pages with HTTPS.Audits
Avoids requesting the geolocation permission on page load When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids front-end JavaScript libraries with known security vulnerabilities Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Ensure CSP is effective against XSS attacks Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).
| Description | Directive | Severity |
|---|---|---|
| No CSP found in enforcement mode | High |
Audits
Allows users to paste into password fields Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.
Displays images with correct aspect ratio Ensure that image display dimensions match their natural aspect ratio.
Fonts with `font-display: optional` are preloaded It is recommended that optional fonts are preloaded.
Audits
Page has the HTML doctype Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Properly defines charset It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.
Audits
Detected JavaScript libraries Below is a list of all front-end JavaScript libraries that were detected on the page.
Avoids deprecated APIs Avoid deprecated APIs which will eventually be removed the browser.
Page has valid source maps Consider deploying source maps for added benefits such as the ability to debug while in production.
No issues in the `Issues` panel in Chrome Devtools There may be unresolved issues logged to Chrome Devtools.
Audits
Does not use HTTPS — 1 insecure request found Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
| Insecure URL | Request Resolution |
|---|---|
| http://future-boy.jp/ | Allowed |
Audits
Serves images with low resolution For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
| URL | Displayed size | Actual size | Expected size |
|---|---|---|---|
| https://future-boy.jp/img/index.jpg | 980 x 907 | 980 x 907 | 1960 x 1814 |
Audits
Browser errors were logged to the console Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
| Source | Description |
|---|---|
| Failed to load resource: the server responded with a status of 404 (Not Found) | |
| Failed to load resource: the server responded with a status of 404 (Not Found) |
SEO
Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for future-boy.jp. This includes optimizations such as providing meta data.Content Best Practices
Document has a `<title>` element Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Links have descriptive text Make use of descriptive link text to assist search engines in understanding the content.
Image elements have `[alt]` attributes Provide short and descriptive alternative text where possible on informative elements.
Document has a valid `hreflang` Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical` Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.
Crawling and Indexing
Page has successful HTTP status code Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Links are crawlable Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.
Page isn’t blocked from indexing Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
robots.txt is valid Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.
Mobile Friendly
Does not have a `<meta name="viewport">` tag with `width` or `initial-scale` It is advised to use a '<meta name="viewport">' tag for the optimization of future-boy.jp on mobile screens.
Document doesn't use legible font sizes Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Tap targets are not sized appropriately Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.
Content Best Practices
Document does not have a meta description Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
Manual Checks
Structured data is valid Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
PWA
Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of future-boy.jp. This includes details about web app manifests.Installable
Web app manifest or service worker do not meet the installability requirements — 1 reason User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
| Failure reason |
|---|
| No manifest was fetched |
PWA Optimized
Does not register a service worker that controls page and `start_url` A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Is not configured for a custom splash screen Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar. A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Content is not sized correctly for the viewport Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Does not have a `<meta name="viewport">` tag with `width` or `initial-scale` It is advised to use a '<meta name="viewport">' tag for the optimization of future-boy.jp on mobile screens.
Does not provide a valid `apple-touch-icon` iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.
Manifest doesn't have a maskable icon Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.
Manual Checks
Site works cross-browser Ensure that the Progressive Web App works correctly across every major browser.
Page transitions don't feel like they block on the network Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.
Each page has a URL Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.
Hosting
Server Location
| Server IP Address: | 210.172.210.244 |
| Continent: | Asia |
| Country: | Japan  |
| Region: | |
| City: | |
| Longitude: | 139.69 |
| Latitude: | 35.69 |
| Currencies: | JPY |
| Languages: | Japanese |
Web Hosting Provider
| Name | IP Address |
|---|---|
| Japan Network Information Center |
Registration
Domain Registrant
| Private Registration: | No |
| Name: | Futures Entertainment Co., Ltd. |
| Organization: |
| Country: | |
| City: | |
| State: | |
| Post Code: | |
| Email: | nakamura@futuresvideo.com |
| Phone: |
Note: Registration information is derived from various sources and may be inaccurate.
Domain Registrar
Security
Visitor Safety
| Mature Content: | Yes |
| McAfee WebAdvisor Rating: | Unknown |
| WOT Rating: | |
| WOT Trustworthiness: | |
| WOT Child Safety: |
Note: Safety information is not guaranteed.
SSL/TLS Certificate
| Issued To: | www.future-boy.jp |
| Issued By: | GlobalSign GCC R3 DV TLS CA 2020 |
| Valid From: | 18th April, 2022 |
| Valid To: | 20th May, 2023 |
| Subject: | CN = www.future-boy.jp |
| Hash: | ed1fe9a1 |
| Issuer: | CN = GlobalSign GCC R3 DV TLS CA 2020 O = GlobalSign nv-sa S = BE |
| Version: | 2 |
| Serial Number: | 28294901295883848040218735151 |
| Serial Number (Hex): | 5B6CFE68C354911ACC05B22F |
| Valid From: | 18th April, 2024 |
| Valid To: | 20th May, 2024 |
| Signature Algorithm (Short Name): | RSA-SHA256 |
| Signature Algorithm (Long Name): | sha256WithRSAEncryption |
| Authority Key Identifier: | keyid:0D:98:C0:73:7F:AB:BD:BD:D9:47:4B:49:AD:0A:4A:0C:AC:3E:C7:7C |
| Extended Key Usage: | TLS Web Server Authentication, TLS Web Client Authentication |
| CRL Distribution Points: | Full Name: URI:http://crl.globalsign.com/gsgccr3dvtlsca2020.crl |
| Certificate Policies: | Policy: 1.3.6.1.4.1.4146.1.10 CPS: https://www.globalsign.com/repository/ Policy: 2.23.140.1.2.1 |
| Authority Information Access: | CA Issuers - URI:http://secure.globalsign.com/cacert/gsgccr3dvtlsca2020.crt OCSP - URI:http://ocsp.globalsign.com/gsgccr3dvtlsca2020 |
| SCT List: | Signed Certificate Timestamp: Version : v1 (0x0) Log ID : E8:3E:D0:DA:3E:F5:06:35:32:E7:57:28:BC:89:6B:C9: 03:D3:CB:D1:11:6B:EC:EB:69:E1:77:7D:6D:06:BD:6E Timestamp : Apr 18 01:26:33.099 2022 GMT Extensions: none Signature : ecdsa-with-SHA256 30:46:02:21:00:D4:ED:6D:94:9E:99:C5:9C:BA:1B:21: A0:9F:20:66:79:83:85:6B:94:89:6A:C7:86:B2:B9:F2: 07:07:7D:8F:71:02:21:00:F4:7D:33:99:6D:1C:2B:46: 35:38:31:ED:10:AA:2A:A4:82:5E:02:37:07:7B:0C:52: BF:C3:C9:56:6B:DC:90:CD Signed Certificate Timestamp: Version : v1 (0x0) Log ID : 6F:53:76:AC:31:F0:31:19:D8:99:00:A4:51:15:FF:77: 15:1C:11:D9:02:C1:00:29:06:8D:B2:08:9A:37:D9:13 Timestamp : Apr 18 01:26:32.611 2022 GMT Extensions: none Signature : ecdsa-with-SHA256 30:46:02:21:00:AF:2C:B2:B1:D7:4C:69:D1:AE:A5:FE: D9:00:0D:0F:A0:CE:5D:3A:39:FC:81:4B:0E:48:00:74: 90:97:D9:AE:04:02:21:00:F9:08:E6:3F:D8:B3:92:A2: 2E:C1:8D:04:C4:78:FF:E5:48:0A:1A:83:86:3E:54:7B: 09:EE:DC:3D:49:E1:A3:D8 Signed Certificate Timestamp: Version : v1 (0x0) Log ID : 35:CF:19:1B:BF:B1:6C:57:BF:0F:AD:4C:6D:42:CB:BB: B6:27:20:26:51:EA:3F:E1:2A:EF:A8:03:C3:3B:D6:4C Timestamp : Apr 18 01:26:32.806 2022 GMT Extensions: none Signature : ecdsa-with-SHA256 30:45:02:21:00:F8:0F:FC:E3:8B:C0:77:F2:57:0C:9B: 14:39:94:BA:1C:5E:8C:FC:42:D4:B4:9F:AF:C7:FE:01: 52:68:B4:E4:1E:02:20:4D:89:B5:B0:FB:95:C5:B1:27: 6D:23:6F:36:D4:56:07:12:07:FE:03:F9:F1:77:AD:D8: DC:E2:4E:B8:4D:D6:36 |
| Key Usage: | Digital Signature, Key Encipherment |
| Basic Constraints: | CA:FALSE |
| Subject Alternative Name: | DNS:future-boy.jp DNS:www.future-boy.jp |
Technical
DNS Lookup
A Records
| Host | IP Address | Class | TTL |
|---|---|---|---|
| future-boy.jp. | 210.172.210.244 | IN | 21600 |
NS Records
| Host | Nameserver | Class | TTL |
|---|---|---|---|
| future-boy.jp. | ns3.mmrs.jp. | IN | 21600 |
| future-boy.jp. | mp02.mmrs.jp. | IN | 21600 |
MX Records
| Priority | Host | Server | Class | TTL |
|---|---|---|---|---|
| 10 | future-boy.jp. | mail.mp02.drive.ne.jp. | IN | 21600 |
SOA Records
| Domain Name | Primary NS | Responsible Email | TTL |
|---|---|---|---|
| future-boy.jp. | future-boy.jp. | root.future-boy.jp. | 21600 |
TXT Records
| Host | Value | Class | TTL |
|---|---|---|---|
| future-boy.jp. | v=spf1 | IN | 21600 |
HTTP Response Headers
| HTTP-Code: | HTTP/1.1 200 OK |
| Date: | 11th March, 2023 |
| Server: | Apache |
| Expires: | 19th November, 1981 |
| Cache-Control: | no-store, no-cache, must-revalidate, post-check=0, pre-check=0 |
| Content-Type: | text/html; charset=UTF-8 |
| Pragma: | no-cache |
| Set-Cookie: | * |
| Vary: | Accept-Encoding |
Whois Lookup
| Created: | |
| Changed: | |
| Expires: | |
| Status: |
| Nameservers: | mp02.mmrs.jp ns3.mmrs.jp |
| Owner Name: | Futures Entertainment Co., Ltd. |
| Owner Street: | Shinjuku-ku |
| Owner Email: | nakamura@futuresvideo.com |
| Full Whois: | [ JPRS database provides information on network administration. Its use is ]
[ restricted to network administration purposes. For further information, ] [ use 'whois -h whois.jprs.jp help'. To suppress Japanese output, add'/e' ] [ at the end of command, e.g. 'whois -h whois.jprs.jp xxx/e'. ] Domain Information: [ドメイン情報] [Domain Name] FUTURE-BOY.JP [登録者名] （株）フューチャーズエンターテインメント [Registrant] Futures Entertainment Co., Ltd. [Name Server] mp02.mmrs.jp [Name Server] ns3.mmrs.jp [Signing Key] [登録年月日] 2009/04/16 [有効期限] 2023/04/30 [状態] Active [最終更新] 2022/05/01 01:05:08 (JST) Contact Information: [公開連絡窓口] [名前] （株）フューチャーズエンターテインメント [Name] Futures Entertainment Co., Ltd. [Email] nakamura@futuresvideo.com [Web Page] [郵便番号] 160-0023 [住所] 東京都新宿区 西新宿7-9-15 [Postal Address] Shinjuku-ku 7-9-15 Nishishinjuku [電話番号] 03-3361-5299 [FAX番号] |
Nameservers
| Name | IP Address |
|---|---|
| mp02.mmrs.jp | 210.172.210.67 |
| ns3.mmrs.jp | 210.172.209.112 |
Love W3 Snoop?
Share This 