10 sec in total
548 ms
8.8 sec
646 ms
Visit bigsize.co.jp now to see the best up-to-date Bigsize content for Japan and also check out these interesting facts you probably never knew about bigsize.co.jp
大きいサイズのメンズ服専門通販ミッド。2L~10L、帽子・靴もビッグサイズ。営業日の16時までのご注文・ご入金確認で当日出荷!
Visit bigsize.co.jpWe analyzed Bigsize.co.jp page load time and found that the first response time was 548 ms and then it took 9.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
bigsize.co.jp performance score
name
value
score
weighting
Value3.6 s
32/100
10%
Value9.2 s
1/100
25%
Value9.3 s
12/100
10%
Value320 ms
76/100
30%
Value0.089
92/100
15%
Value12.4 s
15/100
10%
548 ms
1168 ms
354 ms
1067 ms
1798 ms
Our browser made a total of 173 requests to load all elements on the main page. We found that 47% of them (82 requests) were addressed to the original Bigsize.co.jp, 17% (29 requests) were made to Static.xx.fbcdn.net and 12% (21 requests) were made to Scontent-iad3-1.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (3.2 sec) belongs to the original domain Bigsize.co.jp.
Page size can be reduced by 520.9 kB (36%)
1.5 MB
946.3 kB
In fact, the total size of Bigsize.co.jp main page is 1.5 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 723.9 kB which makes up the majority of the site volume.
Potential reduce by 70.2 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 70.2 kB or 80% of the original size.
Potential reduce by 5.8 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. Bigsize images are well optimized though.
Potential reduce by 355.8 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 355.8 kB or 65% of the original size.
Potential reduce by 89.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. Bigsize.co.jp needs all CSS files to be minified and compressed as it can save up to 89.1 kB or 84% of the original size.
Number of requests can be reduced by 78 (46%)
168
90
The browser has sent 168 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Bigsize. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 44 to 1 for JavaScripts and from 16 to 1 for CSS and as a result speed up the page load time.
bigsize.co.jp
548 ms
www.bigsize.co.jp
1168 ms
info.css
354 ms
yui-min.js
1067 ms
yui.module.combo.js
1798 ms
mid-analytics-purchaseCycle.js
544 ms
gaEventTracker.js
380 ms
marqueeBanner.css
703 ms
marqueeBanner.js
902 ms
calendar.css
734 ms
calendar.js
1255 ms
mid-youtube-player.js
906 ms
Screen.js
739 ms
getseal
601 ms
commonAction-min.js
930 ms
conversion.js
30 ms
s_retargeting.js
557 ms
conversion.js
528 ms
brick.js
37 ms
UA-366439-24.js
350 ms
master.css
1254 ms
contents.css
1267 ms
dc.js
127 ms
analytics.js
125 ms
logo_mid_kensuke2.png
189 ms
sprite_3.png
745 ms
icon_cart.png
396 ms
2509_a.jpeg
725 ms
2502_a.jpeg
726 ms
1957_a.jpeg
745 ms
2496_a.jpeg
703 ms
2454_a.gif
1001 ms
getImage.php
1357 ms
getImage.php
1382 ms
getImage.php
1390 ms
getImage.php
1378 ms
getImage.php
1383 ms
1011586180-1-1.jpeg
1345 ms
1011735315-1-1.jpeg
1891 ms
1011533340-5-1.jpeg
1736 ms
1011534350-1-1.jpeg
1912 ms
1011576101-1-1.jpeg
1738 ms
1011576111-1-1.jpeg
1743 ms
1020023307-1-1.jpeg
1733 ms
1020023306-1-1.jpeg
2092 ms
1011746100-2-1.jpeg
2097 ms
1011545500-1-1.jpeg
2282 ms
1011844350-2-1.jpeg
2108 ms
1011545340-2-1.jpeg
2234 ms
1020023099-2-1.jpeg
2290 ms
1011404340-1-1.jpeg
2618 ms
1020020059-2-1.jpeg
2841 ms
1020022390-1-1.jpeg
2651 ms
7700-1.jpeg
2761 ms
7735-1.jpeg
2645 ms
7697-1.jpeg
2832 ms
staff2.jpg
3171 ms
no1.gif
3019 ms
1011586160-1-1.jpeg
3009 ms
no2.gif
3073 ms
likebox.php
253 ms
collect
32 ms
__utm.gif
31 ms
widgets.js
14 ms
ga-audiences
53 ms
getseal
463 ms
widget-base.css
3022 ms
jTuqQ-OPDr6.css
42 ms
n370yiaI2G6.css
50 ms
dbNRhrdsQao.css
60 ms
uzCGVqplqq-.css
68 ms
1-xIpmMldel.css
85 ms
cCIltMJutxu.css
75 ms
_rx8naC75Dy.js
98 ms
x5F9OMjKyLw.js
114 ms
ICDbTSzjQEg.js
71 ms
TTCre3391I0.js
83 ms
njO1TPvGzoR.js
113 ms
rFmE1g6Dkoz.js
132 ms
7cm7D75Y0Sf.js
128 ms
C-h3nYPqETO.js
127 ms
oRoBXlHCpEy.js
126 ms
336JejShbZp.js
127 ms
sj-JwAJi4AH.js
126 ms
DKRU1bYTkTw.js
172 ms
ZNPAadQNc33.js
129 ms
W0OV23mIOyO.js
128 ms
36TdwhIHusi.js
127 ms
b_6HNn_J2BZ.js
128 ms
autocomplete-list.css
2805 ms
12669639_1076043485759323_48689581983260353_n.jpg
145 ms
11880541_991332960897043_8445973143041051649_n.jpg
16 ms
12552688_157786637926969_8181600905619561695_n.jpg
17 ms
11140033_847786155336659_5286031669771548182_n.jpg
22 ms
12572991_1013138688745627_4156778440299251695_n.jpg
17 ms
10374918_673238582748304_7910073264381259761_n.jpg
22 ms
922_943737779043569_2563639651979378541_n.jpg
22 ms
10462770_1602687560008580_8775847588038419253_n.jpg
25 ms
11693896_1667179853568010_4806568485170766018_n.jpg
27 ms
1017360_1382572155292040_1801432401_n.jpg
30 ms
578387_407299012686285_1172100187_n.jpg
27 ms
12573783_153409695037770_4384563440283678711_n.jpg
28 ms
10959646_1603618223192460_558447365764013726_n.jpg
29 ms
12417812_968696213177967_2940514825482269453_n.jpg
28 ms
542996_120259161444075_1801415475_n.jpg
30 ms
607_1087336524630019_4090843756298740800_n.jpg
32 ms
12717940_1087329281297410_4233164311708870065_n.jpg
31 ms
12745648_1081689158528089_3857954208182696811_n.jpg
31 ms
12745552_1081689201861418_6381280026369992757_n.jpg
31 ms
12798958_1087986091231729_8646400885219265436_n.jpg
31 ms
1451317_1087959041234434_176723176786133877_n.jpg
32 ms
wL6VQj7Ab77.png
17 ms
s7jcwEQH7Sx.png
21 ms
QDwYpIaRyfG.png
19 ms
a-ZN6WoEOje.png
18 ms
pUFVdPjIRct.png
19 ms
I6-MnjEovm5.js
10 ms
vlXaquuXMrr.js
15 ms
1011776112-1-1.jpeg
2698 ms
no3.gif
2688 ms
1011585340-2-1.jpeg
2778 ms
no4.gif
2788 ms
1011735200-3-1.jpeg
2816 ms
no5.gif
2570 ms
1011546110-1-1.jpeg
2420 ms
1011586143-1-1.jpeg
2417 ms
1011576112-1-1.jpeg
2479 ms
1011635300-1-1.jpeg
2496 ms
1011775301-1-1.jpeg
2513 ms
1011582502-3-1.jpeg
2550 ms
1180_a.gif
2591 ms
2416_a.jpeg
2590 ms
367_a.jpeg
2632 ms
2505_a.jpeg
2702 ms
1360_a.jpeg
2534 ms
712_a.jpeg
2572 ms
2432_a.jpeg
2580 ms
2430_a.jpeg
2771 ms
2507_a.jpeg
2795 ms
mobileinfo.gif
2545 ms
snsIcons.png
2551 ms
li.gif
2563 ms
sprite_navi_banner.png
2610 ms
footerbg.jpg
2514 ms
footercontents.jpg
2550 ms
35 ms
conversion.js
607 ms
22 ms
788 ms
brick.common.js
317 ms
brick.heatmap.js
167 ms
brick.ltv.js
327 ms
timeline.1b43d11859b7663a2225b885f87704a5.js
21 ms
sync.php
709 ms
syndication
102 ms
345088852341440512
292 ms
brick.lib.js
359 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
3 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
5 ms
lhRMH5zp_normal.png
107 ms
6vZTvypY_normal.jpg
144 ms
QCkU5AJq_normal.jpg
108 ms
CcICQGHVIAAByHM.jpg:small
106 ms
Cb-BV4YXIAEXn4V.jpg:small
112 ms
Cb8qFYuVAAAu49U.jpg:small
109 ms
Cb4lD3XUMAAc4QQ.jpg:small
110 ms
brick.heatmap_base.js
328 ms
jot
26 ms
sync.php
168 ms
collect
10 ms
collect
60 ms
collect
24 ms
facebookWallView.css
363 ms
bigsize.co.jp accessibility score
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
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>).
bigsize.co.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
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
bigsize.co.jp SEO score
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 Bigsize.co.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 Bigsize.co.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.
bigsize.co.jp
Open Graph description is not detected on the main page of Bigsize. 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: