Access onewe.jp. ONEWE JAPAN OFFICIAL SITE

name

value

score

weighting

FCP (First Contentful Paint)

Value5.4 s

7/100

10%

LCP (Largest Contentful Paint)

Value32.3 s

0/100

25%

SI (Speed Index)

Value28.8 s

0/100

10%

TBT (Total Blocking Time)

Value46,800 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.491

17/100

15%

TTI (Time to Interactive)

Value84.8 s

0/100

10%

onewe.jp

352 ms

onewe.jp

1207 ms

gtm.js

86 ms

application-1471b5d43ddabe33036ffa0e1a6897c6.css

441 ms

js

141 ms

Our browser made a total of 79 requests to load all elements on the main page. We found that 25% of them (20 requests) were addressed to the original Onewe.jp, 23% (18 requests) were made to Platform.twitter.com and 20% (16 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Onewe.jp.

Content Size

2.3 MB

After Optimization

2.2 MB

In fact, the total size of Onewe.jp main page is 2.3 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.6 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 31.5 kB

Original 40.6 kB
After minification 39.5 kB
After compression 9.1 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 31.5 kB or 78% of the original size.

Image Optimization

-0%

Potential reduce by 1.0 kB

Original 1.6 MB
After minification 1.6 MB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. ONEWE images are well optimized though.

JavaScript Optimization

-6%

Potential reduce by 31.5 kB

Original 553.5 kB
After minification 553.5 kB
After compression 522.0 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. This website has mostly compressed JavaScripts.

CSS Optimization

-10%

Potential reduce by 10.6 kB

Original 111.2 kB
After minification 111.2 kB
After compression 100.6 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Onewe.jp has all CSS files already compressed.

Requests Now

After Optimization

The browser has sent 60 CSS, Javascripts, AJAX and image requests in order to completely render the main page of ONEWE. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 32 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.

Accessibility Issues

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

High

[aria-*] attributes do not match their roles

High

[aria-hidden="true"] elements contain focusable descendents

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

[aria-*] attributes do not have valid values

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

These are opportunities to improve the interpretation of your content by users in different locales.

High

<html> element does not have a [lang] attribute

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

High

Links do not have a discernible name

These items highlight common accessibility best practices.

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

Low

Detected JavaScript libraries

High

Page has valid source maps

Search Engine Optimization Advices

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

Language Detected

JA
Language Claimed

N/A
Encoding

UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Onewe.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Onewe.jp main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

onewe.jp

Open Graph data is detected on the main page of ONEWE. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook:

Report Summary

Performance

Accessibility

Best Practices

SEO

ONEWE JAPAN OFFICIAL SITE

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

onewe.jp

onewe.jp

gtm.js

application-1471b5d43ddabe33036ffa0e1a6897c6.css

js

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

onewe.jp

onewe.jp

gtm.js

application-1471b5d43ddabe33036ffa0e1a6897c6.css

js

api.js

application-6a629cb9b119b5eaf399371eeedc7198.js

ajaxzip3.js

widgets.js

loader.min.js

element.js

sdk.js

css

notosansjp.css

logo.png

arrow_left-37b24471abd07f03f33590972d8c8cee.png

arrow_right-ce998db5ab51b603abe2738311c06c33.png

pattern-ef92a393826068fc3b4e4929a7f0b9dd.png

_ONEWE__Profile_image2.jpg

_ONEWE__group1%E4%B8%AD.jpg

2012_onewe_online_M_.jpg

WE%E3%82%B5%E3%82%A4%E3%83%88%E3%83%9F%E3%83%8B%E3%83%A9%E3%82%A4%E3%83%96.jpg

ONEWE_%E4%BC%9A%E5%93%A1%E5%8B%9F%E9%9B%86.jpg

kiss_entertainment.png

rbw.png

recaptcha__en.js

IStPoTECtkE

dot-d112b5831107b38f05561c8f9310778c.png

logo-99ddaabf5bd5916f2f8e42797020e142.png

fontawesome-webfont-1d1a4a1a1482c78e33164b8d3f70687f.woff

TK3_WkUHHAIjg75cFRf3bXL8LICs1xZosUZiYA.ttf

TK3_WkUHHAIjg75cFRf3bXL8LICs18NvsUZiYA.ttf

TK3_WkUHHAIjg75cFRf3bXL8LICs1_FvsUZiYA.ttf

TK3_WkUHHAIjg75cFRf3bXL8LICs169vsUZiYA.ttf

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFCMj35zS1g.ttf

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFBEj35zS1g.ttf

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFE8j35zS1g.ttf

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFJEj35zS1g.ttf

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFBEi35zS1g.ttf

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFM8k35zS1g.ttf

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFPYk35zS1g.ttf

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFJEk35zS1g.ttf

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFLgk35zS1g.ttf