Report Summary

  • 52

    Performance

    Renders faster than
    70% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 89% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

pi-pi.com

盗聴器の販売とレンタルGQU|全国通販|即日発送

Page Load Speed

5.9 sec in total

First Response

894 ms

Resources Loaded

4.7 sec

Page Rendered

260 ms

About Website

Welcome to pi-pi.com homepage info - get ready to check Pi best content for Japan right away, or after learning these important things about pi-pi.com

GQUは盗聴器専門店です。販売とレンタルに対応。全商品在庫で素早く全国配送。専門家による充実サポートで安心のお店です。

Visit pi-pi.com

Key Findings

We analyzed Pi-pi.com page load time and found that the first response time was 894 ms and then it took 5 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

pi-pi.com performance score

52

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.8 s

4/100

10%

LCP (Largest Contentful Paint)

Value7.6 s

4/100

25%

SI (Speed Index)

Value8.5 s

18/100

10%

TBT (Total Blocking Time)

Value20 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.108

88/100

15%

TTI (Time to Interactive)

Value7.2 s

51/100

10%

Network Requests Diagram

pi-pi.com

894 ms

style.css

871 ms

top-01b.gif

2887 ms

souryou-muryou.gif

360 ms

rojyou-huka.gif

653 ms

Our browser made a total of 37 requests to load all elements on the main page. We found that 92% of them (34 requests) were addressed to the original Pi-pi.com, 5% (2 requests) were made to Google-analytics.com and 3% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (3.1 sec) belongs to the original domain Pi-pi.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 135.0 kB (69%)

Content Size

195.2 kB

After Optimization

60.2 kB

In fact, the total size of Pi-pi.com main page is 195.2 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. CSS take 85.1 kB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 24.3 kB

  • Original 34.1 kB
  • After minification 34.1 kB
  • After compression 9.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 24.3 kB or 71% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 23.1 kB
  • After minification 23.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. Pi images are well optimized though.

JavaScript Optimization

-60%

Potential reduce by 32.0 kB

  • Original 52.9 kB
  • After minification 52.9 kB
  • After compression 20.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 32.0 kB or 60% of the original size.

CSS Optimization

-93%

Potential reduce by 78.7 kB

  • Original 85.1 kB
  • After minification 62.8 kB
  • After compression 6.4 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. Pi-pi.com needs all CSS files to be minified and compressed as it can save up to 78.7 kB or 93% of the original size.

Requests Breakdown

Number of requests can be reduced by 14 (40%)

Requests Now

35

After Optimization

21

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

Accessibility Review

pi-pi.com accessibility score

96

Accessibility Issues

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

pi-pi.com best practices score

92

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

SEO Factors

pi-pi.com SEO score

82

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

Links do not have descriptive text

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

    SHIFT_JIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pi-pi.com 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 Pi-pi.com main page’s claimed encoding is shift_jis. 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

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