Report Summary

  • 62

    Performance

    Renders faster than
    76% of other websites

  • 56

    Accessibility

    Visual factors better than
    that of 24% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 58

    SEO

    Google-friendlier than
    21% of websites

thirdear.co.jp

プログレ,サイケ&ハード・ロック,アシッド・フォーク,トラッドのCD&LP専門店 サード・イアー

Page Load Speed

5.8 sec in total

First Response

858 ms

Resources Loaded

4.1 sec

Page Rendered

871 ms

thirdear.co.jp screenshot

About Website

Welcome to thirdear.co.jp homepage info - get ready to check Thirdear best content right away, or after learning these important things about thirdear.co.jp

ブリティッシュ・プログレ、ジャズ・ロック、ユーロ・ロック、サイケ、ハード・ロック、アシッド・フォーク、トラッド、実験音楽の60,70年代プログレッシブ・ロックCD&LP専門店。輸入盤・紙ジャケ、通販店

Visit thirdear.co.jp

Key Findings

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

Performance Metrics

thirdear.co.jp performance score

62

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

35/100

10%

LCP (Largest Contentful Paint)

Value3.6 s

62/100

25%

SI (Speed Index)

Value5.0 s

63/100

10%

TBT (Total Blocking Time)

Value160 ms

93/100

30%

CLS (Cumulative Layout Shift)

Value0.937

3/100

15%

TTI (Time to Interactive)

Value4.8 s

79/100

10%

Network Requests Diagram

thirdear.co.jp

858 ms

sps_common.css

337 ms

default.css

495 ms

jquery.min.js

21 ms

floating_menu.js

512 ms

Our browser made a total of 73 requests to load all elements on the main page. We found that 38% of them (28 requests) were addressed to the original Thirdear.co.jp, 59% (43 requests) were made to Image1.shopserve.jp and 1% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (1.9 sec) relates to the external source Image1.shopserve.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 145.5 kB (7%)

Content Size

2.2 MB

After Optimization

2.1 MB

In fact, the total size of Thirdear.co.jp main page is 2.2 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. 55% of websites need less resources to load. Images take 2.0 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 89.8 kB

  • Original 106.2 kB
  • After minification 87.2 kB
  • After compression 16.5 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 19.0 kB, which is 18% 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 89.8 kB or 84% of the original size.

Image Optimization

-1%

Potential reduce by 12.1 kB

  • Original 2.0 MB
  • After minification 2.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. Thirdear images are well optimized though.

JavaScript Optimization

-42%

Potential reduce by 39.7 kB

  • Original 93.7 kB
  • After minification 93.7 kB
  • After compression 54.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 39.7 kB or 42% of the original size.

CSS Optimization

-39%

Potential reduce by 3.9 kB

  • Original 10.1 kB
  • After minification 10.1 kB
  • After compression 6.2 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. Thirdear.co.jp needs all CSS files to be minified and compressed as it can save up to 3.9 kB or 39% of the original size.

Requests Breakdown

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

Requests Now

72

After Optimization

62

The browser has sent 72 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Thirdear. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests and as a result speed up the page load time.

Accessibility Review

thirdear.co.jp accessibility score

56

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.

Internationalization and localization

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

Impact

Issue

High

<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

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

Best Practices

thirdear.co.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

SEO Factors

thirdear.co.jp SEO score

58

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

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

High

Image elements do not have [alt] attributes

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 Thirdear.co.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 Thirdear.co.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

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