5 sec in total
626 ms
3.9 sec
471 ms
Welcome to g-age.jp homepage info - get ready to check G AGE best content right away, or after learning these important things about g-age.jp
2004年創立の広告制作プロダクションです。以来、広告業界での企画・立案・デザイン制作に注力してまいりました。そして、今期から我々は「デザインをさらなる大きな領域で!」を合言葉にもっと広い意味でのデザイン、3つのデザイン業務に取り組んでまいります。
Visit g-age.jpWe analyzed G-age.jp page load time and found that the first response time was 626 ms and then it took 4.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
g-age.jp performance score
name
value
score
weighting
Value2.9 s
53/100
10%
Value3.8 s
55/100
25%
Value11.5 s
5/100
10%
Value480 ms
59/100
30%
Value0.335
34/100
15%
Value13.4 s
11/100
10%
626 ms
198 ms
76 ms
337 ms
82 ms
Our browser made a total of 75 requests to load all elements on the main page. We found that 41% of them (31 requests) were addressed to the original G-age.jp, 20% (15 requests) were made to Scontent.xx.fbcdn.net and 13% (10 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain G-age.jp.
Page size can be reduced by 211.1 kB (7%)
2.8 MB
2.6 MB
In fact, the total size of G-age.jp main page is 2.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. 50% of websites need less resources to load. Images take 2.6 MB which makes up the majority of the site volume.
Potential reduce by 15.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 15.6 kB or 71% of the original size.
Potential reduce by 60.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. G AGE images are well optimized though.
Potential reduce by 120.9 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 120.9 kB or 56% of the original size.
Potential reduce by 13.9 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. G-age.jp needs all CSS files to be minified and compressed as it can save up to 13.9 kB or 76% of the original size.
Number of requests can be reduced by 19 (28%)
68
49
The browser has sent 68 CSS, Javascripts, AJAX and image requests in order to completely render the main page of G AGE. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
g-age.jp
626 ms
device.min.js
198 ms
css
76 ms
main.css
337 ms
jquery.min.js
82 ms
jquery.easing.min.js
7 ms
jquery.plugin.js
633 ms
main.js
378 ms
desktop.css
201 ms
analytics.js
7 ms
desktop.js
181 ms
linkid.js
8 ms
collect
14 ms
logo-1.svg
267 ms
visual-blank.png
266 ms
visual-blank.png
305 ms
visual-logo3.png
581 ms
sg-pic1.jpg
786 ms
sg-pic1.jpg
932 ms
labo-pic1.jpg
919 ms
labo-pic1.jpg
968 ms
thumb.jpg
634 ms
thumb.jpg
943 ms
thumb.jpg
1195 ms
thumb.jpg
1110 ms
thumb.jpg
1286 ms
thumb.jpg
1330 ms
thumb.jpg
1322 ms
thumb.jpg
1370 ms
ico-mail.png
1275 ms
ico-phone.png
1369 ms
ico-facebook.png
1445 ms
ico-map.png
1472 ms
sdk.js
54 ms
visual-1.jpg
2312 ms
visual-2.jpg
2425 ms
visual-3.jpg
2051 ms
visual-4.jpg
1758 ms
ga.js
44 ms
PRmiXeptR36kaC0GEAetxi8cqLH4MEiSE0ROcU-qHOA.ttf
88 ms
PRmiXeptR36kaC0GEAetxp_TkvowlIOtbR7ePgFOpF4.ttf
129 ms
xjAJXh38I15wypJXxuGMBp0EAVxt0G0biEntp43Qt6E.ttf
153 ms
MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf
153 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
158 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
187 ms
__utm.gif
47 ms
176 ms
xd_arbiter.php
51 ms
xd_arbiter.php
124 ms
page.php
185 ms
yIdHYsCA3B1.css
23 ms
q68gy-v_YMF.js
32 ms
k19Xse48j5I.js
63 ms
ihptErjAmMX.js
78 ms
1654054_1606263199633387_785181250828546535_n.jpg
217 ms
10423716_1605946059665101_5809253242325147869_n.jpg
91 ms
12654562_556001014565449_5702231691349601534_n.jpg
44 ms
11252859_10206965830807734_5602335576037449153_n.jpg
45 ms
10420259_309550362585866_6243422536184790435_n.jpg
41 ms
11054268_857802467637899_3365213177783470354_n.jpg
41 ms
10917873_1534220016863076_5832150503481125801_n.jpg
44 ms
149357_105581956246237_1251436462_n.jpg
106 ms
1379841_10150004552801901_469209496895221757_n.jpg
45 ms
10999096_776543905755845_937525215615272966_n.jpg
128 ms
416916_122400587924946_364990374_n.jpg
46 ms
10407951_807332825967889_6869347191914560010_n.jpg
46 ms
251879_256053691171220_1179127383_n.jpg
49 ms
12799026_647974305341335_5288330443803305041_n.jpg
172 ms
10665130_813905618654593_9120095928695871947_n.jpg
51 ms
wL6VQj7Ab77.png
9 ms
s7jcwEQH7Sx.png
9 ms
R9a_DtVRZgv.js
7 ms
cUDgRFxaoIk.js
4 ms
0JBr1QHp8Gi.js
3 ms
kDOzhTr2W91.js
6 ms
g-age.jp accessibility score
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.
g-age.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
Page has valid source maps
g-age.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
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise G-age.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 G-age.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.
g-age.jp
Open Graph description is not detected on the main page of G AGE. 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: