Report Summary

  • 10

    Performance

    Renders faster than
    23% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 0

    Best Practices

  • 78

    SEO

    Google-friendlier than
    39% of websites

rasin.co.jp

東京・大阪の高級ブランド腕時計の販売・通販サイト GINZA RASIN(銀座ラシン)

Page Load Speed

7.7 sec in total

First Response

543 ms

Resources Loaded

6.6 sec

Page Rendered

564 ms

rasin.co.jp screenshot

About Website

Visit rasin.co.jp now to see the best up-to-date RASIN content for Japan and also check out these interesting facts you probably never knew about rasin.co.jp

GINZA RASINでは、パテックフィリップ、ロレックス、ウブロ、フランクミュラー、オーデマピゲ、パネライ等の中古・新品の時計の販売、買取をしております。東京 銀座へお越しの際にはぜひお立ち寄りください。ブランド時計のクオリティにこだわりご好評を頂いております。

Visit rasin.co.jp

Key Findings

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

Performance Metrics

rasin.co.jp performance score

10

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.3 s

1/100

10%

LCP (Largest Contentful Paint)

Value21.0 s

0/100

25%

SI (Speed Index)

Value30.8 s

0/100

10%

TBT (Total Blocking Time)

Value8,160 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.196

63/100

15%

TTI (Time to Interactive)

Value48.6 s

0/100

10%

Network Requests Diagram

rasin.co.jp

543 ms

www.rasin.co.jp

834 ms

sps_common.css

330 ms

default.css

640 ms

jquery.min.js

27 ms

Our browser made a total of 191 requests to load all elements on the main page. We found that 66% of them (126 requests) were addressed to the original Rasin.co.jp, 6% (12 requests) were made to Kaitori-ginza.com and 3% (5 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (3.4 sec) relates to the external source Kaitori-ginza.com.

Page Optimization Overview & Recommendations

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

Content Size

5.4 MB

After Optimization

5.0 MB

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

HTML Optimization

-88%

Potential reduce by 275.0 kB

  • Original 312.7 kB
  • After minification 262.8 kB
  • After compression 37.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. This page needs HTML code to be minified as it can gain 49.9 kB, which is 16% 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 275.0 kB or 88% of the original size.

Image Optimization

-0%

Potential reduce by 18.7 kB

  • Original 4.6 MB
  • After minification 4.6 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. RASIN images are well optimized though.

JavaScript Optimization

-30%

Potential reduce by 119.6 kB

  • Original 393.0 kB
  • After minification 392.6 kB
  • After compression 273.3 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 119.6 kB or 30% of the original size.

CSS Optimization

-34%

Potential reduce by 33.5 kB

  • Original 97.4 kB
  • After minification 97.4 kB
  • After compression 63.9 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. Rasin.co.jp needs all CSS files to be minified and compressed as it can save up to 33.5 kB or 34% of the original size.

Requests Breakdown

Number of requests can be reduced by 89 (47%)

Requests Now

188

After Optimization

99

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

Accessibility Review

rasin.co.jp accessibility score

88

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

Image elements do not have [alt] attributes

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

High

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

SEO Factors

rasin.co.jp SEO score

78

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

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

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 Rasin.co.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 Rasin.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 RASIN. 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: