Tools & Wizards About Us
parco.jp screenshot

Report Summary

  • 13

    Performance

    Renders faster than
    25% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 72% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

parco.jp

パルコ - PARCO

Page Load Speed

3.2 sec in total

First Response

9 ms

Resources Loaded

3.1 sec

Page Rendered

66 ms

parco.jp screenshot

About Website

Click here to check amazing PARCO content for Japan. Otherwise, check out these important facts you probably never knew about parco.jp

PARCOの公式サイト。全国のパルコの店舗情報、キャンペーン、オンラインショップ、メルマガ、〈PARCOカード〉のご案内、エンタテインメント情報などをご紹介します。

Visit parco.jp

Key Findings

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

Performance Metrics

parco.jp performance score

13

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

47/100

10%

LCP (Largest Contentful Paint)

Value18.8 s

0/100

25%

SI (Speed Index)

Value19.1 s

0/100

10%

TBT (Total Blocking Time)

Value1,980 ms

8/100

30%

CLS (Cumulative Layout Shift)

Value0.294

40/100

15%

TTI (Time to Interactive)

Value26.5 s

0/100

10%

Network Requests Diagram

parco.jp

9 ms

parco.jp

612 ms

common.min.css

740 ms

cl.first_lang.js

1236 ms

polyfill.min.js

29 ms

Our browser made a total of 23 requests to load all elements on the main page. We found that 74% of them (17 requests) were addressed to the original Parco.jp, 9% (2 requests) were made to Hpadmin.transer.com and 4% (1 request) were made to Sitectl.athp.transer.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Sitectl.athp.transer.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 26.9 kB (12%)

Content Size

229.6 kB

After Optimization

202.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Parco.jp main page is 229.6 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. 15% of websites need less resources to load. Javascripts take 160.9 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 25.1 kB

  • Original 30.3 kB
  • After minification 26.0 kB
  • After compression 5.1 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 4.2 kB, which is 14% 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 25.1 kB or 83% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 18.8 kB
  • After minification 18.8 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. PARCO images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 1.7 kB

  • Original 160.9 kB
  • After minification 160.9 kB
  • After compression 159.1 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

-0%

Potential reduce by 82 B

  • Original 19.7 kB
  • After minification 19.7 kB
  • After compression 19.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. Parco.jp has all CSS files already compressed.

Requests Breakdown

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

Requests Now

21

After Optimization

11

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

parco.jp

parco.jp

9 ms

parco.jp

parco.jp

612 ms

common.min.css

common.min.css

740 ms

cl.first_lang.js

cl.first_lang.js

1236 ms

polyfill.min.js

polyfill.min.js

29 ms

react.js

react.js

602 ms

react-dom.js

react-dom.js

594 ms

jquery-3.4.1.min.js

jquery-3.4.1.min.js

18 ms

common.js

common.js

610 ms

header_language.js

header_language.js

609 ms

cl_langselecter.js

cl_langselecter.js

860 ms

home.js

home.js

781 ms

gtm.js

gtm.js

59 ms

img_language_pc.svg

img_language_pc.svg

610 ms

members_title.svg

members_title.svg

463 ms

logo_header.png

logo_header.png

464 ms

sprite.png

sprite.png

760 ms

icon_facebook.svg

icon_facebook.svg

602 ms

icon_twitter.svg

icon_twitter.svg

595 ms

icon_insta.svg

icon_insta.svg

604 ms

members_icon_l.svg

members_icon_l.svg

545 ms

bg_navi.png

bg_navi.png

1053 ms

first_lang

first_lang

185 ms

Accessibility Review

parco.jp accessibility score

89

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

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

parco.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

parco.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 doesn't use legible font sizes

High

Tap targets are not sized appropriately

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 Parco.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 Parco.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

parco.jp

Open Graph data is detected on the main page of PARCO. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: