Report Summary

  • 29

    Performance

    Renders faster than
    50% of other websites

  • 63

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    57% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

parco-city.co.jp

株式会社パルコデジタルマーケティング

Page Load Speed

6.6 sec in total

First Response

1.2 sec

Resources Loaded

5.2 sec

Page Rendered

220 ms

parco-city.co.jp screenshot

About Website

Click here to check amazing Parco City content for Japan. Otherwise, check out these important facts you probably never knew about parco-city.co.jp

パルコデジタルマーケティングは、新しい時代のリアル商業をサポートします。ショッピングセンター、百貨店、専門店のパートナーとして、Webから店頭まで、お客様の課題を、デジタルマーケティングで解決します。

Visit parco-city.co.jp

Key Findings

We analyzed Parco-city.co.jp page load time and found that the first response time was 1.2 sec and then it took 5.4 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

parco-city.co.jp performance score

29

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

22/100

10%

LCP (Largest Contentful Paint)

Value23.7 s

0/100

25%

SI (Speed Index)

Value10.8 s

6/100

10%

TBT (Total Blocking Time)

Value280 ms

81/100

30%

CLS (Cumulative Layout Shift)

Value0.58

11/100

15%

TTI (Time to Interactive)

Value16.7 s

5/100

10%

Network Requests Diagram

parco-city.co.jp

1161 ms

css

24 ms

typesquare.js

188 ms

bootstrap.css

1473 ms

bootstrap-responsive.css

679 ms

Our browser made a total of 52 requests to load all elements on the main page. We found that 87% of them (45 requests) were addressed to the original Parco-city.co.jp, 4% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.9 sec) belongs to the original domain Parco-city.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 272.0 kB (35%)

Content Size

780.4 kB

After Optimization

508.5 kB

In fact, the total size of Parco-city.co.jp main page is 780.4 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. 25% of websites need less resources to load. Images take 452.5 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 21.9 kB

  • Original 27.0 kB
  • After minification 20.6 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 6.4 kB, which is 24% 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 21.9 kB or 81% of the original size.

Image Optimization

-6%

Potential reduce by 26.3 kB

  • Original 452.5 kB
  • After minification 426.1 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 City images are well optimized though.

JavaScript Optimization

-57%

Potential reduce by 64.5 kB

  • Original 114.1 kB
  • After minification 111.9 kB
  • After compression 49.6 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 64.5 kB or 57% of the original size.

CSS Optimization

-85%

Potential reduce by 159.2 kB

  • Original 186.8 kB
  • After minification 152.6 kB
  • After compression 27.7 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-city.co.jp needs all CSS files to be minified and compressed as it can save up to 159.2 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 13 (26%)

Requests Now

50

After Optimization

37

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

Accessibility Review

parco-city.co.jp accessibility score

63

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-*] attributes do not match their roles

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

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

Image elements do not have [alt] attributes

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

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

parco-city.co.jp best practices score

83

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

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

parco-city.co.jp SEO score

77

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

High

robots.txt is not valid

Content Best Practices

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

Impact

Issue

High

Image elements do not have [alt] attributes

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

    N/A

  • Encoding

    UTF-8

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