centervillage.co.jp

centervillage.co.jp is SSL secured

Free website and domain report on centervillage.co.jp

Last Updated: 27th August, 2024 Update Now
Overview

Snoop Summary for centervillage.co.jp

This is a free and comprehensive report about centervillage.co.jp. The domain centervillage.co.jp is currently hosted on a server located in Japan with the IP address 163.43.106.83, where the local currency is JPY and Japanese is the local language. Our records indicate that centervillage.co.jp is owned/operated by CVC INC. Centervillage.co.jp has the potential to be earning an estimated $6 USD per day from advertising revenue. If centervillage.co.jp was to be sold it would possibly be worth $4,233 USD (based on the daily revenue potential of the website over a 24 month period). Centervillage.co.jp is quite popular with an estimated 2,030 daily unique visitors. This report was last updated 27th August, 2024.

About centervillage.co.jp

Site Preview: centervillage.co.jp centervillage.co.jp
Title: 年齢確認 | 熟女人妻最強メーカー・センタービレッジ 公式ページ
Description: 熟女人妻最強メーカーセンタービレッジ公式サイト、作品情報の他、DVDの通信販売やダウンロード販売等を行っております。
Keywords and Tags: adult content, dvd, online shopping, センタービレッジ, センビレ, 人妻, 公式, 初撮り, 熟女, 通信販売
Related Terms:
Fav Icon:
Age:
Domain Created:
Domain Updated:
Domain Expires:
Review

Snoop Score

2/5

Valuation

$4,233 USD
Note: All valuation figures are estimates.

Popularity

Modest
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 306,098
Alexa Reach:
SEMrush Rank (US):
SEMrush Authority Score:
Moz Domain Authority: 0
Moz Page Authority: 0

Organic vs Paid (Google Ads)

Traffic

Visitors

Daily Visitors: 2,030
Monthly Visitors: 61,787
Yearly Visitors: 740,950
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $6 USD
Monthly Revenue: $176 USD
Yearly Revenue: $2,112 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: centervillage.co.jp 19
Domain Name: centervillage 13
Extension (TLD): cojp 4

Page Speed Analysis

Average Load Time: 1.46 seconds
Load Time Comparison: Faster than 60% of sites

PageSpeed Insights

Avg. (All Categories) 70
Performance 88
Accessibility 94
Best Practices 75
SEO 91
PWA 0
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://www.centervillage.co.jp//
Updated: 3rd May, 2022

1.98 seconds
First Contentful Paint (FCP)
74%
10%
16%

0.00 seconds
First Input Delay (FID)
100%
0%
0%

Simulate loading on desktop
88

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for centervillage.co.jp. This includes details about optimizing page load times which can result in a better user experience.

Metrics

First Contentful Paint — 0.8 s
The time taken for the first image or text on the page to be rendered.
Time to Interactive — 0.8 s
The time taken for the page to become fully interactive.
Total Blocking Time — 0 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
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Audits

Max Potential First Input Delay — 20 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 0.8 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://centervillage.co.jp/
http/1.1
0
472.73500007577
310
0
301
text/html
https://www.centervillage.co.jp//
http/1.1
473.10699999798
1534.0700000525
7402
6418
200
text/html
Document
https://cdn-cg.centervillage.co.jp/images/sogo/style_index.css
http/1.1
1546.6260000831
2807.7430000994
4551
4145
200
text/css
Stylesheet
https://cdn-cg.centervillage.co.jp/images/sogo/jquery.js
http/1.1
1546.7960000969
3124.3610000238
86346
85924
200
application/javascript
Script
https://cdn-cg.centervillage.co.jp/images/sogo/rollover.js
http/1.1
1547.1700000344
2821.5650001075
5022
4602
200
application/javascript
Script
https://cdn-cg.centervillage.co.jp/images/sogo/copy.js
http/1.1
1547.542000073
2803.3770000329
585
168
200
application/javascript
Script
https://cdn-cg.centervillage.co.jp/images/sogo/yes_btn.gif
http/1.1
2823.1300000334
3625.5050000036
5101
4695
200
image/gif
Image
https://cdn-cg.centervillage.co.jp/images/sogo/no_btn.gif
http/1.1
3131.5170000307
4247.4740000907
4982
4575
200
image/gif
Image
https://cdn-cg.centervillage.co.jp/images/sogo/img_right.png
http/1.1
3144.68700008
4837.6480001025
264270
263860
200
image/png
Image
https://cdn-cg.centervillage.co.jp/images/sogo/ie.gif
http/1.1
3144.8530000634
3959.6390000079
2071
1666
200
image/gif
Image
https://cdn-cg.centervillage.co.jp/images/sogo/wmp.gif
http/1.1
3145.0210000621
3942.2100000083
2026
1621
200
image/gif
Image
https://cdn-cg.centervillage.co.jp/images/sogo/get_flash_player.gif
http/1.1
3145.1400000369
4277.647000039
2085
1679
200
image/gif
Image
https://cdn-cg.centervillage.co.jp/images/sogo/get_adobe_reader.gif
http/1.1
3145.3040000051
3942.7170000272
2102
1697
200
image/gif
Image
https://www.googletagmanager.com/gtm.js?id=GTM-TQZ275K
h2
3145.4480000539
3169.384000008
41560
106383
200
application/javascript
Script
https://cdn-cg.centervillage.co.jp/images/sogo/body_base.gif
http/1.1
3146.9230001094
4246.497000102
7297
6890
200
image/gif
Image
https://cdn-cg.centervillage.co.jp/images/sogo/index-logo.png
http/1.1
3147.224000073
4277.2880000994
10798
10391
200
image/png
Image
https://cdn-cg.centervillage.co.jp/images/sogo/age18-bg.png
http/1.1
3147.4960000487
4092.1550000785
15769
15362
200
image/png
Image
https://www.google-analytics.com/analytics.js
h2
3248.6300000455
3253.8380000042
20631
50205
200
text/javascript
Script
https://www.google-analytics.com/j/collect?v=1&_v=j96&a=1143881162&t=pageview&_s=1&dl=https%3A%2F%2Fwww.centervillage.co.jp%2F%2F&ul=en-us&de=UTF-8&dt=%E5%B9%B4%E9%BD%A2%E7%A2%BA%E8%AA%8D%20%EF%BD%9C%20%E7%86%9F%E5%A5%B3%E4%BA%BA%E5%A6%BB%E6%9C%80%E5%BC%B7%E3%83%A1%E3%83%BC%E3%82%AB%E3%83%BC%E3%83%BB%E3%82%BB%E3%83%B3%E3%82%BF%E3%83%BC%E3%83%93%E3%83%AC%E3%83%83%E3%82%B8%20%E5%85%AC%E5%BC%8F%E3%83%9A%E3%83%BC%E3%82%B8&sd=24-bit&sr=800x600&vp=1350x940&je=0&_u=YEBAAAABAAAAAC~&jid=1647693011&gjid=971328064&cid=1781463555.1651608706&tid=UA-168423563-1&_gid=1264102680.1651608706&_r=1&gtm=2wg520TQZ275K&z=34956252
h2
3280.9470000211
3284.4920000061
621
1
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)
1577.66
8.171
3171.877
14.634
3186.527
67.256
3253.966
11.854
3273.476
7.628
3281.531
7.852
3298.808
23.465
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Other

Properly size images
Images can slow down the page's load time. Centervillage.co.jp should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Centervillage.co.jp should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Centervillage.co.jp should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Centervillage.co.jp should consider minifying JS files.
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Centervillage.co.jp should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats — Potential savings of 244 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://cdn-cg.centervillage.co.jp/images/sogo/img_right.png
263860
241599.45
https://cdn-cg.centervillage.co.jp/images/sogo/age18-bg.png
15362
8213.85
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. Centervillage.co.jp should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://centervillage.co.jp/
190
https://www.centervillage.co.jp//
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Centervillage.co.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://cdn-cg.centervillage.co.jp/images/sogo/body_base.gif
0
Avoids enormous network payloads — Total size was 472 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://cdn-cg.centervillage.co.jp/images/sogo/img_right.png
264270
https://cdn-cg.centervillage.co.jp/images/sogo/jquery.js
86346
https://www.googletagmanager.com/gtm.js?id=GTM-TQZ275K
41560
https://www.google-analytics.com/analytics.js
20631
https://cdn-cg.centervillage.co.jp/images/sogo/age18-bg.png
15769
https://cdn-cg.centervillage.co.jp/images/sogo/index-logo.png
10798
https://www.centervillage.co.jp//
7402
https://cdn-cg.centervillage.co.jp/images/sogo/body_base.gif
7297
https://cdn-cg.centervillage.co.jp/images/sogo/yes_btn.gif
5101
https://cdn-cg.centervillage.co.jp/images/sogo/rollover.js
5022
Avoids an excessive DOM size — 43 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
43
Maximum DOM Depth
9
Maximum Child Elements
4
Avoid chaining critical requests — 4 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Centervillage.co.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.0 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.centervillage.co.jp//
90.871
3.648
1.601
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)
Style & Layout
71.035
Script Evaluation
56.661
Other
36.351
Rendering
7.643
Script Parsing & Compilation
6.298
Parse HTML & CSS
4.558
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 — 19 requests • 472 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
19
483529
Image
10
316501
Script
5
154144
Document
1
7402
Stylesheet
1
4551
Other
2
931
Media
0
0
Font
0
0
Third-party
3
62812
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)
41560
0
21252
0
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 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
Below is a list of all DOM elements that contribute to the CLS of the page.
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoid long main-thread tasks
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Image elements have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
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

Largest Contentful Paint — 1.5 s
The timing of the largest text or image that is painted.

Other

Eliminate render-blocking resources — Potential savings of 330 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Centervillage.co.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://cdn-cg.centervillage.co.jp/images/sogo/style_index.css
4551
230
https://cdn-cg.centervillage.co.jp/images/sogo/jquery.js
86346
350
https://cdn-cg.centervillage.co.jp/images/sogo/rollover.js
5022
230
https://cdn-cg.centervillage.co.jp/images/sogo/copy.js
585
230
Reduce unused JavaScript — Potential savings of 79 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://cdn-cg.centervillage.co.jp/images/sogo/jquery.js
86346
59496
https://www.googletagmanager.com/gtm.js?id=GTM-TQZ275K
41560
21612
Enable text compression — Potential savings of 64 KiB
Text-based resources should be served with compression, such as gzip, deflate or brotli.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://cdn-cg.centervillage.co.jp/images/sogo/jquery.js
85924
55986
https://www.centervillage.co.jp//
6418
4016
https://cdn-cg.centervillage.co.jp/images/sogo/rollover.js
4602
3269
https://cdn-cg.centervillage.co.jp/images/sogo/style_index.css
4145
2718

Metrics

Speed Index — 2.8 s
The time taken for the page contents to be visibly populated.

Other

Reduce initial server response time — Root document took 1,060 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://www.centervillage.co.jp//
1061.957
Serve static assets with an efficient cache policy — 15 resources found
Centervillage.co.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://cdn-cg.centervillage.co.jp/images/sogo/img_right.png
0
264270
https://cdn-cg.centervillage.co.jp/images/sogo/jquery.js
0
86346
https://cdn-cg.centervillage.co.jp/images/sogo/age18-bg.png
0
15769
https://cdn-cg.centervillage.co.jp/images/sogo/index-logo.png
0
10798
https://cdn-cg.centervillage.co.jp/images/sogo/body_base.gif
0
7297
https://cdn-cg.centervillage.co.jp/images/sogo/yes_btn.gif
0
5101
https://cdn-cg.centervillage.co.jp/images/sogo/rollover.js
0
5022
https://cdn-cg.centervillage.co.jp/images/sogo/no_btn.gif
0
4982
https://cdn-cg.centervillage.co.jp/images/sogo/style_index.css
0
4551
https://cdn-cg.centervillage.co.jp/images/sogo/get_adobe_reader.gif
0
2102
https://cdn-cg.centervillage.co.jp/images/sogo/get_flash_player.gif
0
2085
https://cdn-cg.centervillage.co.jp/images/sogo/ie.gif
0
2071
https://cdn-cg.centervillage.co.jp/images/sogo/wmp.gif
0
2026
https://cdn-cg.centervillage.co.jp/images/sogo/copy.js
0
585
https://www.google-analytics.com/analytics.js
7200000
20631
Avoid `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.
Source
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 centervillage.co.jp on mobile screens.
94

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of centervillage.co.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"]`
Centervillage.co.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.
75

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that centervillage.co.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.
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

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.
Name Version
jQuery
1.5.2
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
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://centervillage.co.jp/
Allowed
Includes front-end JavaScript libraries with known security vulnerabilities — 8 vulnerabilities detected
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.
Library Version Vulnerability Count Highest Severity
8
Medium

Audits

Page lacks the HTML doctype, thus triggering quirks-mode
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
91

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for centervillage.co.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.
Document has 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.
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 centervillage.co.jp on mobile screens.

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.
0

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 centervillage.co.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 centervillage.co.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) 61
Performance 66
Accessibility 94
Best Practices 67
SEO 77
PWA 0
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://www.centervillage.co.jp//
Updated: 3rd May, 2022

3.68 seconds
First Contentful Paint (FCP)
57%
12%
31%

0.27 seconds
First Input Delay (FID)
1%
94%
5%

Simulate loading on mobile
66

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for centervillage.co.jp. This includes details about optimizing page load times which can result in a better user experience.

Metrics

Total Blocking Time — 40 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
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Audits

Max Potential First Input Delay — 110 ms
Users could experience a delay when interacting with the page.
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://centervillage.co.jp/
http/1.1
0
482.39700001432
325
0
301
text/html
https://www.centervillage.co.jp//
http/1.1
482.75100000319
2031.5709999995
7402
6418
200
text/html
Document
https://cdn-cg.centervillage.co.jp/images/sogo/style_index.css
http/1.1
2046.0360000143
3337.1470000129
4551
4145
200
text/css
Stylesheet
https://cdn-cg.centervillage.co.jp/images/sogo/jquery.js
http/1.1
2046.2840000109
3671.9750000047
86346
85924
200
application/javascript
Script
https://cdn-cg.centervillage.co.jp/images/sogo/rollover.js
http/1.1
2046.9680000097
3351.725000015
5022
4602
200
application/javascript
Script
https://cdn-cg.centervillage.co.jp/images/sogo/copy.js
http/1.1
2047.2850000078
3345.5250000115
585
168
200
application/javascript
Script
https://cdn-cg.centervillage.co.jp/images/sogo/yes_btn.gif
http/1.1
3353.8509999926
4346.1349999998
5101
4695
200
image/gif
Image
https://cdn-cg.centervillage.co.jp/images/sogo/no_btn.gif
http/1.1
3681.6239999898
4352.8039999946
4981
4575
200
image/gif
Image
https://cdn-cg.centervillage.co.jp/images/sogo/img_right.png
http/1.1
3694.4599999988
5321.9040000113
264269
263860
200
image/png
Image
https://cdn-cg.centervillage.co.jp/images/sogo/ie.gif
http/1.1
3694.6560000069
4511.2340000051
2071
1666
200
image/gif
Image
https://cdn-cg.centervillage.co.jp/images/sogo/wmp.gif
http/1.1
3694.789000001
4681.7699999956
2026
1621
200
image/gif
Image
https://cdn-cg.centervillage.co.jp/images/sogo/get_flash_player.gif
http/1.1
3694.874000008
4507.8140000114
2084
1679
200
image/gif
Image
https://cdn-cg.centervillage.co.jp/images/sogo/get_adobe_reader.gif
http/1.1
3695.0450000004
4809.5449999964
2103
1697
200
image/gif
Image
https://www.googletagmanager.com/gtm.js?id=GTM-TQZ275K
h2
3695.1600000029
3719.9540000001
41562
106383
200
application/javascript
Script
https://cdn-cg.centervillage.co.jp/images/sogo/body_base.gif
http/1.1
3695.9839999909
4664.3690000055
7297
6890
200
image/gif
Image
https://cdn-cg.centervillage.co.jp/images/sogo/index-logo.png
http/1.1
3696.1670000164
4937.2910000093
10799
10391
200
image/png
Image
https://cdn-cg.centervillage.co.jp/images/sogo/age18-bg.png
http/1.1
3696.3209999958
5150.7170000114
15770
15362
200
image/png
Image
https://www.google-analytics.com/analytics.js
h2
3831.3780000026
3837.4509999994
20631
50205
200
text/javascript
Script
https://www.google-analytics.com/j/collect?v=1&_v=j96&a=413482591&t=pageview&_s=1&dl=https%3A%2F%2Fwww.centervillage.co.jp%2F%2F&ul=en-us&de=UTF-8&dt=%E5%B9%B4%E9%BD%A2%E7%A2%BA%E8%AA%8D%20%EF%BD%9C%20%E7%86%9F%E5%A5%B3%E4%BA%BA%E5%A6%BB%E6%9C%80%E5%BC%B7%E3%83%A1%E3%83%BC%E3%82%AB%E3%83%BC%E3%83%BB%E3%82%BB%E3%83%B3%E3%82%BF%E3%83%BC%E3%83%93%E3%83%AC%E3%83%83%E3%82%B8%20%E5%85%AC%E5%BC%8F%E3%83%9A%E3%83%BC%E3%82%B8&sd=24-bit&sr=360x640&vp=980x1742&je=0&_u=YEBAAAABAAAAAC~&jid=173160205&gjid=346034957&cid=766937165.1651608727&tid=UA-168423563-1&_gid=445805980.1651608727&_r=1&gtm=2wg520TQZ275K&z=135140747
h2
3869.3239999993
3872.5960000011
621
1
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)
2093.093
7.811
3734.75
14.758
3749.52
84.29
3838.219
16.026
3855.159
10.084
3865.431
13.165
3879.189
8.063
3898.696
27.1
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Other

Properly size images
Images can slow down the page's load time. Centervillage.co.jp should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Centervillage.co.jp should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Centervillage.co.jp should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Centervillage.co.jp should consider minifying JS files.
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Centervillage.co.jp should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
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. Centervillage.co.jp should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://centervillage.co.jp/
630
https://www.centervillage.co.jp//
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Centervillage.co.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://cdn-cg.centervillage.co.jp/images/sogo/body_base.gif
0
Avoids enormous network payloads — Total size was 472 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://cdn-cg.centervillage.co.jp/images/sogo/img_right.png
264269
https://cdn-cg.centervillage.co.jp/images/sogo/jquery.js
86346
https://www.googletagmanager.com/gtm.js?id=GTM-TQZ275K
41562
https://www.google-analytics.com/analytics.js
20631
https://cdn-cg.centervillage.co.jp/images/sogo/age18-bg.png
15770
https://cdn-cg.centervillage.co.jp/images/sogo/index-logo.png
10799
https://www.centervillage.co.jp//
7402
https://cdn-cg.centervillage.co.jp/images/sogo/body_base.gif
7297
https://cdn-cg.centervillage.co.jp/images/sogo/yes_btn.gif
5101
https://cdn-cg.centervillage.co.jp/images/sogo/rollover.js
5022
Avoids an excessive DOM size — 43 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
43
Maximum DOM Depth
9
Maximum Child Elements
4
Avoid chaining critical requests — 4 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Centervillage.co.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.3 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.centervillage.co.jp//
474.96
12.132
4.964
Unattributable
115.192
12.88
0.96
https://www.google-analytics.com/analytics.js
113.356
103.232
4.844
https://cdn-cg.centervillage.co.jp/images/sogo/jquery.js
105.64
55.352
6.12
https://www.googletagmanager.com/gtm.js?id=GTM-TQZ275K
88.708
74.588
10.208
Minimizes main-thread work — 0.9 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)
Style & Layout
359.536
Script Evaluation
262.052
Other
137.808
Rendering
83.824
Script Parsing & Compilation
27.848
Parse HTML & CSS
19.172
Garbage Collection
16.828
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 — 19 requests • 472 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
19
483546
Image
10
316501
Script
5
154146
Document
1
7402
Stylesheet
1
4551
Other
2
946
Media
0
0
Font
0
0
Third-party
3
62814
Minimize third-party usage — Third-party code blocked the main thread for 50 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)
21252
49.324
41562
0
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 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
Below is a list of all DOM elements that contribute to the CLS of the page.
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoid long main-thread tasks — 4 long tasks 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.centervillage.co.jp//
1410
169
https://www.google-analytics.com/analytics.js
5962
108
https://cdn-cg.centervillage.co.jp/images/sogo/jquery.js
3690
59
https://www.googletagmanager.com/gtm.js?id=GTM-TQZ275K
4979
53
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Image elements have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
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

First Contentful Paint — 2.8 s
The time taken for the first image or text on the page to be rendered.
Time to Interactive — 5.5 s
The time taken for the page to become fully interactive.

Audits

First Meaningful Paint — 2.9 s
The time taken for the primary content of the page to be rendered.

Other

Serve images in next-gen formats — Potential savings of 244 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://cdn-cg.centervillage.co.jp/images/sogo/img_right.png
263860
241599.45
https://cdn-cg.centervillage.co.jp/images/sogo/age18-bg.png
15362
8213.85

Metrics

Speed Index — 8.3 s
The time taken for the page contents to be visibly populated.
Largest Contentful Paint — 5.2 s
The timing of the largest text or image that is painted.

Other

Eliminate render-blocking resources — Potential savings of 1,270 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Centervillage.co.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://cdn-cg.centervillage.co.jp/images/sogo/style_index.css
4551
780
https://cdn-cg.centervillage.co.jp/images/sogo/jquery.js
86346
1380
https://cdn-cg.centervillage.co.jp/images/sogo/rollover.js
5022
780
https://cdn-cg.centervillage.co.jp/images/sogo/copy.js
585
780
Reduce unused JavaScript — Potential savings of 79 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://cdn-cg.centervillage.co.jp/images/sogo/jquery.js
86346
59496
https://www.googletagmanager.com/gtm.js?id=GTM-TQZ275K
41562
21613
Enable text compression — Potential savings of 64 KiB
Text-based resources should be served with compression, such as gzip, deflate or brotli.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://cdn-cg.centervillage.co.jp/images/sogo/jquery.js
85924
55986
https://www.centervillage.co.jp//
6418
4016
https://cdn-cg.centervillage.co.jp/images/sogo/rollover.js
4602
3269
https://cdn-cg.centervillage.co.jp/images/sogo/style_index.css
4145
2718
Reduce initial server response time — Root document took 1,550 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://www.centervillage.co.jp//
1549.813
Serve static assets with an efficient cache policy — 15 resources found
Centervillage.co.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://cdn-cg.centervillage.co.jp/images/sogo/img_right.png
0
264269
https://cdn-cg.centervillage.co.jp/images/sogo/jquery.js
0
86346
https://cdn-cg.centervillage.co.jp/images/sogo/age18-bg.png
0
15770
https://cdn-cg.centervillage.co.jp/images/sogo/index-logo.png
0
10799
https://cdn-cg.centervillage.co.jp/images/sogo/body_base.gif
0
7297
https://cdn-cg.centervillage.co.jp/images/sogo/yes_btn.gif
0
5101
https://cdn-cg.centervillage.co.jp/images/sogo/rollover.js
0
5022
https://cdn-cg.centervillage.co.jp/images/sogo/no_btn.gif
0
4981
https://cdn-cg.centervillage.co.jp/images/sogo/style_index.css
0
4551
https://cdn-cg.centervillage.co.jp/images/sogo/get_adobe_reader.gif
0
2103
https://cdn-cg.centervillage.co.jp/images/sogo/get_flash_player.gif
0
2084
https://cdn-cg.centervillage.co.jp/images/sogo/ie.gif
0
2071
https://cdn-cg.centervillage.co.jp/images/sogo/wmp.gif
0
2026
https://cdn-cg.centervillage.co.jp/images/sogo/copy.js
0
585
https://www.google-analytics.com/analytics.js
7200000
20631
Avoid `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.
Source
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 centervillage.co.jp on mobile screens.
First Contentful Paint (3G) — 5849 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.
94

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of centervillage.co.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"]`
Centervillage.co.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.
67

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that centervillage.co.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.
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

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.
Name Version
jQuery
1.5.2
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
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://centervillage.co.jp/
Allowed
Includes front-end JavaScript libraries with known security vulnerabilities — 8 vulnerabilities detected
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.
Library Version Vulnerability Count Highest Severity
8
Medium

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://cdn-cg.centervillage.co.jp/images/sogo/img_right.png
420 x 495
420 x 495
840 x 990
https://cdn-cg.centervillage.co.jp/images/sogo/yes_btn.gif
220 x 50
220 x 50
440 x 100
https://cdn-cg.centervillage.co.jp/images/sogo/no_btn.gif
160 x 50
160 x 50
320 x 100
https://cdn-cg.centervillage.co.jp/images/sogo/get_adobe_reader.gif
32 x 32
32 x 32
64 x 64
https://cdn-cg.centervillage.co.jp/images/sogo/get_flash_player.gif
32 x 32
32 x 32
64 x 64
https://cdn-cg.centervillage.co.jp/images/sogo/ie.gif
32 x 32
32 x 32
64 x 64
https://cdn-cg.centervillage.co.jp/images/sogo/wmp.gif
32 x 32
32 x 32
64 x 64

Audits

Page lacks the HTML doctype, thus triggering quirks-mode
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
77

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for centervillage.co.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.
Document has 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.
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 centervillage.co.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.

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.
0

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 centervillage.co.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 centervillage.co.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: 163.43.106.83
Continent: Asia
Country: Japan
Japan Flag
Region:
City:
Longitude: 139.69
Latitude: 35.69
Currencies: JPY
Languages: Japanese

Web Hosting Provider

Name IP Address
SAKURA Internet Inc.
Registration

Domain Registrant

Private Registration: No
Name:
Organization: CVC INC
Country:
City:
State:
Post Code:
Email:
Phone:
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Security

Visitor Safety

Mature Content: Not Likely
McAfee WebAdvisor Rating: Unknown
WOT Rating:
WOT Trustworthiness: 61/100
WOT Child Safety: 10/100
Note: Safety information is not guaranteed.

SSL/TLS Certificate

Issued To: *.centervillage.co.jp
Issued By: R11
Valid From: 1st August, 2024
Valid To: 30th October, 2024
Subject: CN = *.centervillage.co.jp
Hash: 05008f4c
Issuer: CN = R11
O = Let's Encrypt
S = US
Version: 2
Serial Number: 0x03E973897DA03BFDD67CCA0376778986491A
Serial Number (Hex): 03E973897DA03BFDD67CCA0376778986491A
Valid From: 1st August, 2024
Valid To: 30th October, 2024
Signature Algorithm (Short Name): RSA-SHA256
Signature Algorithm (Long Name): sha256WithRSAEncryption
Authority Key Identifier: keyid:C5:CF:46:A4:EA:F4:C3:C0:7A:6C:95:C4:2D:B0:5E:92:2F:26:E3:B9
Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication
Certificate Policies: Policy: 2.23.140.1.2.1

Authority Information Access: OCSP - URI:http://r11.o.lencr.org
CA Issuers - URI:http://r11.i.lencr.org/

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 3F:17:4B:4F:D7:22:47:58:94:1D:65:1C:84:BE:0D:12:
ED:90:37:7F:1F:85:6A:EB:C1:BF:28:85:EC:F8:64:6E
Timestamp : Aug 2 00:06:12.156 2024 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:21:00:9B:79:FD:62:38:62:52:44:A8:B7:9E:
39:69:B1:1F:B2:52:BF:94:D5:0C:18:51:0C:F1:E3:28:
9C:7B:2D:13:1E:02:20:59:E6:FF:AA:1E:40:A9:F7:36:
2B:BE:D5:93:69:2B:61:4B:DA:EF:84:99:71:BA:E2:87:
5D:B4:30:A1:3F:83:8F
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : DF:E1:56:EB:AA:05:AF:B5:9C:0F:86:71:8D:A8:C0:32:
4E:AE:56:D9:6E:A7:F5:A5:6A:01:D1:C1:3B:BE:52:5C
Timestamp : Aug 2 00:06:14.367 2024 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:21:00:D1:DB:7C:28:36:34:A7:82:BC:8D:16:
D1:3B:0D:B1:54:34:39:5F:18:0E:5E:65:D7:83:AB:2A:
C0:91:7D:29:84:02:20:42:BE:43:2D:33:3E:F4:DF:CF:
5D:55:F3:AD:0F:1A:19:C3:84:CF:56:55:67:F0:DD:F2:
DD:E5:F6:1B:D7:E9:B5
Key Usage: Digital Signature, Key Encipherment
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:centervillage.co.jp
DNS:*.centervillage.co.jp
Technical

DNS Lookup

A Records

Host IP Address Class TTL
centervillage.co.jp. 163.43.106.83 IN 60

NS Records

Host Nameserver Class TTL
centervillage.co.jp. 02.dnsv.jp. IN 21600
centervillage.co.jp. 04.dnsv.jp. IN 21600
centervillage.co.jp. 01.dnsv.jp. IN 21600
centervillage.co.jp. 03.dnsv.jp. IN 21600

MX Records

Priority Host Server Class TTL
10 centervillage.co.jp. dmail.kagoya.net. IN 60

SOA Records

Domain Name Primary NS Responsible Email TTL
centervillage.co.jp. 01.dnsv.jp. hostmaster.dnsv.jp. 21600

TXT Records

Host Value Class TTL
centervillage.co.jp. v=spf1 IN 60

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Date: 27th August, 2024
Server: Apache/2.4.37 (centos) OpenSSL/1.1.1c PHP/7.2.11
Cache-Control: no-cache, private
Content-Type: text/html; charset=UTF-8
X-Powered-By: PHP/7.2.11
Set-Cookie: *
Connection: close

Whois Lookup

Created:
Changed:
Expires:
Status:
Nameservers: 01.dnsv.jp
02.dnsv.jp
03.dnsv.jp
04.dnsv.jp
Owner Organization: CVC INC
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: [ドメイン情報]
a. [ドメイン名] CENTERVILLAGE.CO.JP
e. [そしきめい] ゆうげんがいしゃしーぶいしー
f. [組織名] 有限会社CVC
g. [Organization] CVC INC
k. [組織種別] 有限会社
l. [Organization Type] Corporation
m. [登録担当者] SN3688JP
n. [技術連絡担当者] YE5838JP
p. [ネームサーバ] 01.dnsv.jp
p. [ネームサーバ] 02.dnsv.jp
p. [ネームサーバ] 03.dnsv.jp
p. [ネームサーバ] 04.dnsv.jp
s. [署名鍵]
[状態] Connected (2025/06/30)
[登録年月日] 2002/06/04
[接続年月日] 2002/06/05
[最終更新] 2024/08/02 09:02:41 (JST)

Nameservers

Name IP Address
01.dnsv.jp 157.7.32.53
02.dnsv.jp 157.7.33.53
03.dnsv.jp 157.7.34.53
04.dnsv.jp 157.7.35.53
Related

Subdomains

Similar Sites

Domain Valuation Snoop Score
0/5
$818 USD 2/5
$645 USD 1/5
$74,706 USD 3/5
0/5

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
0/5
$4,408 USD 2/5

Sites hosted on the same IP address