Access tower.jp. タワーレコードオンライン | CD・ブルーレイ・DVD・本・雑誌・グッズの通販

tower.jp screenshot

5

Performance

Renders faster than
21% of other websites
70

Accessibility

Visual factors better than
that of 35% of websites
75

Best Practices

More advanced features
available than in
35% of websites
85

SEO

Google-friendlier than
55% of websites

First Response

598 ms

Resources Loaded

12.6 sec

Page Rendered

463 ms

tower.jp screenshot

About Website

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.jp

Key Findings

We analyzed Tower.jp page load time and found that the first response time was 598 ms and then it took 13.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

name

value

score

weighting

FCP (First Contentful Paint)

Value7.2 s

1/100

10%

LCP (Largest Contentful Paint)

Value15.4 s

0/100

25%

SI (Speed Index)

Value23.0 s

0/100

10%

TBT (Total Blocking Time)

Value1,730 ms

10/100

30%

CLS (Cumulative Layout Shift)

Value0.595

11/100

15%

TTI (Time to Interactive)

Value27.4 s

0/100

10%

tower.jp

598 ms

tower.jp

1896 ms

all.css

36 ms

09common.css

862 ms

12common.css

1214 ms

Our browser made a total of 298 requests to load all elements on the main page. We found that 20% of them (61 requests) were addressed to the original Tower.jp, 37% (110 requests) were made to Cdn.tower.jp and 31% (91 requests) were made to Cdfront.tower.jp. The less responsive or slowest element that took the longest time to load (4.7 sec) relates to the external source Cdfront.tower.jp.

Content Size

5.8 MB

After Optimization

4.4 MB

In fact, the total size of Tower.jp main page is 5.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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 4.5 MB which makes up the majority of the site volume.

HTML Optimization

-91%

Potential reduce by 400.0 kB

Original 441.3 kB
After minification 291.3 kB
After compression 41.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. This page needs HTML code to be minified as it can gain 150.1 kB, which is 34% 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 400.0 kB or 91% of the original size.

Image Optimization

-11%

Potential reduce by 501.0 kB

Original 4.5 MB
After minification 4.0 MB

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 501.0 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-60%

Potential reduce by 441.1 kB

Original 732.6 kB
After minification 575.1 kB
After compression 291.5 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.1 kB or 60% of the original size.

CSS Optimization

-16%

Potential reduce by 11.0 kB

Original 66.4 kB
After minification 66.1 kB
After compression 55.4 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 11.0 kB or 16% of the original size.

Requests Now

296

After Optimization

233

The browser has sent 296 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 41 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.

Accessibility Issues

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.

High

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

These are opportunities to improve keyboard navigation in your application.

High

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

These are opportunities to improve the interpretation of your content by users in different locales.

High

<html> element does not have a [lang] attribute

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

These items highlight common accessibility best practices.

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

High

Displays images with incorrect aspect ratio

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

Search Engine Optimization Advices

To appear in search results, crawlers need access to your app.

High

Links are not crawlable

Format your HTML in a way that enables crawlers to better understand your app’s content.

High

Image elements do not have [alt] attributes

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/).

High

Document uses legible font sizes

Language and Encoding

Language Detected

JA
Language Claimed

N/A
Encoding

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.

Social Sharing Optimization

tower.jp

Open Graph data is detected on the main page of Tower. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: