5 sec in total
1.3 sec
3.3 sec
346 ms
Visit firekids.jp now to see the best up-to-date FIRE KIDS content for Japan and also check out these interesting facts you probably never knew about firekids.jp
ファイアーキッズは、1995年に横浜の白楽で創業したヴィンテージ・アンティークウォッチ専門の時計店です。
Visit firekids.jpWe analyzed Firekids.jp page load time and found that the first response time was 1.3 sec and then it took 3.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
firekids.jp performance score
name
value
score
weighting
Value4.2 s
20/100
10%
Value18.8 s
0/100
25%
Value9.4 s
12/100
10%
Value2,200 ms
6/100
30%
Value0.416
23/100
15%
Value22.7 s
1/100
10%
1272 ms
521 ms
369 ms
72 ms
555 ms
Our browser made a total of 143 requests to load all elements on the main page. We found that 36% of them (51 requests) were addressed to the original Firekids.jp, 10% (15 requests) were made to Google.com and 8% (12 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Firekids.jp.
Page size can be reduced by 611.9 kB (41%)
1.5 MB
885.7 kB
In fact, the total size of Firekids.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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 837.4 kB which makes up the majority of the site volume.
Potential reduce by 50.6 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 50.6 kB or 78% of the original size.
Potential reduce by 25.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. FIRE KIDS images are well optimized though.
Potential reduce by 515.2 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 515.2 kB or 62% of the original size.
Potential reduce by 20.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. Firekids.jp needs all CSS files to be minified and compressed as it can save up to 20.3 kB or 78% of the original size.
Number of requests can be reduced by 66 (49%)
136
70
The browser has sent 136 CSS, Javascripts, AJAX and image requests in order to completely render the main page of FIRE KIDS. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 43 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
firekids.jp
1272 ms
common.css
521 ms
top.css
369 ms
jquery.min.js
72 ms
rhinoslider-1.05.min.js
555 ms
jquery.cookie.js
383 ms
ui.js
572 ms
slide.js
551 ms
reset.css
175 ms
bookmark_button.js
350 ms
jsapi
22 ms
header-bg.gif
217 ms
ga.js
18 ms
sdk.js
29 ms
share.jpg
135 ms
button-only.gif
337 ms
logo.jpg
198 ms
adrs-top.gif
223 ms
line.gif
222 ms
font-switch.gif
222 ms
navi.gif
447 ms
main-bg2.gif
377 ms
main-bg.gif
376 ms
category.gif
758 ms
top-charm_s.gif
609 ms
top-column_s.jpg
446 ms
top-customer_s.gif
572 ms
top-special_s.jpg
570 ms
pay-icon.gif
606 ms
pay-lv1.gif
604 ms
banner-fb-page.gif
755 ms
info.gif
754 ms
rss.gif
767 ms
info-arrow.gif
772 ms
new-item.gif
772 ms
timthumb.php
1088 ms
newicon.gif
985 ms
status-sale.gif
1054 ms
list-detail.gif
1055 ms
timthumb.php
1060 ms
timthumb.php
1097 ms
timthumb.php
1187 ms
timthumb.php
1269 ms
topimage00.jpg
1548 ms
topimage01.jpg
1450 ms
topimage02.jpg
1450 ms
topimage03.jpg
1480 ms
topimage04.jpg
1558 ms
top-charm.gif
1427 ms
top-column.jpg
1602 ms
top-customer.gif
1612 ms
plusone.js
113 ms
__utm.gif
43 ms
likebox.php
244 ms
324 ms
collect
143 ms
widgets.js
90 ms
xd_arbiter.php
50 ms
xd_arbiter.php
79 ms
294 ms
97 ms
top-special.gif
1444 ms
syugo.jpg
1670 ms
cb=gapi.loaded_0
51 ms
cb=gapi.loaded_1
73 ms
fastbutton
116 ms
to-top.gif
1512 ms
default+ja.css
22 ms
default.css
26 ms
default+ja.I.js
24 ms
default.css
59 ms
postmessageRelay
78 ms
cb=gapi.loaded_0
49 ms
cb=gapi.loaded_1
21 ms
410ucuAGgaJ.css
106 ms
tSbl8xBI27R.css
116 ms
q68gy-v_YMF.js
130 ms
FJmpeSpHpjS.js
147 ms
0wM5s1Khldu.js
130 ms
1bNoFZUdlYZ.js
129 ms
sub-bg.gif
1375 ms
sub-list.gif
1423 ms
adrs.gif
1420 ms
3193398744-postmessagerelay.js
197 ms
rpc:shindig_random.js
87 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
246 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
274 ms
async-ads.js
160 ms
google_custom_search_watermark.gif
129 ms
small-logo.png
44 ms
search_box_icon.png
108 ms
clear.png
162 ms
link-blank.gif
1388 ms
598402_192759540850269_572317545_n.jpg
125 ms
11800235_745004718959079_4656241488314458925_n.jpg
82 ms
11026229_702582306530810_8557622128728934553_n.jpg
208 ms
10439509_227553104120411_5662312167573413111_n.jpg
90 ms
11021154_792169837533954_4547063380875884516_n.jpg
90 ms
11038562_138959713104897_9215232969212644710_n.jpg
157 ms
12189996_773558462772082_7700655332851086176_n.jpg
88 ms
wL6VQj7Ab77.png
55 ms
s7jcwEQH7Sx.png
54 ms
embed
492 ms
like.php
90 ms
cb=gapi.loaded_0
32 ms
wy1X4hBW7e7.js
27 ms
LVx-xkvaJ0b.png
16 ms
syndication
109 ms
344784276375621632
169 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html
47 ms
I6-MnjEovm5.js
9 ms
pQrUxxo5oQp.js
3 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.dark.ltr.css
27 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.dark.ltr.css
111 ms
firekids-twitter-logo_normal.jpg
153 ms
js
85 ms
init_embed.js
63 ms
common.js
62 ms
map.js
63 ms
google4.png
96 ms
overlay.js
94 ms
util.js
121 ms
onion.js
91 ms
search_impl.js
112 ms
StaticMapService.GetMapImage
221 ms
stats.js
102 ms
ViewportInfoService.GetViewportInfo
53 ms
transparent.png
45 ms
kh
115 ms
controls.js
33 ms
vt
107 ms
vt
111 ms
vt
125 ms
vt
122 ms
vt
121 ms
css
72 ms
mapcnt6.png
28 ms
jot.html
27 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
27 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
28 ms
Hgo13k-tfSpn0qi1SFdUfT8E0i7KZn-EPnyo3HZu7kw.woff
42 ms
d-6IYplOFocCacKzxwXSOD8E0i7KZn-EPnyo3HZu7kw.woff
42 ms
AuthenticationService.Authenticate
22 ms
firekids.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>).
firekids.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
firekids.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 Firekids.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 Firekids.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.
firekids.jp
Open Graph description is not detected on the main page of FIRE KIDS. 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: