Access pirika.org. Pirika

Report Summary

About Website

Click here to check amazing Pirika content for Japan. Otherwise, check out these important facts you probably never knew about pirika.org

ごみを拾って投稿するだけ！あなたの小さな行動から世界が変わっていく、世界中へと繋がっていく新感覚ソーシャルアプリ「ピリカ」

Visit pirika.org

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

45/100

10%

LCP (Largest Contentful Paint)

Value5.4 s

20/100

25%

SI (Speed Index)

Value4.0 s

80/100

10%

TBT (Total Blocking Time)

Value890 ms

32/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value7.9 s

43/100

10%

pirika.org

48 ms

corp.pirika.org

68 ms

gtm.js

141 ms

index.css

91 ms

index.js

26 ms

Our browser made a total of 36 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Pirika.org, 86% (31 requests) were made to Corp.pirika.org and 6% (2 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (179 ms) relates to the external source Corp.pirika.org.

Content Size

8.5 MB

After Optimization

8.5 MB

In fact, the total size of Pirika.org main page is 8.5 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 8.5 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 23.6 kB

Original 29.6 kB
After minification 26.1 kB
After compression 6.0 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 3.5 kB, which is 12% 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 23.6 kB or 80% of the original size.

Image Optimization

-0%

Potential reduce by 30.3 kB

Original 8.5 MB
After minification 8.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. Pirika images are well optimized though.

JavaScript Optimization

-3%

Potential reduce by 37 B

Original 1.1 kB
After minification 1.1 kB
After compression 1.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

-2%

Potential reduce by 142 B

Original 7.3 kB
After minification 7.3 kB
After compression 7.2 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. Pirika.org has all CSS files already compressed.

Requests Now

After Optimization

The browser has sent 32 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pirika. According to our analytics all requests are already optimized.

Accessibility Issues

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

Buttons do not have an accessible name

High

Links do not have a discernible name

Areas of Improvement

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

High

Browser errors were logged to the console

Search Engine Optimization Advices

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

High

Links do not have descriptive text

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 uses legible font sizes

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 Pirika.org 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 Pirika.org 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

pirika.org

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

Report Summary

Performance

Accessibility

Best Practices

SEO

Pirika

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)