Access hosei.cc. 補正下着専門店

hosei.cc screenshot

20

Performance

Renders faster than
37% of other websites
98

Accessibility

Visual factors better than
that of 94% of websites
67

Best Practices

More advanced features
available than in
24% of websites
86

SEO

Google-friendlier than
60% of websites

First Response

672 ms

Resources Loaded

11.9 sec

Page Rendered

1.3 sec

hosei.cc screenshot

About Website

Visit hosei.cc now to see the best up-to-date Hosei content and also check out these interesting facts you probably never knew about hosei.cc

補正下着専門店美Bodyは、良質な補正下着の専門店です。エル・ローズ、ラピアンズ、ティナプリ、プレミアムリフトアップ、ZEITAKU、トルマリンガードルなどの補正下着を取り扱っております。

Visit hosei.cc

Key Findings

We analyzed Hosei.cc page load time and found that the first response time was 672 ms and then it took 13.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

name

value

score

weighting

FCP (First Contentful Paint)

Value6.5 s

2/100

10%

LCP (Largest Contentful Paint)

Value9.5 s

0/100

25%

SI (Speed Index)

Value12.4 s

3/100

10%

TBT (Total Blocking Time)

Value710 ms

42/100

30%

CLS (Cumulative Layout Shift)

Value0.273

45/100

15%

TTI (Time to Interactive)

Value15.7 s

6/100

10%

hosei.cc

672 ms

hosei.co.uk

1019 ms

colormekit.css

310 ms

colormekit-responsive.css

316 ms

cross-border-cart.css

341 ms

Our browser made a total of 260 requests to load all elements on the main page. We found that 34% of them (88 requests) were addressed to the original Hosei.cc, 55% (143 requests) were made to Img06.shop-pro.jp and 3% (8 requests) were made to Hosei.co.uk. The less responsive or slowest element that took the longest time to load (3 sec) relates to the external source Img06.shop-pro.jp.

Content Size

2.9 MB

After Optimization

2.1 MB

In fact, the total size of Hosei.cc main page is 2.9 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. 70% of websites need less resources to load. Images take 2.3 MB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 94.9 kB

Original 106.4 kB
After minification 92.9 kB
After compression 11.5 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. This page needs HTML code to be minified as it can gain 13.6 kB, which is 13% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 94.9 kB or 89% of the original size.

Image Optimization

-14%

Potential reduce by 312.6 kB

Original 2.3 MB
After minification 2.0 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. Obviously, Hosei needs image optimization as it can save up to 312.6 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-73%

Potential reduce by 322.6 kB

Original 443.9 kB
After minification 331.9 kB
After compression 121.3 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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 322.6 kB or 73% of the original size.

CSS Optimization

-81%

Potential reduce by 48.1 kB

Original 59.1 kB
After minification 47.9 kB
After compression 11.0 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. Hosei.cc needs all CSS files to be minified and compressed as it can save up to 48.1 kB or 81% of the original size.

Requests Now

258

After Optimization

197

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

Accessibility Issues

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

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

High

Serves images with low resolution

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

Search Engine Optimization Advices

To appear in search results, crawlers need access to your app.

High

Links are not crawlable

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

Language and Encoding

Language Detected

JA
Language Claimed

JA
Encoding

EUC-JP

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hosei.cc can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it matches the claimed language. Our system also found out that Hosei.cc main page’s claimed encoding is euc-jp. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

hosei.cc

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