12.1 sec in total
996 ms
10.9 sec
253 ms
Visit brandol.jp now to see the best up-to-date Brandol content for Japan and also check out these interesting facts you probably never knew about brandol.jp
海外ブランド専門 バッグ・財布・時計の通販ショップ「Brandol(ブランドル)」。在庫品は営業日即日出荷対応。3,980円以上のお買い上げで送料無料でお届けいたします。
Visit brandol.jpWe analyzed Brandol.jp page load time and found that the first response time was 996 ms and then it took 11.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
brandol.jp performance score
name
value
score
weighting
Value3.2 s
42/100
10%
Value4.9 s
29/100
25%
Value8.7 s
16/100
10%
Value150 ms
94/100
30%
Value0.054
98/100
15%
Value4.2 s
86/100
10%
996 ms
27 ms
337 ms
339 ms
340 ms
Our browser made a total of 111 requests to load all elements on the main page. We found that 24% of them (27 requests) were addressed to the original Brandol.jp, 74% (82 requests) were made to Rakuten.ne.jp and 1% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (9.2 sec) belongs to the original domain Brandol.jp.
Page size can be reduced by 243.3 kB (5%)
4.9 MB
4.6 MB
In fact, the total size of Brandol.jp main page is 4.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. 50% of websites need less resources to load. Images take 4.7 MB which makes up the majority of the site volume.
Potential reduce by 42.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. 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 42.5 kB or 86% of the original size.
Potential reduce by 103.0 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. Brandol images are well optimized though.
Potential reduce by 41.2 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 41.2 kB or 47% of the original size.
Potential reduce by 56.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. Brandol.jp needs all CSS files to be minified and compressed as it can save up to 56.6 kB or 80% of the original size.
Number of requests can be reduced by 8 (7%)
110
102
The browser has sent 110 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Brandol. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 4 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
brandol.jp
996 ms
jquery.min.js
27 ms
brandol.js
337 ms
site.js
339 ms
base.css
340 ms
pc.css
345 ms
slick.css
349 ms
slick.min.js
1003 ms
sanitize.css
336 ms
icono.css
674 ms
css
27 ms
im_100.png
389 ms
im_120.jpg
402 ms
im_130.jpg
420 ms
im_136.jpg
415 ms
im_140.jpg
437 ms
im_150.jpg
402 ms
im_160.jpg
654 ms
im_170.jpg
589 ms
im_175.jpg
1111 ms
im_180.jpg
1088 ms
im_185.jpg
596 ms
im_188.jpg
635 ms
im_300.png
764 ms
im_310.jpg
772 ms
im_320.jpg
806 ms
im_330.jpg
935 ms
im_340.jpg
1201 ms
im_400.png
1429 ms
im_420.jpg
981 ms
im_410.jpg
1127 ms
im_430.jpg
1620 ms
im_435.jpg
1261 ms
im_820.jpg
1292 ms
im_770.jpg
1320 ms
im_772.jpg
1391 ms
im_774.jpg
1924 ms
im_811.jpg
2151 ms
im_812.jpg
1560 ms
im_821.jpg
1615 ms
im_930.jpg
2136 ms
im_900.jpg
1768 ms
im_700.png
1791 ms
im_720.jpg
1790 ms
im_730.jpg
1957 ms
im_740.jpg
1966 ms
im_500.png
1986 ms
logo0.png
171 ms
mk-co.jpg
678 ms
mk-om.jpg
995 ms
mk-gu.jpg
1011 ms
mk-bu.jpg
1045 ms
mk-pr.jpg
873 ms
mk-gu_s.png
1343 ms
mk-co_s.png
2013 ms
mk-dh_s.png
2263 ms
mk-bv_s.png
2522 ms
mk-bu_s.png
2577 ms
mk-pr_s.png
2261 ms
mk-vw_s.png
2741 ms
mk-ds_s.png
3727 ms
mk-ea_s.png
3277 ms
mk-nf_s.png
9198 ms
mk-mm_s.png
3701 ms
mk-lc_s.png
3625 ms
im_500i.jpg
1732 ms
im_504.jpg
1764 ms
im_960.png
1781 ms
im_961.jpg
1749 ms
im_965.jpg
1874 ms
im_969.jpg
1949 ms
if_100.png
1748 ms
if_120.jpg
1742 ms
if_125.jpg
1712 ms
if_130.jpg
1719 ms
if_136.jpg
1702 ms
if_150.jpg
1744 ms
if_140.jpg
1727 ms
if_160.jpg
1600 ms
if_180.jpg
1739 ms
if_185.jpg
1476 ms
if_188.jpg
1542 ms
if_300.png
1583 ms
if_310.jpg
1508 ms
if_320.jpg
1450 ms
if_330.jpg
2036 ms
if_340.jpg
1515 ms
if_400.png
1502 ms
if_420.jpg
1605 ms
if_410.jpg
1678 ms
if_430.jpg
1275 ms
if_435.jpg
1397 ms
if_450.jpg
1321 ms
if_790.jpg
1753 ms
if_880.jpg
1883 ms
if_811.jpg
1385 ms
if_812.jpg
1347 ms
if_930.jpg
1484 ms
if_821.jpg
1535 ms
if_900.jpg
1365 ms
if_700.png
1436 ms
if_710.jpg
1565 ms
if_720.jpg
1522 ms
if_730.jpg
1583 ms
if_740.jpg
1538 ms
if_500.png
1454 ms
if_500i.jpg
1572 ms
if_504.jpg
2061 ms
if_960.png
2018 ms
if_965.jpg
1534 ms
if_969.jpg
1557 ms
brandol.jp accessibility score
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
[aria-hidden="true"] elements contain focusable descendents
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Image elements do not have [alt] attributes
Links do not have a discernible name
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
brandol.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
brandol.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
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
Document uses legible font sizes
Tap targets are not sized appropriately
![]()
JA
![]()
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Brandol.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 Brandol.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.
brandol.jp
Open Graph description is not detected on the main page of Brandol. 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: