Report Summary

  • 15

    Performance

    Renders faster than
    27% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 47% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

brandear.jp

ブランド品の買取なら【ブランディア】

Page Load Speed

10.7 sec in total

First Response

369 ms

Resources Loaded

9 sec

Page Rendered

1.3 sec

About Website

Welcome to brandear.jp homepage info - get ready to check Brandear best content for Japan right away, or after learning these important things about brandear.jp

\400万人のご利用実績で安心・安全/ブランド宅配買取サービス「ブランディア」♪ハイブランドからカジュアルブランドまで幅広く、1点からでも査定を承ります。汚れや傷があってもOK! 適正価格で買い取ります!!

Visit brandear.jp

Key Findings

We analyzed Brandear.jp page load time and found that the first response time was 369 ms and then it took 10.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

brandear.jp performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.1 s

1/100

10%

LCP (Largest Contentful Paint)

Value28.3 s

0/100

25%

SI (Speed Index)

Value19.6 s

0/100

10%

TBT (Total Blocking Time)

Value5,950 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.042

99/100

15%

TTI (Time to Interactive)

Value30.5 s

0/100

10%

Network Requests Diagram

brandear.jp

369 ms

brandear.jp

439 ms

gtm.js

87 ms

brandear_takuhai.css

199 ms

top.css

739 ms

Our browser made a total of 128 requests to load all elements on the main page. We found that 45% of them (57 requests) were addressed to the original Brandear.jp, 5% (6 requests) were made to Googletagmanager.com and 3% (4 requests) were made to Cm.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (3 sec) relates to the external source Gdn.socdm.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 349.2 kB (39%)

Content Size

900.5 kB

After Optimization

551.3 kB

In fact, the total size of Brandear.jp main page is 900.5 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 a small number of websites need less resources to load. Javascripts take 437.5 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 105.0 kB

  • Original 125.4 kB
  • After minification 74.0 kB
  • After compression 20.4 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 51.4 kB, which is 41% 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 105.0 kB or 84% of the original size.

Image Optimization

-3%

Potential reduce by 9.6 kB

  • Original 282.9 kB
  • After minification 273.2 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. Brandear images are well optimized though.

JavaScript Optimization

-44%

Potential reduce by 193.4 kB

  • Original 437.5 kB
  • After minification 431.2 kB
  • After compression 244.1 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 193.4 kB or 44% of the original size.

CSS Optimization

-75%

Potential reduce by 41.1 kB

  • Original 54.8 kB
  • After minification 39.6 kB
  • After compression 13.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. Brandear.jp needs all CSS files to be minified and compressed as it can save up to 41.1 kB or 75% of the original size.

Requests Breakdown

Number of requests can be reduced by 92 (79%)

Requests Now

116

After Optimization

24

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

Accessibility Review

brandear.jp accessibility score

79

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

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

<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

brandear.jp best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

brandear.jp SEO score

83

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Brandear.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 Brandear.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

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