9.4 sec in total
528 ms
8.1 sec
734 ms
Welcome to brickle.jp homepage info - get ready to check Brickle best content for Japan right away, or after learning these important things about brickle.jp
レゴ ショップ brickle!はレゴのネット通販専門店です。廃盤品・絶版品・日本未入荷商品・海外限定品・店舗限定品・レア物・ビンテージ品などのレアなレゴを中心に幅広い品揃えで展開しております。コレクション目的での商品探しなど、レゴに関することならなんでもお任せください!
Visit brickle.jpWe analyzed Brickle.jp page load time and found that the first response time was 528 ms and then it took 8.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
brickle.jp performance score
name
value
score
weighting
Value6.4 s
2/100
10%
Value11.4 s
0/100
25%
Value14.1 s
1/100
10%
Value2,470 ms
4/100
30%
Value0.905
3/100
15%
Value25.5 s
0/100
10%
528 ms
1318 ms
328 ms
521 ms
43 ms
Our browser made a total of 152 requests to load all elements on the main page. We found that 76% of them (115 requests) were addressed to the original Brickle.jp, 5% (8 requests) were made to Shop.brickle.jp and 3% (5 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (2.7 sec) belongs to the original domain Brickle.jp.
Page size can be reduced by 177.6 kB (5%)
3.6 MB
3.4 MB
In fact, the total size of Brickle.jp main page is 3.6 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. 65% of websites need less resources to load. Images take 3.3 MB which makes up the majority of the site volume.
Potential reduce by 51.8 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 51.8 kB or 79% of the original size.
Potential reduce by 9.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. Brickle images are well optimized though.
Potential reduce by 113.6 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 113.6 kB or 46% of the original size.
Potential reduce by 2.9 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. Brickle.jp needs all CSS files to be minified and compressed as it can save up to 2.9 kB or 12% of the original size.
Number of requests can be reduced by 34 (23%)
148
114
The browser has sent 148 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Brickle. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
brickle.jp
528 ms
shop.brickle.jp
1318 ms
colormekit.css
328 ms
colormekit-responsive.css
521 ms
index.css
43 ms
jquery.min.js
44 ms
js
84 ms
import.js
703 ms
all.css
53 ms
loader.min.js
43 ms
import.css
692 ms
cart.js
424 ms
async_cart_in.js
503 ms
product_stock.js
532 ms
js.cookie.js
526 ms
favorite_button.js
532 ms
style.css
193 ms
lightbox.css
199 ms
logo_header.png
187 ms
ico_facebook.png
187 ms
ico_twitter.png
375 ms
ico_rss.png
371 ms
img_shipping.png
560 ms
btn_insidecart.png
578 ms
ttl_news.png
695 ms
40409_frnt_img.jpg
1040 ms
40370_frnt_img.jpg
1050 ms
40252_frnt_img.jpg
1076 ms
40290_frnt_img.jpg
1085 ms
40188_frnt_img.jpg
1106 ms
71024_frnt_img.jpg
1219 ms
30453_frnt_img.jpg
1415 ms
30554_frnt_img.jpg
1417 ms
30527_frnt_img.jpg
1446 ms
853921_frnt_img.jpg
1273 ms
30384_frnt_img.jpg
1463 ms
6075.2_frnt_img.jpg
1576 ms
5614_frnt_img.jpg
1619 ms
4677_frnt_img.jpg
1613 ms
4418_frnt_img.jpg
1776 ms
5615_frnt_img.jpg
1994 ms
7955_frnt_img.jpg
1830 ms
1807_frnt_img.jpg
1938 ms
7953_frnt_img.jpg
2312 ms
4415_frnt_img.jpg
1976 ms
8398_frnt_img.jpg
2136 ms
40004_frnt_img.jpg
2022 ms
21309_frnt_img.jpg
2140 ms
10271_frnt_img.jpg
2190 ms
40465_frnt_img.jpg
2206 ms
76896_frnt_img.jpg
2221 ms
75179_frnt_img.jpg
2698 ms
60141_frnt_img.jpg
2341 ms
acc-track.js
858 ms
jquery.min.js
5 ms
lightbox.js
2358 ms
jquery.cookie.js
2234 ms
common.js
2299 ms
60168_frnt_img.jpg
2528 ms
31065_frnt_img.jpg
2190 ms
41148_frnt_img.jpg
2053 ms
41146_frnt_img.jpg
2092 ms
ttl_mailmag.png
2006 ms
li.php
177 ms
ttl_search.png
1711 ms
ttl_set.png
1728 ms
li.php
177 ms
ttl_calendar.png
1753 ms
img_calendar.png
1776 ms
btn_totop.png
1756 ms
ttl_shipping.png
1719 ms
li.php
178 ms
img_yamato.png
1687 ms
img_clickpost.png
1609 ms
ttl_payment.png
1645 ms
img_yamatocollect.png
1607 ms
img_creditcard.png
1627 ms
img_yucyo.png
1559 ms
img_ufj.png
1541 ms
img_shinsei.png
1601 ms
img_paypaybank.png
1465 ms
img_rakuten.png
1420 ms
img_paypal.png
1335 ms
img_paypay.png
1340 ms
ttl_packing.png
1343 ms
ttl_calendar.png
1393 ms
img_profile.jpg
1297 ms
logo_footer.png
1298 ms
sdk.js
74 ms
bg_catch.gif
968 ms
bg_bottom_news.png
1024 ms
ico_1x1brick_black.png
1034 ms
ico_goldstar.png
1126 ms
ico_silverstrar.png
1129 ms
ico_bronzestar.png
1132 ms
ico_star.png
1154 ms
ico_new_01.png
1218 ms
widgets.js
144 ms
fa-solid-900.woff
50 ms
fa-regular-400.woff
52 ms
ico_new_02.png
1168 ms
plugins.js
104 ms
sdk.js
34 ms
ico_new_03.png
1200 ms
share
210 ms
ico_new_04.png
1149 ms
ico_new_05.png
1115 ms
ico_new_06.png
1144 ms
widget_iframe.2f70fb173b9000da126c79afe2098f02.html
56 ms
ico_new_07.png
1153 ms
settings
101 ms
btn_submit.png
1133 ms
ico_search.png
1177 ms
btn_search.png
1149 ms
ico_1x1plate_black.png
1147 ms
widget.1.23.2.0.css
106 ms
button.1.23.2.0.js
117 ms
sentry.1.23.2.0.js
119 ms
button.856debeac157d9669cf51e73a08fbc93.js
23 ms
ico_1x1brick_blue.png
1142 ms
embeds
44 ms
embeds
61 ms
follow_button.2f70fb173b9000da126c79afe2098f02.ja.html
39 ms
tweet_button.2f70fb173b9000da126c79afe2098f02.ja.html
60 ms
ico_1x1plate_blue.png
1141 ms
ico_1x1brick_yellow.png
1135 ms
torimochi.js
10 ms
line_v3@3x.png
10 ms
ico_1x1plate_yellow.png
1181 ms
ico_1x1brick_red.png
1147 ms
ico_1x1plate_red.png
1139 ms
ico_1x1brick_orange.png
1132 ms
ico_1x1plate_orange.png
1139 ms
ico_1x1brick_lime.png
1134 ms
ico_1x1plate_lime.png
1165 ms
ico_1x1brick_pink.png
1145 ms
ico_1x1plate_pink.png
1149 ms
ico_1x1brick_green.png
1134 ms
ico_1x1plate_green.png
1144 ms
ico_1x1brick_purple.png
1142 ms
ico_1x1plate_purple.png
1155 ms
ico_1x1plate_brown.png
1141 ms
bg_information.png
1157 ms
bg_copyright.gif
1139 ms
ico_facebook_mini.png
1132 ms
ico_twitter_mini.png
1144 ms
ico_1x1brick_white.png
1150 ms
ico_set.png
1142 ms
prev.png
1167 ms
next.png
1142 ms
loading.gif
1124 ms
close.png
1138 ms
brickle.jp accessibility score
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
<frame> or <iframe> elements do not have a title
brickle.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
Browser errors were logged to the console
Page has valid source maps
brickle.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
JA
JA
EUC-JP
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Brickle.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 Brickle.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.
brickle.jp
Open Graph data is detected on the main page of Brickle. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: