7.6 sec in total
557 ms
6.2 sec
796 ms
Welcome to details.co.jp homepage info - get ready to check Details best content for Japan right away, or after learning these important things about details.co.jp
スタジオディテイルズは名古屋・東京で活動するクリエイティブエージェンシー。意思あるブランドを正しく機能させ、高く飛び立たせるために、スタジオディテイルズはビジネスデザインを社会に提供する。
Visit details.co.jpWe analyzed Details.co.jp page load time and found that the first response time was 557 ms and then it took 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.
details.co.jp performance score
name
value
score
weighting
Value6.1 s
3/100
10%
Value12.8 s
0/100
25%
Value19.0 s
0/100
10%
Value340 ms
74/100
30%
Value0
100/100
15%
Value22.8 s
1/100
10%
557 ms
1277 ms
508 ms
362 ms
43 ms
Our browser made a total of 107 requests to load all elements on the main page. We found that 35% of them (37 requests) were addressed to the original Details.co.jp, 14% (15 requests) were made to Scontent.xx.fbcdn.net and 12% (13 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Details.co.jp.
Page size can be reduced by 504.0 kB (29%)
1.7 MB
1.2 MB
In fact, the total size of Details.co.jp main page is 1.7 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. 60% of websites need less resources to load. Images take 1.0 MB which makes up the majority of the site volume.
Potential reduce by 21.8 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 21.8 kB or 74% of the original size.
Potential reduce by 46.4 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. Details images are well optimized though.
Potential reduce by 406.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 406.3 kB or 65% of the original size.
Potential reduce by 29.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. Details.co.jp needs all CSS files to be minified and compressed as it can save up to 29.5 kB or 82% of the original size.
Number of requests can be reduced by 52 (50%)
104
52
The browser has sent 104 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Details. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 38 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
details.co.jp
557 ms
www.details.co.jp
1277 ms
style.css
508 ms
curtain.css
362 ms
jquery.min.js
43 ms
curtain.js
964 ms
detailslp.js
372 ms
jquery.easing.1.3.js
569 ms
entrylink.js
538 ms
jquery.nicescroll.min.js
921 ms
entry.png
236 ms
office_text.png
237 ms
office01.jpg
1669 ms
office02.jpg
898 ms
office03.jpg
675 ms
office04.jpg
1297 ms
philosophy_text.png
740 ms
company_h2.png
393 ms
map.gif
965 ms
g_map_link.gif
843 ms
good_design.gif
927 ms
award_masda.png
1011 ms
facebook_h2.png
1097 ms
footer.png
1111 ms
sdk.js
280 ms
navi_top.png
1152 ms
navi_message.png
1175 ms
navi_ourfield.png
1250 ms
navi_office.png
1291 ms
navi_philosophy.png
1342 ms
navi_works.png
1344 ms
navi_company.png
1431 ms
logo.png
1473 ms
one_text.png
1475 ms
shadow.png
1531 ms
message_text.png
1512 ms
ourfield_text.png
1788 ms
ourfield_text2.png
1667 ms
plugins.js
313 ms
plusone.js
102 ms
widgets.js
32 ms
ga.js
47 ms
pta.js
499 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
33 ms
__utm.gif
30 ms
launch_text.gif
1558 ms
cb=gapi.loaded_0
48 ms
cb=gapi.loaded_1
47 ms
fastbutton
105 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html
22 ms
postmessageRelay
109 ms
cb=gapi.loaded_0
39 ms
cb=gapi.loaded_1
37 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
81 ms
147 ms
3193398744-postmessagerelay.js
33 ms
rpc:shindig_random.js
35 ms
xd_arbiter.php
210 ms
xd_arbiter.php
422 ms
jot
101 ms
cb=gapi.loaded_0
21 ms
32c5dd8b.js
476 ms
pn
524 ms
favorite.pl
384 ms
like.php
90 ms
like_box.php
214 ms
8i5wLKr4CIi.js
485 ms
LVx-xkvaJ0b.png
368 ms
wIQ5cz_qN26.css
221 ms
DrE_LqJc1gV.css
208 ms
1kPfZUdGrka.js
271 ms
cwV0x8mDYml.js
339 ms
Mpe38fuBVZ2.js
293 ms
n8qIhCw3vMx.js
293 ms
mixi_check_entry.css
374 ms
errorreport.production.js
373 ms
json.js
377 ms
underscore-string-1.3.3-2.0.0-compress.js
378 ms
namespace-brook-compress.js
380 ms
prototype-effects-1.6.1-1.8.3-compress.js
498 ms
mixi.js
382 ms
favorite.production.js
582 ms
jquery-1.7.1.min-noconflict-compress.js
731 ms
8i5wLKr4CIi.js
285 ms
399596_436150266424479_907689964_n.jpg
664 ms
538599_436149819757857_183535981_n.jpg
788 ms
62554_286841844753862_1643311541_n.jpg
896 ms
12108299_463863130483313_5455795374672706706_n.jpg
917 ms
262435_100735303366146_7836585_n.jpg
925 ms
10557285_786783394717112_916851531473781449_n.jpg
893 ms
969372_310020389136591_1179693235_n.jpg
865 ms
10690348_818826121539425_5253864350545996860_n.jpg
907 ms
12112363_756581577801788_6152972184732503754_n.jpg
957 ms
12341584_1140696412607487_1457628344219292785_n.jpg
1138 ms
12208256_124958254531457_3825654607845410455_n.jpg
957 ms
299054_104601139643102_6255353_n.jpg
971 ms
1234533_528843773862932_1370263160_n.jpg
980 ms
1510023_578992915508529_432422222_n.jpg
1044 ms
163918_190684034279328_3427279_n.jpg
1025 ms
wL6VQj7Ab77.png
68 ms
s7jcwEQH7Sx.png
70 ms
analytics.js
11 ms
comment001.gif
148 ms
favorite_button004.png
147 ms
comment_content_top001.gif
289 ms
VXcANLwwL5J.js
68 ms
AmlxWlqMvlv.js
137 ms
details.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
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.
details.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
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
details.co.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Details.co.jp can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Details.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.
details.co.jp
Open Graph data is detected on the main page of Details. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: