Tools & Wizards About Us
o-pal.co.jp screenshot

Report Summary

  • 47

    Performance

    Renders faster than
    66% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 50% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

o-pal.co.jp

株式会社オーパル

Page Load Speed

3.3 sec in total

First Response

751 ms

Resources Loaded

2.4 sec

Page Rendered

142 ms

o-pal.co.jp screenshot

About Website

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

ガラスのオーパル（株式会社オーパル）

Visit o-pal.co.jp

Key Findings

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

Performance Metrics

o-pal.co.jp performance score

47

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

32/100

10%

LCP (Largest Contentful Paint)

Value14.1 s

0/100

25%

SI (Speed Index)

Value9.6 s

11/100

10%

TBT (Total Blocking Time)

Value280 ms

81/100

30%

CLS (Cumulative Layout Shift)

Value0.106

88/100

15%

TTI (Time to Interactive)

Value6.8 s

55/100

10%

Network Requests Diagram

o-pal.co.jp

751 ms

hpbparts.css

389 ms

container_1A_3c_left.css

373 ms

main_1A_3c1.css

397 ms

user.css

420 ms

Our browser made a total of 43 requests to load all elements on the main page. We found that 40% of them (17 requests) were addressed to the original O-pal.co.jp, 23% (10 requests) were made to Static.xx.fbcdn.net and 7% (3 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain O-pal.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 95.9 kB (30%)

Content Size

324.9 kB

After Optimization

229.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-71%

Potential reduce by 15.8 kB

  • Original 22.3 kB
  • After minification 21.0 kB
  • After compression 6.6 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 15.8 kB or 71% of the original size.

Image Optimization

-20%

Potential reduce by 48.7 kB

  • Original 248.9 kB
  • After minification 200.2 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. Obviously, O Pal needs image optimization as it can save up to 48.7 kB or 20% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 41 B

  • Original 18.4 kB
  • After minification 18.4 kB
  • After compression 18.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. This website has mostly compressed JavaScripts.

CSS Optimization

-89%

Potential reduce by 31.4 kB

  • Original 35.3 kB
  • After minification 22.1 kB
  • After compression 3.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. O-pal.co.jp needs all CSS files to be minified and compressed as it can save up to 31.4 kB or 89% of the original size.

Requests Breakdown

Number of requests can be reduced by 17 (40%)

Requests Now

42

After Optimization

25

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

o-pal.co.jp

o-pal.co.jp

751 ms

hpbparts.css

hpbparts.css

389 ms

container_1A_3c_left.css

container_1A_3c_left.css

373 ms

main_1A_3c1.css

main_1A_3c1.css

397 ms

user.css

user.css

420 ms

widgets.js

widgets.js

83 ms

share.js

share.js

295 ms

widget.js

widget.js

64 ms

ga.js

ga.js

35 ms

bg_1A_01_01.png

bg_1A_01_01.png

190 ms

all.js

all.js

33 ms

fbg_1A.png

fbg_1A.png

215 ms

share_button.html

share_button.html

318 ms

__utm.gif

__utm.gif

22 ms

logo_1A2.png

logo_1A2.png

243 ms

top_mainimg_1A_01.png

top_mainimg_1A_01.png

1116 ms

top_indexBg_1A.png

top_indexBg_1A.png

296 ms

point_1A.png

point_1A.png

339 ms

returnTop_1A.png

returnTop_1A.png

362 ms

navtitle_1A_02.png

navtitle_1A_02.png

1011 ms

mainmenu_1A_01.png

mainmenu_1A_01.png

397 ms

top_banner_1A_01.png

top_banner_1A_01.png

484 ms

top_banner_1A_03.png

top_banner_1A_03.png

550 ms

button.0308b81ff1714e446f674b5b9793f2cd.js

button.0308b81ff1714e446f674b5b9793f2cd.js

145 ms

76 ms

fpoint_1A.png

fpoint_1A.png

529 ms

xd_arbiter.php

xd_arbiter.php

47 ms

xd_arbiter.php

xd_arbiter.php

66 ms

like.php

like.php

177 ms

like_box.php

like_box.php

44 ms

hQThvcX2PmE.css

hQThvcX2PmE.css

28 ms

t3u7Vo4PVNb.css

t3u7Vo4PVNb.css

31 ms

TKuNj0xVh4A.js

TKuNj0xVh4A.js

45 ms

ehA1CqzHyzE.js

ehA1CqzHyzE.js

64 ms

0wM5s1Khldu.js

0wM5s1Khldu.js

62 ms

1bNoFZUdlYZ.js

1bNoFZUdlYZ.js

61 ms

tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html

tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html

84 ms

I6-MnjEovm5.js

I6-MnjEovm5.js

34 ms

pQrUxxo5oQp.js

pQrUxxo5oQp.js

37 ms

pp1est-vS-1.js

pp1est-vS-1.js

33 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

25 ms

bt_check_1.png

bt_check_1.png

12 ms

jot

jot

76 ms

Accessibility Review

o-pal.co.jp accessibility score

80

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

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

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

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

Best Practices

o-pal.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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

o-pal.co.jp SEO score

92

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

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

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    SHIFT_JIS

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

o-pal.co.jp

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