Tools & Wizards About Us
royalpurple.co.jp screenshot

Report Summary

  • 49

    Performance

    Renders faster than
    68% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 60% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 91

    SEO

    Google-friendlier than
    71% of websites

royalpurple.co.jp

トップページ - ロイヤルパープル日本販売元－有限会社ウィズプロジェクト

Page Load Speed

2.2 sec in total

First Response

551 ms

Resources Loaded

1.5 sec

Page Rendered

113 ms

royalpurple.co.jp screenshot

About Website

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

唯一無二の高性能潤滑剤...それがROYAL PURPLE - ロイヤルパープル日本販売元－有限会社ウィズプロジェクト

Visit royalpurple.co.jp

Key Findings

We analyzed Royalpurple.co.jp page load time and found that the first response time was 551 ms and then it took 1.7 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

royalpurple.co.jp performance score

49

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.3 s

3/100

10%

LCP (Largest Contentful Paint)

Value7.9 s

3/100

25%

SI (Speed Index)

Value13.6 s

2/100

10%

TBT (Total Blocking Time)

Value180 ms

91/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value6.6 s

57/100

10%

Network Requests Diagram

royalpurple.co.jp

551 ms

acclog.cgi

632 ms

rogo.gif

249 ms

with-rogo.gif

322 ms

1-.gif

325 ms

Our browser made a total of 32 requests to load all elements on the main page. We found that 75% of them (24 requests) were addressed to the original Royalpurple.co.jp, 9% (3 requests) were made to S.ytimg.com and 6% (2 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (805 ms) belongs to the original domain Royalpurple.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 344.4 kB (75%)

Content Size

461.5 kB

After Optimization

117.1 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Royalpurple.co.jp main page is 461.5 kB. 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. CSS take 244.2 kB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 7.1 kB

  • Original 10.1 kB
  • After minification 9.4 kB
  • After compression 2.9 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 7.1 kB or 71% of the original size.

JavaScript Optimization

-65%

Potential reduce by 134.6 kB

  • Original 207.2 kB
  • After minification 207.1 kB
  • After compression 72.6 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 134.6 kB or 65% of the original size.

CSS Optimization

-83%

Potential reduce by 202.6 kB

  • Original 244.2 kB
  • After minification 244.1 kB
  • After compression 41.5 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. Royalpurple.co.jp needs all CSS files to be minified and compressed as it can save up to 202.6 kB or 83% of the original size.

Requests Breakdown

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

Requests Now

29

After Optimization

26

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

royalpurple.co.jp

royalpurple.co.jp

551 ms

acclog.cgi

acclog.cgi

632 ms

rogo.gif

rogo.gif

249 ms

with-rogo.gif

with-rogo.gif

322 ms

1-.gif

1-.gif

325 ms

4.gif

4.gif

332 ms

2.gif

2.gif

332 ms

3.gif

3.gif

347 ms

5.gif

5.gif

363 ms

6.gif

6.gif

479 ms

com-title.gif

com-title.gif

485 ms

mail-image.gif

mail-image.gif

496 ms

facebook.gif

facebook.gif

498 ms

link-title.gif

link-title.gif

521 ms

b-e.gif

b-e.gif

722 ms

jdda.gif

jdda.gif

638 ms

nhra.gif

nhra.gif

805 ms

new-title.gif

new-title.gif

661 ms

nj-0w3qKpb4

nj-0w3qKpb4

68 ms

www-embed-player-vflfNyN_r.css

www-embed-player-vflfNyN_r.css

23 ms

www-embed-player.js

www-embed-player.js

40 ms

base.js

base.js

56 ms

fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js

fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js

32 ms

ad_status.js

ad_status.js

74 ms

2UX7WLTfW3W8TclTUvlFyQ.woff

2UX7WLTfW3W8TclTUvlFyQ.woff

49 ms

RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff

RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff

51 ms

mail-b-.gif

mail-b-.gif

167 ms

4-.gif

4-.gif

176 ms

2-.gif

2-.gif

167 ms

3-.gif

3-.gif

163 ms

5-.gif

5-.gif

182 ms

6-.gif

6-.gif

160 ms

Accessibility Review

royalpurple.co.jp accessibility score

85

Accessibility Issues

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

Buttons do not have an accessible name

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.

Best Practices

royalpurple.co.jp best practices score

75

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

royalpurple.co.jp SEO score

91

Search Engine Optimization Advices

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

    N/A

  • Encoding

    SHIFT_JIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Royalpurple.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 Royalpurple.co.jp main page’s claimed encoding is shift_jis. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

royalpurple.co.jp

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