5.8 sec in total
555 ms
4.9 sec
283 ms
Click here to check amazing Tower content for Japan. Otherwise, check out these important facts you probably never knew about tower.jp
CD・ブルーレイ・DVD・本・雑誌・タワレコ限定グッズなど多数取扱い!新規登録でクーポンプレゼント!対象アイテムはフラゲ可能!セブン-イレブン受け取りで送料無料!Amazon Pay・d払いご利用可 | タワーレコード オンライン公式通販サイト・NO MUSIC, NO LIFE.・全国フラゲ
Visit tower.jpWe analyzed Tower.jp page load time and found that the first response time was 555 ms and then it took 5.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
tower.jp performance score
name
value
score
weighting
Value6.7 s
2/100
10%
Value14.0 s
0/100
25%
Value11.6 s
4/100
10%
Value1,050 ms
25/100
30%
Value0.443
21/100
15%
Value16.2 s
6/100
10%
555 ms
492 ms
504 ms
490 ms
34 ms
Our browser made a total of 188 requests to load all elements on the main page. We found that 16% of them (31 requests) were addressed to the original Tower.jp, 48% (91 requests) were made to Cdfront.tower.jp and 9% (17 requests) were made to Cdn.tower.jp. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Tower.jp.
Page size can be reduced by 847.1 kB (53%)
1.6 MB
742.9 kB
In fact, the total size of Tower.jp main page is 1.6 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. 65% of websites need less resources to load. Images take 631.4 kB which makes up the majority of the site volume.
Potential reduce by 68.1 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. This page needs HTML code to be minified as it can gain 11.4 kB, which is 13% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 68.1 kB or 80% of the original size.
Potential reduce by 85.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, Tower needs image optimization as it can save up to 85.8 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 441.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 441.9 kB or 75% of the original size.
Potential reduce by 251.3 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. Tower.jp needs all CSS files to be minified and compressed as it can save up to 251.3 kB or 87% of the original size.
Number of requests can be reduced by 58 (32%)
182
124
The browser has sent 182 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 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 39 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
tower.jp
555 ms
09common.css
492 ms
12common.css
504 ms
lab.css
490 ms
jquery.min.js
34 ms
jquery-1.7.2.js
47 ms
common.js
502 ms
dayChecker.js
518 ms
towerrecords.js
574 ms
jquery.lightbox-0.5.min.js
821 ms
jplayer.js
1246 ms
heightLine.js
853 ms
jquery.ba-hashchange.min.js
859 ms
top.css
809 ms
jquery.readmore.js
866 ms
jquery.readmoreDetail.js
953 ms
jquery.tools.min.js
1126 ms
jquery.tools.detail.js
1201 ms
suggest.css
1226 ms
suggest.js
1182 ms
suggest_search.js
1197 ms
ojs
524 ms
ojs
542 ms
ClickIndex.js
575 ms
newslide.js
1264 ms
recommend.js
9 ms
banner.php
461 ms
headerNav_bg_01.gif
24 ms
zaP2_G2784849W.JPG
45 ms
zaP2_G6295624W.JPG
51 ms
zaP2_G6296904W.JPG
65 ms
9784056110203.jpg
42 ms
zaP2_G2784537W.JPG
43 ms
4988031147047.jpg
51 ms
8804775068997.jpg
51 ms
4523132114019.jpg
64 ms
zaP2_G2786324W.JPG
67 ms
zaP2_G2786323W.JPG
77 ms
2050267549062.jpg
71 ms
2050267549079.jpg
74 ms
4029759109235.jpg
77 ms
8809269505866.jpg
80 ms
9788996955498.jpg
91 ms
814337019228.jpg
85 ms
zaP2_G6295262W.JPG
95 ms
mainLeft_btn_06.png
197 ms
ranking1.gif
195 ms
ranking2.gif
195 ms
ranking3.gif
194 ms
ranking4.gif
193 ms
ranking5.gif
316 ms
bt_top_01.png
518 ms
bottomNav_copyright_01.gif
521 ms
headerNav_bg_10.gif
17 ms
headerNav_ic_03.gif
18 ms
headerNav_logo_01.gif
19 ms
headerNav_bt_01_stay.gif
20 ms
headerNav_bt_02.gif
20 ms
headerNav_bt_03.gif
21 ms
headerNav_banner_members.gif
21 ms
headerNav_bt_06_stay.gif
23 ms
headerNav_bt_07.gif
23 ms
headerNav_bt_08.gif
23 ms
headerNav_bt_09.gif
23 ms
headerNav_bt_10.gif
24 ms
headerNav_bt_11.gif
25 ms
headerNav_bt_12.png
26 ms
headerNav_bt_13.png
30 ms
bt_01.png
33 ms
sideNavLeft_h2_12.gif
32 ms
sideNavLeft_h2_10_top.gif
31 ms
11.gif
41 ms
11.gif
40 ms
main_h2_01.png
33 ms
recommendTitle.png
43 ms
ico_jpop_01.gif
39 ms
icon_privilege_03.gif
41 ms
icon_privilege_02.gif
39 ms
ico_books_01.gif
62 ms
icon_privilege_01.gif
59 ms
ico_soundtrack_01.gif
59 ms
ico_goods_01.gif
56 ms
ico_world_01.gif
63 ms
ico_rock_01.gif
61 ms
rankingTitle.png
65 ms
itemTitle.png
66 ms
0703_02.jpg
67 ms
0702_03.jpg
69 ms
15_0111_02.jpeg
60 ms
0104_02.jpg
63 ms
14_0101_02.jpg
65 ms
0229_4001_17.jpg
59 ms
15.gif
59 ms
15.gif
60 ms
15.gif
62 ms
15.gif
62 ms
040.gif
64 ms
15.gif
62 ms
10.gif
63 ms
02.gif
65 ms
02.gif
64 ms
10.gif
64 ms
10.gif
59 ms
02.jpg
60 ms
0104_01.jpg
59 ms
ico_jazz_01.gif
62 ms
0702.jpg
61 ms
01_2501_02.jpg
58 ms
ico_movietvdrama_overseamovie_01.gif
53 ms
3001_160227.jpg
55 ms
ico_magazines_01.gif
73 ms
17_4001_03.jpg
71 ms
banner_01tower.gif
70 ms
banner_02twitter.gif
59 ms
tol_cafedining_banner240x75.png
54 ms
banner_08mikiki.gif
55 ms
headerNav_bg_03.gif
53 ms
bg_suggest_04.png
54 ms
ico_link_01.png
54 ms
infoArrow.gif
53 ms
bg_line_01.gif
40 ms
featureLinkArrow.gif
38 ms
tabBg.gif
40 ms
tab_on.gif
39 ms
tab_off.gif
37 ms
sideNavRightInner06TitleBg.png
40 ms
ojs2
348 ms
conversion.js
16 ms
61 ms
bg_top_01.png
24 ms
bottomNav_bg_02.gif
23 ms
bottomNav_ico_01.gif
21 ms
mikiki_icon_14.gif
11 ms
bottomNav_ico_02.gif
11 ms
bottomNav_ico_08.gif
11 ms
bottomNav_ico_03.gif
10 ms
bottomNav_ico_04.gif
10 ms
bottomNav_ico_05.gif
11 ms
bottomNav_ico_06.gif
13 ms
bottomNav_ico_07.gif
14 ms
towerrevo.gif
16 ms
bottomNav_bg_01.gif
16 ms
ojs2
346 ms
33 ms
conversion.js
36 ms
s_retargeting.js
615 ms
14 ms
13 ms
15 ms
17 ms
19 ms
segmentation.js
5 ms
dc.js
30 ms
gtm.js
61 ms
20100528.js
551 ms
20130110183831.js
370 ms
exec.js
377 ms
cnt
370 ms
__utm.gif
12 ms
itm.js
361 ms
so_sg.js
998 ms
so_sg.js
1035 ms
audience
200 ms
580 ms
495 ms
447 ms
600 ms
bg_suggest_02.png
7 ms
beacon.html
10 ms
bg_suggest_03.png
10 ms
pixel
20 ms
cs
296 ms
Pug
24 ms
set
303 ms
gtm.js
46 ms
sync
8 ms
sync
334 ms
beacon.html
15 ms
td-1.2.0.js
796 ms
set
306 ms
tap.php
288 ms
sd
72 ms
sync
219 ms
mapuser
153 ms
sync
298 ms
js
590 ms
js
600 ms
pageviews
43 ms
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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
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
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
Image elements do not have [alt] attributes
Links do not have a discernible name
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>).
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.
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
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
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 uses legible font sizes
Tap targets are not sized appropriately
JA
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tower.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese 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 Tower.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.
tower.jp
Open Graph description is not detected on the main page of 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: