Access piega.jp. Home

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

26/100

10%

LCP (Largest Contentful Paint)

Value20.8 s

0/100

25%

SI (Speed Index)

Value5.6 s

53/100

10%

TBT (Total Blocking Time)

Value100 ms

98/100

30%

CLS (Cumulative Layout Shift)

Value0.084

93/100

15%

TTI (Time to Interactive)

Value4.4 s

84/100

10%

piega.jp

537 ms

piega.jp

952 ms

jquery-ui.css

12 ms

mplus_webfonts.css

20286 ms

jquery.min.js

29 ms

Our browser made a total of 47 requests to load all elements on the main page. We found that 74% of them (35 requests) were addressed to the original Piega.jp, 15% (7 requests) were made to Fonts.gstatic.com and 4% (2 requests) were made to Code.jquery.com. The less responsive or slowest element that took the longest time to load (20.3 sec) relates to the external source Mplus-fonts.sourceforge.jp.

Content Size

801.0 kB

After Optimization

409.5 kB

In fact, the total size of Piega.jp main page is 801.0 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. 75% 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 270.3 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 13.3 kB

Original 17.4 kB
After minification 14.3 kB
After compression 4.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 3.1 kB, which is 18% 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 13.3 kB or 76% of the original size.

Image Optimization

-2%

Potential reduce by 5.8 kB

Original 270.3 kB
After minification 264.5 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. PIEGA images are well optimized though.

JavaScript Optimization

-62%

Potential reduce by 166.8 kB

Original 269.2 kB
After minification 250.8 kB
After compression 102.4 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 166.8 kB or 62% of the original size.

CSS Optimization

-84%

Potential reduce by 205.6 kB

Original 244.1 kB
After minification 199.5 kB
After compression 38.5 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. Piega.jp needs all CSS files to be minified and compressed as it can save up to 205.6 kB or 84% of the original size.

Requests Now

After Optimization

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

Accessibility Issues

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

These are opportunities to improve keyboard navigation in your application.

High

Heading elements are not in a sequentially-descending order

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

High

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

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

Links do not have a discernible name

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

High

Serves images with low resolution

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

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

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

High

Links are not crawlable

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

piega.jp

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

Report Summary

Performance

Accessibility

Best Practices

SEO

Home - PIEGA

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)

Network Requests Diagram

piega.jp

piega.jp

jquery-ui.css

mplus_webfonts.css

jquery.min.js

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

piega.jp

piega.jp

jquery-ui.css

mplus_webfonts.css

jquery.min.js

k2.css

bootstrap.min.css

bootstrap-responsive.min.css

bootstrap-lightbox.min.css

main.css

template.css

slideshow.css

mootools-core.js

core.js

k2.js

modernizr-2.6.2-respond-1.1.0.min.js

mootools-mobile.js

rokmediaqueries.js

roksprocket.js

moofx.js

features.js

slideshow.js

jquery-ui.js

bootstrap.min.js

bootstrap-lightbox.min.js

spritespin.js

plugins.js

main.js

notosansjapanese.css

facebook.png

SwissDesign-logo.png

Piega-Logo.png

bildschatten-1240.png

Premium_header701.jpg

GitarreBIG.jpg

MasterLineSource2-header-mainslide.jpg

sprite-btn-right.png

sprite-btn-left.png

Piega-Logo-Klein.png

sprite-btn-up.png

NotoSansJP-Regular.woff

NotoSansJP-Medium.woff

NotoSansJP-DemiLight.woff