9.2 sec in total
2 sec
6.9 sec
250 ms
Welcome to form-i.co.jp homepage info - get ready to check Form I best content for Japan right away, or after learning these important things about form-i.co.jp
ボタン付けやパンツの裾上げ、サイズ変更など様々な洋服のお直しに対応、その他にも毛皮・皮革のお直しやニットのほつれ直し、着物から洋服へのリメイクなども承っております。バッグの修理もお任せください。全国にある店舗でお待ちしています。
Visit form-i.co.jpWe analyzed Form-i.co.jp page load time and found that the first response time was 2 sec and then it took 7.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
form-i.co.jp performance score
name
value
score
weighting
Value5.0 s
10/100
10%
Value11.0 s
0/100
25%
Value10.2 s
8/100
10%
Value1,880 ms
9/100
30%
Value0
100/100
15%
Value12.0 s
16/100
10%
2005 ms
498 ms
1413 ms
1064 ms
361 ms
Our browser made a total of 94 requests to load all elements on the main page. We found that 80% of them (75 requests) were addressed to the original Form-i.co.jp, 11% (10 requests) were made to Google.com and 3% (3 requests) were made to Cse.google.com. The less responsive or slowest element that took the longest time to load (3.1 sec) belongs to the original domain Form-i.co.jp.
Page size can be reduced by 743.6 kB (27%)
2.8 MB
2.1 MB
In fact, the total size of Form-i.co.jp main page is 2.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 2.2 MB which makes up the majority of the site volume.
Potential reduce by 54.1 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 54.1 kB or 79% of the original size.
Potential reduce by 310.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. Obviously, Form I needs image optimization as it can save up to 310.9 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 243.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 243.1 kB or 59% of the original size.
Potential reduce by 135.5 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. Form-i.co.jp needs all CSS files to be minified and compressed as it can save up to 135.5 kB or 86% of the original size.
Number of requests can be reduced by 40 (44%)
91
51
The browser has sent 91 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Form I. 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 9 to 1 for CSS and as a result speed up the page load time.
form-i.co.jp
2005 ms
html5.css
498 ms
style.css
1413 ms
pc.css
1064 ms
styles.css
361 ms
lightbox.min.css
562 ms
jquery.js
1663 ms
jquery-migrate.min.js
652 ms
common.js
576 ms
iview.css
178 ms
iview.skin.home.css
234 ms
jquery.form.min.js
453 ms
scripts.js
360 ms
jquery.touchwipe.min.js
422 ms
jquery.lightbox.min.js
535 ms
wp-embed.min.js
534 ms
jquery.easing.js
610 ms
raphael-min.js
949 ms
iview.min.js
733 ms
iview.config.home.js
733 ms
wp-emoji-release.min.js
184 ms
header_logo_1.png
445 ms
header_button_1.gif
444 ms
homeCM_4.png
446 ms
homeCM_2.png
447 ms
homeCM_3.png
444 ms
homeCM_6.jpg
443 ms
daimaru_kobe_20160129_i.jpg
628 ms
23ed8869ed58127c1f9bed7774002eea-186x186.jpg
631 ms
web_cam1.jpg
628 ms
tenjinbashi_20160209_2-300x225.jpg
629 ms
crysta_anniversary_20160216_i.jpg
637 ms
hep_sale_201602_i.jpg
622 ms
yurakucho_160114_6-225x300.jpg
758 ms
tenjinbashi_20160118-186x186.jpg
778 ms
d093c88e03415b7bf69f59c7621308d2-186x186.jpg
778 ms
image2-300x225.jpg
780 ms
mitsukoshi_fukuoka_20160128_i.jpg
784 ms
classy_ec-186x186.jpg
823 ms
hanako_20151008_1-231x300.jpg
926 ms
3a9112487125ef83e8c14cdef83e2d19-300x225.jpg
954 ms
84ec77c4becfa4730171cfc19e88a7e7-300x225.jpg
956 ms
mz_nagoya001-300x225.jpg
958 ms
659abac1fc6e6dcad977b732e2d115ae-300x225.jpg
964 ms
02e28f30ad94669c29c40a0f9b980f27-300x273.jpg
1013 ms
8c49dd87263725c96457c2edd2bd585d-186x186.jpg
1090 ms
b7bb2990338712196809d4ccf1941c4f-287x300.jpg
1133 ms
menstk000-222x300.jpg
1137 ms
isetan_urawa_e-186x186.jpg
1136 ms
side_banner_5.png
1145 ms
side_banner_1.png
1199 ms
side_banner_6.png
1255 ms
side_banner_4.png
1308 ms
footer_nav_1.gif
1311 ms
footer_logo_1.png
1312 ms
analytics.js
33 ms
global_header_nav_bg_1.gif
1320 ms
cse.js
20 ms
homeCM_1.png
1352 ms
cse.js
398 ms
like.php
360 ms
collect
22 ms
collect
73 ms
index_bg_1.png
1323 ms
index_ttl_1.gif
1051 ms
layer_bg_1.png
1055 ms
icon_arrow_1.png
1055 ms
index_bg_2.png
1811 ms
jsapi
56 ms
index_bg_3.png
1700 ms
rU2ubZ6l1Q5.js
502 ms
LVx-xkvaJ0b.png
569 ms
default+ja.css
9 ms
default.css
20 ms
default+ja.I.js
24 ms
default.css
40 ms
async-ads.js
71 ms
google_custom_search_watermark.gif
49 ms
small-logo.png
44 ms
search_box_icon.png
45 ms
clear.png
46 ms
nav_logo114.png
43 ms
index_bg_4.jpg
1048 ms
index_ttl_3.gif
1047 ms
index_ttl_2.gif
1047 ms
icon_arrow_2.png
1221 ms
index_bg_5.png
1404 ms
index_ttl_4.gif
1218 ms
index_ttl_5.gif
1171 ms
slider_bg_1.png
1248 ms
header_button_1_on.gif
1257 ms
tn_001.jpg
3136 ms
tn_002.jpg
1773 ms
tn_003.jpg
2096 ms
form-i.co.jp accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
form-i.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
Page has valid source maps
form-i.co.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 Form-i.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 Form-i.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.
form-i.co.jp
Open Graph data is detected on the main page of Form I. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: