Access pars.co.jp. 自分の肌色に変わるファンデーション・エイジングケア化粧品、健康維持にお役立ちのサプリメントなどを取り揃えた卸メーカー、通信販売(株)パース本店

pars.co.jp screenshot

32

Performance

Renders faster than
52% of other websites
69

Accessibility

Visual factors better than
that of 35% of websites
67

Best Practices

More advanced features
available than in
24% of websites
69

SEO

Google-friendlier than
28% of websites

First Response

756 ms

Resources Loaded

6.4 sec

Page Rendered

634 ms

pars.co.jp screenshot

About Website

Welcome to pars.co.jp homepage info - get ready to check Pars best content right away, or after learning these important things about pars.co.jp

コスメサイトや口コミで話題のあなたの肌色に変化するプレミアムパースマジックファンデーション（PMGCクリーム）、乾燥小じわを目立たなくする抗しわ効能評価試験済みEPIGENEスキンケア、発売からずっと売れ続けるロングセラーサプリメントなど、こだわりのオリジナル商品卸・販売【パース本店】

Visit pars.co.jp

Key Findings

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

name

value

score

weighting

FCP (First Contentful Paint)

Value7.5 s

1/100

10%

LCP (Largest Contentful Paint)

Value17.1 s

0/100

25%

SI (Speed Index)

Value46.9 s

0/100

10%

TBT (Total Blocking Time)

Value370 ms

71/100

30%

CLS (Cumulative Layout Shift)

Value0.175

69/100

15%

TTI (Time to Interactive)

Value17.1 s

4/100

10%

pars.co.jp

756 ms

default.css

522 ms

pcsmpflg.js

351 ms

01.css

383 ms

center.css

254 ms

Our browser made a total of 168 requests to load all elements on the main page. We found that 48% of them (80 requests) were addressed to the original Pars.co.jp, 36% (61 requests) were made to Image1.shopserve.jp and 10% (16 requests) were made to Pbs.twimg.com. The less responsive or slowest element that took the longest time to load (2.7 sec) relates to the external source Image1.shopserve.jp.

Content Size

1.3 MB

After Optimization

1.2 MB

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

HTML Optimization

-80%

Potential reduce by 51.4 kB

Original 64.2 kB
After minification 58.7 kB
After compression 12.8 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 51.4 kB or 80% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

Original 1.2 MB
After minification 1.2 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. Pars images are well optimized though.

JavaScript Optimization

-17%

Potential reduce by 3.9 kB

Original 22.8 kB
After minification 20.9 kB
After compression 18.9 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 3.9 kB or 17% of the original size.

CSS Optimization

-87%

Potential reduce by 42.8 kB

Original 49.4 kB
After minification 33.7 kB
After compression 6.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. Pars.co.jp needs all CSS files to be minified and compressed as it can save up to 42.8 kB or 87% of the original size.

Requests Now

118

After Optimization

91

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

Accessibility Issues

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

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.

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

High

Serves images with low resolution

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

Search Engine Optimization Advices

To appear in search results, crawlers need access to your app.

High

Links are not crawlable

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

High

Image elements do not have [alt] attributes

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

High

Document doesn't use legible font sizes

Language and Encoding

Language Detected

JA
Language Claimed

N/A
Encoding

EUC-JP

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pars.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 Pars.co.jp main page’s claimed encoding is euc-jp. 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

pars.co.jp

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