Tools & Wizards About Us
brelio.jp screenshot

Report Summary

  • 26

    Performance

    Renders faster than
    46% 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

  • 92

    SEO

    Google-friendlier than
    75% of websites

brelio.jp

ブレイリオ公式ウェブサイト｜brelio.jp

Page Load Speed

2.6 sec in total

First Response

693 ms

Resources Loaded

1.6 sec

Page Rendered

260 ms

brelio.jp screenshot

About Website

Click here to check amazing Brelio content. Otherwise, check out these important facts you probably never knew about brelio.jp

ブレイリオは最高級の素材にこだわり、磨きあげられた技術で、生涯をともに過ごしていただける逸品をお届けします。

Visit brelio.jp

Key Findings

We analyzed Brelio.jp page load time and found that the first response time was 693 ms and then it took 1.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

brelio.jp performance score

26

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

25/100

10%

LCP (Largest Contentful Paint)

Value8.7 s

1/100

25%

SI (Speed Index)

Value8.0 s

22/100

10%

TBT (Total Blocking Time)

Value470 ms

61/100

30%

CLS (Cumulative Layout Shift)

Value0.964

2/100

15%

TTI (Time to Interactive)

Value10.0 s

27/100

10%

Network Requests Diagram

brelio.jp

693 ms

common.css

171 ms

space.gif

312 ms

header.gif

469 ms

brelio_green.jpg

336 ms

Our browser made a total of 12 requests to load all elements on the main page. We found that all of those requests were addressed to Brelio.jp and no external sources were called. The less responsive or slowest element that took the longest time to load (854 ms) belongs to the original domain Brelio.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 12.4 kB (8%)

Content Size

154.9 kB

After Optimization

142.5 kB

  • HTML
  • Images
  • CSS

In fact, the total size of Brelio.jp main page is 154.9 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. Only 10% of websites need less resources to load. Images take 139.7 kB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 4.1 kB

  • Original 5.7 kB
  • After minification 5.2 kB
  • After compression 1.6 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 4.1 kB or 72% of the original size.

Image Optimization

-0%

Potential reduce by 30 B

  • Original 139.7 kB
  • After minification 139.7 kB

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. Brelio images are well optimized though.

CSS Optimization

-87%

Potential reduce by 8.2 kB

  • Original 9.4 kB
  • After minification 7.8 kB
  • After compression 1.2 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. Brelio.jp needs all CSS files to be minified and compressed as it can save up to 8.2 kB or 87% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

11

After Optimization

11

  • Images
  • CSS

The browser has sent 11 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Brelio. According to our analytics all requests are already optimized.

Network Requests Diagram

brelio.jp

brelio.jp

693 ms

common.css

common.css

171 ms

space.gif

space.gif

312 ms

header.gif

header.gif

469 ms

brelio_green.jpg

brelio_green.jpg

336 ms

main.jpg

main.jpg

854 ms

recommend.jpg

recommend.jpg

675 ms

bg.gif

bg.gif

170 ms

leftbg.gif

leftbg.gif

296 ms

menubg1.gif

menubg1.gif

335 ms

footerbg.gif

footerbg.gif

336 ms

footerGreen.gif

footerGreen.gif

757 ms

Accessibility Review

brelio.jp accessibility score

98

Accessibility Issues

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

Links do not have a discernible name

Best Practices

brelio.jp best practices score

67

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

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

brelio.jp SEO score

92

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

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    SHIFT-JIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Brelio.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 Brelio.jp main page’s claimed encoding is shift-jis. 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

brelio.jp

Open Graph description is not detected on the main page of Brelio. 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: