9.3 sec in total
752 ms
8.2 sec
341 ms
Visit feeriede.jp now to see the best up-to-date Feeriede content and also check out these interesting facts you probably never knew about feeriede.jp
ランドセル専門ショップ「フェリーデ」は、榮伸の人気ブランド「Feerie de email」フェリー・デ・エマイユと「Basic Style」ベーシックスタイル2016最新ランドセルをお取り扱いしています。
Visit feeriede.jpWe analyzed Feeriede.jp page load time and found that the first response time was 752 ms and then it took 8.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
feeriede.jp performance score
752 ms
317 ms
336 ms
1204 ms
510 ms
Our browser made a total of 100 requests to load all elements on the main page. We found that 87% of them (87 requests) were addressed to the original Feeriede.jp, 4% (4 requests) were made to Google-analytics.com and 2% (2 requests) were made to T10.aqtracker.com. The less responsive or slowest element that took the longest time to load (3.8 sec) belongs to the original domain Feeriede.jp.
Page size can be reduced by 298.7 kB (17%)
1.8 MB
1.5 MB
In fact, the total size of Feeriede.jp main page is 1.8 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. 45% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 58.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. This page needs HTML code to be minified as it can gain 18.8 kB, which is 27% 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 58.5 kB or 83% of the original size.
Potential reduce by 19.7 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. Feeriede images are well optimized though.
Potential reduce by 151.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 151.1 kB or 60% of the original size.
Potential reduce by 69.3 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. Feeriede.jp needs all CSS files to be minified and compressed as it can save up to 69.3 kB or 84% of the original size.
Number of requests can be reduced by 44 (44%)
99
55
The browser has sent 99 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Feeriede. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
feeriede.jp
752 ms
m_sys_common.css
317 ms
import.css
336 ms
script.js
1204 ms
jquery.min.js
510 ms
jquery.bxslider.min.js
357 ms
jquery.bxslider.css
361 ms
top_slide.css
628 ms
jquery.min.js
863 ms
common.js
669 ms
check_history.css
387 ms
pager.css
644 ms
shopdetail.css
694 ms
ranking.css
745 ms
basket.css
891 ms
security.css
958 ms
category_menu.css
1029 ms
topicpath.css
1074 ms
catalog.css
1271 ms
ga.js
25 ms
count.makeshop.jp
518 ms
logo.jpg
253 ms
txt_header_concept.jpg
495 ms
cart.jpg
338 ms
slide1.jpg
1003 ms
slide2.jpg
1259 ms
slide3.jpg
2582 ms
slide4.jpg
1410 ms
information.jpg
665 ms
privilege.jpg
823 ms
catalog.jpg
1023 ms
top_rank1.gif
1157 ms
top_rank2.jpg
1527 ms
top_rank3.jpg
1697 ms
top_rank4.jpg
1791 ms
top_rank5.jpg
1876 ms
top_rank6.gif
1862 ms
top_bnr1.jpg
2358 ms
top_bnr2.jpg
2458 ms
top_bnr3.jpg
2390 ms
top_bnr4.jpg
2376 ms
top_tokuten1.jpg
2487 ms
top_tokuten2.jpg
3192 ms
top_tokuten4.jpg
2733 ms
top_osusume1.gif
2748 ms
top_osusume2.jpg
2967 ms
top_osusume3.jpg
2988 ms
top_osusume4.jpg
3086 ms
top_osusume5.jpg
3232 ms
top_line.gif
3106 ms
top_select1.gif
3277 ms
top_select2.jpg
3831 ms
top_select3.jpg
3423 ms
top_select4.jpg
3418 ms
top_select5.jpg
3507 ms
top_select6.jpg
3565 ms
top_voice1.gif
3622 ms
__utm.gif
19 ms
aq_tag_aos.js
137 ms
392 ms
analytics.js
6 ms
collect
14 ms
EM34BYVZ46DUGEQNJE6A
141 ms
top_voice2.jpg
3510 ms
top_ico_pink.gif
3446 ms
gmsync
298 ms
segmentation.js
29 ms
382 ms
cnt
365 ms
top_voice4.jpg
3363 ms
newstitle.gif
3246 ms
left_edge.gif
3157 ms
right_edge.gif
3095 ms
free_shipping.jpg
3292 ms
quality_assurance.jpg
3176 ms
sample.jpg
3142 ms
pagetopBtn.png
2860 ms
background.jpg
2812 ms
header.jpg
2927 ms
i_arrow04.gif
2810 ms
globalmenu.jpg
2943 ms
left_ttl_01.jpg
2815 ms
i_bag11.jpg
2341 ms
i_bag01.jpg
2398 ms
i_bag02.jpg
2565 ms
i_bag03.jpg
2515 ms
i_bag04.jpg
2529 ms
i_bag05.jpg
2487 ms
i_bag06.jpg
2420 ms
i_bag07.jpg
2390 ms
i_bag08.jpg
2339 ms
i_bag09.jpg
2321 ms
i_bag10.jpg
2238 ms
i_arrow01.jpg
2314 ms
top_voice3.jpg
2248 ms
top_voice5.jpg
2362 ms
footer.jpg
2232 ms
i_arrow02.gif
2239 ms
beacon.html
10 ms
bx_loader.gif
168 ms
feeriede.jp SEO score
JA
JA
EUC-JP
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Feeriede.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 Feeriede.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.
feeriede.jp
Open Graph description is not detected on the main page of Feeriede. 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: