Tools & Wizards About Us
tamstarrecords.jp screenshot

Report Summary

  • 44

    Performance

    Renders faster than
    63% of other websites

  • 62

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 62

    SEO

    Google-friendlier than
    23% of websites

tamstarrecords.jp

TamStar Records

Page Load Speed

22.4 sec in total

First Response

706 ms

Resources Loaded

21.3 sec

Page Rendered

447 ms

tamstarrecords.jp screenshot

About Website

Welcome to tamstarrecords.jp homepage info - get ready to check Tam Star Records best content right away, or after learning these important things about tamstarrecords.jp

本レーベルは、インターネット系のミュージシャン、アーティストを多数世の中に輩出し、インターネットミュージックシーンを活性化させることを目的とし、そして、将来有望な新人アーティストやミュージシャン、作家の発掘、開発、育成、リリースやイベントキャスティングといった活躍の場を提供していきます。

Visit tamstarrecords.jp

Key Findings

We analyzed Tamstarrecords.jp page load time and found that the first response time was 706 ms and then it took 21.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there were 8 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

tamstarrecords.jp performance score

44

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

57/100

10%

LCP (Largest Contentful Paint)

Value7.4 s

4/100

25%

SI (Speed Index)

Value7.8 s

24/100

10%

TBT (Total Blocking Time)

Value370 ms

71/100

30%

CLS (Cumulative Layout Shift)

Value0.175

68/100

15%

TTI (Time to Interactive)

Value9.7 s

29/100

10%

Network Requests Diagram

tamstarrecords.jp

706 ms

layout.css

332 ms

local.css

330 ms

jquery.min.js

8 ms

plugin.js

513 ms

Our browser made a total of 65 requests to load all elements on the main page. We found that 40% of them (26 requests) were addressed to the original Tamstarrecords.jp, 12% (8 requests) were made to Ws-fe.amazon-adsystem.com and 12% (8 requests) were made to Ir-jp.amazon-adsystem.com. The less responsive or slowest element that took the longest time to load (20.2 sec) relates to the external source Ir-jp.amazon-adsystem.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 81.2 kB (8%)

Content Size

1.1 MB

After Optimization

972.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Tamstarrecords.jp main page is 1.1 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 764.5 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 29.4 kB

  • Original 38.5 kB
  • After minification 37.1 kB
  • After compression 9.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. 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 29.4 kB or 76% of the original size.

Image Optimization

-2%

Potential reduce by 14.7 kB

  • Original 764.5 kB
  • After minification 749.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. Tam Star Records images are well optimized though.

JavaScript Optimization

-11%

Potential reduce by 27.2 kB

  • Original 238.1 kB
  • After minification 234.1 kB
  • After compression 211.0 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 27.2 kB or 11% of the original size.

CSS Optimization

-78%

Potential reduce by 10.0 kB

  • Original 12.7 kB
  • After minification 10.4 kB
  • After compression 2.8 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. Tamstarrecords.jp needs all CSS files to be minified and compressed as it can save up to 10.0 kB or 78% of the original size.

Requests Breakdown

Number of requests can be reduced by 14 (33%)

Requests Now

42

After Optimization

28

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 42 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Tam Star Records. 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 as a result speed up the page load time.

Network Requests Diagram

tamstarrecords.jp

tamstarrecords.jp

706 ms

layout.css

layout.css

332 ms

local.css

local.css

330 ms

jquery.min.js

jquery.min.js

8 ms

plugin.js

plugin.js

513 ms

common.js

common.js

342 ms

home.js

home.js

347 ms

tamstarrecords.jp

tamstarrecords.jp

167 ms

ga.js

ga.js

92 ms

q

q

88 ms

ir

ir

20199 ms

widgets.js

widgets.js

69 ms

plusone.js

plusone.js

47 ms

hea_txt.gif

hea_txt.gif

179 ms

hea_logo.gif

hea_logo.gif

169 ms

tamstar.jpg

tamstar.jpg

498 ms

cho3.png

cho3.png

170 ms

idx_info_131226_ava2.jpg

idx_info_131226_ava2.jpg

523 ms

idx_info_131228_tamstar.jpg

idx_info_131228_tamstar.jpg

517 ms

idx_info_131227_postcard.jpg

idx_info_131227_postcard.jpg

497 ms

idx_info_131226_beatless.jpg

idx_info_131226_beatless.jpg

336 ms

idx_info_130327.jpg

idx_info_130327.jpg

527 ms

idx_info_121228_rapbit.jpg

idx_info_121228_rapbit.jpg

670 ms

idx_info_121227_supercell.jpg

idx_info_121227_supercell.jpg

662 ms

idx_info_121225_vocaloid.jpg

idx_info_121225_vocaloid.jpg

666 ms

idx_info_121226_livetune.jpg

idx_info_121226_livetune.jpg

848 ms

idx_info_121221_yanaginagi.jpg

idx_info_121221_yanaginagi.jpg

869 ms

idx_info_121214.jpg

idx_info_121214.jpg

703 ms

2012_rapbit_t.jpg

2012_rapbit_t.jpg

836 ms

side_bn_nico.jpg

side_bn_nico.jpg

831 ms

btn_pagetop.gif

btn_pagetop.gif

854 ms

ir

ir

20117 ms

ir

ir

20117 ms

ir

ir

20118 ms

ir

ir

20117 ms

ir

ir

20117 ms

ir

ir

20117 ms

ir

ir

20118 ms

q

q

4 ms

q

q

4 ms

q

q

4 ms

q

q

4 ms

q

q

4 ms

q

q

4 ms

q

q

22 ms

amerigomdbt.woff

amerigomdbt.woff

882 ms

all.js

all.js

66 ms

__utm.gif

__utm.gif

31 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

33 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

64 ms

fastbutton

fastbutton

62 ms

fastbutton

fastbutton

59 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

160 ms

all.js

all.js

37 ms

postmessageRelay

postmessageRelay

93 ms

developers.google.com

developers.google.com

386 ms

developers.google.com

developers.google.com

661 ms

3604799710-postmessagerelay.js

3604799710-postmessagerelay.js

20 ms

rpc:shindig_random.js

rpc:shindig_random.js

16 ms

settings

settings

69 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

4 ms

button.856debeac157d9669cf51e73a08fbc93.js

button.856debeac157d9669cf51e73a08fbc93.js

22 ms

embeds

embeds

21 ms

embeds

embeds

51 ms

tweet_button.2f70fb173b9000da126c79afe2098f02.ja.html

tweet_button.2f70fb173b9000da126c79afe2098f02.ja.html

43 ms

Accessibility Review

tamstarrecords.jp accessibility score

62

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

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

High

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

Best Practices

tamstarrecords.jp best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

tamstarrecords.jp SEO score

62

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

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

High

Image elements do not have [alt] attributes

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tamstarrecords.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 Tamstarrecords.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

tamstarrecords.jp

Open Graph description is not detected on the main page of Tam Star Records. 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: