6.9 sec in total
1.2 sec
5.5 sec
160 ms
Visit age.ne.jp now to see the best up-to-date Age content for Japan and also check out these interesting facts you probably never knew about age.ne.jp
インターネットサービスプロバイダーとして創業し、現在ではWEBホスティング、など多彩な事業領域に展開しています。
Visit age.ne.jpWe analyzed Age.ne.jp page load time and found that the first response time was 1.2 sec and then it took 5.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
age.ne.jp performance score
name
value
score
weighting
Value2.7 s
60/100
10%
Value3.5 s
64/100
25%
Value9.7 s
10/100
10%
Value4,560 ms
0/100
30%
Value0.276
44/100
15%
Value11.9 s
17/100
10%
1225 ms
648 ms
761 ms
876 ms
973 ms
Our browser made a total of 66 requests to load all elements on the main page. We found that 55% of them (36 requests) were addressed to the original Age.ne.jp, 15% (10 requests) were made to Static.xx.fbcdn.net and 15% (10 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Age.ne.jp.
Page size can be reduced by 71.6 kB (20%)
365.2 kB
293.6 kB
In fact, the total size of Age.ne.jp main page is 365.2 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 35% of websites need less resources to load. Images take 236.4 kB which makes up the majority of the site volume.
Potential reduce by 13.3 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.3 kB or 78% of the original size.
Potential reduce by 4.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. Age images are well optimized though.
Potential reduce by 46.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 46.8 kB or 46% of the original size.
Potential reduce by 7.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. Age.ne.jp needs all CSS files to be minified and compressed as it can save up to 7.5 kB or 80% of the original size.
Number of requests can be reduced by 25 (40%)
63
38
The browser has sent 63 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 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 15 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
www.age.ne.jp
1225 ms
style.css
648 ms
flexslider.css
761 ms
top_img_01.jpg
876 ms
top_img_02.jpg
973 ms
top_img_03.jpg
1559 ms
top_img_04.jpg
805 ms
top_img_05.jpg
968 ms
top_img_06.jpg
968 ms
top_img_07.jpg
1049 ms
jquery.js
1642 ms
yuga.js
974 ms
footerFixed.js
973 ms
gototop.js
990 ms
jquery.min.js
29 ms
loop.js
1063 ms
logo.gif
1134 ms
m_01.gif
1135 ms
m_02.gif
1164 ms
m_03.gif
1235 ms
m_04.gif
1297 ms
m_05.gif
1299 ms
top_pic_03.jpg
1339 ms
arrow.gif
1407 ms
top_pic_02.jpg
1465 ms
top_news_t.gif
1465 ms
top_news_list.gif
1518 ms
top_banner_02.gif
1426 ms
top_banner_03.gif
1427 ms
common.css
1144 ms
content.css
625 ms
widgets.js
92 ms
m_01_on.gif
164 ms
m_02_on.gif
176 ms
m_03_on.gif
187 ms
m_04_on.gif
180 ms
m_05_on.gif
180 ms
top_news_list_on.gif
308 ms
likebox.php
245 ms
timeline.1b43d11859b7663a2225b885f87704a5.js
138 ms
syndication
98 ms
475262087992578048
126 ms
jTuqQ-OPDr6.css
208 ms
n370yiaI2G6.css
251 ms
_rx8naC75Dy.js
329 ms
x5F9OMjKyLw.js
389 ms
ICDbTSzjQEg.js
324 ms
TTCre3391I0.js
327 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
38 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
73 ms
RDZvPwRq_normal.png
317 ms
10500484_604955746287391_6626311782662703324_n.jpg
263 ms
11227559_823362021113428_3006308819414927377_n.png
344 ms
487633_10151915223129196_1059913751_n.jpg
376 ms
12512617_1721859504713829_3862254163021506417_n.jpg
374 ms
9241_469851903123090_615302433_n.jpg
376 ms
11249836_1921766761381930_1181196822575739162_n.jpg
379 ms
11025812_599322916870426_6801336344556200612_n.jpg
439 ms
10407646_855555751175435_7193797829230509107_n.jpg
383 ms
263313_335373033257679_201117660_n.jpg
412 ms
10363814_730164900437400_606382901312274283_n.jpg
413 ms
wL6VQj7Ab77.png
42 ms
s7jcwEQH7Sx.png
42 ms
jot
105 ms
I6-MnjEovm5.js
42 ms
vlXaquuXMrr.js
80 ms
age.ne.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
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
age.ne.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
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
age.ne.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
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
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Age.ne.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 Age.ne.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.
age.ne.jp
Open Graph description is not detected on the main page of 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: