9.2 sec in total
1.3 sec
7.3 sec
635 ms
Visit 0038.co.jp now to see the best up-to-date 0038 content for Thailand and also check out these interesting facts you probably never knew about 0038.co.jp
杉養蜂園オンラインショップ|杉養蜂園について
Visit 0038.co.jpWe analyzed 0038.co.jp page load time and found that the first response time was 1.3 sec and then it took 7.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
0038.co.jp performance score
name
value
score
weighting
Value1.5 s
95/100
10%
Value2.3 s
93/100
25%
Value3.8 s
83/100
10%
Value0 ms
100/100
30%
Value0.067
97/100
15%
Value1.5 s
100/100
10%
1330 ms
332 ms
334 ms
8 ms
901 ms
Our browser made a total of 153 requests to load all elements on the main page. We found that 87% of them (133 requests) were addressed to the original 0038.co.jp, 2% (3 requests) were made to Google.com and 1% (2 requests) were made to Googleadservices.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain 0038.co.jp.
Page size can be reduced by 380.3 kB (22%)
1.7 MB
1.4 MB
In fact, the total size of 0038.co.jp main page is 1.7 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. 60% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 38.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 38.8 kB or 78% of the original size.
Potential reduce by 28.9 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. 0038 images are well optimized though.
Potential reduce by 184.9 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 184.9 kB or 63% of the original size.
Potential reduce by 127.7 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. 0038.co.jp needs all CSS files to be minified and compressed as it can save up to 127.7 kB or 83% of the original size.
Number of requests can be reduced by 66 (45%)
147
81
The browser has sent 147 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 0038. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 26 to 1 for CSS and as a result speed up the page load time.
1330 ms
colorbox.css
332 ms
import.css
334 ms
jquery-ui.css
8 ms
jquery-2.1.1.min.js
901 ms
jquery.scrolldepth.min.js
366 ms
eccube.js
557 ms
eccube.legacy.js
383 ms
jquery.colorbox-min.js
490 ms
jquery-ui-1.10.3.custom.min.js
823 ms
jquery.ui.datepicker-ja.js
543 ms
jquery.flickslide.js
763 ms
fixheights.js
656 ms
scroll.js
720 ms
jquery.hint.js
740 ms
jquery.bxslider.js
1031 ms
conversion.js
13 ms
getseal
87 ms
reset.css
571 ms
common.css
600 ms
contents.css
815 ms
table.css
660 ms
bloc.css
747 ms
bloc_alpha.css
752 ms
popup.css
783 ms
jquery-ui-1.10.3.multi.custom.css
990 ms
flickslide.css
869 ms
print.css
929 ms
default.css
931 ms
top.css
970 ms
commodity.css
1004 ms
under.css
1035 ms
cosme.css
1103 ms
shopping.css
1107 ms
guide.css
1153 ms
cart.css
1147 ms
jquery.bxslider.css
1193 ms
list.css
1200 ms
auto_teiki.css
1281 ms
first.css
1283 ms
subou.css
1310 ms
logo.gif
242 ms
btn_eng.gif
255 ms
btn_chn.gif
254 ms
btn_kra.gif
257 ms
head_tel.gif
252 ms
btn_contact.gif
239 ms
submenu01.gif
427 ms
submenu02.gif
424 ms
submenu03.gif
425 ms
submenu04.gif
426 ms
btn_search.gif
423 ms
gmenu01.jpg
428 ms
gmenu02.jpg
561 ms
gmenu03.jpg
568 ms
gmenu04.jpg
566 ms
gmenu05.jpg
574 ms
gmenu06.jpg
557 ms
main01.jpg
1201 ms
main02.jpg
1213 ms
main03.jpg
1222 ms
main04.jpg
1278 ms
thumb01.jpg
744 ms
thumb02.jpg
757 ms
thumb03.jpg
921 ms
thumb04.jpg
943 ms
n_tit01.gif
1101 ms
201603_PC_banner_01.jpg
1314 ms
201603_PC_banner_02.jpg
1459 ms
201603_PC_banner_03.jpg
1388 ms
first.jpg
1539 ms
mitsubako.jpg
1553 ms
n_tit02.gif
1453 ms
n_honey01.jpg
1497 ms
n_honey02.jpg
1583 ms
n_honey03.jpg
1632 ms
gtm.js
56 ms
n_honey04.jpg
1633 ms
pta.js
539 ms
89 ms
sdk.js
206 ms
analytics.js
39 ms
getseal
265 ms
261 ms
190 ms
n_tit03.gif
1456 ms
n_mtit01.gif
1462 ms
n_ph01_02.jpg
1479 ms
n_ph01_03.jpg
1528 ms
n_ph01_04.jpg
1567 ms
collect
106 ms
n_ph01_01.jpg
1508 ms
92 ms
collect
90 ms
81 ms
n_mtit02.gif
1458 ms
n_ph02_01.jpg
1454 ms
n_ph02_04.jpg
1473 ms
n_ph02_03.jpg
1547 ms
85 ms
n_ph02_02.jpg
1572 ms
xd_arbiter.php
93 ms
xd_arbiter.php
157 ms
n_mtit03.gif
1573 ms
ga-audiences
28 ms
n_ph03_01.jpg
1484 ms
71eaa112.js
172 ms
n_ph03_02.jpg
1504 ms
n_ph03_03.jpg
1495 ms
n_mtit04.gif
1595 ms
n_ph04_01.jpg
1603 ms
n_ph04_02.jpg
1439 ms
n_ph04_03.jpg
1448 ms
n_mtit05.gif
1307 ms
n_ph05_01.jpg
1305 ms
n_ph05_02.jpg
1249 ms
n_ph05_03.jpg
1155 ms
n_ph05_04.jpg
1149 ms
n_mtit06.gif
1149 ms
n_ph06_01.jpg
1121 ms
n_ph06_02.jpg
1119 ms
n_ph06_03.jpg
1152 ms
n_mtit07.gif
1076 ms
n_ph07_02.jpg
1079 ms
n_ph07_03.jpg
1032 ms
n_mtit08.gif
1026 ms
n_mtit10.gif
1065 ms
btn_rss.jpg
1123 ms
btn_login.gif
1066 ms
sidebtn_fukusu.jpg
1078 ms
sidebtn01.gif
1045 ms
sidebtn02.gif
1025 ms
sidebtn14.jpg
1086 ms
sidebtn05.gif
1093 ms
sidebtn12.jpg
1076 ms
sidebtn08.jpg
1080 ms
sidebtn11.jpg
1029 ms
sidebtn13.jpg
1051 ms
sidebtn09.jpg
1104 ms
sidebtn10.gif
1067 ms
sidebtn03.jpg
1075 ms
sidebtn04.jpg
1076 ms
sidemenu01.jpg
1029 ms
sidemenu02.jpg
1058 ms
sidemenu03.jpg
1121 ms
sidemenu04.jpg
1040 ms
sidemenu05.jpg
1061 ms
sidemenu06.jpg
1067 ms
pagetop.gif
1054 ms
footer_img01.gif
1080 ms
copyright.gif
1121 ms
footer_img02.gif
1177 ms
main01.jpg
1217 ms
0038.co.jp accessibility score
0038.co.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
0038.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
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 0038.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 0038.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.
0038.co.jp
Open Graph description is not detected on the main page of 0038. 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: