Tools & Wizards About Us

Report Summary

  • 13

    Performance

    Renders faster than
    25% of other websites

  • 61

    Accessibility

    Visual factors better than
    that of 27% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

pieri.sc

[レイク&ハッピーサイドモール] PIERI（ピエリ）守山｜滋賀県守山琵琶湖沿いショッピングモール

Page Load Speed

27.2 sec in total

First Response

541 ms

Resources Loaded

25.8 sec

Page Rendered

862 ms

About Website

Welcome to pieri.sc homepage info - get ready to check PIERI best content for Japan right away, or after learning these important things about pieri.sc

滋賀県びわこ大橋東詰、ショッピングモール【ピエリ守山】のホームページです

Visit pieri.sc

Key Findings

We analyzed Pieri.sc page load time and found that the first response time was 541 ms and then it took 26.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.

Performance Metrics

pieri.sc performance score

13

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.5 s

1/100

10%

LCP (Largest Contentful Paint)

Value10.6 s

0/100

25%

SI (Speed Index)

Value19.9 s

0/100

10%

TBT (Total Blocking Time)

Value980 ms

28/100

30%

CLS (Cumulative Layout Shift)

Value0.379

28/100

15%

TTI (Time to Interactive)

Value27.0 s

0/100

10%

Network Requests Diagram

pieri.sc

541 ms

pieri.sc

761 ms

www.pieri.sc

547 ms

www.pieri.sc

1538 ms

gtm.js

61 ms

Our browser made a total of 154 requests to load all elements on the main page. We found that 94% of them (144 requests) were addressed to the original Pieri.sc, 2% (3 requests) were made to Google.com and 1% (2 requests) were made to Connect.facebook.net. The less responsive or slowest element that took the longest time to load (10.9 sec) belongs to the original domain Pieri.sc.

Page Optimization Overview & Recommendations

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

Content Size

7.6 MB

After Optimization

6.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Pieri.sc main page is 7.6 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. 55% of websites need less resources to load. Images take 7.1 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 80.7 kB

  • Original 95.9 kB
  • After minification 79.8 kB
  • After compression 15.3 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 16.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 80.7 kB or 84% of the original size.

Image Optimization

-9%

Potential reduce by 611.4 kB

  • Original 7.1 MB
  • After minification 6.5 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. PIERI images are well optimized though.

JavaScript Optimization

-52%

Potential reduce by 181.0 kB

  • Original 347.5 kB
  • After minification 295.0 kB
  • After compression 166.5 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 181.0 kB or 52% of the original size.

CSS Optimization

-69%

Potential reduce by 29.7 kB

  • Original 42.8 kB
  • After minification 33.7 kB
  • After compression 13.1 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. Pieri.sc needs all CSS files to be minified and compressed as it can save up to 29.7 kB or 69% of the original size.

Requests Breakdown

Number of requests can be reduced by 22 (15%)

Requests Now

148

After Optimization

126

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

pieri.sc accessibility score

61

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

High

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

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

ARIA toggle fields do not have accessible names

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.

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

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

pieri.sc 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

pieri.sc SEO score

90

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

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

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 Pieri.sc 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 Pieri.sc 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 PIERI. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: