Tools & Wizards About Us

Report Summary

  • 3

    Performance

    Renders faster than
    20% of other websites

  • 70

    Accessibility

    Visual factors better than
    that of 35% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

bloom-style.jp

補正下着の専門通販　【ご愛用者7万人 ブルームリュクススタイル】

Page Load Speed

16.2 sec in total

First Response

764 ms

Resources Loaded

13.7 sec

Page Rendered

1.7 sec

About Website

Visit bloom-style.jp now to see the best up-to-date Bloom Style content for Japan and also check out these interesting facts you probably never knew about bloom-style.jp

人気の補正ブラ3/17まで70-50%OFF!!日本製の補正アイテムをお得に買えるチャンス！育乳ブラ補正ブラ50%off●初めての方にもお勧めの補正インナー●人気セットはプレゼント付で登場！☆新規会員登録で-1000Ptご利用可☆日本製補正下着インナー(bloom･MDN･Luxage)《高機能・高品質》矯正下着・補整インナーを超える新感覚の補正下着です。確かな品質・補正力をお試しください。【BL...

Visit bloom-style.jp

Key Findings

We analyzed Bloom-style.jp page load time and found that the first response time was 764 ms and then it took 15.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

bloom-style.jp performance score

3

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.5 s

6/100

10%

LCP (Largest Contentful Paint)

Value14.4 s

0/100

25%

SI (Speed Index)

Value14.3 s

1/100

10%

TBT (Total Blocking Time)

Value3,290 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.55

13/100

15%

TTI (Time to Interactive)

Value31.9 s

0/100

10%

Network Requests Diagram

bloom-style.jp

764 ms

m_sys_common.css

251 ms

import.css

428 ms

js

69 ms

ytag.js

705 ms

Our browser made a total of 155 requests to load all elements on the main page. We found that 8% of them (13 requests) were addressed to the original Bloom-style.jp, 79% (122 requests) were made to Gigaplus.makeshop.jp and 3% (5 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (4.5 sec) relates to the external source Gigaplus.makeshop.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 241.0 kB (4%)

Content Size

6.8 MB

After Optimization

6.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Bloom-style.jp main page is 6.8 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 6.5 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 109.2 kB

  • Original 130.4 kB
  • After minification 109.7 kB
  • After compression 21.3 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 20.7 kB, which is 16% 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 109.2 kB or 84% of the original size.

Image Optimization

-0%

Potential reduce by 31.0 kB

  • Original 6.5 MB
  • After minification 6.4 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. Bloom Style images are well optimized though.

JavaScript Optimization

-48%

Potential reduce by 66.3 kB

  • Original 137.3 kB
  • After minification 135.7 kB
  • After compression 70.9 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 66.3 kB or 48% of the original size.

CSS Optimization

-62%

Potential reduce by 34.5 kB

  • Original 55.6 kB
  • After minification 47.1 kB
  • After compression 21.1 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. Bloom-style.jp needs all CSS files to be minified and compressed as it can save up to 34.5 kB or 62% of the original size.

Requests Breakdown

Number of requests can be reduced by 65 (44%)

Requests Now

149

After Optimization

84

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

bloom-style.jp accessibility score

70

Accessibility Issues

ARIA

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

Impact

Issue

High

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

Names and labels

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

Impact

Issue

High

Buttons do not have an accessible name

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

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

Best Practices

bloom-style.jp best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

bloom-style.jp SEO score

77

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

Mobile Friendly

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

Impact

Issue

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 Bloom-style.jp 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 Bloom-style.jp 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

Open Graph description is not detected on the main page of Bloom Style. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: