Tools & Wizards About Us
pointpyuru.co.jp screenshot

Report Summary

  • 44

    Performance

    Renders faster than
    63% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 82% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

pointpyuru.co.jp

ポイントピュール 化粧品OEMのポイントピュール

Page Load Speed

6.4 sec in total

First Response

1.4 sec

Resources Loaded

4.8 sec

Page Rendered

160 ms

pointpyuru.co.jp screenshot

About Website

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

ポイントピュールでは沖縄の豊かな自然環境をを生かした化粧品創りを行っています。沖縄海洋深層水を配合した、小ロット・低コスト・多品種のオリジナル化粧品創りを企画から製造までサポートします。OEM化粧品、ホテルアメニティの御相談ならポイントピュールへ！

Visit pointpyuru.co.jp

Key Findings

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

Performance Metrics

pointpyuru.co.jp performance score

44

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

18/100

10%

LCP (Largest Contentful Paint)

Value15.0 s

0/100

25%

SI (Speed Index)

Value10.1 s

9/100

10%

TBT (Total Blocking Time)

Value330 ms

75/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value9.0 s

33/100

10%

Network Requests Diagram

pointpyuru.co.jp

1449 ms

style.css

907 ms

rollover.js

376 ms

jquery.min.js

30 ms

jquery.cross-slide.js

188 ms

Our browser made a total of 53 requests to load all elements on the main page. We found that 92% of them (49 requests) were addressed to the original Pointpyuru.co.jp, 4% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Pointpyuru.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 279.7 kB (19%)

Content Size

1.4 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-78%

Potential reduce by 12.3 kB

  • Original 15.8 kB
  • After minification 14.5 kB
  • After compression 3.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. 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 12.3 kB or 78% of the original size.

Image Optimization

-15%

Potential reduce by 193.9 kB

  • Original 1.3 MB
  • After minification 1.1 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. Obviously, Pointpyuru needs image optimization as it can save up to 193.9 kB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-64%

Potential reduce by 43.6 kB

  • Original 67.9 kB
  • After minification 62.5 kB
  • After compression 24.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 43.6 kB or 64% of the original size.

CSS Optimization

-84%

Potential reduce by 29.9 kB

  • Original 35.6 kB
  • After minification 26.7 kB
  • After compression 5.6 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. Pointpyuru.co.jp needs all CSS files to be minified and compressed as it can save up to 29.9 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 8 (16%)

Requests Now

51

After Optimization

43

  • Images
  • JavaScript
  • CSS

The browser has sent 51 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pointpyuru. 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

pointpyuru.co.jp

pointpyuru.co.jp

1449 ms

style.css

style.css

907 ms

rollover.js

rollover.js

376 ms

jquery.min.js

jquery.min.js

30 ms

jquery.cross-slide.js

jquery.cross-slide.js

188 ms

analytics.js

analytics.js

67 ms

img_logo.png

img_logo.png

189 ms

img_bullet_arrow.png

img_bullet_arrow.png

190 ms

img_tel_num.png

img_tel_num.png

183 ms

languageBtn01.png

languageBtn01.png

355 ms

languageBtn02.png

languageBtn02.png

366 ms

languageBtn03.png

languageBtn03.png

364 ms

languageBtn04.png

languageBtn04.png

373 ms

languageBtn05.png

languageBtn05.png

374 ms

navi_01.png

navi_01.png

375 ms

navi_02.png

navi_02.png

533 ms

navi_03.png

navi_03.png

544 ms

navi_04.png

navi_04.png

546 ms

navi_05.png

navi_05.png

558 ms

navi_06.png

navi_06.png

560 ms

navi_07.png

navi_07.png

561 ms

1.png

1.png

1766 ms

bnr_oem_01.png

bnr_oem_01.png

736 ms

bnr_oem_02.png

bnr_oem_02.png

916 ms

bnr_oem_03.png

bnr_oem_03.png

937 ms

ttl_news.png

ttl_news.png

746 ms

img_news_bg.png

img_news_bg.png

754 ms

dot_line.gif

dot_line.gif

922 ms

img_bullet_arrow_02.png

img_bullet_arrow_02.png

940 ms

brand_lineup.png

brand_lineup.png

946 ms

ryuspa-bana.png

ryuspa-bana.png

1099 ms

ryusparefining-bana.png

ryusparefining-bana.png

1105 ms

bnr_qa.png

bnr_qa.png

1307 ms

bnr_material.png

bnr_material.png

1126 ms

bnr_catalog.png

bnr_catalog.png

1326 ms

bnr_pure_cosme.png

bnr_pure_cosme.png

1279 ms

footer_bg.png

footer_bg.png

1286 ms

2.png

2.png

2385 ms

3.png

3.png

2139 ms

collect

collect

19 ms

collect

collect

80 ms

navi_01_o.png

navi_01_o.png

190 ms

navi_02_o.png

navi_02_o.png

191 ms

navi_03_o.png

navi_03_o.png

183 ms

navi_04_o.png

navi_04_o.png

179 ms

navi_05_o.png

navi_05_o.png

184 ms

navi_06_o.png

navi_06_o.png

190 ms

navi_07_o.png

navi_07_o.png

355 ms

bnr_oem_01_o.png

bnr_oem_01_o.png

368 ms

bnr_oem_02_o.png

bnr_oem_02_o.png

370 ms

bnr_oem_03_o.png

bnr_oem_03_o.png

377 ms

bnr_qa_o.png

bnr_qa_o.png

376 ms

bnr_material_o.png

bnr_material_o.png

372 ms

Accessibility Review

pointpyuru.co.jp accessibility score

93

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

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

pointpyuru.co.jp best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

pointpyuru.co.jp SEO score

79

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

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

    UTF-8

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

pointpyuru.co.jp

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