9.4 sec in total
452 ms
8.6 sec
332 ms
Click here to check amazing Focal content for Taiwan. Otherwise, check out these important facts you probably never knew about focal.co.jp
フォーカルポイント株式会社は、iPhone、iPad、スマートフォンなどのデジタル機器をこれまで以上に楽しくするケース、アクセサリを世界中のメーカーから選りすぐり日本国内で販売・サポートを行っております。
Visit focal.co.jpWe analyzed Focal.co.jp page load time and found that the first response time was 452 ms and then it took 8.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.
focal.co.jp performance score
name
value
score
weighting
Value7.9 s
0/100
10%
Value74.6 s
0/100
25%
Value21.7 s
0/100
10%
Value1,290 ms
18/100
30%
Value0.041
99/100
15%
Value34.4 s
0/100
10%
452 ms
1832 ms
956 ms
759 ms
386 ms
Our browser made a total of 157 requests to load all elements on the main page. We found that 56% of them (88 requests) were addressed to the original Focal.co.jp, 13% (20 requests) were made to Static.xx.fbcdn.net and 6% (9 requests) were made to D.adroll.com. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Focal.co.jp.
Page size can be reduced by 398.9 kB (26%)
1.6 MB
1.2 MB
In fact, the total size of Focal.co.jp main page is 1.6 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.0 MB which makes up the majority of the site volume.
Potential reduce by 61.9 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 61.9 kB or 76% of the original size.
Potential reduce by 41.0 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. Focal images are well optimized though.
Potential reduce by 223.3 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 223.3 kB or 61% of the original size.
Potential reduce by 72.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. Focal.co.jp needs all CSS files to be minified and compressed as it can save up to 72.7 kB or 80% of the original size.
Number of requests can be reduced by 68 (47%)
145
77
The browser has sent 145 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Focal. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 45 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
focal.co.jp
452 ms
www.focal.co.jp
1832 ms
basestyle.css
956 ms
jquery-ui-1.10.3.custom.css
759 ms
colorbox.css
386 ms
jquery.fancybox.css
640 ms
a51c7caa-ddf8-48fd-8c95-0383656585ac.js
61 ms
AC_RunActiveContent.js
559 ms
jquery-1.8.3.min.js
1622 ms
jquery.ui.core.min.js
594 ms
jquery.ui.widget.min.js
638 ms
jquery.ui.tabs.min.js
992 ms
jquery.pin.min.js
792 ms
jquery.colorbox-min.js
801 ms
jPages.min.js
1051 ms
jquery.tile.js
1012 ms
animatescroll.min.js
1019 ms
owl.carousel.min.js
1032 ms
jquery.fancybox.pack.js
1717 ms
jsapi
43 ms
base.js
1276 ms
detail.js
1288 ms
css.js
1317 ms
navi.js
1313 ms
win_op.js
1525 ms
site.js
1542 ms
feeds.js
1549 ms
plusone.js
202 ms
ga_social_tracking.js
1550 ms
owl.carousel.css
1524 ms
topdataset.js
1553 ms
conversion.js
18 ms
mti_cjk.js
40 ms
16 ms
print.css
364 ms
default+en.css
5 ms
default+en.I.js
7 ms
cb=gapi.loaded_0
36 ms
analytics.js
35 ms
ios.css
194 ms
subtlenet2.png
222 ms
formobile.png
185 ms
focal_logo_b.png
220 ms
search.png
220 ms
device.png
359 ms
banner.jpg
561 ms
banner.jpg
375 ms
banner.jpg
424 ms
banner.jpg
425 ms
banner.jpg
490 ms
banner.jpg
533 ms
banner.jpg
560 ms
banner.jpg
607 ms
banner.jpg
620 ms
banner.jpg
669 ms
banner.jpg
709 ms
banner.jpg
740 ms
banner.jpg
909 ms
banner.jpg
800 ms
banner.jpg
818 ms
banner.jpg
848 ms
banner.jpg
883 ms
banner.jpg
1104 ms
banner.jpg
992 ms
banner.jpg
1016 ms
banner.jpg
1033 ms
logo.svg
1061 ms
cart.svg
1085 ms
01261812_56a7387e25277.jpg
1758 ms
04201241_553475645f143.jpg
1418 ms
11191316_546c19b6ddc17.jpg
1994 ms
12101315_5487c8eb8844f.jpg
1857 ms
02261333_56cfd5802b4e9.jpg
1273 ms
02231752_56cc1dcf4e8be.jpg
1287 ms
collect
12 ms
entypo.woff
1494 ms
sdk.js
179 ms
widgets.js
67 ms
86 ms
02231700_56cc11b677ff4.jpg
1261 ms
02231608_56cc055f9b4dd.jpg
1405 ms
02231324_56cbdefb272a4.jpg
1467 ms
02081844_56b8638f5bfb3.jpg
1620 ms
16 ms
02081818_56b85d5a7c778.jpg
1561 ms
02081846_56b863db07ae9.jpg
1519 ms
02051332_56b425d79e2e0.jpg
1582 ms
02021745_56b06cbfd2f65.jpg
1613 ms
59 ms
02051043_56b3fe3b2afb5.jpg
1607 ms
xd_arbiter.php
124 ms
xd_arbiter.php
243 ms
01281926_56a9ece3d513e.jpg
1564 ms
banner.jpg
1717 ms
side_fb.jpg
1591 ms
side_tw.jpg
1616 ms
side_ig.jpg
1626 ms
newitems.gif
1594 ms
side_banner.jpg
1744 ms
tips.jpg
1637 ms
iphone6s-banner.jpg
1637 ms
appcessories.jpg
1596 ms
biz-style.jpg
1622 ms
casestudy_banner.jpg
1772 ms
news.php
378 ms
info.php
296 ms
Gfeeds
418 ms
page.php
200 ms
roundtrip.js
366 ms
xPv7gOXb_eI.css
174 ms
JzYLmHeY7gb.css
210 ms
LLJ7pJgsgEx.css
250 ms
XJLRWANetSB.css
282 ms
GH5LE4jl1pF.css
284 ms
_rx8naC75Dy.js
327 ms
t-KLv3gqZy0.js
287 ms
uLtKx7ldlvR.js
405 ms
xoyOB9tkUFt.js
292 ms
wyIfBc7KBcg.js
391 ms
6ANB6AXLXVBIRD7NN53EZX.js
344 ms
10995117_896746967014645_8363831377631439871_n.jpg
183 ms
safe_image.php
194 ms
safe_image.php
260 ms
safe_image.php
941 ms
safe_image.php
1512 ms
12799005_1075739135782093_4955298074389380606_n.jpg
238 ms
31441_495557760505092_1324624773_n.jpg
275 ms
wL6VQj7Ab77.png
105 ms
CSXXCvknpgK.png
102 ms
7NEHk19WerA.png
104 ms
bNvHN6v1NeH.png
104 ms
t-wz8gw1xG1.png
104 ms
lRyN50VcaFW.js
54 ms
out
6 ms
tr
4 ms
25 ms
out
7 ms
out
13 ms
out
13 ms
out
15 ms
out
14 ms
out
17 ms
u.php
58 ms
sync
32 ms
adsct
103 ms
pixel
70 ms
51 ms
sd
29 ms
sd
16 ms
in
6 ms
377928.gif
5 ms
tap.php
193 ms
in
5 ms
R9a_DtVRZgv.js
43 ms
cUDgRFxaoIk.js
39 ms
0JBr1QHp8Gi.js
43 ms
kDOzhTr2W91.js
46 ms
focal.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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
focal.co.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
focal.co.jp SEO score
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 Focal.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 Focal.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.
focal.co.jp
Open Graph data is detected on the main page of Focal. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: