Access piggynote.com. 雑貨ショップ検索サイト::::: piggynote :::::

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

50/100

10%

LCP (Largest Contentful Paint)

Value4.4 s

40/100

25%

SI (Speed Index)

Value18.0 s

0/100

10%

TBT (Total Blocking Time)

Value180 ms

91/100

30%

CLS (Cumulative Layout Shift)

Value0.426

22/100

15%

TTI (Time to Interactive)

Value4.5 s

83/100

10%

piggynote.com

114 ms

piggynote.com

252 ms

style_piggynote.css

172 ms

jquery-2.1.1.min.js

248 ms

bootstrap.js

285 ms

Our browser made a total of 143 requests to load all elements on the main page. We found that 78% of them (111 requests) were addressed to the original Piggynote.com, 6% (8 requests) were made to Static.affiliate.rakuten.co.jp and 6% (8 requests) were made to Thumbnail.image.rakuten.co.jp. The less responsive or slowest element that took the longest time to load (20.4 sec) relates to the external source Ir-jp.amazon-adsystem.com.

Content Size

2.2 MB

After Optimization

1.8 MB

In fact, the total size of Piggynote.com main page is 2.2 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 1.7 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 37.7 kB

Original 47.6 kB
After minification 46.8 kB
After compression 9.9 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 37.7 kB or 79% of the original size.

Image Optimization

-2%

Potential reduce by 38.9 kB

Original 1.7 MB
After minification 1.6 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. Piggynote images are well optimized though.

JavaScript Optimization

-57%

Potential reduce by 135.1 kB

Original 236.3 kB
After minification 236.3 kB
After compression 101.3 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 135.1 kB or 57% of the original size.

CSS Optimization

-62%

Potential reduce by 144.7 kB

Original 232.4 kB
After minification 230.2 kB
After compression 87.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. Piggynote.com needs all CSS files to be minified and compressed as it can save up to 144.7 kB or 62% of the original size.

Requests Now

127

After Optimization

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

Accessibility Issues

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.

High

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

These are opportunities to improve keyboard navigation in your application.

High

[id] attributes on active, focusable elements are not unique

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

These items highlight common accessibility best practices.

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

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

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

High

Links are not crawlable

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

High

Image elements do not have [alt] attributes

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

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

piggynote.com

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

雑貨ショップ検索サイト::::: piggynote :::::

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

piggynote.com

piggynote.com

style_piggynote.css

jquery-2.1.1.min.js

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

piggynote.com

piggynote.com

style_piggynote.css

jquery-2.1.1.min.js

bootstrap.js

tooltip.js

java.js

jquery.flexslider.js

javamenu.js

javaaff.js

rakuten_widget.js

ads.js

css

css

css

normalize.css

bootstrap.css

bootstrap_custombtn.css

font-awesome.min.css

flaticon.css

style_flowarea.css

dropdownmenu.css

gifbanner

ybm16.gif

gifbanner

bg.png

logo_piggynote2.png

icon.gif

left.gif

bar.gif

shopbbs.gif

itembbs.gif

mynote.gif

right.gif

20141201_1.jpg

20141201_3.jpg

20141201_2.jpg

0209-2.jpg

ukashop-2.jpg

fiji-2.jpg

19671006-2.jpg

kamencyu-2.jpg

charin-2.jpg