8.2 sec in total
1 sec
7 sec
109 ms
Welcome to aoyama-tower.jp homepage info - get ready to check Aoyama Tower best content for Japan right away, or after learning these important things about aoyama-tower.jp
【公式】パークアクシス青山一丁目タワー | 「青山一丁目」駅徒歩2分、地上46階建、コンシェルジュ・フィットネスジム・ゲストルーム・入居者専用レストランがある賃貸タワーレジデンス
Visit aoyama-tower.jpWe analyzed Aoyama-tower.jp page load time and found that the first response time was 1 sec and then it took 7.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
aoyama-tower.jp performance score
name
value
score
weighting
Value6.1 s
3/100
10%
Value15.8 s
0/100
25%
Value16.1 s
0/100
10%
Value2,670 ms
4/100
30%
Value0.625
9/100
15%
Value27.7 s
0/100
10%
1047 ms
575 ms
586 ms
410 ms
45 ms
Our browser made a total of 158 requests to load all elements on the main page. We found that 21% of them (33 requests) were addressed to the original Aoyama-tower.jp, 8% (13 requests) were made to Pixel.mathtag.com and 5% (8 requests) were made to Tg.socdm.com. The less responsive or slowest element that took the longest time to load (1.5 sec) relates to the external source Global.ib-ibi.com.
Page size can be reduced by 207.9 kB (61%)
342.0 kB
134.2 kB
In fact, the total size of Aoyama-tower.jp main page is 342.0 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. 30% of websites need less resources to load. Javascripts take 292.6 kB which makes up the majority of the site volume.
Potential reduce by 15.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 15.7 kB or 70% of the original size.
Potential reduce by 7.8 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. Obviously, Aoyama Tower needs image optimization as it can save up to 7.8 kB or 35% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 180.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 180.8 kB or 62% of the original size.
Potential reduce by 3.7 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. Aoyama-tower.jp needs all CSS files to be minified and compressed as it can save up to 3.7 kB or 80% of the original size.
Number of requests can be reduced by 107 (76%)
140
33
The browser has sent 140 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Aoyama Tower. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and as a result speed up the page load time.
aoyama-tower.jp
1047 ms
style.css
575 ms
AC_RunActiveContent.js
586 ms
over.js
410 ms
satelliteLib-fafbe33c69f380d90bd117133f8d178ffc6232f4.js
45 ms
ojs
518 ms
js
19 ms
lb
45 ms
bg_head.gif
206 ms
head_img_4.gif
200 ms
spacer.gif
192 ms
head_img_1.gif
188 ms
img_btn_5.jpg
955 ms
head_img_2.gif
373 ms
head_img_3.gif
380 ms
navi_1.gif
405 ms
navi_2.gif
396 ms
navi_3.gif
410 ms
navi_4.gif
558 ms
navi_5.gif
568 ms
navi_6.gif
593 ms
navi_7.gif
598 ms
navi_8.gif
615 ms
ind_img_2.gif
743 ms
ind_img_5.gif
757 ms
ind_img_6.gif
790 ms
ind_img_7.gif
1002 ms
foot_img_2.gif
819 ms
ind_img_3.gif
931 ms
ga.js
32 ms
__utm.gif
13 ms
tag.js
527 ms
us0
541 ms
14BUBqfnI4dB
345 ms
gtm.js
50 ms
i.js
37 ms
s-code-contents-3841321585ac24d66b9b2f581fc0269d789cd96e.js
70 ms
us
312 ms
analytics.js
49 ms
conversion_async.js
48 ms
segmentation.js
48 ms
blade_track_jp.js
396 ms
lb
7 ms
so_sg.js
1026 ms
collect
27 ms
collect
61 ms
45 ms
cnt
352 ms
redirect.js
395 ms
44 ms
js
39 ms
32 ms
30 ms
s61433841232210
11 ms
img
46 ms
pixel
16 ms
iframe
35 ms
sync
358 ms
sync
386 ms
hs=1458179583108
479 ms
img
14 ms
img
19 ms
cookie_enabled_get.html
331 ms
bl_track.cgi
350 ms
usync
330 ms
js
767 ms
so_sg.js
178 ms
js
498 ms
s_retargeting.js
575 ms
pixel
11 ms
img
14 ms
conversion.js
515 ms
sosync
251 ms
13 ms
sync
648 ms
sync_before
206 ms
sync_before
198 ms
sync_before
402 ms
idsync
404 ms
sync
405 ms
16 ms
sync
581 ms
cs
308 ms
pixel
15 ms
sync
596 ms
conversion.js
701 ms
sd
5 ms
is
752 ms
Pug
16 ms
859 ms
tap.php
327 ms
img
73 ms
sd
18 ms
Pug
32 ms
u.php
25 ms
us.gif
75 ms
rtset
32 ms
UserMatch.ashx
21 ms
rum
25 ms
match.aspx
38 ms
info.php
172 ms
166 ms
s.kau.li
368 ms
311 ms
user-registering
74 ms
338 ms
sync
182 ms
GenericUserSync.ashx
32 ms
2948
40 ms
22 ms
image.sbxx
1505 ms
4448
64 ms
tap.php
261 ms
img
42 ms
img
51 ms
img
45 ms
img
56 ms
img
46 ms
merge
19 ms
mapuser
26 ms
match
25 ms
rum
44 ms
xrefid.xgi
29 ms
img
61 ms
sync
30 ms
img
54 ms
spacer.gif
28 ms
img
120 ms
sync
90 ms
pixel.gif
56 ms
xrefid.xgi
6 ms
lr.gif
6 ms
trpx.gif
88 ms
1by1.png
4 ms
info2
120 ms
navi_1_on.gif
415 ms
beacon.html
18 ms
navi_2_on.gif
410 ms
navi_3_on.gif
409 ms
navi_4_on.gif
437 ms
navi_5_on.gif
415 ms
navi_6_on.gif
439 ms
navi_7_on.gif
601 ms
navi_8_on.gif
601 ms
DIGITALICE_REC.js
584 ms
sd
7 ms
pixel
21 ms
tap.php
15 ms
Pug
17 ms
set
302 ms
sync
300 ms
sync
80 ms
sync
316 ms
sync
312 ms
mapuser
150 ms
sync
180 ms
gcs
344 ms
361 ms
aoyama-tower.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.
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
<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.
Definition list items are not wrapped in <dl> elements
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
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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.
aoyama-tower.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
Browser errors were logged to the console
aoyama-tower.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
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 doesn't use legible font sizes
Tap targets are not sized appropriately
JA
JA
SHIFT_JIS
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Aoyama-tower.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 Aoyama-tower.jp main page’s claimed encoding is shift_jis. 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.
aoyama-tower.jp
Open Graph description is not detected on the main page of Aoyama Tower. 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: