Report Summary

  • 35

    Performance

    Renders faster than
    55% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 82% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 97

    SEO

    Google-friendlier than
    91% of websites

pelicansoap.co.jp

ペリカン石鹸|石鹸製造に携わり半世紀。私たちだからできる製品をお届けします。

Page Load Speed

4.7 sec in total

First Response

532 ms

Resources Loaded

4 sec

Page Rendered

201 ms

pelicansoap.co.jp screenshot

About Website

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

東京都港区。石鹸・化粧品の製造・輸出入。会社概要、製品や受託製造などの業務 紹介。

Visit pelicansoap.co.jp

Key Findings

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

Performance Metrics

pelicansoap.co.jp performance score

35

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.1 s

9/100

10%

LCP (Largest Contentful Paint)

Value11.9 s

0/100

25%

SI (Speed Index)

Value9.1 s

14/100

10%

TBT (Total Blocking Time)

Value230 ms

87/100

30%

CLS (Cumulative Layout Shift)

Value0.669

8/100

15%

TTI (Time to Interactive)

Value6.6 s

58/100

10%

Network Requests Diagram

pelicansoap.co.jp

532 ms

import.css

166 ms

slide.css

335 ms

jquery.simpleTicker.css

348 ms

jquery-1.7.1.min.js

1012 ms

Our browser made a total of 71 requests to load all elements on the main page. We found that 62% of them (44 requests) were addressed to the original Pelicansoap.co.jp, 20% (14 requests) were made to Scontent.xx.fbcdn.net and 14% (10 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Pelicansoap.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 177.3 kB (18%)

Content Size

1.0 MB

After Optimization

828.0 kB

In fact, the total size of Pelicansoap.co.jp main page is 1.0 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 803.1 kB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 9.2 kB

  • Original 12.8 kB
  • After minification 10.7 kB
  • After compression 3.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. This page needs HTML code to be minified as it can gain 2.1 kB, which is 17% 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 9.2 kB or 72% of the original size.

Image Optimization

-5%

Potential reduce by 42.8 kB

  • Original 803.1 kB
  • After minification 760.3 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. Pelicansoap images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 103.6 kB

  • Original 162.6 kB
  • After minification 145.8 kB
  • After compression 59.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 103.6 kB or 64% of the original size.

CSS Optimization

-81%

Potential reduce by 21.8 kB

  • Original 26.8 kB
  • After minification 20.6 kB
  • After compression 5.0 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. Pelicansoap.co.jp needs all CSS files to be minified and compressed as it can save up to 21.8 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 21 (30%)

Requests Now

69

After Optimization

48

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

Accessibility Review

pelicansoap.co.jp accessibility score

93

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-hidden="true"] elements contain focusable descendents

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

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

pelicansoap.co.jp best practices score

83

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

SEO Factors

pelicansoap.co.jp SEO score

97

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

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pelicansoap.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 Pelicansoap.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 data is detected on the main page of Pelicansoap. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: