8.2 sec in total
1.4 sec
5.8 sec
924 ms
Click here to check amazing Castle Iphone content for Japan. Otherwise, check out these important facts you probably never knew about castle-iphone.com
iPhone(アイフォン)修理なら、大阪・梅田・難波・天王寺・天六・京橋などに店舗を構え、送料無料で全国対応も可能なiPhone修理専門店キャッスルへ。iPhone4・4S・5・5s・5c・6・6plusのガラス割れ・液晶交換など、各種故障に格安で対応いたします。店舗持ち込みなら、最短30分で修理可能です。
Visit castle-iphone.comWe analyzed Castle-iphone.com page load time and found that the first response time was 1.4 sec and then it took 6.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
castle-iphone.com performance score
1438 ms
651 ms
345 ms
350 ms
33 ms
Our browser made a total of 109 requests to load all elements on the main page. We found that 82% of them (89 requests) were addressed to the original Castle-iphone.com, 5% (5 requests) were made to Platform.twitter.com and 4% (4 requests) were made to O.twimg.com. The less responsive or slowest element that took the longest time to load (2.7 sec) belongs to the original domain Castle-iphone.com.
Page size can be reduced by 428.4 kB (9%)
4.8 MB
4.4 MB
In fact, the total size of Castle-iphone.com main page is 4.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. 70% of websites need less resources to load. Images take 4.3 MB which makes up the majority of the site volume.
Potential reduce by 42.7 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 42.7 kB or 81% of the original size.
Potential reduce by 46.2 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. Castle Iphone images are well optimized though.
Potential reduce by 224.4 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 224.4 kB or 74% of the original size.
Potential reduce by 115.0 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. Castle-iphone.com needs all CSS files to be minified and compressed as it can save up to 115.0 kB or 83% of the original size.
Number of requests can be reduced by 31 (29%)
107
76
The browser has sent 107 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Castle Iphone. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.
castle-iphone.com
1438 ms
common.css
651 ms
style2.css
345 ms
menu_smp.js
350 ms
jquery.min.js
33 ms
jquery.easing.1.3.js
377 ms
jquery.accordion.js
380 ms
jquery.mobile-1.4.5.min.js
976 ms
jquery-1.10.2.min.js
6 ms
styles.css
513 ms
styles.css
520 ms
font-awesome.css
6 ms
responsive.dataTables.min.css
562 ms
tablepress-combined.min.css
564 ms
tablepress-responsive-flip.min.css
682 ms
jquery.min.js
34 ms
jquery.easing.min.js
14 ms
nivo-slider.css
378 ms
public.css
435 ms
default.css
438 ms
jquery.form.min.js
491 ms
scripts.js
537 ms
scripts.js
550 ms
scroll-back-to-top.js
625 ms
wp-embed.min.js
626 ms
jquery.nivo.slider.pack.js
777 ms
wp-emoji-release.min.js
197 ms
logo.jpg
365 ms
tel2.jpg
262 ms
free2.jpg
264 ms
head1.jpg
263 ms
head3.jpg
265 ms
head4.jpg
305 ms
head2.jpg
365 ms
free0.jpg
369 ms
tel0.jpg
395 ms
menu.jpg
568 ms
slide2.jpg
961 ms
slide3.jpg
1566 ms
slide4.jpg
1664 ms
%E6%98%A5%E3%83%88%E3%82%AF%E3%82%AD%E3%83%A3%E3%83%B3%E3%83%9A%E3%83%BC%E3%83%B3.jpg
1948 ms
6S%E6%96%99%E9%87%91%E5%80%A4%E4%B8%8B%E3%81%92.jpg
1898 ms
repair1.jpg
948 ms
repair2.jpg
1326 ms
repair3.jpg
1124 ms
repair4.jpg
1289 ms
repair5.jpg
1457 ms
repair6.jpg
1515 ms
repair7.jpg
1619 ms
repair8.jpg
1706 ms
repair9.jpg
1736 ms
repair10.jpg
1783 ms
repair11.jpg
1984 ms
taiou1.jpg
1895 ms
taiou-phone.jpg
1908 ms
taiou-pad.jpg
1947 ms
banner1.jpg
2273 ms
banner2.jpg
2084 ms
banner3.jpg
2078 ms
free3.png
2119 ms
tel3.png
2112 ms
shop1.png
2127 ms
widgets.js
97 ms
fontawesome-webfont.woff
5 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
138 ms
shop2.png
1999 ms
banner4.jpg
2206 ms
top-content1.jpg
2679 ms
top-content2.jpg
2383 ms
banner5.jpg
2059 ms
banner7.jpg
2468 ms
syndication
96 ms
700113591773454337
324 ms
logo2.jpg
2242 ms
mixi-b.jpg
2223 ms
facebook-b.jpg
2289 ms
ameba-b.jpg
2356 ms
f-kinki.jpg
2228 ms
proxy.jpg
43 ms
proxy.jpg
32 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.dark.ltr.css
32 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.dark.ltr.css
71 ms
castlelogo_1s_normal.png
38 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
41 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
35 ms
proxy.jpg
11 ms
proxy.jpg
11 ms
f-uketuke.jpg
1872 ms
free1.jpg
1877 ms
tel1.jpg
1786 ms
jot.html
30 ms
f5.jpg
1653 ms
f6.jpg
1678 ms
f7.jpg
1539 ms
side-banner1.jpg
1518 ms
side-banner2.jpg
1511 ms
side-banner3.jpg
1486 ms
side-banner4.jpg
1454 ms
side-icon.jpg
1464 ms
side-banner5.jpg
1455 ms
side-banner6.jpg
1439 ms
side-banner7.jpg
1340 ms
sp-button.jpg
1700 ms
sp-button2.jpg
1548 ms
h2.jpg
1398 ms
phone-bg.jpg
1444 ms
pad-bg.jpg
1427 ms
banner6.jpg
1319 ms
arrows.png
1432 ms
castle-iphone.com SEO score
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Castle-iphone.com 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 Castle-iphone.com 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.
castle-iphone.com
Open Graph description is not detected on the main page of Castle Iphone. 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: