4.8 sec in total
671 ms
3.9 sec
293 ms
Visit idin.co.jp now to see the best up-to-date Idin content and also check out these interesting facts you probably never knew about idin.co.jp
被リンクに頼らないSEO内部施策を専門で行っております。SEO内部対策、サイト制作は、株式会社アイディーンにお任せ下さい。その他SEM、リスティング運用、インターネット広告等もご相談下さい。
Visit idin.co.jpWe analyzed Idin.co.jp page load time and found that the first response time was 671 ms and then it took 4.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
idin.co.jp performance score
name
value
score
weighting
Value3.7 s
29/100
10%
Value18.2 s
0/100
25%
Value10.7 s
7/100
10%
Value2,540 ms
4/100
30%
Value0
100/100
15%
Value20.9 s
1/100
10%
671 ms
323 ms
868 ms
352 ms
351 ms
Our browser made a total of 73 requests to load all elements on the main page. We found that 75% of them (55 requests) were addressed to the original Idin.co.jp, 7% (5 requests) were made to Youtube.com and 5% (4 requests) were made to Jnn-pa.googleapis.com. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source V1.chamo-chat.com.
Page size can be reduced by 125.8 kB (11%)
1.1 MB
1.0 MB
In fact, the total size of Idin.co.jp main page is 1.1 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. Images take 736.9 kB which makes up the majority of the site volume.
Potential reduce by 13.2 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 13.2 kB or 71% of the original size.
Potential reduce by 4.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. Idin images are well optimized though.
Potential reduce by 78.8 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 78.8 kB or 27% of the original size.
Potential reduce by 29.6 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. Idin.co.jp needs all CSS files to be minified and compressed as it can save up to 29.6 kB or 31% of the original size.
Number of requests can be reduced by 24 (34%)
70
46
The browser has sent 70 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Idin. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
idin.co.jp
671 ms
import.css
323 ms
jquery-1.4.4.min.js
868 ms
jquery.page-scroller-308.js
352 ms
opacity-rollover2.1.js
351 ms
jquery.colorbox.js
529 ms
jquery.colorbox-base.js
376 ms
common.css
164 ms
style.css
378 ms
class.color.css
204 ms
class.font.css
240 ms
class.layout.css
326 ms
clearfix.css
379 ms
colorbox.css
382 ms
ga.js
86 ms
chamo.js
726 ms
bg-info.gif
420 ms
btn-quotation-h.gif
423 ms
btn-contact-h.gif
420 ms
logo.gif
562 ms
bg-menu.jpg
421 ms
m-top.jpg
420 ms
m-service.jpg
563 ms
m-seo.jpg
564 ms
m-corporate.jpg
563 ms
m-privacy.jpg
563 ms
m-contact.jpg
564 ms
m-sitemap.jpg
564 ms
bg-visual.jpg
649 ms
img-visual.jpg
1065 ms
btn-quotation-v.png
699 ms
btn-contact-v.png
951 ms
bg-contents.jpg
647 ms
hl-seo.jpg
951 ms
btn-detail.jpg
951 ms
hl-premium.jpg
1061 ms
ico-sma.png
958 ms
hl-penalty.jpg
1206 ms
fig-penalty.jpg
1208 ms
btn-contact.jpg
1063 ms
hl-movie.jpg
1221 ms
hl-speed.jpg
1205 ms
hl-service.jpg
1206 ms
tl-service-01.jpg
1206 ms
tl-service-02.jpg
1297 ms
tl-service-03.jpg
1314 ms
ico-binder.png
1329 ms
bg-sm-off.jpg
1335 ms
bg-bnr-tel.jpg
1371 ms
btn-bnrin-quotation.jpg
1395 ms
btn-bnrin-contact.jpg
1460 ms
bnr-snacker.jpg
1490 ms
6Nbg1veBeq8
115 ms
__utm.gif
14 ms
www-player.css
7 ms
www-embed-player.js
28 ms
base.js
66 ms
ad_status.js
293 ms
bg-footer.jpg
1089 ms
btn-pagetop.png
1097 ms
logo.png
1144 ms
loading.gif
1155 ms
xk0PjXGe3Weoch_wsJrbTmMShFu5SdJ84GkfFnEjZYE.js
216 ms
embed.js
124 ms
controls.png
1068 ms
KFOmCnqEu92Fr1Mu4mxPKTU1Kg.ttf
156 ms
KFOlCnqEu92Fr1MmEU9fBBc9AMP6lQ.ttf
301 ms
widget.js.php
1727 ms
id
52 ms
Create
255 ms
Create
365 ms
GenerateIT
21 ms
GenerateIT
19 ms
idin.co.jp accessibility score
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
idin.co.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
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
idin.co.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
JA
JA
EUC-JP
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Idin.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 Idin.co.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.
idin.co.jp
Open Graph description is not detected on the main page of Idin. 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: